IVS-04 OS Hardening and Base Controls
Harden host and guest operating systems, hypervisors and the infrastructure control plane to a documented security baseline enforced by technical controls.
4
artefacts
1
held by a system
1
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 baselines · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
- Exception records for deviations · Cloud console / configuration management
governing documentDocuments that govern the control
- The hardening baselines per platform and the standard they derive from · Policy repository / GRC workspace
- Technical enforcement such as configuration management or policy as code · Policy repository / GRC workspace
First move
Start with the 1 of 4 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
- Baselines documented but compliance never measured
- Control plane excluded, with only guest operating systems hardened
- Deviations found repeatedly and never remediated or accepted
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 sheetIVS-03 Network Security · IVS-05 Production and Non-Production Environments