GlobalProtect
Configure a Split Tunnel Based on the Domain and Application
Table of Contents
Expand All
|
Collapse All
GlobalProtect Docs
-
10.1 & Later
- 10.1 & Later
- 9.1 (EoL)
-
- How Does the App Know Which Certificate to Supply?
- Set Up Cloud Identity Engine Authentication
- Configure GlobalProtect to Facilitate Multi-Factor Authentication Notifications
- Enable Delivery of VSAs to a RADIUS Server
- Enable Group Mapping
-
-
- GlobalProtect App Minimum Hardware Requirements
- Download the GlobalProtect App Software Package for Hosting on the Portal
- Host App Updates on the Portal
- Host App Updates on a Web Server
- Test the App Installation
- Download and Install the GlobalProtect Mobile App
- View and Collect GlobalProtect App Logs
-
-
- Deploy App Settings in the Windows Registry
- Deploy App Settings from Msiexec
- Deploy Scripts Using the Windows Registry
- Deploy Scripts Using Msiexec
- Deploy Connect Before Logon Settings in the Windows Registry
- Deploy GlobalProtect Credential Provider Settings in the Windows Registry
- SSO Wrapping for Third-Party Credential Providers on Windows Endpoints
- Enable SSO Wrapping for Third-Party Credentials with the Windows Registry
- Enable SSO Wrapping for Third-Party Credentials with the Windows Installer
- Deploy App Settings to Linux Endpoints
- GlobalProtect Processes to be Whitelisted on EDR Deployments
-
-
- Mobile Device Management Overview
- Set Up the MDM Integration With GlobalProtect
- Qualified MDM Vendors
-
-
- Set Up the Microsoft Intune Environment for Android Endpoints
- Deploy the GlobalProtect App on Android Endpoints Using Microsoft Intune
- Create an App Configuration on Android Endpoints Using Microsoft Intune
- Configure Lockdown Mode for Always On Connect Method on Android Endpoints Using Microsoft Intune
-
- Deploy the GlobalProtect Mobile App Using Microsoft Intune
- Configure an Always On VPN Configuration for iOS Endpoints Using Microsoft Intune
- Configure a User-Initiated Remote Access VPN Configuration for iOS Endpoints Using Microsoft Intune
- Configure a Per-App VPN Configuration for iOS Endpoints Using Microsoft Intune
-
-
-
- Create a Smart Computer Group for GlobalProtect App Deployment
- Create a Single Configuration Profile for the GlobalProtect App for macOS
- Deploy the GlobalProtect Mobile App for macOS Using Jamf Pro
-
- Enable GlobalProtect System Extensions on macOS Endpoints Using Jamf Pro
- Enable GlobalProtect Network Extensions on macOS Big Sur Endpoints Using Jamf Pro
- Add a Configuration Profile for the GlobalProtect Enforcer by Using Jamf Pro 10.26.0
- Verify Configuration Profiles Deployed by Jamf Pro
- Remove System Extensions on macOS Monterey Endpoints Using Jamf Pro
- Non-Removable System Extensions on macOS Sequoia Endpoints Using Jamf Pro
- Uninstall the GlobalProtect Mobile App Using Jamf Pro
-
- Configure HIP-Based Policy Enforcement
- Configure HIP Exceptions for Patch Management
- Collect Application and Process Data From Endpoints
- Redistribute HIP Reports
-
- Identification and Quarantine of Compromised Devices Overview and License Requirements
- View Quarantined Device Information
- Manually Add and Delete Devices From the Quarantine List
- Automatically Quarantine a Device
- Use GlobalProtect and Security Policies to Block Access to Quarantined Devices
- Redistribute Device Quarantine Information from Panorama
- Troubleshoot HIP Issues
-
-
- Enable and Verify FIPS-CC Mode on Windows Endpoints
- Enable and Verify FIPS-CC Mode on macOS Endpoints
- Enable and Verify FIPS-CC Mode Using Workspace ONE on iOS Endpoints
- Enable FIPS Mode on Linux EndPoints with Ubuntu or RHEL
- Enable and Verify FIPS-CC Mode Using Microsoft Intune on Android Endpoints
- FIPS-CC Security Functions
- Resolve FIPS-CC Mode Issues
-
-
- Remote Access VPN (Authentication Profile)
- Remote Access VPN (Certificate Profile)
- Remote Access VPN with Two-Factor Authentication
- GlobalProtect Always On VPN Configuration
- Remote Access VPN with Pre-Logon
- User-Initiated Pre-Logon Connection
- GlobalProtect Multiple Gateway Configuration
- GlobalProtect for Internal HIP Checking and User-Based Access
- Mixed Internal and External Gateway Configuration
- Captive Portal and Enforce GlobalProtect for Network Access
- GlobalProtect on Windows 365 Cloud PC
-
- About GlobalProtect Cipher Selection
- Cipher Exchange Between the GlobalProtect App and Gateway
-
- Reference: GlobalProtect App Cryptographic Functions
-
- Reference: TLS Ciphers Supported by GlobalProtect Apps on macOS Endpoints
- Reference: TLS Ciphers Supported by GlobalProtect Apps on Windows Endpoints
- Reference: TLS Ciphers Supported by GlobalProtect Apps on Android 6.0.1 Endpoints
- Reference: TLS Ciphers Supported by GlobalProtect Apps on iOS 10.2.1 Endpoints
- Reference: TLS Ciphers Supported by GlobalProtect Apps on Chromebooks
- Ciphers Used to Set Up IPsec Tunnels
- SSL APIs
-
- View a Graphical Display of GlobalProtect User Activity in PAN-OS
- View All GlobalProtect Logs on a Dedicated Page in PAN-OS
- Event Descriptions for the GlobalProtect Logs in PAN-OS
- Filter GlobalProtect Logs for Gateway Latency in PAN-OS
- Restrict Access to GlobalProtect Logs in PAN-OS
- Forward GlobalProtect Logs to an External Service in PAN-OS
- Configure Custom Reports for GlobalProtect in PAN-OS
-
6.3
- 6.3
- 6.2
- 6.1
- 6.0
- 5.1
-
- Download and Install the GlobalProtect App for Windows
- Use Connect Before Logon
- Use Single Sign-On for Smart Card Authentication
- Use the GlobalProtect App for Windows
- Report an Issue From the GlobalProtect App for Windows
- Disconnect the GlobalProtect App for Windows
- Uninstall the GlobalProtect App for Windows
- Fix a Microsoft Installer Conflict
-
- Download and Install the GlobalProtect App for macOS
- Use the GlobalProtect App for macOS
- Report an Issue From the GlobalProtect App for macOS
- Disconnect the GlobalProtect App for macOS
- Uninstall the GlobalProtect App for macOS
- Remove the GlobalProtect Enforcer Kernel Extension
- Enable the GlobalProtect App for macOS to Use Client Certificates for Authentication
-
6.1
- 6.1
- 6.0
- 5.1
-
6.3
- 6.3
- 6.2
- 6.1
- 6.0
- 5.1
Configure a Split Tunnel Based on the Domain and Application
Configure a split tunnel based on the destination domain
and application.
When you configure a split tunnel to include
all traffic—IPv4 and IPv6—based the destination domain and port (optional)
or application, all traffic going to that specific domain or application
is sent through the VPN tunnel for inspection and policy enforcement.
For example, you can allow all Salesforce traffic to go through
the VPN tunnel using the *Salesforce.com destination domain. By
including all Salesforce traffic in the VPN tunnel, you can provide
secure access to the entire Salesforce domain and subdomains. You
can configure a split tunnel without specifying a destination IP
address subnet, which extends the split tunnel capability to domains
and applications with dynamic public IP addresses, such as SaaS
and public cloud applications.
When you configure a split
tunnel to exclude traffic—IPv4 and IPv6—based on the destination
domain and port (optional) or application, all traffic for that
specific application or domain is sent directly to the physical
adapter on the endpoint without inspection. For example, you can
exclude all Skype traffic from the VPN tunnel using the C:\Program
Files (x86)\Skype\Phone\Skype application process name.
Follow
these recommendations when configuring a split tunnel based on the
destination domain and application:
- With a GlobalProtect license, you can enforce or apply split tunnel rules based on the destination domain and application to Windows and macOS endpoints.
- On Linux endpoints running GlobalProtect app 6.1 or later you can apply split tunnel rules based on domain or access route only; split tunneling based on application is not supported on Linux endpoints.
- On Windows devices, domain-based tunneling supports TCP traffic only; UDP traffic is not supported in domain-based split tunneling on Windows.
- ICMP requests such as for latency, jitter, trace route tests are not supported for split tunneling based on the destination domain.
- Supported on endpoints with Windows 7 Service Pack 2 and later releases and macOS 10.10 and later releases.
Use the following steps to configure
a split tunnel to include or exclude traffic based on the destination
domain or application process name.
- Before you begin:
- Select NetworkGlobalProtectGateways<gateway-config> to modify an existing gateway or add a new one.
- Enable a split tunnel.
- In the GlobalProtect Gateway Configuration dialog, select AgentTunnel Settings to enable Tunnel Mode.
- Configure the tunnel parameters for the GlobalProtect app.
- (Tunnel Mode only) Configure split tunnel settings based on the destination domain. These settings are assigned to the virtual network adapter on the endpoint when the GlobalProtect app establishes a tunnel with the gateway.You can apply DNS traffic in addition to network traffic if you have already specified Both Network Traffic and DNS as the Split-Tunnel Option in the App Configurations area of your GlobalProtect portal.
- In the GlobalProtect Gateway Configuration dialog, select AgentClient Settings<client-setting-config> to select an existing client settings configuration or add a new one.
- (Optional) Add the SaaS or public cloud applications that you want to route to GlobalProtect through the VPN connection using the destination domain and port (Split TunnelDomain and ApplicationInclude Domain). You can add up to 200 entries to the list. For example, add *.gmail.com to allow all Gmail traffic to go through the VPN tunnel.
- (Optional) Add the SaaS or public cloud applications that you want to exclude from the VPN tunnel using the destination domain and port (Split TunnelDomain and ApplicationExclude Domain). You can add up to 200 entries to the list. For example, add *.target.com to exclude all Target traffic from the VPN tunnel.
- Click OK to save the split tunnel settings.
- (Tunnel Mode only) Configure split tunnel settings based on the application.Safari traffic cannot be added to the application-based split tunnel rule on macOS endpoints.You can use environment variables to configure a split tunnel based on the application on Windows and macOS endpoints.
- In the GlobalProtect Gateway Configuration dialog, select AgentClient Settings<client-setting-config> to select an existing client settings configuration or add a new one.
- (Optional) Add the SaaS or public cloud applications that you want to route to GlobalProtect through the VPN connection using the application process name (Split TunnelDomain and ApplicationInclude Client Application Process Name. You can add up to 200 entries to the list. For example, add /Applications/RingCentral for Mac.app/Contents/MacOS/Softphone to allow all RingCentral-based traffic to go through the VPN tunnel on macOS endpoints.
- (Optional) Add the SaaS or public cloud applications that you want to exclude from the VPN tunnel using the application process name (Split TunnelDomain and ApplicationExclude Client Application Process Name). You can add up to 200 entries to the list. For example, add /Applications/Microsoft Lync.app/Contents/MacOS/Microsoft Lync to exclude all Microsoft Lync application traffic from the VPN tunnel.
- Click OK to save the split tunnel settings.
- Save the gateway configuration.
- Click OK to save the gateway configuration.
- Commit your changes.