AWS Well-Architected Security Pillar
Identity & Access Management

AWS Well-Architected Security Pillar 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.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 20 controls across 13 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

NIST SP 800-171 Rev 3 · 3 controls

FedRAMP High · 2 controls

  • AC-21 Information Sharing
  • AC-4 Information Flow Enforcement

FedRAMP Moderate · 2 controls

  • AC-21 Information Sharing
  • AC-4 Information Flow Enforcement

NIST SP 800-161 Rev 1 · 2 controls

NIST SP 800-53 Rev 5 · 2 controls

  • ASBv3-GS-2 Define and implement enterprise segmentation/separation of duties strategy

CMMC 2.0 · 1 control

HIPAA Security Rule · 1 control

ISO 27001:2022 · 1 control

  • 5.14 Information transfer

ISO 27002:2022 · 1 control

  • 8.3 Information access restriction
  • NIST-CSF-PR.AA-05 Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Identity & Access Management

You are reading one control. How much of AWS Well-Architected Security Pillar have you already done?

AWS Well-Architected Security Pillar SEC03-BP08 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of AWS Well-Architected Security Pillar your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 52 of 63 AWS Well-Architected Security Pillar controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.

Query this from an agent

The graph holds this control, the 20 it maps to, and the evidence behind each claim, over MCP and REST.