UCF STIG Viewer Logo

The IDPS must produce audit log records that contain sufficient information to establish what type of event occurred.


Overview

Finding ID Version Rule ID IA Controls Severity
V-34540 SRG-NET-000074-IDPS-00059 SV-45382r1_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. Associating event types with detected events in the sensor and audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured IDPS. Without this capability, it will be difficult to establish, correlate, and investigate the events leading up to an outage or attack. To support the auditing requirement, the IDPS account and audit management functions must be configured to transmit the required audit events to the site's central audit server (e.g., SYSLOG server), as required by CCI-000136.
STIG Date
Intrusion Detection and Prevention Systems (IDPS) Security Requirements Guide 2012-11-19

Details

Check Text ( C-42731r1_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 sufficient information to determine the type or category for each audit event recorded in the audit log.

If the audit log event records do not include enough information to determine the type or category of events, this is a finding.
Fix Text (F-38779r1_fix)
Configure the IDPS components (including the sensors) to ensure entries sent to the audit log include sufficient information to determine the type or category for each audit event recorded in the audit log.