Guides · Secure software development
NIST SSDF: secure software development practices
NIST's Secure Software Development Framework is "a core set of high-level secure software development practices that can be integrated into each SDLC implementation" — because, as NIST notes, few lifecycle models address software security in detail on their own. If the lifecycle model does not already address security in detail, the practices still have to be added — in NIST's words, to each SDLC implementation.
This is a field note about practices inside the lifecycle, not a penetration-test sales page, not a certification OVERSEASGENAI holds, and not an exploit write-up. It contains no attack procedures, no vulnerability walkthroughs, and no invented counts of "bugs caught." It does not claim that OVERSEASGENAI, PrimusNeo, or a named client is SSDF-aligned. Individual SSDF practice IDs (PO, PS, PW, RV, or similar) are not listed here; the practice tables were not quoted in the brief, and they are not reconstructed from memory.
NIST's Secure Software Development Framework, Secure Software Development Framework (SSDF) Version 1.1: Recommendations for Mitigating the Risk of Software Vulnerabilities, February 2022. Authors: Murugiah Souppaya, Karen Scarfone, Donna Dodson. The document "recommends the Secure Software Development Framework (SSDF) – a core set of high-level secure software development practices that can be integrated into each SDLC implementation."
The aim, in complete sentences: following such practices should help software producers reduce the number of vulnerabilities in released software, reduce the potential impact of the exploitation of undetected or unaddressed vulnerabilities, and address the root causes of those vulnerabilities.
NIST CSRC publication page: "Few software development life cycle (SDLC) models explicitly address software security in detail, so secure software development practices usually need to be added to each SDLC model to ensure that the software being developed is well-secured." Date published: February 2022; supersedes a NIST companion paper on the same framework (23 April 2020).
What SSDF is
Version 1.1, February 2022; a recommended, high-level set of practices; intended to reduce vulnerabilities, reduce the impact of those that remain, and address root causes. Not a checklist badge. A delivery program can point at the framework. Pointing at it is not the same as wearing it.
The working-software and verifiable-requirements guides are the delivery-test siblings. Security is not a phase that starts after the demo has already shipped, in the sense NIST is describing.
The first conversation still ends with a yes, a no, or a better idea, at Start.
The useful next step is to read NIST's Secure Software Development Framework, or to ask whether secure-development practices are already in the lifecycle, or still waiting for a later phase. If something on this page is wrong, write to us.