GlobalProtect
Tunnel Connections Over Proxies
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
Tunnel Connections Over Proxies
You can now configure the GlobalProtect app to use proxies
or bypass proxies.
On Windows and macOS platforms, you can configure GlobalProtect to bypass proxies so
that all HTTP/HTTPS traffic that matches the proxy/PAC file rules is required to
traverse the GlobalProtect VPN tunnel before reaching the intended destination. When
you configure the option to bypass proxies, you can prevent users from setting up a
personal proxy to access web resources without going through the VPN tunnel for
inspection and policy enforcement.
If you enable GlobalProtect to use proxies on Windows endpoints, only the HTTP/HTTPS
traffic that matches the proxy/PAC file rules goes through the proxy directly after
users establish the GlobalProtect connection. All other traffic that matches the
access routes configured on the GlobalProtect gateway goes through the tunnel
established over the proxy. On macOS endpoints, proxies are disabled after users
establish the GlobalProtect connection. This occurs because proxy settings are not
copied from the physical network adapter of the endpoint to the virtual network
adapter of the endpoint, and the virtual network adapter becomes the primary adapter
from which the macOS endpoint receives proxy settings.
The following tables describe network traffic behavior based on the endpoint OS,
tunnel type, and GlobalProtect proxy use.
Tunnel Type
|
GlobalProtect Uses Proxies
|
GlobalProtect Bypasses Proxies
|
---|---|---|
SSL
|
![]() |
![]() |
1—All login requests go through the proxy.
|
1—All login requests bypass the proxy and go directly
to the gateway.
| |
2—SSL tunnel setup goes through the proxy.
|
2—SSL tunnel setup bypasses the proxy and goes
directly to the gateway.
| |
3—HTTP/HTTPS traffic that matches the proxy/PAC file
rules goes through the proxy and bypasses the SSL
tunnel.
|
3—HTTP/HTTPS traffic that matches the proxy/PAC file
rules goes through the SSL tunnel and then through the
proxy.
If the proxy is unreachable from the gateway, HTTP/HTTPS
traffic is dropped, and users cannot access the intended
destination. | |
4—Other traffic that matches the access routes
configured on the gateway goes through the SSL tunnel built
over the proxy.
|
4—Other traffic that matches the access routes
configured on the gateway bypasses the proxy and goes
through the SSL tunnel.
| |
IPSec
|
![]() You cannot set up an IPSec tunnel through a proxy because
proxies do not support UDP traffic. |
![]() |
1—All login requests go through the proxy.
|
1—All login requests bypass the proxy and go directly
to the gateway.
| |
2—IPSec tunnel setup bypasses the proxy and goes
directly to the gateway.
|
2—IPSec tunnel setup bypasses the proxy and goes
directly to the gateway.
| |
3—HTTP/HTTPS traffic that matches the proxy/PAC file
rules goes through the proxy and bypasses the IPSec
tunnel.
|
3—HTTP/HTTPS traffic that matches the proxy/PAC file
rules goes through the IPSec tunnel and then through the
proxy.
If the proxy is unreachable from the gateway, HTTP/HTTPS
traffic is dropped, and users cannot access the intended
destination. | |
4—Other traffic that matches the access routes
configured on the gateway bypasses the proxy and goes
through the IPSec tunnel.
|
4—Other traffic that matches the access routes
configured on the gateway bypasses the proxy and goes
through the IPSec tunnel.
|
Tunnel Type
|
GlobalProtect Uses Proxies
|
GlobalProtect Bypasses Proxies
|
---|---|---|
SSL
|
![]() |
![]() |
1—All login requests go through the proxy.
|
1—All login requests go through the proxy.
| |
2—SSL tunnel setup goes through the proxy.
|
2—SSL tunnel setup bypasses the proxy and goes
directly to the gateway.
| |
3—HTTP/HTTPS traffic that matches the proxy/PAC file
rules goes through the SSL tunnel built over the proxy.
|
3—HTTP/HTTPS traffic that matches the proxy/PAC file
rules bypasses the proxy and goes through the SSL
tunnel.
| |
4—Other traffic that matches the access routes
configured on the gateway goes through the SSL tunnel built
over the proxy.
|
4—Other traffic that matches the access routes
configured on the gateway bypasses the proxy and goes
through the SSL tunnel.
| |
IPSec
|
![]() You cannot set up an IPSec tunnel through a proxy because
proxies do not support UDP traffic. | |
1—All login requests go through the proxy.
| ||
3—IPSec tunnel setup bypasses the proxy and goes
directly to the gateway.
| ||
3—HTTP/HTTPS traffic that matches the proxy/PAC file
rules bypasses the proxy and goes through the IPSec
tunnel.
| ||
4—Other traffic that matches the access routes
configured on the gateway bypasses the proxy and goes
through the IPSec tunnel.
|