UCF STIG Viewer Logo

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


Overview

Finding ID Version Rule ID IA Controls Severity
V-34542 SRG-NET-000076-IDPS-00061 SV-45384r1_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 network location information for each detected event provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying 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
Intrusion Detection and Prevention Systems (IDPS) Security Requirements Guide 2012-11-19

Details

Check Text ( C-42733r1_chk )
Examine the audit log configuration on the IDPS components (including the sensors) or view several alert records on organization's central audit log server.
Verify the entries sent to the audit log include the location of each event (e.g., network name, network subnet, network segment, or organization).

If the audit log events do not include the event location, this is a finding.
Fix Text (F-38781r1_fix)
Configure the IDPS components to ensure entries sent to the audit log include the location of each event (e.g., network name, network subnet, network segment, or organization).