What evidence do auditors commonly ask for on CCC-08 Exception Management?

Emergency and exception change procedure; Exception register for configuration and change deviations with approver and expiry; Sample emergency change records with retrospective review; Cross-reference from the procedure to the GRC-04 policy exception process.

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

Emergency changes never reviewed after the event

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

`CCC-08` Exception Management

A procedure manages exceptions, emergencies included, within the change and configuration process, and it is aligned with the policy exception process required by GRC-04.

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

Document repository

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 emergency change records with retrospective review · Document repository

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

Emergency and exception change procedure · Policy repository / GRC workspace
Exception register for configuration and change deviations with approver and expiry · Policy repository / GRC workspace
Cross-reference from the procedure to the GRC-04 policy exception process · Policy repository / GRC workspace

First move

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

Common gaps auditors find

Emergency changes never reviewed after the event
Exceptions granted with no expiry date
Change exceptions handled outside the organisation's policy exception process

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