NIST SP 800-53 Rev 5
CP - Contingency Planning

NIST SP 800-53 Rev 5 NIST800-CP-1: CP-1 Policy and Procedures

a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]: 1. [Selection (one or more): organization-level; mission/business process-level; system-level] contingency planning policy that: (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and 2. Procedures to facilitate the implementation of the contingency planning policy and the associated contingency planning controls; b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the contingency planning policy and procedures; and c. Review and update the current contingency planning: 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 38 controls across 24 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

ISO 22301:2019 · 4 controls

  • 5.2 Policy
  • 5.2.1 Establishing the business continuity policy
  • 5.2.2 Communicating the business continuity policy
  • 8.4.4 Business continuity plans

C5 (Germany) · 3 controls

  • C5-BCM-01 Top management responsibility
  • C5-BCM-02 Business impact analysis policies and instructions
  • C5-BCM-03 Planning business continuity
  • CPS230-26 Critical Operations Register, Continuity Plan and Activation
  • CPS230-8 Board Oversight, Approval of the BCP, Tolerance Levels and Service Provider Policy

CIS Controls v8 · 2 controls

  • CIS-11.1 Establish and Maintain a Data Recovery Process
  • CIS-11.5 Test Data Recovery

ISO 27001:2022 · 2 controls

  • 5.24 Information security incident management planning and preparation 
  • 5.37 Documented operating procedures

ISO 27002:2022 · 2 controls

  • 5.24 Information security incident management planning and preparation
  • 5.29 Information security during disruption
  • NIST-CSF-GV.PO-01 Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced
  • NIST-CSF-ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved

SOC 2 · 2 controls

  • SOC2-A1.3 A1.3 Testing recovery plan procedures
  • SOC2-CC5.3 CC5.3 Deploying controls through policies and procedures (COSO principle 12)

API 1164 · 1 control

  • API1164-13 Business Continuity and Recovery
  • ASBv3-GS-8 Define and implement backup and recovery strategy
  • CFTC-SS-8 Business Continuity and Disaster Recovery Plan and Resources
  • ITSG33-CP Contingency Planning (CP)
  • CCM-BCR-01 Business Continuity Management Policy and Procedures

DORA · 1 control

  • DORA-Art.12 Backup policies and procedures, restoration and recovery

FedRAMP High · 1 control

  • CP-1 Policy and Procedures

FedRAMP Moderate · 1 control

  • CP-1 Policy and Procedures

HIPAA Security Rule · 1 control

  • CP-1 CP-1 Policy and Procedures
  • CP-1 CP-1 Policy and Procedures
  • CP-1 CP-1 Policy and Procedures

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in CP - Contingency Planning

You are reading one control. How much of NIST SP 800-53 Rev 5 have you already done?

NIST SP 800-53 Rev 5 NIST800-CP-1 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-53 Rev 5 your existing evidence covers. Hold ISO 27001:2022 and 163 of 1014 NIST SP 800-53 Rev 5 controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 342 were rejected on the ISO 27001:2022 pair alone.

Query this from an agent

The graph holds this control, the 38 it maps to, and the evidence behind each claim, over MCP and REST.