HIPAA Security Rule 164.312(a)(2)(ii): Emergency Access Procedure (Required)

What else in your programme already covers this

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

SOC 2 · 6 controls

SOC2-A1.3 A1.3 Testing recovery plan procedures
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
SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
SOC2-CC7.4 CC7.4 Responding to security incidents
SOC2-CC9.1 CC9.1 Mitigating risks of business disruption

NIST SP 800-53 Rev 5 · 4 controls

NIST800-AC-6 AC-6 Least Privilege
NIST800-AU-12 AU-12 Audit Record Generation
NIST800-CP-13 CP-13 Alternative Security Mechanisms
NIST800-CP-2 CP-2 Contingency Plan

ISO 27001:2022 · 3 controls

5.29 Information security during disruption
8.15 Logging
8.2 Privileged access rights

ISO 27002:2022 · 3 controls

5.29 Information security during disruption
8.15 Logging
8.2 Privileged access rights

AWS Well-Architected Security Pillar · 2 controls

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

ISO 27701:2019 · 2 controls

6.14.1 Information security continuity
6.9.4 Logging and monitoring

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

Azure Security Benchmark · 1 control

ASBv3-PA-5 Set up emergency 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

NIST Cybersecurity Framework 2.0 · 1 control

NIST-CSF-PR.IR-03 Mechanisms are implemented to achieve resilience requirements in normal and adverse situations

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 HIPAA Security Rule have you already done?

HIPAA Security Rule 164.312(a)(2)(ii) is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of HIPAA Security Rule your existing evidence covers. Hold ISO 27001:2022 and 53 of 67 HIPAA Security Rule controls already carry evidence.

If you hold ISO 27001:202279.1% covered · 14 gaps If you hold ISO 27002:202279.1% covered · 14 gaps If you hold FedRAMP Moderate77.6% covered · 15 gaps If you hold NIST SP 800-53 Rev 577.6% covered · 15 gaps If you hold C5 (Germany)76.1% covered · 16 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.167.2% covered · 22 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. 64 were rejected on the ISO 27001:2022 pair alone.

See the released pairs, $299 each Browse the graph free