CIS Control 8: Audit Log Management
Collect, keep and review the logs your systems produce, so you can spot an attack early and understand what happened afterward. Without logs, many breaches go unnoticed for months.
What it means
Collect, alert on, review and retain audit logs of events that could help you detect, understand or recover from an attack.
Why it matters
IBM's 2026 Cost of a Data Breach Report puts the average time to find and contain a breach at 247 days, and breaches contained in under 200 days cost about 25% less. Logs are how you find out what happened, and when.
Key safeguards
Establish and maintain an audit log management process (IG1)
Collect audit logs and ensure adequate log storage (IG1)
Standardize time synchronization and collect detailed logs, including DNS, URL and command-line logs (IG2)
Centralize audit logs, keep them for at least 90 days, and review them regularly (IG2)
Collect service provider logs (IG3)
How Prominic helps
Monitoring and alerts handled by Prominic engineers for the systems we manage (log scope: to confirm)
ControlUp desktop experience monitoring records session events for every user
Email security reporting through Proofpoint (details: to confirm)
Log collection and review as part of a CIS baseline project (details: to confirm)
Where it fits
Basic log collection is IG1; centralized logging and regular review come in IG2.
See also: Control 13: Network Monitoring and Defense, and Control 17: Incident Response Management.
