GlobalProtect
Changes to Default Behavior
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.0
- 6.3
- 6.2
- 6.1
- 6.0
- 5.1
Changes to Default Behavior
Changes to default behavior in GlobalProtect app 6.0.
The following topics describe changes to default behavior in GlobalProtect app 6.0 versions:
- Changes to Default Behavior in GlobalProtect App 6.0.12
- Changes to Default Behavior in GlobalProtect App 6.0.11
- Changes to Default Behavior in GlobalProtect App 6.0.10
- Changes to Default Behavior in GlobalProtect App 6.0.8
- Changes to Default Behavior in GlobalProtect App 6.0.7
- Changes to Default Behavior in GlobalProtect App 6.0.6
- Changes to Default Behavior in GlobalProtect App 6.0.5
- Changes to Default Behavior in GlobalProtect App 6.0.4
- Changes to Default Behavior in GlobalProtect APP 6.0.3
- Changes to Default Behavior in GlobalProtect App 6.0.2
- Changes to Default Behavior in GlobalProtect App 6.0.1
- Changes to Default Behavior in GlobalProtect App 6.0.0
Changes to Default Behavior in GlobalProtect App 6.0.12
There are no changes in default behavior in GlobalProtect app version 6.0.12.
Changes to Default Behavior in GlobalProtect App 6.0.11
You can now use the new system extension type Non-removable system
extensions from UI introduced by Jamf Pro for the devices running on
macOS 15 Sequoia or later versions to prevent the end users from disabling the
GlobalProtect system extensions on the endpoints. GlobalProtect app
version 6.0.11 and later supports macOS 15 Sequoia. This functionality is available
only for the devices running on macOS 15 Sequoia or later versions.
You can configure this feature to prevent the end users from disabling GlobalProtect
system extensions on their endpoints thereby reducing the risks associated with
disabled system extensions.
Previously, end users could disable the GlobalProtect system extension through the
MDM settings (GeneralSettingsNetwork Extensions.) However, with this new feature, the Non-removable system
extensions from UI system extension type in Jamf Pro restricts users
from disabling the GlobalProtect system extension.
To enable this functionality, you must perform the following procedures:
- Upgrade the GlobalProtect app to version 6.0.11 or later
- Upgrade the macOS to version 15 Sequoia or later
- In the mobile device management (MDM), Jamf Pro, set the System Extension Type as Non-removable system extensions from UI while configuring Configuration Profile.
If the GlobalProtect system extensions are disabled by the end-user, the following
GlobalProtect features do not work:
- Enforcer
- Split-tunnel by domain
- Split-tunnel by app
- Split-DNS
- Traffic Enforcement
Changes to Default Behavior in GlobalProtect App 6.0.10
There are no changes in default behavior in GlobalProtect app version 6.0.10.
Changes to Default Behavior in GlobalProtect App 6.0.8
There are no changes in default behavior in GlobalProtect app version 6.0.8.
Changes to Default Behavior in GlobalProtect App 6.0.7
There are no changes in default behavior in GlobalProtect app version 6.0.7.
Changes to Default Behavior in GlobalProtect App 6.0.6
There are no changes in default behavior in GlobalProtect app version 6.0.6.
Changes to Default Behavior in GlobalProtect App 6.0.5
Beginning with GlobalProtect app 6.0.5, the first time
users launch the GlobalProtect app for Android, they will be prompted
to read and acknowledge a disclosure about the information that
may be collected by the app.
Changes to Default Behavior in GlobalProtect App 6.0.4
ADEM agent installer has been bundled with GlobalProtect
installer since GlobalProtect version 5.2.6. ADEM installer bundled
with GlobalProtect version 6.0.4 has been updated and contains the
new ADEM Self-Serve feature
due to which there is a notable increase in the size of the GlobalProtect
installer.
Changes to Default Behavior in GlobalProtect App 6.0.3
There are no changes to default behavior in GlobalProtect
app 6.0.3.
Changes to Default Behavior in GlobalProtect App 6.0.2
There are no changes to default behavior in GlobalProtect
app 6.0.2.
Changes to Default Behavior in GlobalProtect App 6.0.1
There are no changes to default behavior in GlobalProtect
app 6.0.1.
Changes to Default Behavior in GlobalProtect App 6.0.0
(Windows only) Starting with GlobalProtect
app 6.0, the GlobalProtect virtual adapter name on Windows endpoint
has been changed from PANGP Virtual Ethernet Adapter to PANGP Virtual Ethernet Adapter Secure.
The addition of the keyword secure ensures that Microsoft delivery optimization and
peer caching can identify that a device is connected to a VPN. This
change ensures that delivery optimization and peer caching work
properly for a large number of Windows updates, upgrades, and application
downloads.