# NIST SP 800-53 Rev. 5 CP-3 — Contingency Training

- Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/cp-3-contingency-training
- 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-3`·high·Component: **Contingency Planning**

## What this control requires

> Provide role-based contingency training to users within a specified period, during system changes, and regularly. Update training content periodically or post-incident. This control supports the Training capability within the Contingency Planning family.
> 
> — NIST SP 800-53 Rev. 5, Control CP-3

### In plain English

Provide role-based contingency training to users within a specified period, during system changes, and regularly. In practice, this means you can prove you security 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-3) and look for objective evidence on the latest two assessment cycles.

## How to implement

#### Incident Response

**Runbook.** Maintain a runbook keyed by incident type with named roles (IC, comms, scribe), an out-of-band comms channel, and a 72-hour timeline for external notification.

**Tabletop.** Run a quarterly tabletop exercise (ransomware, insider, supply-chain) and feed gaps back into the runbook.

### Operational checklist

-   **Security.** Document the trigger, the owner and the cadence.
-   **Content.** Document the trigger, the owner and the cadence.
-   **Response.** Document the trigger, the owner and the cadence.
-   **Changes.** Document the trigger, the owner and the cadence.
-   **System.** Document the trigger, the owner and the cadence.
-   **Scope:** management, system, system changes, capability, content, response, security.

## Evidence to collect

-   **Ticketing Workflow.** `ticketing_workflow` evidence

Workflow metrics (ServiceNow, Jira) show approvals and remediation. Focus: Contingency Training.

## Common pitfalls

-   Runbooks that name a role but no person, or list a paging channel that no longer exists.

## 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.

-   [**NIST SP 800-171 Rev. 3 3.6.4** — Incident Response Training](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-6-4-incident-response-training)
-   [**BSI C5:2020 HR-03** — Security training and awareness programme](https://support.icompaas.com/compliance/bsi-c5-2020/hr-03-security-training-and-awareness-programme)
-   [**SOC 2 (2017 TSC) CC7.4** — Incident Response](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc7-4-incident-response)
-   [**ISO/IEC 27001:2022 A.5.27** — Learning from information security incidents](https://support.icompaas.com/compliance/iso-27001-2022/a-5-27-learning-from-information-security-incidents)

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

-   [**Control IR-2** — Incident Response Training](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ir-2-incident-response-training)
-   [**Control IR-2(2)** — Automated Training Environments](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ir-2-2-automated-training-environments)
-   [**Control AT-2** — Literacy Training And Awareness](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/at-2-literacy-training-and-awareness)
-   [**Control IR-2(1)** — Simulated Events](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ir-2-1-simulated-events)
-   [**Control SA-15(10)** — Incident Response Plan](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-15-10-incident-response-plan)
-   [**Control AT-2(1)** — Practical Exercises](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/at-2-1-practical-exercises)

## 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-3`

Topics: incident responseawareness trainingchange managementpatch managementsecurity training

## 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.
