Filter

Expand All | Collapse All

Prisma Access Docs

Administration
Version
- Prisma Access China
- 4.0 & Later
- 3.2 Preferred and Innovation
- 3.1 Preferred and Innovation
- 3.0 Preferred and Innovation
- 2.2 Preferred
Integrations
Incidents & Alerts
Release Notes
Version
- 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

Focus

Prisma Access

Changes to Default Behavior

Table of Contents

Filter

Expand All | Collapse All

Prisma Access Docs

Administration
Version
- Prisma Access China
- 4.0 & Later
- 3.2 Preferred and Innovation
- 3.1 Preferred and Innovation
- 3.0 Preferred and Innovation
- 2.2 Preferred
Integrations
Incidents & Alerts
Release Notes
Version
- 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

New Features in Prisma Access 4.0

Prisma Access Known Issues

Changes to Default Behavior

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` 4.0 Preferred

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

Component	Change
169.254.0.0/16 Subnet Disallowed in the `Prisma Access` Infrastructure	Because of the introduction of Support for RFC 6598 Addresses in the Prisma Access Infrastructure IP Addresses, you can no longer specify the use of the 169.254.0.0/16 subnet for the following `Prisma Access` infrastructure addresses: Securing Inbound Access to Remote Network Locations Overlapping Subnets with Remote Network Locations Traffic Steering Infrastructure subnet IP addresses IP address pools used in Mobile Users—GlobalProtect deployments Static subnets used for service connections and remote networks
Remapped Poland Location	To better optimize performance of `Prisma Access`, starting with the `Prisma Access` 4.0 infrastructure upgrade, the Poland location is remapped to the Europe Central (Warsaw) compute location. This remapping applies to all existing `Prisma Access` deployments, even if you have not installed the Cloud Services plugin 4.0. Your current compute location-to-location mapping is not affected; however, if you have an existing `Prisma Access` deployment that uses one of these locations and you want to take advantage of the remapped compute location, follow the procedure to add a new compute location to a deployed . New deployments have this mapping applied automatically.
Bulk Import of Remote Networks	The number of remote networks that you can onboard in bulk using a CSV file has changed from 1000 to 100.

New Features in Prisma Access 4.0

Prisma Access Known Issues