STIGhubSTIGhub
STIGsSearchCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 3 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Cisco ASA Firewall Security Technical Implementation Guide

V-239856

CAT II (Medium)

The Cisco ASA must be configured to generate traffic log entries containing information to establish when (date and time) the events occurred.

Rule ID

SV-239856r665854_rule

STIG

Cisco ASA Firewall Security Technical Implementation Guide

Version

V2R1

CCIs

CCI-000131

Discussion

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.

Check Content

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

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

ASA(config)# logging timestamp