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.
3
artefacts
0
held by a system
0
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
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
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
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