PO.1.2 Implement Security Requirements in the Toolchain
Configure development tools, source control, build systems, and artifact repositories to enforce the security requirements. Automate enforcement so that compliance is the default behavior rather than a manual checklist.
4
artefacts
0
held by a system
1
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Monthly compliance metrics across repositories · Source control / CI pipeline
governing documentDocuments that govern the control
- Toolchain hardening baseline · Policy repository / GRC workspace
- Policy as code in CI configuration · Policy repository / GRC workspace
- Exception process for bypassing tool gates · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- tool gates can be bypassed by anyone with admin in CI
- no enforcement for legacy repositories
- exception process exists but is rarely used because gates are weak
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetPO.1.1 Define Security Requirements for Software Development · PO.1.3 Communicate Requirements to Third-Party Providers