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.3
- 6.3
- 6.2
- 6.1
- 6.0
- 5.1
Changes to Default Behavior
Changes to default behavior in GlobalProtect app 6.3.
Changes to Default Behavior in GlobalProtect App 6.3.2
There are no changes in default behavior in GlobalProtect app version 6.3.2
Changes to Default Behavior in GlobalProtect App 6.3.1
The following topics describe changes to default behavior in GlobalProtect app
6.3.1:
- Starting from GlobalProtect 6.3.1, if you set the Enable Intelligent Internal
Host Detection parameter to yes, GlobalProtect is unable to discover the
external network. This triggers the network discovery retry mechanism and
GlobalProtect retries network discovery in 5, 10, 20, and then 30 second
intervals until internal host detection is resolved to an internal gateway (for
example, Cisco AnyConnect). If the parameter is set as no (the default value), the GlobalProtect app first connects to the internal gateway followed by the external gateway upon connection failure.
- Starting from GlobalProtect version 6.3.1, when you configure Tunnel and Proxy mode for the
GlobalProtect app along with Always-on mode as the connect method and you want
to disconnect the Tunnel and Proxy mode, you must perform
the following steps:
- Disconnect the GlobalProtect app to disconnect the tunnel (VPN) connection. When you disconnect the app, the tunnel (VPN) connection gets disconnected and the app will still be connected through the proxy mode.
- Disable the GlobalProtect app to disconnect both the tunnel and proxy mode. When you disable the app, both the tunnel and proxy mode will be disconnected and the app will not be connected anymore.
Changes to Default Behavior in GlobalProtect App 6.3
The following topics describe changes to default behavior in GlobalProtect app
6.3.0:
- (Windows Only) Starting with GlobalProtect app 6.3, the maximum value for User Switch Tunnel Rename Timeout app setting of the GlobalProtect portal configuration is increased from 600 sec to 7200 secs. With this enhancement, you can configure the app to stay connected for a longer period (the range is 0-7200 seconds, the default value is 0) when end users switch the RDP connections. End users are prompted to reenter their credentials and authenticate to the app when they switch the RDP connections. GlobalProtect app will get disconnected if they fail to reenter the credentials before the expiry of the set User Switch Tunnel Rename Timeout.Previously, the time range that you can configure for User Switch Tunnel Rename Timeout in the app settings was 0-600 secs.
- Starting with GlobalProtect app 6.3, the Connect with SSL Only option has been renamed. See the table below information about the changes.
GlobalProtect Release Version Available Options GlobalProtect version earlier than 6.3 Field name: Connect with SSL Only- Yes
- No
- User can ChangeThis is the default value.
GlobalProtect version 6.3 and later Field name: Advanced Control for Tunnel Mode Behavior- No
- Connect with SSL Only
- Connect with SSL Only - User can
Change
This is the default value.
- IPSec Only
If you are using the existing Connect with SSL Only feature, the same options will be available for you with no behavior change. - Starting with Content Release version 8845-8731, the Autonomous DEM endpoint agent for Prisma Access parameter on the App tab of the GlobalProtect portal in Panorama Managed Prisma Access been renamed. The parameter name and available options depend on the GlobalProtect release version in your environment.
GlobalProtect Release Version Configuration Name Configuration Options GlobalProtect 6.3 and later Access Experience (ADEM, App Acceleration, End user coaching) for GP 6.3 and above (Windows & MAC only) - Install the Agent
- Uninstall the Agent
- No action
This is the default value.
GlobalProtect 6.2 and earlier Autonomous DEM endpoint agent for Prisma Access for GP version 6.2 and below - Install and user cannot enable/disable agent from GlobalProtect
- Install and user can enable/disable agent from GlobalProtect
- Do not install
This is the default value.
There is no change if the Content Release version in your environment is earlier than 8845-8731. - The GlobalProtect app now displays the following message when there are network connectivity issues in the user environment:The connection from this device to GlobalProtect Gateway has been interrupted for the keep-alive timeout duration. Please check your network connectivity and re-connect.
- The maximum value for User Switch Tunnel Rename Timeout
has been increased from 600 seconds to 7200 seconds. To set the value for this
parameter, follow the navigation path as follows:
- Select NetworkGlobalProtectPortals.
- Select a portal.
- On the Agent tab, select the agent configuration that you want to modify.
- Select the App tab.
- In the App Configurations area, specify the desired value forUser Switch Tunnel Rename Timeout.