CM-3 Configuration Change Control
Brings supplier-initiated and vendor-pushed changes inside change control rather than letting them arrive unannounced.
3
artefacts
0
held by a system
2
at each review
hard
to go live
Vendor register / contract repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Change records for supplier-initiated changes · Vendor register / contract repository
- 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
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
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