4.1 Establish and Maintain a Secure Configuration Process
Establish and maintain a secure configuration process for enterprise assets (end-user devices, including portable and mobile, non-computing/IoT devices, and servers) and software (operating systems and applications). Rev
4
artefacts
2
held by a system
1
at each review
easy
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Evidence the safeguard is implemented: Establish and Maintain a Secure Configuration Process · Cloud console / configuration management
- Configuration / tooling output demonstrating the safeguard · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Records showing the safeguard is operating (logs, reports, reviews) · SIEM / log platform
governing documentDocuments that govern the control
- Policy/standard covering CIS Control 4 (Secure Configuration of Enterprise Assets and Software) · Policy repository / GRC workspace
First move
Automate the pull from your Cloud console / configuration management. Configuration snapshots and change history from the cloud console or IaC repository, diffed against the baseline.
Common gaps auditors find
- Safeguard implemented for some assets but not all in scope
- No evidence of ongoing operation (point-in-time only)
- Implementation Group IG1 baseline not met
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 sheet3.14 Log Sensitive Data Access · 4.2 Establish and Maintain a Secure Configuration Process for Network Infrastructure