AWS Well-Architected Security Pillar
Identity & Access Management

AWS Well-Architected Security Pillar SEC03-BP05: Define permission guardrails for your organization

Apply Service Control Policies, resource control policies and declarative guardrails at the organisation or OU level to enforce non-negotiable security boundaries.

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

What else in your programme already covers this

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

CMMC 2.0 · 4 controls

NIST SP 800-171 Rev 3 · 3 controls

  • 03.01.02 Access Enforcement
  • 03.01.07 Least Privilege - Privileged Functions
  • 03.13.06 Network Communications - Deny by Default - Allow by Exception

NIST SP 800-53 Rev 5 · 3 controls

  • AM-2 Use only approved services
  • PV-2 Audit and enforce secure configurations

FedRAMP High · 2 controls

  • AC-3 Access Enforcement
  • AC-6(10) Prohibit Non-Privileged Users from Executing Privileged Functions

FedRAMP Moderate · 2 controls

  • AC-3 Access Enforcement
  • AC-6(10) Prohibit Non-Privileged Users from Executing Privileged Functions

ISO 27001:2022 · 2 controls

  • 5.15 Access control
  • 5.23 Information security for use of cloud services

ISO 27002:2022 · 2 controls

  • 5.15 Access control
  • 5.23 Information security for use of cloud services

NIST SP 800-161 Rev 1 · 2 controls

SOC 2 · 2 controls

  • SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11)
  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • ANSSI-HYG-16 Use a Centralised Management Tool to Standardise Security Policies

C5 (Germany) · 1 control

CIS Controls v8 · 1 control

  • CIS-5.4 Restrict Administrator Privileges to Dedicated Administrator Accounts

HIPAA Security Rule · 1 control

  • 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

PCI DSS 4.0 · 1 control

  • 7.3.3 7.3.3 Access control default deny all

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-BP05 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 34 it maps to, and the evidence behind each claim, over MCP and REST.