Azure Security Benchmark ASBv3-PA-5: Set up emergency access

What else in your programme already covers this

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

ISO 27002:2022 · 3 controls

5.16 Identity management
5.18 Access rights
5.29 Information security during disruption

AWS Well-Architected Security Pillar · 2 controls

SEC03-BP03 Establish emergency access process
SEC10-BP05 Pre-provision access

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

FedRAMP High · 2 controls

AC-2(2) Automated Temporary and Emergency Account Management
AC-2(9) Restrictions on Use of Shared and Group Accounts

FedRAMP Moderate · 2 controls

AC-2(2) Automated Temporary and Emergency Account Management
AC-2(9) Restrictions on Use of Shared and Group Accounts

HIPAA Security Rule · 2 controls

164.308(a)(7)(ii)(C) Emergency Mode Operation Plan (Required)
164.312(a)(2)(ii) Emergency Access Procedure (Required)

ISO 27001:2022 · 2 controls

5.29 Information security during disruption
8.2 Privileged access rights

NIST Cybersecurity Framework 2.0 · 2 controls

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-CSF-PR.IR-03 Mechanisms are implemented to achieve resilience requirements in normal and adverse situations

NIST SP 800-53 Rev 5 · 2 controls

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

NIST SP 800-66 Rev 2 · 2 controls

164.308(a)(7)(ii)(C) Emergency Mode Operation Plan (Required)
164.312(a)(2)(ii) Emergency Access Procedure (Required)

ACSC Essential Eight · 1 control

E8-ADMIN-ML2 Restrict Administrative Privileges (ML2)

Australia My Health Records Act 2012 · 1 control

MYHR-SEC-6 Emergency access controls

NIST SP 800-171 Rev 3 · 1 control

03.01.01 Account Management

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 Azure Security Benchmark have you already done?

Azure Security Benchmark ASBv3-PA-5 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of Azure Security Benchmark your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 71 of 85 Azure Security Benchmark controls already carry evidence.

If you hold NIST SP 800-53 Rev 583.5% covered · 14 gaps If you hold FedRAMP Moderate78.8% covered · 18 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.172.9% covered · 23 gaps If you hold ISO 27002:202269.4% covered · 26 gaps If you hold C5 (Germany)65.9% covered · 29 gaps If you hold ISO 27001:202261.2% covered · 33 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