SEC11-BP07 Regularly assess security properties of the pipelines
Treat the CI CD pipeline itself as a sensitive workload and review its IAM roles, secrets handling, runner isolation and tamper resistance regularly.
4
artefacts
1
held by a system
2
at each review
moderate
to go live
Source control / CI pipeline
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Pipeline threat model · Source control / CI pipeline
periodic reviewEvidence produced at each review
- IAM role review for pipelines · Identity provider / directory
- Self hosted runner hardening evidence · Source control / CI pipeline
governing documentDocuments that govern the control
- OIDC trust policies · Policy repository / GRC workspace
First move
Start with the 1 of 4 artefacts that already live in a system (Source control / CI pipeline); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- pipeline roles have AdministratorAccess
- long lived deploy keys
- shared runner pool with no isolation
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 sheetSEC11-BP06 Deploy software programmatically · SEC11-BP08 Build a program that embeds security ownership in workload teams