EvidenceSheet

CM-1 Policy and Procedures

Extends configuration management policy to cover components sourced externally and changes made by suppliers and integrators.

3
artefacts
0
held by a system
1
at each review
hard
to go live
Vendor register / contract repository
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

  • Review records · Policy repository / GRC workspace

governing documentDocuments that govern the control

  • Configuration management policy covering supplier change · Vendor register / contract repository
  • Contract clauses on change notification · 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

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

CA-7 Continuous Monitoring · CM-2 Baseline Configuration