CM.L2-3.4.1 System Baselining
Establish and maintain baseline configurations and inventories of systems, covering hardware, software, firmware and documentation, across the system life cycle.
3
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
- Evidence baselines are updated as systems change · Cloud console / configuration management
governing documentDocuments that govern the control
- Documented baseline configurations per system type · Policy repository / GRC workspace
- Asset inventory covering hardware, software and firmware · 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
- Inventory maintained but no configuration baseline defined
- Baselines captured once and never maintained
- Firmware and documentation excluded from scope
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.L2-3.12.4 System Security Plan · CM.L2-3.4.2 Security Configuration Enforcement