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

CAT II (Medium)

The Cisco ASA VPN gateway must be configured to renegotiate the IKE security association after 24 hours or less.

Rule ID

SV-239964r1015264_rule

STIG

Cisco ASA VPN Security Technical Implementation Guide

Version

V2R2

CCIs

CCI-004895CCI-002038

Discussion

When a VPN gateway creates an IPsec security association (SA), resources must be allocated to maintain the SA. These resources are wasted during periods of IPsec endpoint inactivity, which could result in the gateway’s inability to create new SAs for other endpoints, thereby preventing new sessions from connecting. The Internet Key Exchange (IKE) idle timeout may also be set to allow SAs associated with inactive endpoints to be deleted before the SA lifetime has expired, although this setting is not recommended at this time. The value of one hour or less is a common best practice.

Check Content

Verify the VPN gateway renegotiates the IKE security association after 24 hours or less as shown in the example below.

crypto ikev2 policy 2
 encryption …
 …
 …
 …
 lifetime seconds 86400

If the VPN gateway does not renegotiate the IKE security association after 24 hours or less, this is a finding.

Fix Text

Configure the VPN gateway to renegotiate the IKE security association after 24 hours or less as shown in the example below.

ASA2(config)# crypto ikev2 policy 2
ASA2(config-ikev2-policy)# lifetime seconds 86400
ASA2(config-ikev2-policy)# end