Focus

Prisma Access

Changes to Default Behavior for Prisma Access 5.2, 5.2.1, and 5.2.2

Table of Contents

Filter

Expand All | Collapse All

Prisma Access Docs

Release Notes
Select a Document
- 6.0 Preferred and Innovation
- 5.2 Preferred and Innovation
- 5.1 Preferred and Innovation
- 5.0 Preferred and Innovation
- 4.2 Preferred
- 4.1 Preferred
- 4.0 Preferred
- 3.2 Preferred and Innovation
- 3.1 Preferred and Innovation
- 3.0 Preferred and Innovation
- 2.2 Preferred
Activation & Onboarding
Administration
Select a Document
- 4.0 & Later
- Prisma Access China
Integrations
Incidents & Alerts

New Features in Prisma Access 5.2, 5.2.1, and 5.2.2

Prisma Access Known Issues

Changes to Default Behavior for `Prisma Access` 5.2, 5.2.1, and 5.2.2

Where Can I Use This?	What Do I Need?
Prisma Access (Managed by Strata Cloud Manager) Prisma Access (Managed by Panorama)	`Prisma Access` license Minimum Required Prisma Access Version 5.2, 5.2.1, or 5.2.2 Preferred or Innovation

The following sections detail the changes in default behavior for Prisma Access version 5.2, version 5.2.1, and version 5.2.2.

Changes to Default Behavior for `Prisma Access` 5.2.2

The following table details the changes in default behavior for Prisma Access version 5.2.2.

Component	Change
South Korea Mobile Users—GlobalProtect Location Group Remapping	Before the `Prisma Access` 5.2.2 infrastructure upgrade, the Location Group for the South Korea location is mapped to a group that also contains Japan South and Japan Central. After the `Prisma Access` 5.2.2 infrastructure upgrade, the South Korea location is mapped to its own location group. If you have IP address pools configured for the Japan South, Japan Central, and South Korea location group, `Prisma Access` uses IP addresses from the Worldwide IP address pool instead of the location group in the following cases: If a Mobile Users—GlobalProtect location in South Korea adds a cloud gateway as a result of an autoscale event. If you add a new Prisma Access—Mobile Users (GlobalProtect) location in South Korea. To use IP pools for the remapped South Korea location group, add a new IP pool for the South Korea location group after the `Prisma Access` 5.2.2 infrastructure upgrade.

Component

Change

South Korea Mobile Users—GlobalProtect Location Group Remapping

Before the Prisma Access 5.2.2 infrastructure upgrade, the Location Group for the South Korea location is mapped to a group that also contains Japan South and Japan Central.

After the Prisma Access 5.2.2 infrastructure upgrade, the South Korea location is mapped to its own location group.

If you have IP address pools configured for the Japan South, Japan Central, and South Korea location group, Prisma Access uses IP addresses from the Worldwide IP address pool instead of the location group in the following cases:

If a Mobile Users—GlobalProtect location in South Korea adds a cloud gateway as a result of an autoscale event.
If you add a new Prisma Access—Mobile Users (GlobalProtect) location in South Korea.

To use IP pools for the remapped South Korea location group, add a new IP pool for the South Korea location group after the Prisma Access 5.2.2 infrastructure upgrade.

Changes to Default Behavior for `Prisma Access` 5.2.1

The following table details the changes in default behavior for Prisma Access version 5.2.1.

Component	Change
IP Optimization Enabled for New Prisma Access Deployments	To enable faster onboarding of `Prisma Access` tenants and simplify IP address allow listing, new `Prisma Access` deployments have IP Optimization enabled. IP Optimization deployments do not support IPv6 for access to public (external) apps; private app access is supported. To enable IPv6 for your new `Prisma Access` deployment, reach out to your Palo Alto Networks account team, who will open a TAC case to accommodate the request. Be sure that all users are running a GlobalProtect app version of 6.1.4 and later, 6.2.3 and later, or 6.3.0 and later before setting up a new `Prisma Access` deployment. New FedRAMP deployments do not have IP Optimization enabled.
Default Mobile Users—GlobalProtect IP Address Pool Changed for New Prisma Access (Managed by Strata Cloud Manager) Deployments	New Prisma Access (Managed by Strata Cloud Manager) Mobile Users—GlobalProtect deployments has a new default IP address pool: 100.92.0.0/16. This is a change from previous deployments that used a default IP address pool of 100.127.0.0/16. You can use this RFC6598 pool for the majority of use cases, including for private app access for mobile users. If you require more IP addresses, you can add them in the Prisma Access UI.
IP Address Consolidation for Deployments that Have Migrated to IP Optimization	If you have an existing Prisma Access that has had one or more regions migrated to IP Optimization and are using Prisma Access Allow listing, some IP addresses that you have allow listed have moved from the Allocated Egress IP addresses area to the Allocated Ingress IP addresses area in the `Prisma Access` UI. This change is a result of IP address consolidation as a part of the Prisma Access 5.2.1 infrastructure upgrade. Your networks can still reach these IP addresses and you no longer have to allow list them.