Details

Without establishing when 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 of network traffic patterns, it is essential for security personnel to know when flow control events occurred (date and time) within the infrastructure.

Associating event types with detected events in the network traffic logs provides a means of investigating an attack, recognizing resource utilization or capacity thresholds, or identifying an improperly configured network element.

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|II
• CCI|CCI-000131
• Rule-ID|SV-239856r665854_rule
• STIG-ID|CASA-FW-000050
• Vuln-ID|V-239856

Source

• Tenable.com/audits