I&S-04 OS Hardening and Base Controls
Harden host and guest operating systems, hypervisors and the infrastructure control plane to their respective good practice, under a security baseline that technical controls enforce.
Source: CSA CCM v4.1, I&S-04. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open CSA CCM v4.1 in the compliance library.
Version 4.1 adds 11 controls (among them API security, log sanitisation and a service bill of materials) and renumbers several domains. CSA accepts v4.0.x during its transition; if your STAR assessment is still on v4.0.1, check the numbering against it.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
- Hardening baselines (for example, CIS Benchmarks) adopted for each OS, hypervisor and control plane · Cloud console / configuration management
- Configuration compliance scan results against the baseline · Vulnerability scanner / patch tooling
- Golden image build pipeline records · Source control / CI pipeline
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Exceptions to the baseline with approval · Policy repository / GRC workspace
First move
Common gaps auditors find
- Baseline defined but drift never measured
- Control plane and hypervisor not covered by the baseline
- Images built manually outside the hardened pipeline
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 sheetI&S-03 Network Security · I&S-05 Production and Non-Production Environments