CCC-06 Change Management Baseline
Record a configuration baseline for every authorised change, so the approved state of each asset is known.
4
artefacts
0
held by a system
1
at each review
hard
to go live
Policy repository / GRC workspace
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
- Baseline updated as part of the change record for recent changes · Ticketing / ITSM
governing documentDocuments that govern the control
- Baseline definitions per asset class and the tool holding them · Policy repository / GRC workspace
- Coverage report showing which assets have a baseline · Policy repository / GRC workspace
- Ownership of each baseline · Policy repository / GRC workspace
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
- Baselines held for servers only, with network and cloud configuration excluded
- Baseline not updated when the change lands, so it immediately reads as drift
- No coverage measure, so gaps are invisible
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 sheetCCC-05 Change Agreements · CCC-07 Detection of Baseline Deviation