What evidence do auditors commonly ask for on CCC-07 Detection of Baseline Deviation?

Configuration drift detection tooling and its rule set; Sample alerts for baseline deviations and their resolution; Alert routing showing who is notified; Reports of drift found and corrected over a period.

What is the most common gap auditors find on CCC-07?

Drift detection runs but alerts go unread

CSA CCM v4.1 · CCC - Change Control and Configuration Management

`CCC-07` Detection of Baseline Deviation

Detection measures with proactive alerting are put in place for changes that depart from the established baseline.

Source: CSA CCM v4.1, CCC-07. 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 CSA CCM v4.1 in the compliance library.

Version 4.1 adds 11 controls (among them API security, log sanitisation and a service bill of materials) and renumbers several domains. CSA accepts v4.0.x during its transition; if your STAR assessment is still on v4.0.1, check the numbering against it.

artefacts

held by a system

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. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

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

Configuration drift detection tooling and its rule set · SIEM / log platform
Sample alerts for baseline deviations and their resolution · SIEM / log platform
Alert routing showing who is notified · SIEM / log platform

periodic reviewEvidence produced at each review

Reports of drift found and corrected over a period · SIEM / log platform

governing documentDocuments that govern the control

none for this control

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

Drift detection runs but alerts go unread
Coverage limited to part of the estate
Deviations accepted without any approval

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

CCC-06 Change Management Baseline · CCC-08 Exception Management