8.10
IG2 IG3

Retain Audit Logs

Control Group: 8. Audit Log Management
Asset Type: Network
Security Function: Protect

Description

Retain audit logs across enterprise assets for a minimum of 90 days.

Implementation Checklist

1
Assess current protection controls in place
2
Configure and deploy required security controls
3
Test control effectiveness in non-production environment
4
Deploy to production and verify functionality
5
Document configuration and operational procedures
6
Enable logging on all in-scope systems
7
Configure log forwarding to centralized SIEM
8
Define log retention periods per policy
9
Establish log review schedule and procedures

Threats & Vulnerabilities (CIS RAM)

Threat Scenarios

Historical Attack Evidence Destroyed by Premature Log Deletion

Integrity

Logs are retained for less than 90 days, and when a breach discovered months after initial compromise requires forensic investigation, the critical evidence from the initial intrusion and lateral movement phases has already been purged.

Compliance Violation from Insufficient Log Retention

Availability

Regulatory requirements mandate specific log retention periods (often 1-7 years), and insufficient retention results in compliance failures, audit findings, and potential penalties during regulatory examinations.

Vulnerabilities (When Safeguard Absent)

Log Retention Below 90-Day Minimum

Audit logs are retained for fewer than 90 days due to storage constraints or misconfigured rotation policies, destroying forensic evidence needed for incident investigations given the average breach detection time exceeds 200 days.

No Log Retention Policy Enforcement Mechanism

Even where retention policies exist on paper, no technical controls enforce minimum retention periods, allowing storage pressure or misconfigurations to silently purge logs before the required retention period expires.

Evidence Requirements

Type Evidence Item Collection Frequency
Technical Configuration screenshots or exports showing protection controls enabled Captured quarterly
Document Procedure documentation for protection measures Reviewed annually
Technical SIEM dashboard showing log sources and collection status Captured monthly
Record Log review records and findings Per review cycle
Document Governing policy document (current, approved, communicated) Reviewed annually