NIST SP 800-161 Rev 1
C-SCRM Family: Contingency Planning

NIST SP 800-161 Rev 1 161R1-CP-2: Contingency Plan

Plans for continued operation when a critical supplier, integrator or component source becomes unavailable.

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

What else in your programme already covers this

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

  • CFTC-SS-11 Testing and Review of Business Continuity and Disaster Recovery Capabilities
  • CFTC-SS-22 Business Continuity and Disaster Recovery Planning Category
  • CFTC-SS-23 Resources Sufficient to Fulfil Obligations
  • CFTC-SS-24 Periodic Update of the Recovery Plan and Emergency Procedures
  • CFTC-SS-25 Same Day Recovery Time Objective for Critical Entities
  • CFTC-SS-27 Coordination of the Recovery Plan with Members and Market Participants
  • CFTC-SS-29 Recovery Plan Accounts for Essential Service Providers
  • CFTC-SS-37 Protection of Swap Data Repository Data
  • CFTC-SS-8 Business Continuity and Disaster Recovery Plan and Resources
  • CFTC-SS-9 Next Business Day Recovery Time Objective

ISO 22301:2019 · 4 controls

  • 8.1 Operational planning and control
  • 8.3 Business continuity strategies and solutions
  • 8.4.4 Business continuity plans
  • 8.4.5 Recovery
  • CPS230-26 Critical Operations Register, Continuity Plan and Activation
  • CPS230-P40 Required Content of the Business Continuity Plan
  • CPS230-P45 Annual Update of the Business Continuity Plan

HIPAA Security Rule · 3 controls

  • NIST-CSF-ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved
  • NIST-CSF-PR.IR-03 Mechanisms are implemented to achieve resilience requirements in normal and adverse situations
  • NIST-CSF-RC.RP-04 Critical mission functions and cybersecurity risk management are considered to establish post-incident operational norms

NIST SP 800-66 Rev 2 · 3 controls

  • ASBv3-GS-8 Define and implement backup and recovery strategy
  • BR-1 Ensure regular automated backups

C5 (Germany) · 2 controls

DORA · 2 controls

ISO 27001:2022 · 2 controls

  • 5.29 Information security during disruption
  • 5.30 ICT readiness for business continuity

ISO 27002:2022 · 2 controls

  • 5.29 Information security during disruption
  • 5.30 ICT readiness for business continuity

SOC 2 · 2 controls

  • SOC2-CC7.5 CC7.5 Recovering from security incidents
  • SOC2-CC9.1 CC9.1 Mitigating risks of business disruption
  • E8-BACKUP-ML1 Regular Backups (ML1)
  • ANSSI-HYG-37 Define and Apply a Backup Policy for Critical Components

APRA CPS 234 · 1 control

  • CPS234-P24 Information Security Response Plans
  • ASD37-35 Business continuity and disaster recovery plans (Very Good)

CIS Controls v8 · 1 control

  • CIS-11.1 Establish and Maintain a Data Recovery Process

FedRAMP High · 1 control

  • CP-2 Contingency Plan

FedRAMP Moderate · 1 control

  • CP-2 Contingency Plan

ISO 27701:2019 · 1 control

  • 6.14.1 Information security continuity

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 C-SCRM Family: Contingency Planning

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

NIST SP 800-161 Rev 1 161R1-CP-2 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-161 Rev 1 your existing evidence covers. Hold C5 (Germany) and 94 of 191 NIST SP 800-161 Rev 1 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. 0 were rejected on the C5 (Germany) pair alone.

Query this from an agent

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