NIST SP 800-53 Rev 5
CP - Contingency Planning

NIST SP 800-53 Rev 5 CP-1: Policy and procedures for contingency planning

Requires a contingency planning policy and supporting procedures to be developed, approved, disseminated to defined personnel, owned by a named official, and reviewed and updated on a defined frequency and after defined events.

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

APRA CPS 230 Operational Risk Management · 2 controls

  • 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 Cybersecurity Framework 2.0 · 2 controls

  • 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 Recovery plan procedures support system recovery from failures
  • SOC2-CC5.3 COSO principle 12: Deploys control activities through policies and procedures

API 1164 · 1 control

Annex 11 to EU GMP - Computerised Systems · 1 control

Azure Security Benchmark · 1 control

  • ASBv3-GS-8 Define and implement backup and recovery strategy

CCSDS 350.0-G-3 - Space Communications Security (Consultative Committee for Space Data Systems) · 1 control

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

  • CFTC-SS-8 Business Continuity and Disaster Recovery Plan and Resources

Canada ITSG-33 - IT Security Risk Management · 1 control

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

  • 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

NIST SP 800-161 Rev 1 · 1 control

NIST SP 800-53 Rev 5 LOW · 1 control

  • CP-1 Policy and Procedures

NIST SP 800-53 Rev 5 MODERATE · 1 control

  • CP-1 Policy and Procedures

NIST SP 800-53 Revision 5.1 HIGH · 1 control

  • CP-1 Policy and Procedures

NIST SP 800-66 Rev 2 · 1 control

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 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 300 NIST SP 800-53 Rev 5 controls already carry evidence.

If you hold ISO 27001:202254.3% covered · 137 gapsIf you hold ISO 27002:202236.7% covered · 190 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.134.3% covered · 197 gapsIf you hold CIS Controls v834% covered · 198 gapsIf you hold NIST SP 800-171 Rev 334% covered · 198 gapsIf you hold C5 (Germany)32.3% covered · 203 gaps

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.

See the released pairs, $299 eachBrowse the graph free

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.

MCP endpointAll NIST SP 800-53 Rev 5 controls