STIGViewer Support

164.310(a)(2)(i)

paragraph (action item)

Contingency operations (Addressable). Establish (and implement as needed) procedures that allow facility access in support of restoration of lost data under the disaster recovery plan and emergency mode operations plan in the event of an emergency.

164.310 Physical safeguards.

Related Frameworks

4 mappings across 5 frameworks
SCF4 mappings
BCD-09.2Alternate Processing Site Accessibility
1.00
HRS-03Defined Roles & Responsibilities
1.00
PES-02Physical Access Authorizations
1.00
PES-02.1Role-Based Physical Access
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 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.

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(7)Privileged User Accounts
1.00
AC-22Publicly Accessible Content
1.00
AC-3(11)Restrict Access to Specific Information Types
1.00
AC-6(7)Review of User Privileges
1.00
AT-1Policy and Procedures
1.00
AT-2Literacy Training and Awareness
1.00

+90 more (top 10 by confidence shown)

NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (5) 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.10.1
1.00
3.10.2
1.00
3.10.3
1.00
3.10.4
1.00
3.10.5
1.00
CCI0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (88) 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.

+78 more (top 10 by confidence shown)

STIG0 mappings

No source states a mapping between these directly.

Also reachable in 4 hops (12) 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-259911r948757_ruleThe LAN hardware supporting VVoIP services must provide redundancy to support command and control (C2) assured services and Fire and Emergency Services (FES) communications.
1.00
SV-259912r948758_ruleThe LAN hardware supporting VVoIP services must provide physically diverse pathways for redundant links supporting command and control (C2) assured services and Fire and Emergency Services (FES) communications.
1.00
SV-259913r948759_ruleThe site's enclave boundary protection must route commercial VoIP traffic via a local Media Gateway (MG) connected to a commercial service provider using PRI, CAS, or POTS analog trunks.
1.00
SV-259914r948760_ruleLocal commercial phone service must be provided in support of continuity of operations (COOP) and Fire and Emergency Services (FES) communications.
1.00
SV-259918r948764_ruleCritical network equipment must be redundant and in geographically diverse locations for a site supporting command and control (C2) users.
1.00
SV-259919r948765_ruleEnclaves with commercial VoIP connections must be approved by the DODIN Waiver Panel and signed by DOD CIO for a permanent alternate connection to the Internet Telephony Service Provider (ITSP).
1.00
SV-259920r948766_ruleThe Fire and Emergency Services (FES) communications over a site's telephone system must be configured to support the Department of Defense Instruction (DODI) 6055.06 telecommunication capabilities.
1.00
SV-259921r948767_ruleThe Fire and Emergency Services (F&ES) communications over a site's private telephone system must provide the originating telephone number to the emergency services answering point or call center through a transfer of Automatic Number Identification (ANI) or Automatic Location Identification (ALI) information.
1.00
SV-259922r948768_ruleThe Fire and Emergency Services (F&ES) communications over a site's private telephone system must provide a direct callback telephone number and physical location of an F&ES caller to the emergency services answering point or call center through a transfer of Automatic Number Identification (ANI) and extended Automatic Location Identification (ALI) information or access to an extended ALI database.
1.00
SV-259923r948769_ruleThe Fire and Emergency Services (F&ES) communications over a site's private telephone system must route emergency calls as a priority call in a nonblocking manner.
1.00

+2 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.