Movaci Movaci CISSP Study
CISSP Domain 8 · 11.2% of the exam

Software Development Security

Domain 8 of the ISC2 CISSP exam outline effective 15 April 2027 carries 11.2% of the exam weight. It covers 5 objectives and 26 study topics, listed below with short explanations written for exam preparation.

Open the Domain 8 mindmap Take the practice test Study the flashcards

8.1 Understand and integrate security in the Software Development Life Cycle (SDLC)

Development methodologies
Waterfall, Agile, Scaled Agile Framework (SAFe), DevOps and DevSecOps (security shifted left and automated in the pipeline).
Maturity models
Capability Maturity Model (CMM/CMMI) levels and OWASP SAMM.
Operation and maintenance
Security continues after release through patching and monitoring.
Change management
Controlled changes to code and configuration.
Integrated product team
Cross-functional team, including security, working together throughout.
SSDF and SBOM requirements
NIST Secure Software Development Framework (SP 800-218) practices, and producing or requiring SBOMs.
Shift left
Move security activities earlier: requirements, design, code and pipeline checks.

8.2 Identify and apply security controls in software development ecosystems

Programming languages
Memory-safe and object-oriented languages; memory safety removes whole classes of bugs.
Libraries
Third-party dependencies must be tracked and patched.
Tool sets
Build and test tools must be trusted and controlled.
Integrated development environment (IDE)
Secure plugins and secret handling on developer machines.
Runtime
Interpreters, virtual machines and containers that execute code.
CI/CD
Pipeline security: signed builds, protected secrets, least privilege runners.
Software configuration management (SCM)
Version control of code and builds.
Code repositories
Access control, branch protection, secret scanning.
Application security testing
SAST (source, no execution) and DAST (running app). IAST instruments the runtime.

8.3 Assess the effectiveness of software security

Auditing and logging of changes
Trace who changed what and when.
Risk analysis and mitigation
Assess and treat software risks throughout the lifecycle.

8.4 Assess security impact of acquired software

Commercial off-the-shelf (COTS)
Limited visibility; rely on vendor assurance and testing.
Open source
Code is visible but maintenance and licensing vary; use Software Composition Analysis (SCA).
Third-party
Contractual security requirements and assessments.
Managed services
Enterprise applications run by a provider.
Cloud services
SaaS, IaaS, PaaS and FaaS under shared responsibility.

8.5 Define and apply secure coding guidelines and standards

Source-code weaknesses and vulnerabilities
Injection, buffer overflow, XSS, CSRF, race conditions (TOCTOU). See OWASP Top 10 and CWE.
Security of APIs
Authentication, authorization per object, rate limiting, input validation. See OWASP API Security Top 10.
Secure coding practices
Input validation, output encoding, parameterized queries, error handling, least privilege.

Key concepts for Domain 8

Shift left
Fixing defects in requirements and design is far cheaper than in production.
SAST versus DAST
SAST reads code without running it (white box). DAST attacks a running application (black box).
Parameterized queries
The primary defense against SQL injection. Input validation is a supporting control.
Acquired software risk
You inherit the vendor's security. Require assurance through contracts, SBOMs and testing.

Key terms and acronyms

SDLC
Software Development Life Cycle.
DevSecOps
Development, Security and Operations integrated.
SAMM
OWASP Software Assurance Maturity Model.
CMMI
Capability Maturity Model Integration.
SAST
Static Application Security Testing.
DAST
Dynamic Application Security Testing.
IAST
Interactive Application Security Testing.
SCA
Software Composition Analysis.
CI/CD
Continuous Integration / Continuous Delivery (or Deployment).
OWASP
Open Worldwide Application Security Project.
CWE
Common Weakness Enumeration.
XSS
Cross-Site Scripting.
CSRF
Cross-Site Request Forgery.
TOCTOU
Time Of Check to Time Of Use race condition.
COTS
Commercial Off-The-Shelf.
SSDF
NIST Secure Software Development Framework, SP 800-218.

Where candidates lose marks

  • SDLC methodologies
  • Application security testing types
  • Common code vulnerabilities
  • Acquired software assurance

Sample practice questions

Q1. Which is the most effective defense against SQL injection?

  1. Input length limits
  2. Parameterized queries
  3. Web application firewall
  4. Error message suppression
Show answer

B. Parameterized queries Parameterized queries separate code from data. The others are supporting controls.

Q2. Which testing type analyzes source code without executing it?

  1. DAST
  2. SAST
  3. Fuzzing
  4. IAST
Show answer

B. SAST Static testing examines code at rest.

Practice all Domain 8 questions