SEC01-BP07 Identify threats and prioritize mitigations using a threat model
Conduct threat modeling for each workload using STRIDE or similar, prioritise mitigations against business impact and review models on significant change.
Source: AWS Well-Architected Security Pillar, SEC01-BP07. 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
none for this control
periodic reviewEvidence produced at each review
- Review cadence record · Document repository
governing documentDocuments that govern the control
- Threat model documents (STRIDE) · Document repository
- Data flow diagrams · Policy repository / GRC workspace
- Mitigation backlog with priority · Document repository
First move
Common gaps auditors find
- no threat models
- models stale after major changes
- threats identified but not tracked to closure
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 sheetSEC01-BP06 Automate deployment of standard security controls · SEC01-BP08 Evaluate and implement new security services and features regularly