Standard and framework · NIST SP 800-218 Version 1.1
NIST SSDF: Secure Software Development Framework
The NIST Secure Software Development Framework (SSDF) is a set of high-level secure software development practices that can be added to any development life cycle.
- 4 practice groups: PO, PS, PW, RV
- 1.1 current final version (February 2022)
- 1.2 draft version (December 2025)
What Is NIST SSDF?
It reduces the number of vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. in released software, limits the impact of those that remain and addresses their root causes, and gives buyers and producers a common vocabulary for secure development.
The SSDFSecure Software Development Framework groups its practices in four groups: Prepare the Organization (PO), Protect the Software (PS), Produce Well-Secured Software (PW) and Respond to Vulnerabilities (RV). Each practice has tasks, notional implementation examples and references to other standards, so it can be mapped to existing methods such as DevSecOps, agile or waterfall development.
SP 800-218A (26 July 2024) is a community profile that adds practices for generative AIGenerative Artificial Intelligence and dual-use foundation models. The draft version 1.2, prepared under Executive Order 14306, updates the framework; its comment period has closed. Under OMBOffice of Management and Budget M-22-18 and M-23-16, federal agencies had to obtain a CISACybersecurity and Infrastructure Security Agency secure software development attestation form, based on SSDFSecure Software Development Framework practices, from software producers. OMBOffice of Management and Budget M-26-05 rescinded both memoranda: agencies now take their own risk-based approach and may still use the form and the SSDFSecure Software Development Framework.
- Full title
- NIST SP 800-218: Secure Software Development Framework (NIST SSDF)
- Original title
- Secure Software Development Framework (SSDF) Version 1.1: Recommendations for Mitigating the Risk of Software Vulnerabilities
- Official reference
- NIST SP 800-218 Version 1.1 (February 2022); draft SP 800-218 Rev. 1, Version 1.2 (December 2025); SP 800-218A (July 2024)
- Type
- Framework
- Issued by
- National Institute of Standards and Technology (NIST), US Department of Commerce
- Applies from
- 3 February 2022
- Status
- In force and applicable
- Countries
- Worldwide
Official text
Does It Apply to You?
Tools that work with this act, free and without signing up.
What NIST SSDF Requires
Group PO
Prepare the Organization
Define security requirements, roles, training, toolchains and criteria for software security checks.
Group PS
Protect the Software
Protect code from unauthorised access and tampering, verify release integrity and archive releases with provenance data.
Group PW
Produce Well-Secured Software
Threat modelling, secure design, reuse of secure components, code review, testing and secure default settings.
Group RV
Respond to Vulnerabilities
Identify, assess and remediate vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. and analyse their root causes.
Show All 5 Requirements
SP 800-218A
Generative AI profile
Additional practices for developing generative AIGenerative Artificial Intelligence and dual-use foundation models.
| Covered entities | Kind | Article | Where defined |
|---|---|---|---|
| Software producers | Apply the practices in their development life cycle. | ||
| Software acquirers | Use the practices to set and check supplier requirements. |
Where it applies: Worldwide; voluntary, used in US federal procurement.
Local representative: Not required.
Software producers of all sizes, including suppliers of commercial, open-source and in-house software and of connected productsConnected Product (General), and the organisations that acquire software.
There are no legal penalties under the framework. False statements in an attestation given to a US federal agency could create liability under federal law, including the False Claims Act.
Latest NIST SSDF Updates
NIST SSDF Milestones Since 2022
- OMB M-26-05 rescinds the mandatory attestation
- Version 1.2 initial public draft
- SP 800-218A generative AI profile published
- Version 1.1 published
How We Help With NIST SSDF
Start with an assessment, or have us run the work.
Questions
NIST SSDF FAQ: Common Questions Answered
Do software suppliers to the US government still have to sign the secure software attestation form?
Not as a general requirement. OMBOffice of Management and Budget Memorandum M-26-05 of 23 January 2026 rescinded M-22-18 and M-23-16, which required agencies to collect the form. Agencies now decide on a risk-based approach and may still ask for the form, SBOMsSoftware Bill of Materials or other evidence in their contracts.
Is SSDF version 1.2 final?
No. SP 800-218 Rev. 1 (SSDF version 1.2) was released as an initial public draft on 17 December 2025. Version 1.1 of February 2022 remains the final version.
How does the SSDF relate to the EU Cyber Resilience Act?
The CRACyber Resilience Act sets legal requirements for products with digital elements sold in the EU. The SSDFSecure Software Development Framework does not give a presumption of conformity, but its practices help manufacturers show secure development and vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. handling.
Preparing for NIST SSDF?
Thirty minutes with a GRC+ consultant: we look at your scope, the requirements that apply and where to start.