SEC11-BP08 Build a program that embeds security ownership in workload teams
Establish security champions inside each workload team, give them training and tooling and measure security KPIs alongside delivery metrics.
4
artefacts
1
held by a system
0
at each review
moderate
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
- Team security KPI dashboard · Cloud console / configuration management
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Security champion roster · Document repository
- Champion charter and time allocation · Policy repository / GRC workspace
- Shared OKRs · Document repository
First move
Start with the 1 of 4 artefacts that already live in a system (Cloud console / configuration management); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- security team owns all risk
- no champions identified
- no security KPIs for product teams
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-BP07 Regularly assess security properties of the pipelines