03.04.02 Configuration Settings
Establish, document, and implement configuration settings that reflect the most restrictive mode consistent with operational requirements; identify, document, and approve deviations.
2
artefacts
1
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
- CIS benchmark scan reports · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Approved deviation registry · 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
- exceptions undocumented
- drift not detected
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 sheet03.04.01 Baseline Configuration · 03.04.03 Configuration Change Control