SEC03-BP03 Establish emergency access process
Define a documented break-glass procedure for emergency access that bypasses normal SSO when the IdP is unavailable, with strong MFA, monitoring and post-use review.
Source: AWS Well-Architected Security Pillar, SEC03-BP03. 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
- Alerts on use · SIEM / log platform
- Post-use review log · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Break glass procedure document · Policy repository / GRC workspace
- Isolated break glass account credentials in vault · Policy repository / GRC workspace
First move
Common gaps auditors find
- no break glass plan
- credentials stored insecurely
- no alarm on use
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 sheetSEC03-BP02 Grant least privilege access · SEC03-BP04 Reduce permissions continuously