SEC03-BP01 Define access requirements
Document who or what requires access to each resource, what actions are permitted and under what conditions, so least privilege policies can be designed and validated against intent.
Source: AWS Well-Architected Security Pillar, SEC03-BP01. 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
none for this control
governing documentDocuments that govern the control
- Access requirements matrix per workload · Policy repository / GRC workspace
- Role catalogue · Policy repository / GRC workspace
- Data classification mapping to roles · Policy repository / GRC workspace
First move
Common gaps auditors find
- no documented access intent
- policies built ad hoc
- no link from requirement to policy
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 sheetSEC02-BP06 Employ user groups and attributes · SEC03-BP02 Grant least privilege access