CM-2 Baseline Configuration
Establishes the baseline for delivered components so that later supplier changes can be detected against a known starting point.
3
artefacts
0
held by a system
2
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
- Comparison evidence against the supplier-shipped state · Vendor register / contract repository
- Baseline update records after supplier change · Vendor register / contract repository
governing documentDocuments that govern the control
- Baseline captured at acceptance for delivered components · 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
- baseline taken after months of operation
- no baseline for appliances and firmware
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-1 Policy and Procedures · CM-3 Configuration Change Control