NIST SP 800-53 Rev. 5 CP-2(2) — Capacity Planning

What this control requires

Conduct capacity planning to ensure adequate resources for processing, telecom, and environmental support during contingency operations, based on risk assessments and system impact levels. This control supports the Capacity capability within the Contingency Planning family.

In plain English

Conduct capacity planning to ensure adequate resources for processing, telecom, and environmental support during contingency operations, based on risk assessments and system impact levels. 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-2(2)) 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.
• 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.
• Impact. Document the trigger, the owner and the cadence.
• Scope: management, system, controls, assessments, capability, operations, policy, resources.

Evidence to collect

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

Signed policy or standard documents the safeguard. Focus: Capacity Planning.

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
• ISO/IEC 27001:2022 A.8.6 — Capacity management
• SOC 2 (2017 TSC) PI1.4 — Output Controls

Related controls in NIST SP 800-53 Rev. 5

• Control PL-2(1) — Concept Of Operations
• Control CP-7 — Alternate Processing Site
• Control CP-5 — Contingency Plan Update
• Control CP-10(3) — Compensating Security Controls
• Control SC-6 — Resource Availability
• Control CP-8 — Telecommunications Services

References

• NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5
• Catalogue identifier: Control CP-2(2)

Topics: governance riskcapacity managementenvironmental controlspolicy management