CM.L2-3.4.3 System Change Management
Track changes to systems, review them, approve or reject them, and log the decision together with the change.
3
artefacts
0
held by a system
2
at each review
hard
to go live
Cloud console / configuration management
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
- Change records showing request, review, decision and implementation · Cloud console / configuration management
- Evidence unapproved changes are detected · Cloud console / configuration management
governing documentDocuments that govern the control
- Change approval authority definition · Policy repository / GRC workspace
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
- Emergency changes bypass the process with no retrospective record
- Approvals recorded without evidence of review
- Infrastructure changes tracked but application changes not
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 sheetCM.L2-3.4.2 Security Configuration Enforcement · CM.L2-3.4.4 Security Impact Analysis