Configure a split tunnel based on the destination domain
and application.
| Where Can I Use This? | What Do I Need? |
- NGFW (managed by Panorama or Strata Cloud Manager)
- Prisma Access (managed by Panorama or Strata Cloud
Manager)
|
- GlobalProtect Gateway license or Prisma Access license
with the Mobile User subscription
|
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.