PR.IP-9 Response and recovery plans in place

NIST Cybersecurity Framework (1.1, legacy) · 1.1

What the standard requires

Response plans (Incident Response and Business Continuity) and recovery plans (Incident Recovery and Disaster Recovery) are in place and managed

Quoted verbatim from NIST Cybersecurity Framework (CSF) 1.1, which is in the public domain.

Maps to 8 controls in 8 other frameworks

Framework	Control
DORA	Art.11(2) Business continuity policy
FedRAMP Moderate	CP-2 Contingency plan
HIPAA Security Rule	164.308(a)(7)(i) Contingency plan
HITRUST CSF v11	12.a.01 Business continuity program integrates information security requirements
ISO/IEC 27001:2022	A.5.29 Information security during disruption
NIST Cybersecurity Framework 2.0	ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved
SOC 2 Type II	A1.2 Recovery planning and testing
TISAX (VDA ISA v6)	3.4.1 Business continuity management is established

Mappings are CMDash’s own, seeded with the product and shown on both frameworks they connect. In the product they mean evidence you attach here also counts against the controls listed above.

Integrations that carry evidence for this family

Okta

MFA & identity coverage

These connectors produce data relevant to NIST Cybersecurity Framework (1.1, legacy)’s Protect (PR) 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 PR.IP-9 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.

Start free trial All NIST Cybersecurity Framework (1.1, legacy) controls