United States

NIST SP 800-204D Software Supply Chain Security in DevSecOps CI/CD Pipelines

33 controls. 0 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

33 controls 0 frameworks share controls with it United States verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

No measured overlap with another framework in the corpus.

Every control

CodeControlAlso in
1Purpose, scope and audience0
2The software supply chain: definition, economics, governance and model0
3.1Risk factors: developer environment, threat actors, attack vectors and targets0
3.2.1aKeep every developer and build system to a defined security baseline0
3.2.1bApprove open-source intake and prefer source over prebuilt binaries0
3.2.1cVerify, scan and inventory newly downloaded open-source packages0
3.2.1dScan stored artifacts for new defects and be able to block their use in builds0
3.2.1eAudit CI/CD processes regularly and automate wherever possible0
3.2.2aControl write access to source code management and require peer review before merge0
3.2.2bGenerate and use SCM provenance data in policy decisions0
4.1aEstablish and verify trust in every entity, artifact and repository in the pipeline0
4.1bRe-establish trust at every handoff and verify each build step's inputs and outputs0
4.2Entities that need trust: artifacts and repositories0
5.1.1aBuild on a hardened, isolated platform and gather evidence of isolation0
5.1.1bProduce environment, process, materials and artifact attestations for each build0
5.1.1cSign attestations with a secure key and store them tamper-proof0
5.1.2aRun automated checks on every pushed change and tie requests to the developer's role0
5.1.2bUse CI tools only when their source origin is trustworthy0
5.1.2cHold outside contributors' workflow runs until a maintainer approves0
5.1.3aProtect software update integrity against known attacks with multi-key, threshold trust0
5.1.3bKeep online signing keys away from roles clients ultimately trust, and guard them when used0
5.1.4aRun static and dynamic security testing on every language before commits are accepted0
5.1.4bEnumerate and evaluate all dependencies, including transitive ones0
5.1.4cCheck committed code for policy adherence and secrets, and enable push protection0
5.2.1aGitOps: rely on automation and preserve all release data0
5.2.1bGitOps: no manual runtime changes, and detect and remediate drift0
5.2aScan containers at build and integrate registry tooling with an automated pipeline0
5.2bScan deploy-ready code and repositories for secrets0
5.2cReview dependency vulnerabilities before pull requests are merged0
5.2dDeploy only artifacts produced by the secure build, with vulnerability scan evidence and policy gating0
5.2eCheck release build scripts periodically for malicious code0
5.3Implementation strategy for SSC security in the pipeline0
6Summary, conclusions and Appendix A mapping to the SSDF0

Tell me when NIST SP 800-204D Software Supply Chain Security in DevSecOps CI/CD Pipelines files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for NIST SP 800-204D Software Supply Chain Security in DevSecOps CI/CD Pipelines, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition