Title

The IDPS must produce audit records containing information to establish where the event was detected, including, at a minimum, network segment, destination address, and IDPS component which detected the event. (Cat II impact)

Discussion

Associating where the event was detected with the event log entries provides a means of investigating an attack or identifying an improperly configured IDPS. This information can be used to determine what systems may have been affected. While auditing and logging are closely related, they are not the same. Logging is recording data about events that take place in a system, while auditing is the use of log records to identify security-relevant information such as system or user accesses. In short, log records are audited to establish an accurate history. Without logging, it would be impossible to establish an audit trail.

Check Content

Verify the IDPS produces audit records containing information to establish where the event was detected, including, at a minimum, network segment, destination address, and IDPS component which detected the event. If the audit log events do not include information which establishes where the event was detected, including, at a minimum, network segment, destination address, and IDPS component which detected the event, this is a finding.

Fix Text

Configure the IDPS to produce audit records containing information to establish where the event was detected, including, at a minimum, network segment, destination address, and IDPS component which detected the event.

Additional Identifiers

Rule ID: SV-45384r2_rule

Vulnerability ID: V-34542

Group Title: SRG-NET-000076-IDPS-00061

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.