AWS Well-Architected Security Pillar SEC03-BP03: Establish emergency access process

What else in your programme already covers this

This control maps to 22 controls across 16 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-53 Rev 5 · 3 controls

NIST800-AC-2 AC-2 Account Management
NIST800-AC-6 AC-6 Least Privilege
NIST800-IA-2 IA-2 Identification and Authentication (Organizational Users)

Azure Security Benchmark · 2 controls

ASBv3-PA-5 Set up emergency access
PA-1 Separate and limit highly privileged/administrative users

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

CCM-IAM-10 Management of Privileged Access Roles
CCM-IAM-12 Safeguard Logs Integrity

ISO 27002:2022 · 2 controls

5.18 Access rights
8.2 Privileged access rights

NIST SP 800-171 Rev 3 · 2 controls

03.01.06 Least Privilege - Privileged Accounts
03.01.12 Remote Access

ACSC Essential Eight · 1 control

E8-ADMIN-ML2 Restrict Administrative Privileges (ML2)

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

ANSSI-HYG-08 Identify Each Person by Name and Separate User and Administrator Roles

CIS Controls v8 · 1 control

CIS-6.5 Require MFA for Administrative Access

CMMC 2.0 · 1 control

AC.L2-3.1.15 Privileged Remote Access

FedRAMP High · 1 control

AC-2(2) Automated Temporary and Emergency Account Management

FedRAMP Moderate · 1 control

AC-2(2) Automated Temporary and Emergency Account Management

HIPAA Security Rule · 1 control

164.312(a)(2)(ii) Emergency Access Procedure (Required)

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

NIST SP 800-66 Rev 2 · 1 control

164.312(a)(2)(ii) Emergency Access Procedure (Required)

PCI DSS 4.0 · 1 control

8.2.2 8.2.2 Shared and generic IDs only by exception

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-BP03 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