V2R2 changes
Ivanti Connect Secure VPN STIG V2R2 (2025-10-01) replaced V2R1 (2024-07-24): 1 check updated. It has 15 checks, against 15 in V2R1.
V2R2 checklistV2R1 checklist Compare V2R1 and V2R2 in STIG Compare
- 0 added
- 0 removed
- 1 updated
Updated fields: Title 1Discussion 1
Updated in V2R2 (1)
V-258591CAT IIThe ICS must terminate remote access network connections after 10 minutes or less.Title, Discussion
Title
The ICS must terminate remote access network connections after an10 organmization-defined utimes periodr less.
Discussion
This SRG requirement is in response to the DoD OIG Audit of Maintaining Cybersecurity in the Coronavirus Disease-2019 Telework Environment.
Best practice is to terminate inactive user sessions after a period; however, when setting timeouts to any VPN connection, the organization must takeconsider into consideration the risk to the mission and the purpose of the VPN. VPN connections that provide user access to the network are the prime candidates for VPN session termination and are the primary focus of this requirement.
To determine if and when the VPN connections warrant termination, the organization must perform a risk assessment to identify the use case for the VPN and determine if periodic VPN session termination puts the mission at significant risk.
The organization must document the results and the determination of the risk assessment in the VPN section of the SSP. The organization must also configure VPN session terminations in accordance with the risk assessment.
This SRG requirement is in response to the DOD OIG Audit of Maintaining Cybersecurity in the Coronavirus Disease-2019 Telework Environment.
Best practice is to terminate inactive user sessions after a period; however, when setting timeouts to any VPN connection, the organization must take into consideration the risk to the mission and the purpose of the VPN. VPN connections that provide user access to the network are the prime candidates for VPN session termination and are the primary focus of this requirement.
To determine if and when the VPN connections warrant termination, the organization must perform a risk assessment to identify the use case for the VPN and determine if periodic VPN session termination puts the mission at significant risk.
The organization must document the results and the determination of the risk assessment in the VPN section of the SSP. The organization must also configure VPN session terminations in accordance with the risk assessment.
Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port that has been left unattended. In addition, quickly terminating an idle session will also free up resources committed by the managed network element.
Terminating network connections associated with communications sessions includes, for example, de-allocatingdeallocating associated TCP/IP address/port pairs at the operating system level, and de-allocatingdeallocating networking assignments at the application level if multiple application sessions are using a single, operating system -level network connection.
This requirement applies to any network element that tracks individual sessions (e.g., stateful inspection firewall, ALG, or VPN).
How these changes are found
Checks are matched across the two releases by V-number. A check counts as updated when DISA gave it a new rule revision (the r number in its SV-…_rule id) and its title, severity, check text, fix text, discussion, CCIs or other fields changed — the same comparison STIG Compare makes. Added checks are new V-numbers; removed checks are V-numbers V2R2 no longer has.
Comparing other releases, or this one against an older release? Pick any two in STIG Compare.