| name | CP-12_safe-mode |
| description | When [organization-defined] are detected, enter a safe mode of operation with [organization-defined]. |
| category | configuration |
| version | 5.2.0 |
| author | cyberstrike-official |
| tags | ["nist","sp800-53","rev5","cp-12","cp"] |
| tech_stack | ["aws","azure","gcp"] |
| cwe_ids | [] |
| chains_with | ["CM-2","SA-8","SC-24","SI-13","SI-17"] |
| prerequisites | [] |
| severity_boost | {"CM-2":"Chain with CM-2 for comprehensive security coverage","SA-8":"Chain with SA-8 for comprehensive security coverage","SC-24":"Chain with SC-24 for comprehensive security coverage"} |
CP-12 Safe Mode
High-Level Description
Family: Contingency Planning (CP)
Framework: NIST SP 800-53 Rev 5
For systems that support critical mission and business functions—including military operations, civilian space operations, nuclear power plant operations, and air traffic control operations (especially real-time operational environments)—organizations can identify certain conditions under which those systems revert to a predefined safe mode of operation. The safe mode of operation, which can be activated either automatically or manually, restricts the operations that systems can execute when those conditions are encountered. Restriction includes allowing only selected functions to execute that can be carried out under limited power or with reduced communications bandwidth.
What to Check
How to Test
Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for CP-12 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
When [organization-defined] are detected, enter a safe mode of operation with [organization-defined].
Implementation Guidance
For systems that support critical mission and business functions—including military operations, civilian space operations, nuclear power plant operations, and air traffic control operations (especially real-time operational environments)—organizations can identify certain conditions under which those systems revert to a predefined safe mode of operation. The safe mode of operation, which can be activated either automatically or manually, restricts the operations that systems can execute when those conditions are encountered. Restriction includes allowing only selected functions to execute that can be carried out under limited power or with reduced communications bandwidth.