# NIST SP 800-53 Rev. 5 CP-12 — Safe Mode

- Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/cp-12-safe-mode
- Section: [Compliance](https://support.icompaas.com/compliance) › [NIST SP 800-53 Rev. 5 Controls](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5) › CP — Contingency Planning
- Last updated: 2026-06-05
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**NIST SP 800-53 Rev. 5**·Control `CP-12`·high·Component: **Contingency Planning**

## What this control requires

> Systems supporting critical functions enter a predefined safe mode with restrictions when specific conditions are detected, operating under reduced power/bandwidth to ensure resilience. This control supports the System Monitoring Tool capability within the Contingency Planning family.
> 
> — NIST SP 800-53 Rev. 5, Control CP-12

### In plain English

Systems supporting critical functions enter a predefined safe mode with restrictions when specific conditions are detected, operating under reduced power/bandwidth to ensure resilience. In practice, this means you can prove you policy management-level controls on a defined cadence.

## Why it matters

SP 800-53 is the catalogue every U.S. federal authorisation (FedRAMP, FISMA, CMMC) and most regulated industries point at. A missing control surfaces as a Plan of Action & Milestones (POA&M) item that an Authorizing Official must approve before the Authority To Operate is granted or renewed.

This control is rated **high**. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation.

## What an auditor looks for

A 3PAO (FedRAMP) or Independent Assessor (NIST RMF) tests against NIST SP 800-53A assessment procedures. For each control they expect a documented implementation that addresses every assessment objective (Examine, Interview, Test) and an implementation summary in the System Security Plan.

Within **Contingency Planning**, the assessor will trace your implementation back to the catalogue reference (Control CP-12) and look for objective evidence on the latest two assessment cycles.

## How to implement

#### Policy Management

**Docs.** Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA.

### Operational checklist

-   **Policy.** Document the trigger, the owner and the cadence.
-   **Restrictions.** Document the trigger, the owner and the cadence.
-   **Environmental.** Document the trigger, the owner and the cadence.
-   **System.** Document the trigger, the owner and the cadence.
-   **Control.** Document the trigger, the owner and the cadence.
-   **Scope:** management, conditions, system, functions, controls, capability, mode, systems.

## Evidence to collect

-   **Policy Document.** A signed and version-controlled policy / standard / procedure document.

Signed policy or standard documents the safeguard. Focus: Safe Mode.

## Common pitfalls

-   Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced.

## How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

-   [**HIPAA (45 CFR Part 164) 164.312(b)** — Audit Controls](https://support.icompaas.com/compliance/hipaa/164-312-b-audit-controls)

## Related controls in NIST SP 800-53 Rev. 5

-   [**Control CP-7(4)** — Preparation For Use](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/cp-7-4-preparation-for-use)
-   [**Control CP-7** — Alternate Processing Site](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/cp-7-alternate-processing-site)
-   [**Control PE-14(1)** — Automatic Controls](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pe-14-1-automatic-controls)
-   [**Control CP-2(2)** — Capacity Planning](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/cp-2-2-capacity-planning)
-   [**Control CP-10(2)** — Transaction Recovery](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/cp-10-2-transaction-recovery)
-   [**Control PE-9(1)** — Redundant Cabling](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pe-9-1-redundant-cabling)

## References

-   [NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5](https://csrc.nist.gov/Projects/risk-management/sp800-53-controls)
-   Catalogue identifier: `Control CP-12`

Topics: governance riskenvironmental controlspolicy management

## Related compliance guidance

- [NIST SP 800-53 Rev. 5: a practical implementation guide for cloud teams](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5): Start with the full NIST SP 800-53 implementation guide — scope, roadmap, evidence and how the assessment runs.
- [NIST SP 800-171 and CMMC: a practical guide to protecting CUI in the cloud](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3): If your obligation is protecting CUI in your own systems for a federal or defence contract, this derived subset — not the full catalogue — is the requirement.
- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Most commercial SaaS already hold a SOC 2 Type 2, and FedRAMP 20x Class A is designed for providers that have one.