SEC03-BP02 Grant least privilege access
Write IAM policies that allow only the specific actions, resources and conditions a job needs, starting broad and narrowing them, with policy generation in IAM Access Analyzer as one aid to the narrowing. Record exceptions.
Source: AWS Well-Architected Security Pillar, SEC03-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
- IAM Access Analyzer policy generation outputs · Policy repository / GRC workspace
periodic reviewEvidence produced at each review
- Policy review records · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Permissions boundary definitions · Policy repository / GRC workspace
- Wildcard policy exception register · Policy repository / GRC workspace
First move
Common gaps auditors find
- AdministratorAccess used broadly
- wildcards in actions and resources
- no permissions boundaries
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-BP01 Define access requirements · SEC03-BP03 Establish emergency access process