03.04.03 Configuration Change Control
Define and document types of changes that require configuration change control; review proposed changes; approve or disapprove with explicit consideration of security impact.
3
artefacts
1
held by a system
1
at each review
moderate
to go live
Ticketing / ITSM
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Change tickets · Ticketing / ITSM
periodic reviewEvidence produced at each review
- CAB minutes · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Change control policy · Policy repository / GRC workspace
First move
Start with the 1 of 3 artefacts that already live in a system (Ticketing / ITSM); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- emergency changes bypass review
- no security impact assessment
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