CCC-07 Detection of Baseline Deviation
Detect drift away from the approved configuration baseline and raise a proactive notification to the responsible party rather than waiting for the next review.
4
artefacts
3
held by a system
0
at each review
easy
to go live
SIEM / log platform
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Drift detection tooling configuration and the assets it covers · Cloud console / configuration management
- Sample alerts raised and the response to them · SIEM / log platform
- Notification routing showing who receives a drift alert · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Time from drift to notification · Document repository
First move
Automate the pull from your SIEM / log platform. Retention and alert rules exported from the SIEM; review evidence is the closed-alert record with reviewer and time.
Common gaps auditors find
- Detection runs but alerts go to an unmonitored mailbox
- Coverage limited to a subset of assets while the baseline claims all
- Alerts suppressed because the noise level was never tuned
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-06 Change Management Baseline · CCC-08 Exception Management