CM-3(2) Testing, Validation, and Documentation of Changes
Test, validate, and document changes before implementing on operational system.
Source: FedRAMP High (NIST SP 800-53 Rev 5 baseline), CM-3(2). 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 High (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
none for this control
periodic reviewEvidence produced at each review
- Validation results · Cloud console / configuration management
governing documentDocuments that govern the control
- Test plan · Policy repository / GRC workspace
First move
Common gaps auditors find
- No pre-prod testing
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 sheetCM-3(1) Automated Documentation, Notification, and Prohibition · CM-3(4) Security and Privacy Representatives