Glossary
Secure development lifecycle
Definition
A secure development lifecycle builds security work into the design, creation, release and maintenance of software.
It integrates security into software design, implementation, release and maintenance, rather than leaving all checking until the end. A late test cannot replace secure design or ongoing maintenance.
A customer may include “Secure development lifecycle” in a supplier security questionnaire or spreadsheet. They want to understand whether this topic affects the service you provide and what safeguards or evidence support your answer.
A secure development lifecycle includes security activities throughout software development. Teams consider security requirements before building, review design decisions, check code and dependencies, and address vulnerabilities after release. The aim is to prevent avoidable faults and handle the ones that still appear.
It is broader than a penetration test at the end of a project. A late test may find a weakness, but it cannot replace decisions about how information is separated or which actions require permission. The development process needs clear ownership for those decisions.
Consider a small software supplier adding document uploads. Security work could include deciding who may download each file, limiting accepted content, reviewing the implementation and checking how reported flaws reach the team after launch.
The process should match the product's risk and the team's resources. A long checklist nobody follows is not useful evidence of secure development. Match the process to product risk and team capacity. Define security needs before implementation, check code and dependencies before release, and track defects through verified fixes. NIST's Secure Software Development Framework offers a reference for structuring this work. NIST's Secure Software Development Framework provides a reference for integrating these practices.