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

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-206719	SRG-NET-000076	SRG-NET-000076-SDN-000130	SV-206719r382861_rule	2024-05-28	2

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.

ℹ️ Check
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
Configure the SDN controller to include where (e.g., service, interface, node, link, etc.) the event occurred in the log records.