8.11 Conduct Audit Log Reviews
Review audit logs at least weekly to find anomalies or unusual events that may point to a threat. 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.11. 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
- Weekly log review procedure and assigned reviewers · SIEM / log platform
- Review records or tickets with findings · SIEM / log platform
periodic reviewEvidence produced at each review
- Correlation rules and alerts supporting review · SIEM / log platform
governing documentDocuments that govern the control
none for this control
First move
Common gaps auditors find
- Reviews happen only after an incident
- No record that reviews took place
- Reviewers lack guidance on what is anomalous
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 sheet