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.
Source: AWS Well-Architected Security Pillar, SEC11-BP08. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open AWS Well-Architected Security Pillar in the compliance library.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
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
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