Skip to main content
CMDashCybersecurity Maturity Dashboard

164.310(a)(2)(i) Contingency operations (A)

HIPAA Security Rule · 2013

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.

Quoted verbatim from 45 CFR Part 164 (eCFR, as in force 2026-01-01), which is in the public domain.

No cross-framework mapping is seeded for this control. That is stated rather than filled in: a mapping nobody authored is worse than a gap you can see.

These connectors produce data relevant to HIPAA Security Rule’s Physical Safeguards family, which is the granularity CMDash publishes — there is no pre-built per-control mapping, and claiming one would be inventing it. You decide which evidence answers which control.

Track 164.310(a)(2)(i) with evidence behind it

In CMDash this control is a row with an owner, a status, uploaded evidence kept with its full history, and an export an assessor can read.

164.310(a)(2)(i) Contingency operations (A) — HIPAA Security Rule | CMDash