Do your resource policies and sharing rules limit access to identities in your own organization?
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
Question 17 of the assessment asks: Do your resource policies and sharing rules limit access to identities in your own organization? Without an organization boundary, one mistaken policy line can give any account on the internet access to your data.
Start the assessment ยท All 40 questions
Why it matters
Without an organization boundary, one mistaken policy line can give any account on the internet access to your data.
Answers and what each is worth
| Answer | Value |
|---|---|
| Yes, enforced by policy | 1 |
| In some policies only | 0.5 |
| No or not known | 0 |
How to check it in each cloud
- AWS
- Check SCPs or resource control policies for aws:PrincipalOrgID and aws:ResourceOrgID conditions, and test with Access Analyzer external access findings.
- Azure
- Check tenant restrictions, B2B cross-tenant access settings and Azure Policy on storage, and review which external tenants are allowed.
- Google Cloud
- Check that the iam.allowedPolicyMemberDomains org policy (domain restricted sharing) is enforced and lists only your own customer IDs.
The fix
Add an organization-boundary condition to resource policies and a deny rule at the organization level. Effort: medium.
Where it comes from
- AWS documentation Data perimeter: Building a data perimeter on AWS
- NIST SP 800-53 Rev. 5 AC-4: source
Related pages
Sources
- AWS documentation Data perimeter, read 16 Nov 2026
- NIST SP 800-53 Rev. 5 AC-4, read 16 Nov 2026
Last reviewed 16 Nov 2026.