← CP-2
CP-2(8) CP · Contingency Planning

Identify Critical Assets

LOW ✓ MODERATE ✓ HIGH
1 Overlay 2 Related Controls
Graph
Export ▾

Requirements NIST SOURCE

Identify critical system assets supporting [one of: all; essential] mission and business functions.

Discussion (NIST Supplemental Guidance)

Organizations may choose to identify critical assets as part of criticality analysis, business continuity planning, or business impact analyses. Organizations identify critical system assets so that additional controls can be employed (beyond the controls routinely implemented) to help ensure that organizational mission and business functions can continue to be conducted during contingency operations. The identification of critical information assets also facilitates the prioritization of organizational resources. Critical system assets include technical and operational aspects. Technical aspects include system components, information technology services, information technology products, and mechanisms. Operational aspects include procedures (i.e., manually executed operations) and personnel (i.e., individuals operating technical controls and/or executing manual procedures). Organizational program protection plans can assist in identifying critical assets. If critical assets are resident within or supported by external service providers, organizations consider implementing CP-2(7) as a control enhancement.

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-2(8) 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. one of the following PARAMETER VALUES is selected: {all; essential};
  2. critical system assets supporting <CP-02(08)_ODP SELECTED PARAMETER VALUE> mission and business functions are identified.

Examine

[SELECT FROM: Contingency planning policy; procedures addressing contingency operations for the system; contingency plan; business impact assessment; system security plan; other relevant documents or records].

Interview

[SELECT FROM: Organizational personnel with contingency planning and plan implementation responsibilities; organizational personnel with knowledge of requirements for mission and business functions; organizational personnel with information security responsibilities].

Overlays

Showing the OT/ICS overlay for the parent control CP-2 — see the CP-2(8) 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) (3) (8)

HIGH

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

STIGs & CCIs

No STIG checks or CCI mappings are currently loaded for CP-2(8). 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
  • system security plan

Other Records

  • procedures addressing contingency operations for the system
  • business impact assessment
  • other relevant documents or records