← Back to Microsoft Windows 11 Security Technical Implementation Guide

V-253338

CAT II (Medium)

The security event log size must be configured to a value that holds at least one week's worth of audit records.

Rule ID

SV-253338r1186375_rule

STIG

Microsoft Windows 11 Security Technical Implementation Guide

Version

V2R7

CCIs

CCI-001849

Discussion

Inadequate log size will cause the log to fill up quickly. This may prevent audit events from being recorded properly and require frequent attention by administrative personnel. System administrators (SAs) must monitor the volume of security event audit records and increase the registry value for the log size as needed.

Check Content

If the system is configured to send audit records directly to an audit server, this requirement is not applicable. This must be documented with the information system security officer (ISSO).

The registry configuration setting below must be set (at least) to a value equal to the size needed to contain one week's worth of audit records in the security event log. The value used below is an example that assumes a typical week’s log size of 5GB.

If the following registry value does not exist or is not configured as specified, this is a finding:

Note: The following registry entry is an example; the value must equal at least one week's worth of records.

Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \SOFTWARE\Policies\Microsoft\Windows\EventLog\Security\

Value Name: MaxSize

Value Type: REG_DWORD
Value:0x49960800 (5120000) (or greater)

Fix Text

Configure the policy value for Computer Configuration >> Administrative Templates >> Windows Components >> Event Log Service >> Security >> "Specify the maximum log file size (KB)" to "Enabled" with a "Maximum Log Size (KB)" of a value that will contain one week of audit records or greater.

If the system is configured to send audit records directly to an audit server, this must be documented with the ISSO.