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 1 hour ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Juniper SRX SG VPN Security Technical Implementation Guide

V-66631

CAT II (Medium)

The Juniper SRX Services Gateway VPN must renegotiate the security association after 8 hours or less.

Rule ID

SV-81121r1_rule

STIG

Juniper SRX SG VPN Security Technical Implementation Guide

Version

V1R2

CCIs

CCI-002361

Discussion

The IPsec SA and its corresponding key will expire either after the number of seconds or amount of traffic volume has exceeded the configured limit. A new SA is negotiated before the lifetime threshold of the existing SA is reached to ensure that a new SA is ready for use when the old one expires. The longer the lifetime of the IPsec SA, the longer the lifetime of the session key used to protect IP traffic. The SA is less secure with a longer lifetime because an attacker has a greater opportunity to collect traffic encrypted by the same key and subject it to cryptanalysis. However, a shorter lifetime causes IPsec peers to renegotiate Phase II more often resulting in the expenditure of additional resources. For the Juniper SRX, specify the lifetime (in seconds) of an Internet Key Exchange (IKE) security association (SA). When the SA expires, it is replaced by a new SA, the security parameter index (SPI), or terminated if the peer cannot be contacted for renegotiation.

Check Content

Review all IPsec security associations configured globally or within IPsec profiles on the VPN gateway and examine the configured idle time. The default is 3600.

[edit]
show security ipsec proposal

View the value of the lifetime-seconds option.

If the IPsec proposal lifetime-seconds are not renegotiated after 8 hours or less of idle time, this is a finding.

If the IPsec proposal lifetime-seconds is not configured, this is a finding.

Fix Text

Set the lifetime (in seconds) of the IPsec proposal to 8 hours or less. 

Example:

[edit]
set security ipsec proposal <P2-PROPOSAL-NAME> lifetime-seconds 28800