STIGhubSTIGhub
STIGsRMF ControlsCompare

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
  • RMF Controls
  • 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 VPN Security Technical Implementation Guide

V-239946

CAT III (Low)

The Cisco ASA must be configured to generate log records containing information to establish when the events occurred.

Rule ID

SV-239946r666244_rule

STIG

Cisco ASA VPN Security Technical Implementation Guide

Version

V2R2

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. 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 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