What evidence do auditors commonly ask for on CCC-03 Change Management Technology?

Change management procedure including risk assessment of each change; Change tickets with risk rating and impact analysis; Change management tooling configuration (for example ticket workflow requiring risk fields); Records of changes to supplier-managed assets passing through the procedure.

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

Risk of change assessed informally or not recorded

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

`CCC-03` Change Management Technology

A change management procedure is put in place to control the risk that comes from changing assets the organisation owns, controls or uses.

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

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

Change tickets with risk rating and impact analysis · Ticketing / ITSM
Change management tooling configuration (for example ticket workflow requiring risk fields) · Ticketing / ITSM

periodic reviewEvidence produced at each review

Records of changes to supplier-managed assets passing through the procedure · Ticketing / ITSM

governing documentDocuments that govern the control

Change management procedure including risk assessment of each change · 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

Risk of change assessed informally or not recorded
Outsourced asset changes outside the procedure
Standard changes never reviewed for risk

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-02 Quality Testing · CCC-04 Unauthorized Change Protection