CM-1 Policy and procedures for configuration management
Requires a configuration management policy with supporting procedures to be developed, approved, disseminated to defined personnel, owned by a named official, and reviewed and updated on a defined frequency and after def
5
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
- Dissemination evidence to the defined recipients · Cloud console / configuration management
governing documentDocuments that govern the control
- Approved configuration management policy with scope, approver and date · Policy repository / GRC workspace
- Designation of the official accountable for the policy · Policy repository / GRC workspace
- Procedures covering baselines, change control and configuration monitoring · Policy repository / GRC workspace
- Review record for the configuration management policy and procedures against the defined frequency and triggering events · 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
- Policy predates the move to infrastructure as code and describes manual builds
- Change control procedure exists but no baseline procedure sits beside it
- Review cadence undefined, so the policy silently ages
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 sheetCA-9 Internal system connections · CM-2 Baseline configuration