NIST SP 800-204D Software Supply Chain Security in DevSecOps CI/CD Pipelines
Section 5.2: Securing workflows in CD pipelines – NIST SP 800-204D Software Supply Chain Security in DevSecOps CI/CD Pipelines

NIST SP 800-204D Software Supply Chain Security in DevSecOps CI/CD Pipelines 5.2.1a: GitOps: rely on automation and preserve all release data

What does 5.2.1a require?

Where GitOps is used for continuous deployment, the process relies on automation rather than manual operations (manually editing hundreds of configuration files to roll back a cluster deployment is avoided), and package managers that support GitOps retain the full record of each release: every module's version number, every associated configuration file and the other release data, so that every release can be reproduced and audited.

Maintained by Gerard Blokdyk

Other controls in Section 5.2: Securing workflows in CD pipelines – NIST SP 800-204D Software Supply Chain Security in DevSecOps CI/CD Pipelines

Query this from an agent

The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.

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