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

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
SRG-NET-000075-IDPS-000083	SRG-NET-000075-IDPS-000083	SRG-NET-000075-IDPS-000083_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 actions of specific events provides a means to investigate an attack, recognize resource utilization or capacity thresholds, or to simply 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 actions of specific events provides a means to investigate an attack, recognize resource utilization or capacity thresholds, or to simply 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
IDPS Security Requirements Guide (SRG)	2012-03-08

Details

Check Text ( C-43211_chk )
Examine the aggregated sensor events log on the management console. View entries for several alerts. Verify the events being captured in the sensor logs include the date and time of each event. If the log events do not include the date and time the events occurred, this is a finding.

Fix Text (F-43211_fix)
Configure the sensor log, so entries in the logs include the date and time of the event.