164.308(a)(7)(i) Contingency Plan (Standard)
164.308(a)(7)(i) in HIPAA Security Rule (the HIPAA Security Rule as it currently stands). All HIPAA Security Rule controls held. Open HIPAA Security Rule on the standards site.
The control as we hold it
Contingency Plan (Standard). Establish policies for responding to emergencies that damage ePHI systems. NIST recommends contingency planning per SP 800-34 with business impact analysis driving recovery priorities.
Reviewed and closest counterparts in the other frameworks
Reviewed rows come from a released pair; a closest match is the nearest held text and is not a reviewed row.
SOC 2
- SOC2-A1.3 A1.3 Testing recovery plan procedures (closest match)
- SOC2-CC3.4 CC3.4 Identifying and assessing significant changes (COSO principle 9) (closest match)
- SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11) (closest match)
- SOC2-CC9.1 CC9.1 Mitigating risks of business disruption (closest match)
NIST SP 800-53 Rev 5
- NIST800-CP-1 CP-1 Policy and Procedures (closest match)
- NIST800-CP-2 CP-2 Contingency Plan (closest match)
- NIST800-PE-23 PE-23 Facility Location (closest match)
- NIST800-SA-8 SA-8 Security and Privacy Engineering Principles (closest match)
- NIST800-SA-17 SA-17 Developer Security and Privacy Architecture and Design (closest match)
What an auditor commonly asks for
General guidance for this control area (domain: Administrative), in our words, not a statement of the standard and not binding on an assessor.
- the risk analysis and risk-management records
- the workforce clearance, training and sanction records
- the access-authorisation and termination records
- the contingency-plan test and evaluation records