The NIST Secure Software Development Framework (SP 800-218) lists 42 tasks that customers and security questionnaires increasingly ask about. Here is how each one is handled when we build the pipeline: what it does on its own, where it applies a rule you set, where we give you a ready template, and what stays with your team.
One square per SSDF task. Select a category to highlight it, or a square to jump to the task.
Set up by us and done by the pipeline on every change, with no extra work from developers.
You decide the rule; the pipeline applies it and keeps the record.
We hand over a ready policy or checklist; your team adopts it and runs it.
Outside a pipeline: training, workstations, product design and customer communication.
SSDF asks for records that show each practice is actually followed. The pipeline produces them during normal work, so a customer review or an audit starts with an export, not a writing project.
Task names are shortened. The full wording, examples and references are in the NIST publication.
| Task | What it covers | Handled by |
|---|---|---|
| PO.1.1 | Document security requirements for development infrastructure and processes | Template |
| PO.1.2 | Document security requirements for the software you build | Pipeline + your policy |
| PO.1.3 | Pass security requirements on to suppliers of commercial components | Your team |
| PO.2.1 | Define roles and responsibilities across the development life cycle | Template |
| PO.2.2 | Provide role-based training | Your team |
| PO.2.3 | Secure management commitment to secure development | Your team |
| PO.3.1 | Specify which tools each toolchain must include and how they integrate | Built in |
| PO.3.2 | Deploy, operate and maintain tools securely, as code | Built in |
| PO.3.3 | Configure tools to generate evidence of secure practices | Built in |
| PO.4.1 | Define criteria for software security checks | Pipeline + your policy |
| PO.4.2 | Gather and protect the information behind those criteria | Built in |
| PO.5.1 | Separate and protect development, build, test and distribution environments | Pipeline + your policy |
| PO.5.2 | Harden developer workstations | Your team |
| Task | What it covers | Handled by |
|---|---|---|
| PS.1.1 | Store all code with least-privilege access and full change history | Built in |
| PS.2.1 | Give customers a way to verify release integrity | Built in |
| PS.3.1 | Archive and protect each release | Built in |
| PS.3.2 | Keep provenance data (SBOM) for every component of each release | Built in |
| Task | What it covers | Handled by |
|---|---|---|
| PW.1.1 | Model threats and assess security risk | Template |
| PW.1.2 | Track security requirements, risks and design decisions | Pipeline + your policy |
| PW.1.3 | Use standard security features instead of custom ones | Your team |
| PW.2.1 | Review the design against security requirements | Template |
| PW.4.1 | Acquire and maintain well-secured third-party components | Built in |
| PW.4.2 | Build well-secured shared components in-house | Your team |
| PW.4.4 | Verify third-party components throughout their life cycle | Built in |
| PW.5.1 | Follow secure coding practices | Pipeline + your policy |
| PW.6.1 | Use current, verified compilers and build tools | Built in |
| PW.6.2 | Use secure compiler and build settings | Pipeline + your policy |
| PW.7.1 | Decide where code review and code analysis apply | Template |
| PW.7.2 | Review and analyse code, and triage every finding | Built in |
| PW.8.1 | Decide which executable testing is needed | Template |
| PW.8.2 | Run security tests and record the results | Pipeline + your policy |
| PW.9.1 | Define secure default settings | Your team |
| PW.9.2 | Implement and document the default settings | Your team |
| Task | What it covers | Handled by |
|---|---|---|
| RV.1.1 | Collect vulnerability reports and monitor public sources | Pipeline + your policy |
| RV.1.2 | Re-analyse supported releases on a regular schedule | Built in |
| RV.1.3 | Set a vulnerability disclosure and response policy | Template |
| RV.2.1 | Analyse each vulnerability and assess its risk | Pipeline + your policy |
| RV.2.2 | Plan and deliver the response, including advisories | Your team |
| RV.3.1 | Find the root cause of each vulnerability | Template |
| RV.3.2 | Analyse root causes over time to spot patterns | Template |
| RV.3.3 | Search for similar vulnerabilities proactively | Pipeline + your policy |
| RV.3.4 | Update the development process so root causes do not recur | Your team |
SSDF describes outcomes and leaves the choice of tools to each organisation. NIST does not certify against it, and neither do we. The map shows how our standard DevSecOps package splits the work; the actual scope for your organisation is fixed after we measure your environment.
A revision of the framework (version 1.2) was published as a public draft in December 2025. We will update this map when the final version is released.
On a 30-minute call we look at what you already have and which tasks are still open.