The SDN controller must be configured to produce audit records containing information to establish where the events occurred.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-80763	SRG-NET-000076-SDN-000130	SV-95473r1_rule		Medium

Description
Without establishing where events occurred, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack. In order to compile an accurate risk assessment, and provide forensic analysis, it is essential for security personnel to know where (e.g., interface, node, source IP, etc.) events occurred. Associating information about where the event occurred within the network provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured network element.

Description

Without establishing where events occurred, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack. In order to compile an accurate risk assessment, and provide forensic analysis, it is essential for security personnel to know where (e.g., interface, node, source IP, etc.) events occurred. Associating information about where the event occurred within the network provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured network element.

STIG	Date
SDN Controller Security Requirements Guide	2020-03-06

Details

Check Text ( C-80499r2_chk )
Review the SDN controller configuration to determine if the audit records will note where (e.g., service, interface, node, link, etc.) the event that is being logged occurred. If the SDN controller is not configured to produce audit records containing information to establish where (e.g., service, interface, node, link, etc.) the events occurred, this is a finding.

Fix Text (F-87617r2_fix)
Configure the SDN controller to include where (e.g., service, interface, node, link, etc.) the event occurred in the log records.