CCC-02 Quality Testing
Put changes through a defined quality control path with approval, established baselines, testing and release standards before they reach production.
4
artefacts
1
held by a system
1
at each review
moderate
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Approval records showing an authority separate from the implementer · Document repository
periodic reviewEvidence produced at each review
- Test results attached to recent production changes · Source control / CI pipeline
governing documentDocuments that govern the control
- The documented change approval and testing process · Policy repository / GRC workspace
- Release standards and the baseline each change was tested against · 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
- Changes approved by the person who wrote them
- Test evidence not retained with the change record
- Release standards defined but unenforced for urgent work
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