NIST SP 800-204D Software Supply Chain Security in DevSecOps CI/CD Pipelines
Section 4: CI/CD pipeline security goals and entities to be trusted – 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 4.1b: Re-establish trust at every handoff and verify each build step's inputs and outputs

What does 4.1b require?

Because artifacts pass through many repositories on the way to the final product, trust is established as a recurring process at each handoff rather than once at the start, and what goes into and comes out of each build step is verified to confirm the expected step was run by the expected component. The trust chain includes the sub-elements, components, workers and attestors involved, and it is renewed through their interactions.

Maintained by Gerard Blokdyk

Other controls in Section 4: CI/CD pipeline security goals and entities to be trusted – 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