CCC-01 Change Management Policy and Procedures
Keep approved change management policies and procedures covering the risk of changing applications, systems, infrastructure and configuration, whether the asset is run in-house or by a supplier, and review them at least
4
artefacts
0
held by a system
1
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
- Annual review record · Document repository
governing documentDocuments that govern the control
- The approved change management policy with scope covering outsourced assets · Policy repository / GRC workspace
- Procedures for standard, normal and emergency change · Policy repository / GRC workspace
- Evidence the policy was communicated to internal teams and suppliers · Vendor register / contract repository
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
- Policy scope silent on supplier-managed assets, leaving them ungoverned
- Emergency change path undefined so it becomes the default route
- Annual review missed
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