EvidenceSheet

CCC-06 Change Management Baseline

Change management and configuration baselines are set, written down and applied for all relevant authorised changes to organisational assets, and the baselines are reviewed and updated every year as a minimum or after significant changes.

Source: CSA CCM v4.1, CCC-06. 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.

4
artefacts
2
held by a system
2
at each review
easy
to go live
Cloud console / configuration management
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 baseline documents per asset type (for example hardened images, CIS benchmark profiles) · Cloud console / configuration management
  • Configuration management database or infrastructure as code repository holding the baselines · Source control / CI pipeline

periodic reviewEvidence produced at each review

  • Baseline review and approval records · Cloud console / configuration management
  • Change records referencing the baseline they update · Cloud console / configuration management

governing documentDocuments that govern the control

none for this control

First move

Automate the pull from your Cloud console / configuration management. Configuration snapshots and change history from the cloud console or IaC repository, diffed against the baseline.

Common gaps auditors find

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-05 Change Agreements · CCC-07 Detection of Baseline Deviation