CM-6 Configuration settings
Requires configuration settings for system components to be established and documented at the most restrictive mode consistent with operations using defined secure configuration baselines, implemented in practice, with a
4
artefacts
2
held by a system
0
at each review
easy
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
- Configuration compliance scan results against those settings · Vulnerability scanner / patch tooling
- Monitoring evidence showing setting changes are detected and reviewed · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Documented configuration settings or hardening standard per component type, citing the source benchmark · Policy repository / GRC workspace
- Approved deviation register with the operational justification for each · Policy repository / GRC workspace
First move
Automate the pull from your Vulnerability scanner / patch tooling. Scan schedule, findings and remediation age straight from the scanner; patch compliance from the patch console.
Common gaps auditors find
- Benchmark adopted but never tailored, so most settings are silently exempted in practice
- Deviations applied locally by engineers with no approval record
- Compliance measured once at build with no drift detection afterwards
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-5 Access restrictions for change · CM-7 Least functionality