8.9 Centralize Audit Logs
Bring log collection and retention together in one place as far as practical, in line with the documented log management process, for example by feeding multiple sources into a SIEM. Implementation Groups: IG2 and IG3 (not in the IG1 baseline; applies from IG2 upward). Asset type: Data. Security function: Detect.
Source: CIS Controls v8.1, 8.9. 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 CIS Controls v8.1 in the compliance library.
Each safeguard shows its Implementation Groups. IG1 is the essential baseline for every enterprise, IG2 adds to it, IG3 is all 153. Version 8.1 adds the Govern security function and asks for more processes to be documented; numbering is unchanged from v8.
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
- Ingestion health dashboard · SIEM / log platform
- Retention configuration in the central platform · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- SIEM or log platform source list against required sources · Policy repository / GRC workspace
First move
Common gaps auditors find
- Many systems keep logs locally only
- Cloud provider logs not ingested
- Ingestion failures unnoticed
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 sheet8.8 Collect Command-Line Audit Logs · 8.10 Retain Audit Logs