STIGViewer Support

164.312(a)(2)(ii)

paragraph (action item)

Emergency access procedure (Required). Establish (and implement as needed) procedures for obtaining necessary electronic protected health information during an emergency.

164.312 Technical safeguards.

Related Frameworks

3 mappings across 5 frameworks
SCF3 mappings
IAC-15Account Management
1.00
IAC-15.2Removal of Temporary / Emergency Accounts
1.00
IAC-15.9Emergency Accounts
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (62) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-1Policy and Procedures
1.00
AC-12Session Termination
1.00
AC-2(12)Account Monitoring for Atypical Usage
1.00
AC-2(2)Automated Temporary and Emergency Account Management
1.00
AC-2(3)Disable Accounts
1.00
AC-2(7)Privileged User Accounts
1.00
AC-2(9)Restrictions on Use of Shared and Group Accounts
1.00
AC-3(11)Restrict Access to Specific Information Types
1.00
AC-6(7)Review of User Privileges
1.00
IA-1Policy and Procedures
1.00

+52 more (top 10 by confidence shown)

NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (2) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

3.1.1
0.50
3.1.2
0.50
CCI0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (44) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

+34 more (top 10 by confidence shown)

STIG0 mappings

No source states a mapping between these directly.

Also reachable in 4 hops (100) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

SV-203592r958364_ruleThe operating system must automatically remove or disable temporary user accounts after 72 hours.
1.00
SV-203652r958508_ruleThe information system must automatically remove or disable emergency accounts after the crisis is resolved or 72 hours.
1.00
SV-204637r960771_ruleAAA Services must be configured to automatically remove temporary user accounts after 72 hours.
1.00
SV-204638r960771_ruleAAA Services must be configured to automatically remove authorizations for temporary user accounts after 72 hours.
1.00
SV-204680r971528_ruleAAA Services must be configured to prevent automatically removing emergency accounts.
1.00
SV-204681r971528_ruleAAA Services must be configured to prevent automatically disabling emergency accounts.
1.00
SV-205445r960771_ruleThe Mainframe Product must automatically remove or disable temporary user accounts after 72 hours.
1.00
SV-205522r971528_ruleThe Mainframe Product must be configured such that emergency accounts are never automatically removed or disabled.
1.00
SV-205624r958364_ruleWindows Server 2019 must automatically remove or disable temporary user accounts after 72 hours.
1.00
SV-205710r958508_ruleWindows Server 2019 must automatically remove or disable emergency accounts after the crisis is resolved or within 72 hours.
1.00

+90 more (top 10 by confidence shown)

Department of Health and Human Services, HIPAA Security and Privacy Rules (45 CFR Part 164). Edition dated 2026-01-01. Read the publication.