CISSP Software Development Security Practice Question
A security architect is defining security requirements for a new software development project that will use an Agile methodology. The organization wants to ensure that security is integrated throughout the development lifecycle. Which TWO of the following practices BEST support this goal? (Choose two.)
⚠ Common exam trap
The trap here is assuming that a single end-of-project penetration test or manual code reviews constitute sufficient security integration in Agile.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Integrate automated static analysis security testing (SAST) into the CI/CD pipeline.
Threat modeling at each sprint and automated SAST in the CI/CD pipeline both embed security into Agile's iterative cycles. Threat modeling addresses design flaws early, while SAST provides continuous code-level checks. Together, they enable rapid feedback and remediation, which are essential for integrating security throughout the development lifecycle without impeding Agile delivery.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Document security requirements in a large specification document at the project start.
Why it's wrong here
A large upfront specification is contrary to Agile principles, which embrace changing requirements and iterative development. Security requirements should be captured as user stories or acceptance criteria and refined over time. A static document may become outdated quickly and does not support continuous integration of security.
- ✗
Require the security team to manually review all code changes before deployment.
Why it's wrong here
Manual review of all changes creates a bottleneck and is not scalable in Agile, where code changes frequently. It can delay releases and frustrate developers. While code review is valuable, relying solely on manual security review does not provide the continuous, automated feedback that Agile requires.
- ✓
Integrate automated static analysis security testing (SAST) into the CI/CD pipeline.
Why this is correct
Automated SAST in the CI/CD pipeline provides continuous code analysis, catching vulnerabilities as code is committed. This aligns with Agile's fast iterations and enables developers to fix issues immediately. It scales security across the team without slowing down delivery, making it a best practice for integrating security into the development lifecycle.
- ✓
Conduct threat modeling sessions at the beginning of each sprint for new features.
Why this is correct
Threat modeling during sprint planning helps identify potential security issues early, when they are cheaper to fix. It aligns with Agile by being iterative and focused on upcoming work. This practice integrates security into the design phase, reducing the likelihood of vulnerabilities being introduced and ensuring that security is considered continuously.
- ✗
Perform a full penetration test only at the end of the project before release.
Why it's wrong here
A single penetration test at the end is a waterfall approach and does not integrate security throughout. It may uncover issues too late, leading to costly rework and delays. Agile requires continuous feedback, so security testing should be frequent and incremental, not a one-time event.
Go deeper
Related to this question
Learn chapter
Software Development Security
Key term
Threat
A threat is any potential danger that could harm a computer system, network, or data, whether from a malicious hacker, a natural disaster, or an accidental mistake.
Key term
Security
Security in IT is the practice of protecting systems, networks, and data from unauthorized access, damage, or theft.
About these practice questions
This CISSP question is part of Courseiva's 816-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official ISC2 exam blueprint
This CISSP practice question is part of Courseiva's free ISC2 certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CISSP exam.