
CSSLP (Certified Secure Software Lifecycle Professional) from ISC2 is the certification for building security into software from requirements to retirement. It covers secure design, threat modelling, secure coding, security testing, secure deployment and operations, and the software supply chain. It suits developers, DevSecOps engineers, application security engineers, QA leads and architects. With software supply chain attacks and AI-assisted coding in the news, these skills appear in many AppSec and product security job posts.
This guide follows ISC2's official CSSLP exam outline (effective 15 September 2023): exam facts, the eight domains with weights and sub-domains, practical secure SDLC ideas, an 8-week plan and 15 original practice questions.
Quick facts (ISC2, November 2026)
| Item | Detail |
|---|---|
| Outline effective | 15 September 2023 |
| Duration | 3 hours |
| Number of items | 125 |
| Format | Multiple choice and advanced item types |
| Passing grade | 700 out of 1000 |
| Language | English |
| Test centre | Pearson VUE |
| Experience | 4 years cumulative, full-time in one or more of the eight domains; a computer science, IT or related degree can cover 1 year; part-time work and internships may count |
| Without experience | Pass the exam to become an Associate of ISC2, then earn the 4 years within 5 years |
Read the official CSSLP exam outline and the CSSLP certification page before you book.
The eight domains and weights
| Domain | Weight | Sub-domains (from the outline) |
|---|---|---|
| 1. Secure Software Concepts | 12% | Core concepts; security design principles |
| 2. Secure Software Lifecycle Management | 11% | Security in the development methodology; standards; strategy and roadmap; documentation; metrics; decommissioning; reporting; integrated risk management; secure operation practices |
| 3. Secure Software Requirements | 13% | Security, compliance, data classification and privacy requirements; data access provisioning; misuse and abuse cases; requirement traceability matrix; third-party vendor requirements |
| 4. Secure Software Architecture and Design | 15% | Security architecture; secure interface design; reusable technologies; threat modelling; architectural risk assessment and design reviews; non-functional security properties; secure operational architecture |
| 5. Secure Software Implementation | 14% | Secure coding practices; code analysis; security controls; fixing identified risks; evaluating components; security in the build process |
| 6. Secure Software Testing | 14% | Test strategy and test cases; verifying documentation; finding undocumented functionality; analysing results; classifying and tracking security errors; securing test data; verification and validation |
| 7. Secure Software Deployment, Operations, Maintenance | 11% | Operational risk; secure configuration and version control; secure release; security data; secure installation; approval to operate; continuous monitoring; incident response; patch and vulnerability management; runtime protection; continuity; SLOs and SLAs |
| 8. Secure Software Supply Chain | 10% | Supply chain risk management; third-party software security; pedigree and provenance; supplier security requirements; contractual requirements |
Secure SDLC ideas in practice
| SDLC phase | Security activity | Example tools or artefacts |
|---|---|---|
| Requirements | Security and privacy requirements, misuse cases, traceability | OWASP ASVS as a requirements checklist |
| Design | Threat modelling and design review | STRIDE, data-flow diagrams |
| Implementation | Secure coding, peer review, static analysis, dependency checks | SAST, software composition analysis (SCA), secret scanning |
| Testing | Dynamic testing, fuzzing, security test cases, masked test data | DAST, fuzzers |
| Build and release | Signed artefacts, protected pipelines, provenance | SBOMs (SPDX or CycloneDX), artefact signing, SLSA levels |
| Operations | Monitoring, patching, vulnerability management, runtime protection | WAF, RASP, logging and alerting |
| Retirement | Secure decommissioning and data disposal | Data retention rules, key destruction |
8-week study plan
| Week | Focus | Hands-on |
|---|---|---|
| 1 | Domains 1–2: CIA, design principles (least privilege, defence in depth, fail secure), SDLC models, metrics | Map your team's SDLC and mark where security happens |
| 2 | Domain 3: requirements, privacy, misuse cases, traceability | Write 10 security requirements for a login feature using OWASP ASVS |
| 3 | Domain 4: architecture, interfaces, threat modelling | Draw a data-flow diagram and run STRIDE on it |
| 4 | Domain 5: secure coding, OWASP Top 10, code analysis, build security | Run SAST and SCA on a sample app in a CI pipeline |
| 5 | Domain 6: security testing, DAST, test data | Scan an intentionally vulnerable lab app that you run yourself |
| 6 | Domain 7: deployment, configuration, monitoring, patching | Add secret scanning and signed releases to the pipeline |
| 7 | Domain 8: supply chain, SBOMs, provenance, vendor contracts | Generate an SBOM and review the licences and vulnerabilities |
| 8 | Timed practice and review | Book the exam |
Only test applications you own or have written permission to test.
15 practice questions with answers
These are original questions written for this guide, not exam questions.
1. When is it cheapest to fix a security flaw?
In requirements or design, before code is written.
2. What is a misuse case?
A description of how an attacker could abuse a feature, used to derive security requirements.
3. Which document links each security requirement to design, code and tests?
A requirements traceability matrix.
4. What does STRIDE stand for?
Spoofing, Tampering, Repudiation, Information disclosure, Denial of service, Elevation of privilege.
5. What does "fail secure" mean?
When a component fails, it defaults to a safe state, such as denying access.
6. Which practice best prevents SQL injection?
Parameterised queries (prepared statements), plus input validation.
7. Which testing analyses source code without running it?
Static application security testing (SAST).
8. Which testing attacks the running application from outside?
Dynamic application security testing (DAST).
9. What finds known vulnerabilities in open-source dependencies?
Software composition analysis (SCA).
10. What is an SBOM?
A software bill of materials: a list of the components and versions in a piece of software.
11. What do pedigree and provenance tell you?
Where a component came from and how it was built and handled.
12. Why mask production data used in testing?
To protect personal and sensitive data in less secure test environments.
13. Where should secrets such as API keys be stored?
In a secrets manager or vault, never in source code.
14. What is "approval to operate"?
Formal acceptance of the residual risk by an authorising official before release.
15. What happens if you pass CSSLP without the required experience?
You become an Associate of ISC2 and have 5 years to earn the 4 years of experience.
Before and after CSSLP
- Add hands-on AppSec with GitHub Advanced Security (GH-500) and policy as code with Kyverno KCA.
- Broaden into CISSP or CCSP.
- Learn it hands-on in our DevSecOps course; see live DevSecOps and AppSec jobs.
Cloud Soft Solutions in Ameerpet, Hyderabad teaches DevSecOps, cyber security and cloud security with real-time projects. See the APEX program and all courses.
📞 Call +91 96660 19191 · WhatsApp · Flat No. 513, 5th Floor, Nilagiri Block, Aditya Enclave, Ameerpet, Hyderabad
Frequently Asked Questions
How long is the CSSLP exam?
3 hours, with 125 items.
What is the CSSLP passing score?
700 out of 1000.
How much experience does CSSLP need?
4 years cumulative, full-time in one or more of the eight domains. A relevant degree can cover 1 year.
Can freshers take CSSLP?
Yes. Passing without the experience makes you an Associate of ISC2, with 5 years to earn the 4 years of experience.
Which CSSLP domain has the most weight?
Secure Software Architecture and Design at 15%.
Who should take CSSLP?
Developers, DevSecOps and application security engineers, testers and architects who build security into software.



