CCC-02 Quality Testing
A defined quality-focused process for controlling, approving and testing changes is set up, kept current and followed, resting on baselines, defined testing and release standards.
Source: CSA CCM v4.1, CCC-02. 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.
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 tickets showing approval, test evidence and release sign-off · Ticketing / ITSM
periodic reviewEvidence produced at each review
- Change advisory board minutes · Ticketing / ITSM
governing documentDocuments that govern the control
- Change control procedure with approval and testing steps · Policy repository / GRC workspace
- Release standards and test criteria for changes · Policy repository / GRC workspace
First move
Common gaps auditors find
- Changes released without recorded test results
- Approvals given after deployment
- Baselines not referenced when testing changes
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 sheetCCC-01 Change Management Policy and Procedures · CCC-03 Change Management Technology