SEC03-BP08 Share resources securely within your organization
Use AWS RAM, resource policies and Organizations conditions to share resources only within trusted account boundaries, avoiding broad public or cross-org sharing.
Source: AWS Well-Architected Security Pillar, SEC03-BP08. 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
- AWS RAM share inventory · Policy repository / GRC workspace
- Resource policies with aws:PrincipalOrgID condition · Policy repository / GRC workspace
- Approval workflow for new shares · Document repository
First move
Common gaps auditors find
- resource policies allow *
- shares outside organisation without justification
- RAM shares with stale principals
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-BP07 Analyze public and cross-account access · SEC03-BP09 Share resources securely with a third party