1 | Purpose, scope and audience | 0 |
2 | The software supply chain: definition, economics, governance and model | 0 |
3.1 | Risk factors: developer environment, threat actors, attack vectors and targets | 0 |
3.2.1a | Keep every developer and build system to a defined security baseline | 0 |
3.2.1b | Approve open-source intake and prefer source over prebuilt binaries | 0 |
3.2.1c | Verify, scan and inventory newly downloaded open-source packages | 0 |
3.2.1d | Scan stored artifacts for new defects and be able to block their use in builds | 0 |
3.2.1e | Audit CI/CD processes regularly and automate wherever possible | 0 |
3.2.2a | Control write access to source code management and require peer review before merge | 0 |
3.2.2b | Generate and use SCM provenance data in policy decisions | 0 |
4.1a | Establish and verify trust in every entity, artifact and repository in the pipeline | 0 |
4.1b | Re-establish trust at every handoff and verify each build step's inputs and outputs | 0 |
4.2 | Entities that need trust: artifacts and repositories | 0 |
5.1.1a | Build on a hardened, isolated platform and gather evidence of isolation | 0 |
5.1.1b | Produce environment, process, materials and artifact attestations for each build | 0 |
5.1.1c | Sign attestations with a secure key and store them tamper-proof | 0 |
5.1.2a | Run automated checks on every pushed change and tie requests to the developer's role | 0 |
5.1.2b | Use CI tools only when their source origin is trustworthy | 0 |
5.1.2c | Hold outside contributors' workflow runs until a maintainer approves | 0 |
5.1.3a | Protect software update integrity against known attacks with multi-key, threshold trust | 0 |
5.1.3b | Keep online signing keys away from roles clients ultimately trust, and guard them when used | 0 |
5.1.4a | Run static and dynamic security testing on every language before commits are accepted | 0 |
5.1.4b | Enumerate and evaluate all dependencies, including transitive ones | 0 |
5.1.4c | Check committed code for policy adherence and secrets, and enable push protection | 0 |
5.2.1a | GitOps: rely on automation and preserve all release data | 0 |
5.2.1b | GitOps: no manual runtime changes, and detect and remediate drift | 0 |
5.2a | Scan containers at build and integrate registry tooling with an automated pipeline | 0 |
5.2b | Scan deploy-ready code and repositories for secrets | 0 |
5.2c | Review dependency vulnerabilities before pull requests are merged | 0 |
5.2d | Deploy only artifacts produced by the secure build, with vulnerability scan evidence and policy gating | 0 |
5.2e | Check release build scripts periodically for malicious code | 0 |
5.3 | Implementation strategy for SSC security in the pipeline | 0 |
6 | Summary, conclusions and Appendix A mapping to the SSDF | 0 |