CM-4(2) Impact Analyses | Verification of Controls (CM-4(2))
Impact Analyses | Verification of Controls. After system changes, verify that the impacted controls are implemented correctly, operating as intended, and producing the desired outcome with regard to meeting the security and privacy requirements
Source: FedRAMP Moderate (NIST SP 800-53 Rev 5 baseline), CM-4(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 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
- Post-change verification reports · Document repository
- Tickets linking change to verification · Ticketing / ITSM
periodic reviewEvidence produced at each review
- Control testing results · Document repository
governing documentDocuments that govern the control
none for this control
First move
Common gaps auditors find
- No post-change testing
- Verification not documented
- Controls drift after change
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