AWS Well-Architected Security Pillar SEC03-BP01: Define access requirements

What else in your programme already covers this

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

FedRAMP High · 3 controls

AC-2 Account Management
AC-6 Least Privilege
AC-6(1) Authorize Access to Security Functions

FedRAMP Moderate · 3 controls

AC-2 Account Management
AC-6 Least Privilege
AC-6(1) Authorize Access to Security Functions

NIST SP 800-53 Rev 5 · 3 controls

NIST800-AC-1 AC-1 Policy and Procedures
NIST800-AC-3 AC-3 Access Enforcement
NIST800-AC-6 AC-6 Least Privilege

C5 (Germany) · 2 controls

C5-IDM-01 Policy for user accounts and access rights
C5-PSS-08 Roles and Rights Concept

CIS Controls v8 · 2 controls

CIS-6.1 Establish an Access Granting Process
CIS-6.8 Define and Maintain Role-Based Access Control

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

CCM-IAM-01 Identity and Access Management Policy and Procedures
CCM-IAM-05 Least Privilege

HIPAA Security Rule · 2 controls

164.308(a)(3)(ii)(A) Authorization and Supervision (Addressable)
164.308(a)(4)(i) Information Access Management (Standard)

ISO 27001:2022 · 2 controls

5.15 Access control
8.3 Information access restriction

NIST SP 800-161 Rev 1 · 2 controls

161R1-AC-3 Access Enforcement
161R1-AC-6 Least Privilege

NIST SP 800-171 Rev 3 · 2 controls

03.01.01 Account Management
03.01.02 Access Enforcement

NIST SP 800-66 Rev 2 · 2 controls

164.308(a)(3)(ii)(A) Authorization and Supervision (Addressable)
164.308(a)(4)(i) Information Access Management (Standard)

PCI DSS 4.0 · 2 controls

7.2.1 7.2.1 Access control model defined
7.2.2 7.2.2 User access assigned by job function and least privilege

SOC 2 · 2 controls

SOC2-CC6.2 CC6.2 Registering and authorising users before issuing credentials
SOC2-CC6.3 CC6.3 Role-based access, least privilege and segregation of duties

ACSC Essential Eight · 1 control

E8-ADMIN-ML1 Restrict Administrative Privileges (ML1)

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

ANSSI-HYG-09 Assign the Correct Rights on Sensitive Resources

Azure Security Benchmark · 1 control

ASBv3-GS-6 Define and implement identity and privileged access strategy

CMMC 2.0 · 1 control

AC.L2-3.1.1 Authorized Access Control

ISO 27701:2019 · 1 control

6.6.1 Business requirements of access control

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

UK Cyber Essentials · 1 control

CE-AC.1 User Account Approval Process

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.

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

AWS Well-Architected Security Pillar SEC03-BP01 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 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.174.6% covered · 16 gaps If you hold ISO 27002:202273% covered · 17 gaps If you hold FedRAMP Moderate69.8% covered · 19 gaps If you hold Azure Security Benchmark65.1% covered · 22 gaps If 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 each Browse the graph free