The Cisco ASA must be configured to generate log records containing information to establish when the events occurred.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-239946 | CASA-VN-000020 | SV-239946r666244_rule | CCI-000131 | low |
| 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. | ||||
| STIG | Date | |||
| Cisco ASA VPN Security Technical Implementation Guide | 2024-08-22 | |||
Details
Check Text (C-239946r666244_chk)
Verify that the logging timestamp command has been configured as shown below.
logging enable
logging timestamp
If the ASA is not configured to generate traffic log entries containing information to establish when the events occurred, this is a finding.
Fix Text (F-43138r666243_fix)
Configure the ASA to generate traffic log entries containing information to establish when the events occurred.
ASA(config)# logging timestamp