SEC01-BP02 Secure account root user and properties
Protect the root user of every AWS account with strong MFA, no programmatic access keys, monitored email and contact details, and use root only for tasks that explicitly require it.
Source: AWS Well-Architected Security Pillar, SEC01-BP02. 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
- Root MFA evidence per account · Identity provider / directory
- Alternate contact configuration · Identity provider / directory
- Root usage CloudTrail alerts · Identity provider / directory
periodic reviewEvidence produced at each review
- Root access key absence report · Identity provider / directory
governing documentDocuments that govern the control
- Break glass procedure · Policy repository / GRC workspace
First move
Common gaps auditors find
- no MFA on root
- active root access keys
- shared root email mailbox
- no alarm on root sign in
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-BP01 Separate workloads using accounts · SEC01-BP03 Identify and validate control objectives