CM.L2-3.4.2 Security Configuration Enforcement
Define security configuration settings for the IT products used in the system and enforce those settings in operation.
3
artefacts
1
held by a system
0
at each review
moderate
to go live
Vulnerability scanner / patch tooling
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Compliance scan results against the defined settings · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Documented security configuration settings or hardening standards · Policy repository / GRC workspace
- Evidence of enforcement, for example policy objects or configuration management tooling · Policy repository / GRC workspace
First move
Start with the 1 of 3 artefacts that already live in a system (Vulnerability scanner / patch tooling); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Standards documented but drift never measured
- Settings applied at build with no ongoing enforcement
- Products in use with no defined hardening standard
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.L2-3.4.1 System Baselining · CM.L2-3.4.3 System Change Management