CCC-03 Change Management Technology
Actively manage the risk each change introduces to applications, systems, infrastructure and configuration, including assets operated by outsourced providers.
4
artefacts
0
held by a system
4
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Risk assessment recorded against individual changes · Policy repository / GRC workspace
- Evidence outsourced provider changes are captured and assessed · Vendor register / contract repository
- Criteria that decide when a change needs deeper assessment · Policy repository / GRC workspace
- Records of changes rejected or reworked on risk grounds · Policy repository / GRC workspace
governing documentDocuments that govern the control
none for this control
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Risk field on the change record filled in as low by default
- Supplier changes arriving with no notice and no assessment
- No criteria, so risk rating is arbitrary between assessors
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-02 Quality Testing · CCC-04 Unauthorized Change Protection