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 2 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Ivanti Connect Secure VPN Security Technical Implementation Guide

V-258596

CAT II (Medium)

The ICS must be configured to disable split-tunneling for remote client VPNs.

Rule ID

SV-258596r1005432_rule

STIG

Ivanti Connect Secure VPN Security Technical Implementation Guide

Version

V2R2

CCIs

CCI-002397

Discussion

Split tunneling would in effect allow unauthorized external connections, making the system more vulnerable to attack and to exfiltration of organizational information. A VPN hardware or software client with split tunneling enabled provides an unsecured backdoor to the enclave from the internet. With split tunneling enabled, a remote client has access to the internet while at the same time has established a secured path to the enclave via an IPsec tunnel. A remote client connected to the internet that has been compromised by an attacker on the internet, provides an attack base to the enclave's private network via the IPsec tunnel. Hence, it is imperative that the VPN gateway enforces a no split-tunneling policy to all remote clients.

Check Content

In the ICS Web UI, navigate to Users >> Resource Policies >> Split Tunneling Networks.

If there are any split-tunnel network policies, this is a finding.

Fix Text

In the ICS Web UI, navigate to Users >> Resource Policies >> Split Tunneling Networks.
1. If there are any split-tunnel network policies configured, select all of them and delete them.
2. If the split tunneling policies are needed for debugging or testing only, ensure the role being applied is only for the debugging or test group.