A company wants to deploy Netskope Client and configure it to co-exist with their VPN...

When the Netskope Client is deployed alongside a VPN solution, the Steering Configuration must be carefully configured to ensure traffic is correctly split between Netskope and the VPN. The recommended approach is to configure a steering exception in the Netskope Client for the VPN server’s FQDN and IP address. This exception instructs the Netskope Client to bypass those specific destinations, allowing the VPN client to establish its tunnel directly to the VPN server without interference. Once the VPN tunnel is established, traffic destined for the corporate network routes through the VPN while all other Internet-bound traffic continues to be steered by the Netskope Client. SSL policy modifications and Real-time Protection policies are not the correct mechanism for managing client-level traffic steering splits between Netskope and VPN clients.