CM-3 Configuration Change Control
Brings supplier-initiated and vendor-pushed changes inside change control rather than letting them arrive unannounced.
Source: NIST SP 800-161 Rev 1 (supply chain), CM-3. 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 NIST SP 800-161 Rev 1 (supply chain) in the compliance library.
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
- Change records for supplier-initiated changes · Vendor register / contract repository
periodic reviewEvidence produced at each review
- Evidence of review before vendor changes are applied · Vendor register / contract repository
governing documentDocuments that govern the control
- Notification requirements in supplier agreements · Vendor register / contract repository
First move
Common gaps auditors find
- automatic vendor updates applied with no record
- supplier changes discovered after the fact
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