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

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
SRG-NET-000076-IDPS-000082	SRG-NET-000076-IDPS-000082	SRG-NET-000076-IDPS-000082_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 source or object of the log record is 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 source or object of the log record is recorded in all log records.

STIG	Date
IDPS Security Requirements Guide (SRG)	2012-03-08

Details

Check Text ( C-43210_chk )
Examine the aggregated sensor events log on the management console. View entries for several alerts. Verify the events in the logs show the location of each event (e.g., network name, network subnet, network segment, or organization). If the log events do not include the event location (e.g., network name, network subnet, network segment, or organization), this is a finding.

Fix Text (F-43210_fix)
Configure the sensors to capture the location of each event (e.g., network name, network subnet, network segment, or organization).