Secure Development Lifecycle (SDLC)
A Secure Development Lifecycle (SDLC) is a software and product development process that integrates security activities - threat modelling, security requirements, code review, security testing - at every stage of development. The CRA does not require a manufacturer to operate an SDLC. An SDLC is a common way to meet the Annex I requirements and to produce the evidence for them.
A Secure Development Lifecycle (SDLC) is a software and product development process that integrates security activities - threat modelling, security requirements, code review, security testing - at every stage of development. The CRA does not require a manufacturer to operate an SDLC. An SDLC is a common way to meet the Annex I requirements and to produce the evidence for them.
Product Security EngineeringLast updated 16 November 2026
What Is a Secure Development Lifecycle?
A Secure Development Lifecycle (SDLC) - sometimes called Secure SDLC or SSDLC - is a product development process that embeds security activities at each phase of development rather than treating security as a final-stage add-on. The concept was popularised by Microsoft's Security Development Lifecycle (SDL), published in the early 2000s, and has since been formalised in standards such as ISO/IEC 27034 (Application Security) and NIST SP 800-64. An SDLC typically includes: security requirements definition, threat modelling, secure design review, secure coding guidelines, static analysis (SAST), dynamic testing (DAST), penetration testing, and security-focused code review. The principle is 'shift left' - finding and fixing security issues early in development when they are cheapest to address.
What the CRA Requires, and Where an SDLC Helps
The CRA does not require a manufacturer to operate an SDLC. Commission guidance C(2026) 5252 (section 7.2) states this for , and ENISA's November 2026 report CRA-Module B and H: CABs accreditation for notification adds that a notified body does not assess whether an SDLC exists. The CRA sets requirements for the product and for vulnerability handling. Several of them map to SDLC activities:
- Risk assessment: Article 13(2) requires a cybersecurity risk assessment, and its outcome is taken into account during planning, design, development, production, delivery and maintenance. Threat modelling is a usual way to do this.
- Secure design: Annex I Part I requires products to be designed, developed and produced to give an appropriate level of cybersecurity based on the risks.
- Testing: requires a product to be made available without known exploitable vulnerabilities, and requires regular tests and reviews of its security.
- Vulnerability handling: Annex I Part II requires the manufacturer to handle vulnerabilities during the support period. A development process that can ship a fix makes this possible.
Annex VII requires a description of the design, development and production of the product, the cybersecurity risk assessment and the test reports. Records from an SDLC can supply this evidence. The SDLC itself is not a conformity criterion.
SDLC Activities by Development Phase
A CRA-aligned SDLC should include the following activities by phase:
Requirements phase: Define security requirements based on the product's threat model; identify applicable CRA essential requirements; document regulatory compliance requirements.
Design phase: Conduct architecture threat modelling (STRIDE or PASTA methodology); design security controls for identified threats; review design against CRA Annex I requirements; document security architecture decisions.
Implementation phase: Apply secure coding standards; use SAST tools in the CI/CD pipeline; conduct peer security code review for security-sensitive components; manage dependency selection and SBOM tracking.
Testing phase: Conduct DAST/fuzzing against network-exposed interfaces; perform penetration testing of the final product build; verify all threat model mitigations are implemented and functional.
Release phase: Final security review; SBOM generation and sign-off; declaration of conformity preparation; CVD policy publication verification.
Maintenance phase: SBOM-based vulnerability monitoring; CVD report intake and triage; security patch development; security advisory publication.
SDLC for Hardware-Software Products
CRA-covered products often combine hardware and software - embedded systems, IoT devices, industrial equipment. SDLC for hardware-software products requires extending traditional software-focused SDLC practices:
- Hardware threat modelling: Physical attack vectors (JTAG access, UART debug, chip-off, side-channel analysis) must be in scope for the threat model.
- Hardware security review: PCB layout review for debug interface exposure; component selection review for security features (HSM availability, TrustZone support).
- Manufacturing security: Security-critical manufacturing steps (key injection, Secure Boot fuse programming, JTAG lockdown) must be documented and verified processes.
- Supply chain review: Hardware component supply chain security review - sourcing from trusted suppliers, component authenticity verification.
These hardware-specific SDLC activities should be documented in the Annex VII technical file alongside software-focused security activities.
Work through the CRA for each product in one workspace.
Classify each product, build the Annex VII technical file and prepare Article 14 notifications. The disclosure portal that receives vulnerability reports stays free.
Frequently asked
Does the CRA require a specific SDLC standard or framework?+
No. The CRA requires no SDLC at all, and so no specific framework. It requires a product that meets Annex I and a risk assessment that is taken into account through design, development, production and maintenance (Article 13(2)). Recognised frameworks include Microsoft SDL, NIST SSDF (Secure Software Development Framework, SP 800-218), OWASP SAMM, and ISO/IEC 27034. IEC 62443-4-1 provides an SDLC framework specifically for industrial control system products. A recognised framework that fits the product category is a practical way to produce the evidence that the technical file needs.
How does SDLC relate to the conformity assessment process?+
Evidence from an SDLC supports the Annex VII technical file. Threat models, security test reports, code review records and the SBOM help to show that the product meets the essential requirements. A notified body, where the route needs one, assesses the product and the vulnerability handling processes. It does not assess whether the manufacturer operates an SDLC, as ENISA's November 2026 report on notified body accreditation states. Development records can still serve as supporting evidence, and complete records shorten the assessment.
Can a startup or small manufacturer implement an SDLC without large team resources?+
Yes. SDLC practices scale to organisation size. A small team can implement a lightweight SDLC using: a simple threat model template for each new product; automated SAST and SCA tools integrated into their CI/CD pipeline (many have free tiers for small organisations); a checklist-based security review before each major release; and a CycloneDX SBOM generated automatically on every build. The key is consistency and documentation - a simple, consistent process with evidence is more valuable for CRA compliance than a sophisticated process poorly documented.
Sector checklists covering Secure Development Lifecycle (SDLC)
This definition is part of the EU Cyber Resilience Act guide, which explains Regulation (EU) 2024/2847 article by article.
Browse the full CRA Compliance Checklist
See how Secure Development Lifecycle (SDLC) fits into your complete CRA compliance programme.