CP-4 Contingency Plan Testing
Test contingency plan at least annually (FedRAMP) using FedRAMP-defined tests; review test results.
Source: FedRAMP Moderate (NIST SP 800-53 Rev 5 baseline), CP-4. 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.
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
- Restoration test logs with success criteria signed off · Backup / DR tooling
- Backup schedule, retention, and offsite or immutable copy evidence · Backup / DR tooling
periodic reviewEvidence produced at each review
- Contingency plan test report with after-action items tracked to closure · Policy repository / GRC workspace
governing documentDocuments that govern the control
- SSP CP-4 statement describing the annual functional test of the contingency plan, test scenarios and results review · Policy repository / GRC workspace
- Business impact analysis identifying critical systems · Document repository
- Contingency plan with recovery time and recovery point objectives · Policy repository / GRC workspace
First move
Common gaps auditors find
- RTO and RPO targets undefined for tier two systems
- Tabletop exercises lack participation from business owners
- Alternate site capacity not validated against current load
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 sheetCP-3 Contingency Training · CP-4(1) Coordinate with Related Plans