The IDPS must produce audit log records containing sufficient information to establish when the events occurred.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-34541	SRG-NET-000075-IDPS-00060	SV-45383r1_rule		Low

Description
It is essential for security personnel to know what is being done, what attempted to be done, where it was done, when it was done, and by whom in order to compile an accurate risk assessment. Logging the date and time of each detected event provides a means to investigate an attack; recognize resource utilization or capacity thresholds; or to identify an improperly configured IDPS. In order to establish and correlate the series of events leading up to an outage or attack, it is imperative the date and time are recorded in all log records.

Description

It is essential for security personnel to know what is being done, what attempted to be done, where it was done, when it was done, and by whom in order to compile an accurate risk assessment. Logging the date and time of each detected event provides a means to investigate an attack; recognize resource utilization or capacity thresholds; or to identify an improperly configured IDPS. In order to establish and correlate the series of events leading up to an outage or attack, it is imperative the date and time are recorded in all log records.

STIG	Date
Intrusion Detection and Prevention Systems (IDPS) Security Requirements Guide	2012-11-19

Details

Check Text ( C-42732r1_chk )
Examine the audit log configuration on the IDPS components (including the sensors) or view several alert records on the organization's central audit log server. Verify the entries sent to the audit log include the date and time of each event. If the audit log event records do not include the date and time the events occurred, this is a finding.

Fix Text (F-38780r1_fix)
Configure the IDPS components to ensure entries sent to the audit log include the date and time of the event.