# Secure development lifecycle: definition and business examples | Aeptus - Kind: Detail - URL: /glossary/secure-development-lifecycle - Canonical: https://www.aeptus.com/glossary/secure-development-lifecycle/ - HTML lang: en-GB - H1: Secure development lifecycle - Description: A secure development lifecycle builds security work into the design, creation, release and maintenance of software. - Structured data: BreadcrumbList, DefinedTerm, ListItem, WebPage - Internal links: 82 - Image coverage: 5/13 images with alt text - Summary: Secure development lifecycle: definition and business examples | Aeptus. A secure development lifecycle builds security work into the design, creation, release and maintenance of software.. Secure development lifecycle - Related links: product-connect-and-prepare-data, product-collect-and-keep-evidence-current, product-report-with-confidence, work-with-ai-agents, automation - Outline: Section: Latest articles Canadian report maps security work in small businesses A review of public data looks at security staffin | Section: Editors’ picks Unauthorized radio signals stopped trains in Poland in 2023 In August 2023, unauthorized radio transmissi | Section: Explore Make security decisions 1 Prepare, respond and recover 2 Protect everyday business 2 Prove security and earn tru ## Section Latest articles Canadian report maps security work in small businesses A review of public data looks at security staffing, written policies and updates among Canadian businesses with 10 to 49 employees. INTERCEPT hosts free cybersecurity webinar for small teams The 18 November online event will cover phishing, multi-factor authentication and a cybersecurity learning platform. A third-party software vulnerability led to a data breach at Frontline Education Frontline has begun notifying people affected by an August incident involving two school administration products. The impact varies between districts and individuals. ## Section Editors’ picks Unauthorized radio signals stopped trains in Poland in 2023 In August 2023, unauthorized radio transmissions triggered Poland’s railway stop function. Reporting said the receiver did not verify who sent the command; no one was injured. A cyberattack disrupted refrigeration at hundreds of French supermarkets An attack on 12 October 2026 changed refrigeration settings and led stores to discard fresh and frozen food. CERT-FR named several affected controller families, warned that activity might continue and did not identify how access began. A secret is not rotated until the old credential stops working Railway’s preliminary report says some environment variables in at most 1.85% of workspaces may have been compromised, but it could not identify which specific variables were affected. Prove a rotation is complete by checking each consumer and confirming the old credential is revoked. ## Section Explore Make security decisions 1 Prepare, respond and recover 2 Protect everyday business 2 Prove security and earn trust 1 Understand threats and change 9 ## Section Topics ## LearnEditorialMobileSection Latest articles Canadian report maps security work in small businesses A review of public data looks at security staffing, written policies and updates among Canadian businesses with 10 to 49 employees. INTERCEPT hosts free cybersecurity webinar for small teams The 18 November online event will cover phishing, multi-factor authentication and a cybersecurity learning platform. A third-party software vulnerability led to a data breach at Frontline Education Frontline has begun notifying people affected by an August incident involving two school administration products. The impact varies between districts and individuals. View all articles → ## LearnEditorialMobileSection How-to Guides Answer security questionnaires without chaos A step-by-step way to respond faster without improvising every answer from scratch. View all guides → ## LearnEditorialMobileSection Editors’ picks Unauthorized radio signals stopped trains in Poland in 2023 In August 2023, unauthorized radio transmissions triggered Poland’s railway stop function. Reporting said the receiver did not verify who sent the command; no one was injured. A cyberattack disrupted refrigeration at hundreds of French supermarkets An attack on 12 October 2026 changed refrigeration settings and led stores to discard fresh and frozen food. CERT-FR named several affected controller families, warned that activity might continue and did not identify how access began. A secret is not rotated until the old credential stops working Railway’s preliminary report says some environment variables in at most 1.85% of workspaces may have been compromised, but it could not identify which specific variables were affected. Prove a rotation is complete by checking each consumer and confirming the old credential is revoked. ## LearnEditorialMobileSection Explore Article categories Make security decisions 1 Prepare, respond and recover 2 Protect everyday business 2 Prove security and earn trust 1 Understand threats and change 9 Topics ## GlossaryTermProof Glossary Secure development lifecycle secure software development lifecycle SSDLC secure SDLC Jump to Definition Sources References 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. Sources NIST: Secure Software Development Framework References NIST: Secure Software Development Framework Wikipedia: Application security — secure development lifecycle Page progress 0% You’re here On this page Definition Sources References How this term connects Related terms Security by design Security by design considers protection from the start of a product or process, rather than adding it after decisions are fixed. Vulnerability management Vulnerability management is the recurring work of finding, assessing, prioritising and addressing security weaknesses in systems and software. Penetration testing Penetration testing is an authorised, scoped security test in which a tester attempts to exploit weaknesses in a system. SBOM A software bill of materials lists the components and relationships that make up a particular software product or release. ## GlossaryDefinitionSummary 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.