Details

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.

Solution

Configure the ASA to generate traffic log entries containing information to establish when the events occurred.

ASA(config)# logging timestamp

Supportive Information

The following resource is also helpful.

• https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_Cisco_ASA_STIG.zip

This security hardening control applies to the following category of controls within NIST 800-53: Audit and Accountability.This control applies to the following type of system Cisco.

References

• 800-53|AU-3
• CAT|III
• CCI|CCI-000131
• Rule-ID|SV-239946r666244_rule
• STIG-ID|CASA-VN-000020
• Vuln-ID|V-239946

Source

• Tenable.com/audits