| name | CP-10_system-recovery-and-reconstitution |
| description | Provide for the recovery and reconstitution of the system to a known state within [organization-defined] after a disruption, compromise, or failure. |
| category | configuration |
| version | 5.2.0 |
| author | cyberstrike-official |
| tags | ["nist","sp800-53","rev5","cp-10","cp"] |
| tech_stack | ["aws","azure","gcp"] |
| cwe_ids | [] |
| chains_with | ["CP-2","CP-4","CP-6","CP-7","CP-9","IR-4","SA-8","SC-24","SI-13"] |
| prerequisites | [] |
| severity_boost | {"CP-2":"Chain with CP-2 for comprehensive security coverage","CP-4":"Chain with CP-4 for comprehensive security coverage","CP-6":"Chain with CP-6 for comprehensive security coverage"} |
CP-10 System Recovery and Reconstitution
High-Level Description
Family: Contingency Planning (CP)
Framework: NIST SP 800-53 Rev 5
Recovery is executing contingency plan activities to restore organizational mission and business functions. Reconstitution takes place following recovery and includes activities for returning systems to fully operational states. Recovery and reconstitution operations reflect mission and business priorities; recovery point, recovery time, and reconstitution objectives; and organizational metrics consistent with contingency plan requirements. Reconstitution includes the deactivation of interim system capabilities that may have been needed during recovery operations. Reconstitution also includes assessments of fully restored system capabilities, reestablishment of continuous monitoring activities, system reauthorization (if required), and activities to prepare the system and organization for future disruptions, breaches, compromises, or failures. Recovery and reconstitution capabilities can include automated mechanisms and manual procedures. Organizations establish recovery time and recovery point objectives as part of contingency planning.
What to Check
How to Test
Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for CP-10 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 | Documentation and interview-based | N/A |
Remediation Guide
Control Statement
Provide for the recovery and reconstitution of the system to a known state within [organization-defined] after a disruption, compromise, or failure.
