What evidence do auditors commonly ask for on CCC-04 Unauthorized Change Protection?

Asset change authorisation procedure; Role-based permissions restricting who can provision or decommission assets; Alerts or reports on unauthorised asset changes detected; Sample asset additions and removals with approval records.

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

Engineers can create or delete cloud resources without approval

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

`CCC-04` Unauthorized Change Protection

A procedure is put in place and enforced so that adding, removing, updating or managing any asset the organisation owns, controls or uses requires authorisation.

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

moderate

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

Alerts or reports on unauthorised asset changes detected · SIEM / log platform

periodic reviewEvidence produced at each review

Sample asset additions and removals with approval records · Ticketing / ITSM

governing documentDocuments that govern the control

Asset change authorisation procedure · Policy repository / GRC workspace
Role-based permissions restricting who can provision or decommission assets · Policy repository / GRC workspace

First move

Start with the 1 of 4 artefacts that already live in a system (SIEM / log platform); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

Engineers can create or delete cloud resources without approval
Unauthorised changes detected but not investigated
Procedure not applied to SaaS assets

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-03 Change Management Technology · CCC-05 Change Agreements