← CP-4
CP-4(5) CP · Contingency Planning

Self-challenge

LOW MODERATE HIGH
1 Overlay 0 Related Controls
Graph
Export ▾

Requirements NIST SOURCE

Employ [mechanisms] to [system or system component] to disrupt and adversely affect the system or system component.

Discussion (NIST Supplemental Guidance)

Often, the best method of assessing system resilience is to disrupt the system in some manner. The mechanisms used by the organization could disrupt system functions or system services in many ways, including terminating or disabling critical system components, changing the configuration of system components, degrading critical functionality (e.g., restricting network bandwidth), or altering privileges. Automated, on-going, and simulated cyber-attacks and service disruptions can reveal unexpected functional dependencies and help the organization determine its ability to ensure resilience in the face of an actual cyber-attack.

Implementation Guidance

Engineering Interpretation

Original engineering commentary written for this explorer — not NIST source text and not authoritative guidance.

No engineering interpretation has been authored for CP-4(5) yet. This section is architected to receive it — see the Requirements and Assessment sections above for the authoritative NIST source content in the meantime.

Assessment

NIST SP 800-53A REV 5.2.0

Assessment Objectives

  1. mechanisms employed to disrupt and adversely affect the system or system component are defined;
  2. system or system component on which to apply disruption mechanisms are defined;
  3. <CP-04(05)_ODP[01] mechanisms> are employed to disrupt and adversely affect the <CP-04(05)_ODP[02] system or system component>.

Examine

[SELECT FROM: Contingency planning policy; procedures addressing system recovery and reconstitution; contingency plan; contingency plan test documentation; contingency plan test results; system security plan; other relevant documents or records].

Interview

[SELECT FROM: Organizational personnel with contingency plan testing responsibilities; organizational personnel with system recovery and reconstitution responsibilities; organizational personnel with information security responsibilities].

Test

[SELECT FROM: Organizational processes for contingency plan testing; mechanisms supporting contingency plan testing].

Overlays

Showing the OT/ICS overlay for the parent control CP-4 — see the CP-4(5) entries within each baseline below.

OT/ICS Overlay SP 800-82r3

NIST SP 800-82r3 Appendix F, Table 22. Blank baseline means the control/control enhancement is not selected in that initial OT baseline.

LOW

  • Base control: Included (matches standard baseline)

MODERATE

  • Base control: Included (matches standard baseline)
  • Included: (1)

HIGH

  • Base control: Included (matches standard baseline)
  • Included: (1) (2)

STIGs & CCIs

No STIG checks or CCI mappings are currently loaded for CP-4(5). This section is architected to display, per product: STIG ID, Finding ID, Severity, Title, Description, Check, Fix, CCI, and NIST control mapping — but nothing is populated here until a real DISA STIG/CCI dataset is ingested.

Learn more about STIG/CCI integration →

Evidence

Potential Evidence — Derived

Categorized from the SP 800-53A "Examine"/"Test" artifact list above by keyword — not an authoritative NIST evidence list.

Policy

  • Contingency planning policy
  • contingency plan
  • contingency plan test documentation
  • contingency plan test results
  • system security plan

Testing

  • Organizational processes for contingency plan testing
  • mechanisms supporting contingency plan testing

Other Records

  • procedures addressing system recovery and reconstitution
  • other relevant documents or records