AWS Well-Architected Security Pillar
Identity & Access Management

AWS Well-Architected Security Pillar SEC03-BP02: Grant least privilege access

Write IAM policies that allow only the specific actions, resources and conditions a job needs, starting broad and narrowing them, with policy generation in IAM Access Analyzer as one aid to the narrowing. Record exceptions.

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

What else in your programme already covers this

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

C5 (Germany) · 6 controls

FedRAMP High · 5 controls

  • AC-17(4) Privileged Commands and Access
  • AC-3 Access Enforcement
  • AC-6 Least Privilege
  • AC-6(1) Authorize Access to Security Functions
  • AU-9(4) Access by Subset of Privileged Users

FedRAMP Moderate · 5 controls

  • AC-17(4) Privileged Commands and Access
  • AC-3 Access Enforcement
  • AC-6 Least Privilege
  • AC-6(1) Authorize Access to Security Functions
  • AU-9(4) Access by Subset of Privileged Users

Azure Security Benchmark · 3 controls

  • ASBv3-AM-4 Limit access to asset management
  • ASBv3-PA-7 Follow just enough administration (least privilege) principle
  • IM-7 Restrict resource access based on conditions

CIS Controls v8 · 3 controls

  • CIS-16.10 Apply Secure Design Principles in Application Architectures
  • CIS-5.4 Restrict Administrator Privileges to Dedicated Administrator Accounts
  • CIS-6.8 Define and Maintain Role-Based Access Control

CMMC 2.0 · 3 controls

HIPAA Security Rule · 3 controls

ISO 27001:2022 · 3 controls

  • 5.15 Access control
  • 8.2 Privileged access rights
  • 8.3 Information access restriction

ISO 27002:2022 · 3 controls

  • 5.15 Access control
  • 8.2 Privileged access rights
  • 8.3 Information access restriction

NIST SP 800-66 Rev 2 · 3 controls

PCI DSS 4.0 · 3 controls

  • 7.2.2 7.2.2 User access assigned by job function and least privilege
  • 7.2.5 7.2.5 Application and system accounts least privilege
  • 7.3.1 7.3.1 Need-to-know access control system covers all components

UK Cyber Essentials · 3 controls

  • CE-AC.4 Privileged Account Approval and Tracking
  • CE-AC.5 Separate Admin Accounts for Administrative Activities
  • CE-AC.6 Periodic Review of Privileged Access

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 2 controls

  • ANSSI-HYG-09 Assign the Correct Rights on Sensitive Resources
  • ANSSI-HYG-29 Limit Administration Rights on Workstations to Operational Need

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 2 controls

ISO 27701:2019 · 2 controls

  • 6.6.1 Business requirements of access control
  • 6.6.4 System and application access control

NIST SP 800-161 Rev 1 · 2 controls

NIST SP 800-171 Rev 3 · 2 controls

NIST SP 800-53 Rev 5 · 2 controls

SOC 2 · 2 controls

  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC6.3 CC6.3 Role-based access, least privilege and segregation of duties

ACSC Essential Eight · 1 control

  • E8-ADMIN-ML3 Restrict Administrative Privileges (ML3)

ASD Strategies to Mitigate Cyber Security Incidents · 1 control

  • ASD37-18 Restrict administrative privileges (Essential)

Australia Consumer Data Right - Banking (CDR) · 1 control

  • AUCDR-IS-1 Limit risk of unauthorised access to the CDR data environment

NIST Cybersecurity Framework 2.0 · 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

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-BP02 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.

If you hold NIST SP 800-53 Rev 582.5% covered · 11 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.174.6% covered · 16 gapsIf you hold ISO 27002:202273% covered · 17 gapsIf you hold FedRAMP Moderate69.8% covered · 19 gapsIf you hold Azure Security Benchmark65.1% covered · 22 gapsIf you hold PCI DSS 4.063.5% covered · 23 gaps

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.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

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

MCP endpointAll AWS Well-Architected Security Pillar controls