Home›DevSecOps Pipeline›NIST SSDF coverage

How our DevSecOps pipeline covers NIST SSDF

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.

42 tasks · SSDF version 1.1 23 handled in the pipeline Evidence collected automatically

All 42 tasks at a glance

One square per SSDF task. Select a category to highlight it, or a square to jump to the task.

13
Built into the pipeline

Set up by us and done by the pipeline on every change, with no extra work from developers.

10
Pipeline enforces your policy

You decide the rule; the pipeline applies it and keeps the record.

9
Template provided

We hand over a ready policy or checklist; your team adopts it and runs it.

10
Your team

Outside a pipeline: training, workstations, product design and customer communication.

Evidence the pipeline collects

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.

All tasks by practice group

Task names are shortened. The full wording, examples and references are in the NIST publication.

POPrepare the organization

TaskWhat it coversHandled by
PO.1.1Document security requirements for development infrastructure and processesTemplate
PO.1.2Document security requirements for the software you buildPipeline + your policy
PO.1.3Pass security requirements on to suppliers of commercial componentsYour team
PO.2.1Define roles and responsibilities across the development life cycleTemplate
PO.2.2Provide role-based trainingYour team
PO.2.3Secure management commitment to secure developmentYour team
PO.3.1Specify which tools each toolchain must include and how they integrateBuilt in
PO.3.2Deploy, operate and maintain tools securely, as codeBuilt in
PO.3.3Configure tools to generate evidence of secure practicesBuilt in
PO.4.1Define criteria for software security checksPipeline + your policy
PO.4.2Gather and protect the information behind those criteriaBuilt in
PO.5.1Separate and protect development, build, test and distribution environmentsPipeline + your policy
PO.5.2Harden developer workstationsYour team

PSProtect the software

TaskWhat it coversHandled by
PS.1.1Store all code with least-privilege access and full change historyBuilt in
PS.2.1Give customers a way to verify release integrityBuilt in
PS.3.1Archive and protect each releaseBuilt in
PS.3.2Keep provenance data (SBOM) for every component of each releaseBuilt in

PWProduce well-secured software

TaskWhat it coversHandled by
PW.1.1Model threats and assess security riskTemplate
PW.1.2Track security requirements, risks and design decisionsPipeline + your policy
PW.1.3Use standard security features instead of custom onesYour team
PW.2.1Review the design against security requirementsTemplate
PW.4.1Acquire and maintain well-secured third-party componentsBuilt in
PW.4.2Build well-secured shared components in-houseYour team
PW.4.4Verify third-party components throughout their life cycleBuilt in
PW.5.1Follow secure coding practicesPipeline + your policy
PW.6.1Use current, verified compilers and build toolsBuilt in
PW.6.2Use secure compiler and build settingsPipeline + your policy
PW.7.1Decide where code review and code analysis applyTemplate
PW.7.2Review and analyse code, and triage every findingBuilt in
PW.8.1Decide which executable testing is neededTemplate
PW.8.2Run security tests and record the resultsPipeline + your policy
PW.9.1Define secure default settingsYour team
PW.9.2Implement and document the default settingsYour team

RVRespond to vulnerabilities

TaskWhat it coversHandled by
RV.1.1Collect vulnerability reports and monitor public sourcesPipeline + your policy
RV.1.2Re-analyse supported releases on a regular scheduleBuilt in
RV.1.3Set a vulnerability disclosure and response policyTemplate
RV.2.1Analyse each vulnerability and assess its riskPipeline + your policy
RV.2.2Plan and deliver the response, including advisoriesYour team
RV.3.1Find the root cause of each vulnerabilityTemplate
RV.3.2Analyse root causes over time to spot patternsTemplate
RV.3.3Search for similar vulnerabilities proactivelyPipeline + your policy
RV.3.4Update the development process so root causes do not recurYour team

What this map is and is not

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.

Related

Sources
  1. NIST Special Publication 800-218, Secure Software Development Framework (SSDF) Version 1.1, February 2022 — doi.org/10.6028/NIST.SP.800-218
  2. NIST SP 800-218 Rev. 1, SSDF Version 1.2, Initial Public Draft, December 2025 — doi.org/10.6028/NIST.SP.800-218r1.ipd

Your customers ask about SSDF?

On a 30-minute call we look at what you already have and which tasks are still open.

Pick a 30-minute slot Opens our booking calendar in a new tab · or write to info@dvs.hk
Book a 30-minute call