The VPN Gateway must generate log records containing information to establish when (date and time) the events occurred.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
low	V-207196	SRG-NET-000078	SRG-NET-000078-VPN-000290	SV-207196r608988_rule	2024-12-19	3

Description
Without establishing when events occurred, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack. VPN gateways often have a separate audit log for capturing VPN status and other information about the traffic (as opposed to the log capturing administrative and configuration actions). Associating event types with detected events in the network audit logs provides a means of investigating an attack, recognizing resource utilization or capacity thresholds, or identifying an improperly configured VPN gateway.

Description

Without establishing when events occurred, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack. VPN gateways often have a separate audit log for capturing VPN status and other information about the traffic (as opposed to the log capturing administrative and configuration actions). Associating event types with detected events in the network audit logs provides a means of investigating an attack, recognizing resource utilization or capacity thresholds, or identifying an improperly configured VPN gateway.

ℹ️ Check
Configure the VPN Gateway generates log records containing information to establish when (date and time) the events occurred. If the VPN Gateway does not generate log records containing information to establish when (date and time) the events occurred, this is a finding.

✔️ Fix
Configure the VPN Gateway to generate log records containing information to establish when (date and time) the events occurred.