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

CCC-01 Change Management Policy and Procedures

Policies and procedures that control the risk arising when changes are made to assets the organisation owns, controls or uses are approved, documented, communicated, applied, evaluated and kept current. They are reviewed and refreshed every year as a minimum and after significant changes.

Source: CSA CCM v4.1, CCC-01. 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
0
at each review
easy
to go live
Ticketing / ITSM
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

  • Sample change records showing compliance with the policy · Ticketing / ITSM
  • Policy review log with yearly and change-triggered reviews · SIEM / log platform

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

  • Approved change management policy covering scope, documentation, testing, approval and emergency changes · Policy repository / GRC workspace
  • Change procedures covering outsourced and cloud-hosted assets · Policy repository / GRC workspace

First move

Automate the pull from your Ticketing / ITSM. The ticket itself, with approver, timestamps and linked change or incident, exported on a schedule.

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

BCR-11 Equipment Redundancy · CCC-02 Quality Testing