CM-3 Configuration change control
Requires the types of change that fall under configuration control to be defined, proposed changes to be reviewed and approved or rejected with explicit consideration of security and privacy impact, decisions and impleme
5
artefacts
2
held by a system
3
at each review
moderate
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
- Documented definition of which change types are configuration controlled · Cloud console / configuration management
- Change records showing security and privacy impact considered before approval · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Change advisory board or approver minutes recording decisions · Cloud console / configuration management
- Retention evidence for change records against the defined period · Cloud console / configuration management
- Post-implementation review or monitoring output for change activity · SIEM / log platform
governing documentDocuments that govern the control
none for this control
First move
Start with the 2 of 5 artefacts that already live in a system (Cloud console / configuration management); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Emergency changes bypass approval and are never retrospectively documented
- Impact analysis recorded as a tick box with no security reasoning behind it
- Infrastructure as code changes merge without passing through the same change control
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