SEC03-BP07 Analyze public and cross-account access
Use IAM Access Analyzer to detect resources that grant public or external account access and validate each finding against documented intent.
Source: AWS Well-Architected Security Pillar, SEC03-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
- Finding closure tickets · Ticketing / ITSM
periodic reviewEvidence produced at each review
- Access Analyzer external access findings · Document repository
governing documentDocuments that govern the control
- Approved sharing register · Policy repository / GRC workspace
- S3 public access block status · Document repository
First move
Common gaps auditors find
- public S3 buckets unintentionally
- cross-account trust without business justification
- Access Analyzer disabled in regions
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-BP06 Manage access based on lifecycle · SEC03-BP08 Share resources securely within your organization