cp-2-8-identify-critical-assets

name	CP-2(8)_identify-critical-assets
description	Identify critical system assets supporting [organization-defined] mission and business functions.
category	configuration
version	5.2.0
author	cyberstrike-official
tags	["nist","sp800-53","rev5","cp-2-8","cp","enhancement"]
tech_stack	["aws","azure","gcp"]
cwe_ids	[]
chains_with	["CM-8","RA-9"]
prerequisites	["CP-2"]
severity_boost	{"CM-8":"Chain with CM-8 for comprehensive security coverage","RA-9":"Chain with RA-9 for comprehensive security coverage"}

CP-2(8) Identify Critical Assets

Enhancement of: CP-2

High-Level Description

Family: Contingency Planning (CP) Framework: NIST SP 800-53 Rev 5

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.

What to Check

• Verify CP-2(8) Identify Critical Assets is documented in SSP
• Confirm control is operating effectively
• Review evidence of continuous monitoring for CP-2(8)
• Verify enhancement builds upon base control CP-2

How to Test

Step 1: Review Documentation

Examine the System Security Plan (SSP) and related artifacts for CP-2(8) implementation details. Verify the organization has documented how this control is satisfied.

Step 2: Validate Implementation

# For cloud environments, use cloud-audit-mcp tools
# For on-premises, review system configurations directly

# Example: Check if account management policies exist
grep -r "account.management\|access.control" /etc/security/ 2>/dev/null

Step 3: Test Operating Effectiveness

Verify the control is actively functioning, not just documented. Check logs, configurations, and operational evidence.

Tools

Tool	Purpose	Usage
Manual Review