PS.1.1 Protect All Forms of Code from Unauthorized Modification
Apply controls to source code, infrastructure as code, and build scripts so that only authorized contributors can change them and all changes are reviewed and logged. Protect main branches and require pull request review
4
artefacts
2
held by a system
0
at each review
easy
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Branch protection configuration · Cloud console / configuration management
- Audit log retention for source control · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Code review policy and tool enforcement · Policy repository / GRC workspace
- Exception register for direct pushes · Policy repository / GRC workspace
First move
Automate the pull from your Cloud console / configuration management. Configuration snapshots and change history from the cloud console or IaC repository, diffed against the baseline.
Common gaps auditors find
- main branch protection disabled in many repositories
- code review can be self approved
- audit logs lost when repositories migrate
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.5.2 Harden Development Endpoints · PS.2.1 Provide a Mechanism for Verifying Software Release Integrity