Home NIST Guidelines CP-10(2)
CP-10(2) Contingency Planning

Transaction Recovery

High Risk Moderate Medium Cost

CP-10(2) (Transaction Recovery) enhances base CP-10 within the NIST Contingency Planning family. Base CP-10 sets the foundational expectation; this enhancement adds specificity: Implement transaction recovery for systems that are transaction-based. Transaction-based systems include database management systems and transaction processing systems. Mechanisms supporting transaction recovery include transaction rollback and transaction journaling. Covered entities and business associates apply it to downtime procedures, backup/restore, and alternate processing that keep clinical operations and ePHI available.

Control Objective

Implement Transaction Recovery so organization-defined contingency planning safeguards operate consistently on systems and networks that handle ePHI, with measurable evidence for HIPAA and NIST assessments.

Implementation Guidance

  1. Map CP-10(2) to systems in scope (EHR, imaging, lab, pharmacy, billing, identity, backups, and BA connections).\n2. Translate “Transaction Recovery” into technical settings, procedures, or architecture patterns owned by named roles.\n3. Prefer enforceable controls (config, automation, mediation) over awareness-only measures where feasible.\n4. Integrate with change, incident, and downtime processes so clinical operations are not surprised.\n5. Log and retain evidence of operation (tickets, configs, test results) aligned to audit needs.\n6. Include vendors/BAs in contracts and connection standards when they touch the control surface.\n7. Test after major EHR, network, or cloud changes — upgrades often reset protections.\n8. Review exceptions at least quarterly; expire “temporary” holes that expose ePHI paths.

Real-World Use Cases

How this control shows up in healthcare and HIPAA-covered environments.

Real-world scenario

Clinical ops apply “Transaction Recovery” (CP-10(2))\nHospital implements Transaction Recovery so ePHI systems stay within approved downtime procedures, backup/restore, and alternate processing that keep clinical operations and ePHI available. Evidence labeled for CP-10(2).\n\n### BA / vendor touchpoint (CP-10(2))\nContracted support must follow Transaction Recovery when connecting to systems that store or process ePHI. Evidence labeled for CP-10(2).\n\n### Audit sample (CP-10(2))\nInternal audit samples evidence that Transaction Recovery operates in production — not only in a policy binder. Evidence labeled for CP-10(2).

Best Practices

  • Name an owner for CP-10(2) in the SSP control matrix.\n- Favor system enforcement on ePHI paths over informal email approval.\n- Measure coverage: percent of in-scope clinical systems where the enhancement operates.\n- Review exceptions quarterly with security and clinical informatics.\n- Feed relevant events to SIEM with a named use case.\n- Keep a one-page evidence pack (config + sample log + last test) ready for assessors.

Common Gaps & Violations

  • Policy cites CP-10(2) but production EHR/network paths show no enforcement of transaction recovery.\n- Permanent exceptions with no expiry for vendors or “special” clinics.\n- Control implemented only on corporate IT — clinical devices and interfaces omitted.\n- No logs or test records; reliance on tribal knowledge.\n- Major upgrade silently disabled the enhancement.

Required Documentation

  • Procedure/standard for Transaction Recovery (CP-10(2))\n- Architecture or configuration baselines showing enforcement points\n- Exception register with owners and expiry\n- Sample logs, alerts, or test results\n- Training or runbook references for clinical/IT operators

How to Test & Validate

  1. Attempt a prohibited or out-of-policy action related to transaction recovery; confirm block, alert, or required workflow.\n2. Complete an authorized clinical/IT path; confirm success and logging.\n3. Sample open exceptions for approval and expiry.\n4. Verify at least one EHR-adjacent and one BA/vendor path are in scope.\n5. Confirm evidence retained for the last 90 days (or per policy).

Audit Considerations

Assessors look for operating evidence of Transaction Recovery on systems touching ePHI — configs, logs, restore/DR artifacts, or failed-test results — not only a policy paragraph referencing CP-10(2).

HIPAA Mapping

How this NIST control supports HIPAA Security Rule expectations.

  • 164.308(a)(7) Contingency Plan — data backup, disaster recovery, and emergency-mode operations for ePHI.\n- 164.308(a)(7)(ii)(A) Data Backup Plan — retrievable exact copies of ePHI.\n- 164.308(a)(7)(ii)(B) Disaster Recovery Plan — restore lost data after disruption.\n- 164.312(a)(2)(ii) Emergency Access Procedure — continue critical access during contingency.

Compliance Tips

  • List CP-10(2) explicitly in the system security plan with system inventory references.\n- Prioritize emergency department, inpatient EHR, and remote access paths first.\n- Bundle evidence with related HIPAA contingency or transmission-security narratives where they overlap.

References & Resources

  • NIST SP 800-53 Rev. 5 — CP-10(2)\n- Related controls: CP-10

Related Guidelines

Related controls that commonly accompany CP-10(2).

CP-10 High

Information System Recovery and Reconstitution

CP-10 requires providing for recovery and reconstitution of the system to a known state after a disruption, compromise, or failure…
CP-1 Critical

Contingency Planning Policy and Procedures

CP-1 requires contingency planning policy and procedures addressing purpose, scope, roles, management commitment, coordination, and…
CP-11 High

Alternate Communications Protocols

CP-11 requires providing the capability to employ alternative communications protocols in support of maintaining continuity of operations…

Need Help Implementing CP-10(2)?

Our auditors map NIST SP 800-53 controls to your HIPAA Security Rule program — policies, technical evidence, and audit readiness.

Contact Our Experts View All Guidelines