EvidenceSheet
FedRAMP Moderate (NIST SP 800-53 Rev 5 baseline) · CP - Contingency Planning

CP-1 Policy and Procedures

Develop, document, disseminate and review the policy for contingency planning, and its procedures, on the FedRAMP-defined cadence: policy at least annually under High and at least every three years under Moderate, procedures at least annually and after significant changes under both.

Source: FedRAMP Moderate (NIST SP 800-53 Rev 5 baseline), CP-1. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open FedRAMP Moderate (NIST SP 800-53 Rev 5 baseline) in the compliance library.

A FedRAMP baseline is a subset of NIST SP 800-53 Rev 5, enhancements included.

7
artefacts
2
held by a system
3
at each review
moderate
to go live
Backup / DR tooling
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

  • Backup schedule, retention, and offsite or immutable copy evidence · Backup / DR tooling
  • Restoration test logs with success criteria signed off · Backup / DR tooling

periodic reviewEvidence produced at each review

  • SSP CP-1 statement naming the contingency planning policy owner, its review cadence (policy yearly for High, at least every three years for Moderate; procedures yearly for both) and the plans it governs · Policy repository / GRC workspace
  • Annual tabletop and full failover test reports · Backup / DR tooling
  • Alternate processing site contract and capacity attestation · Vendor register / contract repository

governing documentDocuments that govern the control

  • Contingency planning policy with dated review approval · Policy repository / GRC workspace
  • Business impact analysis identifying critical systems · Document repository

First move

Start with the 2 of 7 artefacts that already live in a system (Backup / DR tooling); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

CM-12(1) Information Location | Automated Tools to Support Information Location (CM-12(1)) · CP-2 Contingency Plan