You can see it againUnder pressure people bring back shapes and positions long after the wording has gone.
Picture superiority · Shepard 1967, Standing 1973
ISC2Certified Secure Software Lifecycle Professional
The Certified Secure Software Lifecycle Professional (CSSLP) certification validates your ability to integrate security practices—authentication, authorization, and auditing—into every phase of the software development lifecycle (SDLC). It is designed for software and security professionals who build, test, and deploy secure applications. Earning the CSSLP demonstrates advanced application security skills and a commitment to best practices established by ISC2, helping you advance your career and gain recognition from employers and peers.
Exam formatMultiple choice and advanced item types
Duration180 minutes
DeliveryPearson VUE
Passing score700 out of 1000
Free questions1710
Content last reviewed 30 July 2026 · Up to date
The certification
What Certified Secure Software Lifecycle Professional proves, and what it asks of you
What this certification covers, who it is written for, and what the exam itself looks like on the day.
8domains
58objectives
447concepts
US $599exam fee
What it is
What this certification is
What it validates, who it is written for, and the experience it assumes.
About this certification
The Certified Secure Software Lifecycle Professional (CSSLP) certification from ISC2 validates that software professionals have the expertise to incorporate security practices—authentication, authorization, and auditing—into each phase of the software development lifecycle (SDLC), from design and implementation to testing and deployment. This vendor-neutral credential is built around eight domains that cover the full spectrum of secure software development, ensuring relevancy across all disciplines in the field of information security.
Earning the CSSLP demonstrates that you possess the advanced technical skills and knowledge necessary to apply best practices, policies, and procedures established by ISC2's cybersecurity experts. It shows employers and peers that you are committed to building security into software from the ground up, reducing risk and enhancing the overall security posture of your organization. As a globally recognized certification, the CSSLP opens doors to career advancement and connects you with a community of cybersecurity leaders dedicated to professional growth.
Who it’s for
The CSSLP is ideal for software development and security professionals responsible for applying best practices to each phase of the SDLC—from software design and implementation to testing and deployment. This includes roles such as software architect, software engineer, software developer, application security specialist, software program manager, quality assurance tester, penetration tester, software procurement analyst, project manager, security manager, and IT director/manager. If you are involved in developing, deploying, or managing software and want to demonstrate your ability to integrate security throughout the lifecycle, the CSSLP is designed for you. It is particularly valuable for those seeking to formalize their expertise in secure software development and stand out in a competitive job market.
Recommended experience
A minimum of four years of cumulative, full-time experience in one or more of the eight domains of the CSSLP exam outline is required for certification. A post-secondary degree in computer science, IT, or a related field may satisfy up to one year of this experience requirement. Experience in secure software concepts, lifecycle management, requirements, architecture and design, implementation, testing, deployment, operations, maintenance, or supply chain; Part-time work and internships may count toward the experience requirement; Candidates without the required experience can become an Associate of ISC2 by passing the exam and have five years to earn the required experience
The syllabus
What you’ll learn
Every domain and objective ISC2 measures, with the weight they carry on the exam.
The official ISC2 exam outline · checked 30 July 2026 · See the source
Secure Software Concepts
- Understand core concepts
- Understand security design principles
Secure Software Lifecycle Management
- Manage security within a software development methodology (e.g., Agile, waterfall)
- Identify and adopt security standards (e.g., implementing security frameworks, promoting security awareness)
- Outline strategy and roadmap
- Define and develop security documentation
- Define security metrics (e.g., criticality level, average remediation time, complexity, Key Performance Indicators (KPI), objectives and key results)
- Decommission applications
- Create security reporting mechanisms (e.g., reports, dashboards, feedback loops)
- Incorporate integrated risk management methods
- Implement secure operation practices
Secure Software Requirements
- Define software security requirements
- Identify compliance requirements
- Identify data classification requirements
- Identify privacy requirements
- Define data access provisioning
- Develop misuse and abuse
- Develop security requirement traceability matrix
- Define third-party vendor security requirements
Secure Software Architecture and Design
- Define the security architecture
- Perform secure interface design
- Evaluate and select reusable technologies
- Perform threat modeling
- Perform architectural risk assessment and design reviews
- Model (non-functional) security properties and constraints
- Define secure operational architecture (e.g., deployment topology, operational interfaces, Continuous Integration and Continuous Delivery (CI/CD))
Secure Software Implementation
- Adhere to relevant secure coding practices (e.g., standards, guidelines, regulations)
- Analyze code for security risks
- Implement security controls (e.g., watchdogs, file integrity monitoring, anti-malware)
- Address the identified security risks (e.g., risk strategy)
- Evaluate and integrate components
- Apply security during the build process
Secure Software Testing
- Develop security testing strategy & plan
- Develop security test cases
- Verify and validate documentation (e.g., installation and setup instructions, error messages, user guides, release notes)
- Identify undocumented functionality
- Analyze security implications of test results (e.g., impact on product management, prioritization, break/build criteria)
- Classify and track security errors
- Secure test data
- Perform verification and validation testing (e.g., independent/internal verification and validation, acceptance test)
Secure Software Deployment, Operations, Maintenance
- Perform operational risk analysis
- Secure configuration and version control
- Release software securely
- Store and manage security data
- Ensure secure installation
- Obtain security approval to operate (e.g., risk acceptance, sign-off at appropriate level)
- Perform information security continuous monitoring
- Execute the incident response plan
- Perform patch management (e.g. secure release, testing)
- Perform vulnerability management (e.g., tracking, triaging, Common Vulnerabilities and Exposures (CVE))
- Incorporate runtime protection (e.g., Runtime Application Self Protection (RASP), web application firewall (WAF), Address Space Layout Randomization (ASLR), dynamic execution prevention)
- Support continuity of operations
- Integrate service level objectives and service-level agreements (SLA) (e.g., maintenance, performance, availability, qualified personnel)
Secure Software Supply Chain
- Implement software supply chain risk management (e.g., International Organization for Standardization (ISO), National Institute of Standards and Technology (NIST))
- Analyze security of third-party software
- Verify pedigree and provenance
- Ensure and verify supplier security requirements in the acquisition process
- Support contractual requirements (e.g., intellectual property ownership, code escrow, liability, warranty, End-User License Agreement (EULA), service-level agreements (SLA))
On the day
The exam itself
Everything ISC2 publishes about sitting it, and nothing we inferred.
Prerequisites
Minimum of four years cumulative, full-time experience in one or more of the eight domains of the CSSLP exam outline.
CertificationCertified Secure Software Lifecycle Professional
Exam formatMultiple choice and advanced item types
Duration180 minutes
Questions125 questions
Passing score700 out of 1000
DeliveryPearson VUE
LanguagesEnglish
PricingUS $599
Certification levelProfessional
After you pass
Where this credential goes next
The path ISC2 lays out, how the credential is kept, and where to book.
Step-by-step path to Certified Secure Software Lifecycle Professional
PrerequisiteMinimum of four years cumulative, full-time experience in one or more of the eight domains of the CSSLP exam outline.
Credential earnedCertified Secure Software Lifecycle Professional Professional level certification Renewal and maintenance
ISC2 certifications are time-limited and must be renewed on a regular three-year cycle. Certification holders maintain their credentials by earning continuing professional education (CPE) credits and complying with ISC2 policies and ethical standards. An annual maintenance fee (AMF) is also required. Stay current with the latest technologies and maintain your certification.
Learn more about renewal requirements Lifecycle status
This certification is currently active and available. ISC2 maintains this certification to validate current skills and industry relevance.
Exam status: ActiveMaintained by ISC2
Exam registration
Register for the exam through Pearson VUE, ISC2’s authorized testing partner.
Schedule your examVisit the official ISC2 certification page for exam policies and requirements.
View the official pageYour coach
And when you are serious, your coach Pip takes over
Your coach in the app reads what you have answered with the book closed and tells you one thing to do tonight. It will not count an answer you gave with the page open, and it will tell you when you are not ready.
See how the coach worksBefore you book
Questions people ask
Is the CSSLP exam available in languages other than English?
According to the official exam outline, the CSSLP exam is available in English only.
Can I take the CSSLP exam if I don't have the required work experience?
Yes. If you don't have the required experience, you can become an Associate of ISC2 by passing the CSSLP exam. You will then have five years to earn the four years of required experience.
What is the Peace of Mind Protection option for the CSSLP exam?
Peace of Mind Protection is an exam-only purchase that includes two exam attempts at a lower cost than two single exams. Candidates have 180 days from purchase to sit both attempts, with a 30-day waiting period between attempts.
How long do I have to schedule my CSSLP exam after purchasing it?
Exam codes must be scheduled and administered within 365 days of purchase.
What job roles does the CSSLP certification map to?
The CSSLP is ideal for software architects, software engineers, software developers, application security specialists, software program managers, quality assurance testers, penetration testers, software procurement analysts, project managers, security managers, and IT directors/managers.
Is the CSSLP exam accredited?
Yes, the CSSLP is accredited by the ANSI National Accreditation Board (ANAB) to the ISO/IEC 17024 standard and is approved by the U.S. Department of Defense (DoD) under DoDM 8140.03.
Can I recertify by passing a different ISC2 exam?
ISC2 certifications are renewed through continuing professional education (CPE) credits and compliance with ISC2 policies. Passing a different exam may contribute to CPE credits, but the renewal process is based on earning CPEs, not automatically by passing another exam.
Information freshness · Content last reviewed on 2026-07-30 Up to date
Practice free questions 1710 questions, free, no account needed.
The curriculum
The whole exam, mapped and written
Every domain, every objective, and every concept ISC2 measures — each one written out.
8domains
58objectives
447concepts
366free pages
The domains, and what sits inside them
Every objective below is a page you can open and practise now, without an account.
The official ISC2 exam outline · checked 30 July 2026 · See the source
1Secure Software Concepts54 questions
2Secure Software Lifecycle Management278 questions
Manage security within a software development methodology (e.g., Agile, waterfall)8 concepts · 7 pagesOpen →Identify and adopt security standards (e.g., implementing security frameworks, promoting security awareness)5 concepts · 6 pagesOpen →Outline strategy and roadmap9 concepts · 7 pagesOpen →Define and develop security documentation10 concepts · 8 pagesOpen →Define security metrics (e.g., criticality level, average remediation time, complexity, Key Performance Indicators (KPI), objectives and key results)6 concepts · 5 pagesOpen →Decommission applications10 concepts · 7 pagesOpen →Create security reporting mechanisms (e.g., reports, dashboards, feedback loops)8 concepts · 6 pagesOpen →Incorporate integrated risk management methods6 concepts · 7 pagesOpen →Implement secure operation practices4 concepts · 6 pagesOpen →
3Secure Software Requirements192 questions
Define software security requirements5 concepts · 6 pagesOpen →Identify compliance requirements4 concepts · 5 pagesOpen →Identify data classification requirements5 concepts · 4 pagesOpen →Identify privacy requirements5 concepts · 5 pagesOpen →Define data access provisioning3 concepts · 4 pagesOpen →Develop misuse and abuse1 concepts · 4 pagesOpen →Develop security requirement traceability matrix9 concepts · 7 pagesOpen →Define third-party vendor security requirements5 concepts · 5 pagesOpen →
4Secure Software Architecture and Design296 questions
Define the security architecture43 concepts · 24 pagesOpen →Perform secure interface design9 concepts · 7 pagesOpen →Evaluate and select reusable technologies10 concepts · 8 pagesOpen →Perform threat modeling11 concepts · 8 pagesOpen →Perform architectural risk assessment and design reviews8 concepts · 5 pagesOpen →Model (non-functional) security properties and constraints5 concepts · 6 pagesOpen →Define secure operational architecture (e.g., deployment topology, operational interfaces, Continuous Integration and Continuous Delivery (CI/CD))6 concepts · 5 pagesOpen →
5Secure Software Implementation151 questions
Adhere to relevant secure coding practices (e.g., standards, guidelines, regulations)15 concepts · 7 pagesOpen →Analyze code for security risks5 concepts · 5 pagesOpen →Implement security controls (e.g., watchdogs, file integrity monitoring, anti-malware)4 concepts · 4 pagesOpen →Address the identified security risks (e.g., risk strategy)6 concepts · 6 pagesOpen →Evaluate and integrate components5 concepts · 5 pagesOpen →Apply security during the build process5 concepts · 6 pagesOpen →
6Secure Software Testing230 questions
Develop security testing strategy & plan6 concepts · 5 pagesOpen →Develop security test cases12 concepts · 7 pagesOpen →Verify and validate documentation (e.g., installation and setup instructions, error messages, user guides, release notes)7 concepts · 6 pagesOpen →Identify undocumented functionality5 concepts · 5 pagesOpen →Analyze security implications of test results (e.g., impact on product management, prioritization, break/build criteria)4 concepts · 4 pagesOpen →Classify and track security errors6 concepts · 5 pagesOpen →Secure test data10 concepts · 8 pagesOpen →Perform verification and validation testing (e.g., independent/internal verification and validation, acceptance test)15 concepts · 9 pagesOpen →
7Secure Software Deployment, Operations, Maintenance388 questions
Perform operational risk analysis8 concepts · 7 pagesOpen →Secure configuration and version control10 concepts · 7 pagesOpen →Release software securely7 concepts · 7 pagesOpen →Store and manage security data4 concepts · 6 pagesOpen →Ensure secure installation13 concepts · 8 pagesOpen →Obtain security approval to operate (e.g., risk acceptance, sign-off at appropriate level)6 concepts · 4 pagesOpen →Perform information security continuous monitoring9 concepts · 7 pagesOpen →Execute the incident response plan7 concepts · 7 pagesOpen →Perform patch management (e.g. secure release, testing)5 concepts · 4 pagesOpen →Perform vulnerability management (e.g., tracking, triaging, Common Vulnerabilities and Exposures (CVE))7 concepts · 6 pagesOpen →Incorporate runtime protection (e.g., Runtime Application Self Protection (RASP), web application firewall (WAF), Address Space Layout Randomization (ASLR), dynamic execution prevention)6 concepts · 6 pagesOpen →Support continuity of operations11 concepts · 8 pagesOpen →Integrate service level objectives and service-level agreements (SLA) (e.g., maintenance, performance, availability, qualified personnel)8 concepts · 6 pagesOpen →
8Secure Software Supply Chain121 questions
Implement software supply chain risk management (e.g., International Organization for Standardization (ISO), National Institute of Standards and Technology (NIST))4 concepts · 4 pagesOpen →Analyze security of third-party software3 concepts · 5 pagesOpen →Verify pedigree and provenance9 concepts · 6 pagesOpen →Ensure and verify supplier security requirements in the acquisition process6 concepts · 6 pagesOpen →Support contractual requirements (e.g., intellectual property ownership, code escrow, liability, warranty, End-User License Agreement (EULA), service-level agreements (SLA))6 concepts · 6 pagesOpen →
Not a table of contents
Every line on this map already opens
In front of every objective the practice pages are already there, free and without an account. This is one objective, opened.
Understand core concepts6 pagesOpen →
Free in front of it
27 questions on this objective, five to a page. Every range above is a real page, open now, with no account.
Reading the map is not the same as knowing the ground
The curriculum tells you what is on the exam. Proving you know it is a different job — and it is the one the closed-book run does.
Free questions
1710 questions. No account, no card.
The whole bank is open. 5 questions to a page, every answer explained, and a discussion thread on each one.
1710questions
366pages
58objectives
Freealways
Browse by domain
Every objective, and every page range, is a link — so you can pick up exactly where you left off.
1Secure Software Concepts54 questions
2Secure Software Lifecycle Management278 questions
3Secure Software Requirements192 questions
4Secure Software Architecture and Design296 questions
5Secure Software Implementation151 questions
6Secure Software Testing230 questions
7Secure Software Deployment, Operations, Maintenance388 questions
8Secure Software Supply Chain121 questions
What a practice page gives you
1Five to a page
Short enough to finish, long enough to matter.
2Every answer explained
Not only which one is right — why the others are wrong.
3A discussion on each
Ask, answer, and vote. Every question has its own thread.
A question, and the idea behind it
Every question comes from a concept
These are not trivia. Each one is written against a concept in the book, so when you get one wrong there is somewhere to go and find out why.
The visual book
See it once. Carry it into the exam.
The pages shown here come from our AI-900 book — an example of how each concept is written in plain language and, where the idea needs one, drawn as a full page you can take in at a glance.
447concepts
1710free questions
Why a picture, and not another paragraph
Three reasons, and each one is a real finding rather than a slogan.
You can see it againThe whole idea at onceWhere it starts, what happens in the middle, what comes out, and the mistake to avoid.
Multimedia principle · MayerThe look-alikes sit togetherThe pairs the exam tests are drawn side by side, so the difference is seen, not told.
Dual coding · PaivioWhat one page is made of
You are never asked to read a poster here — only to see how one is built. After that, every other page is legible at a glance.
1A numbered strip on top
The idea as a sequence, followed with a finger before a word is read.
2Panels for the parts
What it is, how the machine learns it, when it is the right tool.
3The trap, framed
The distinction the exam tests, given its own box instead of buried in prose.
4One line at the bottom
The sentence to carry into the exam room.
Open book, on purpose
Answer it with the picture beside you
This is the part that teaches. The illustration and the written explanation stay where they are while you work, so a scenario stops being a memory test and becomes something you can simply look at.
It teaches · it does not count
A smartphone uses AI to unlock when the owner looks at the camera. Which AI capability is being used?
AImage classification
BFacial recognition
COptical character recognition
DObject detection
Look at the five steps. Detect finds a face, align straightens it, encode turns it into numbers, search compares it with a stored face, and decide answers one question: is this the same person? Classification would only say “a face”. Detection would only draw a box. Neither decides whose.
Then the page shuts, and it starts counting
The same questions come back with the book closed — that run is the one that counts. After it, your coach picks one thing for tonight, sized to the time you have, and brings pages back before you lose them.
Testing effect · Roediger & Karpicke 2006 · spacing effect · Cepeda et al. 2006
Official resources
Straight from ISC2
Where the exam is defined, scheduled and scored.
4official links
447concepts mapped
The source
ISC2’s own pages
We link to them rather than repeat them, so nothing here goes stale behind them.
Checked against the source
Every objective on the official ISC2 outline already has questions here
We build from the official skills outline, not from a summary of it — 58 objectives, 447 concepts written under them, and free questions against every one. When ISC2 changes the outline, this page changes with it.
58objectives on the outline→447concepts written→1710free questions
An official page tells you what will be asked. It cannot tell you what you will get right.
That is the only question worth answering the night before, and no link answers it. You answer it by taking the questions with the book closed, and seeing what comes back.