PulseSecure VPN

PulseSecure VPN

PulseSecure VPN is a seamless remote access VPN solution that enables you to access the On-prem resources. This document contains the best practices required in PulseSecure VPN and Netskope Client to ensure smooth interoperability.


  • Pulse Server Version: 9.1R14 (build 16847)
  • Pulse Client version: 22.5.1-25375
  • Netskope Client version: 111.0.0

Interoperability Configuration Requirements

Specific configurations in PulseSecure VPN and Netskope tenant web UI ensure processes or traffic from either of the applications are not blocked or directed to the Netskope Cloud.

Configurations In PulseSecure VPN

Create VPN Connection Profile
  1. In the admin console, navigate to Users > Resource Policies > VPN Tunneling > Connection Profiles.
  2. On the Connection Profiles page, click New Profile and enter the IPV4 Address Pool range. (You can use the Pool from AWS External VPC subnet IP range).
  3. Set the Connection settings as ESP mode.
  4. Set the Split Tunnel DNS Search order as Search the device’s DNS servers first, then client.
  5. Save the profile.
Create VPN Split Tunnel Resource
  1. In the admin console, navigate to Users > Resource Policies > VPN Tunneling > Split tunneling networks.
  2. Add a New policy  and fill in the Name and description.
  3. Fill in the Split tunnel Web resources in the field > FQDN Resources. For example, www.cnn.com.
  4. Set the Roles to Policies applies to ALL roles.
  5. Set the Actions as Allow Access.
  6. Save the configuration.
Enable Split Tunnel In User Roles Page
  1. In the admin console, navigate to Users > User Roles > Role Name > VPN Tunneling and click Options.
  2. Under Split tunneling, go to settings and choose Enable. You can choose Disable for Full-tunnel mode.
  3. Under VPN Client Options, select Tunnel routes as the route precedence (Applicable on Windows, MAC OSX, and Linux).
  4. Save the configuration.

Configurations In Netskope Client

When installing Netskope Client along with a VPN client, configure exceptions in steering configurations to bypass traffic from the VPN client. To learn more about adding exceptions for third-party VPN apps, view Exceptions.

Create a Network Location

To add the VPN gateway server URL in Netskope Policy :

  1. Go to Policies > Profiles > Network Location > New Network Location and select either Single Object or Multiple Objects.
  2. To add a Single Object, provide an IP address, IP address range, or a CIDR netmask, When finished, click the adjacent + button, and then click Next. Enter a name for the network location, and then click Save Network Location.
  3. To add Multiple Objects, upload a CSV file with multiple IP addresses or ranges. Enter a name for the network locations, and then click Save Network Location.
  4. When finished, click Apply Changes.
Create Destination Location Exception
  1. To add a Destination Location exception, go to Steering Configuration and select a configuration.
  2. In the EXCEPTIONS tab, click the NEW EXCEPTION drop down list and select Destination Location.
  3. In the New Exception pop-up window, enter select the Network Location profile from the list.
  4. Click ADD to complete the process.

Verifying Interoperability

Netskope Client Functions

Refer to the list of validated use cases that you can use to verify Client operations.

PulseSecure VPN Validation

Ensure that the traffic is going through the VPN.

Share this Doc

PulseSecure VPN

Or copy link

In this topic ...