Focus

Prisma Access

Changes to Default Behavior

Table of Contents

Filter

Expand All | Collapse All

Prisma Access Docs

Release Notes
Select a Document
- 6.2 Preferred and Innovation
- 6.1 Preferred and Innovation
- 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
Activation & Onboarding
Administration
Select a Document
- 4.0 & Later
- Prisma Access China
Integrations
Incidents & Alerts

Software and Feature Prerequisites

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 Prisma Access 6.2 version required.

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

Component	Change
Remapped Ukraine Location	To better optimize the performance of Prisma Access, the Ukraine location is remapped from the Germany Central to the Poland compute location. New deployments have the new remapping applied automatically. 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 Prisma Access location.

Component

Change

Remapped Ukraine Location

To better optimize the performance of Prisma Access, the Ukraine location is remapped from the Germany Central to the Poland compute location.

New deployments have the new remapping applied automatically. 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 Prisma Access location.

The following table details the changes in default behavior for Prisma Access version 6.20-h2.

Component	Change
Internal Host Detection	During MU onboarding, the Internal Host Detection value is now strictly mapped to the DEFAULT Agent Settings profile in the portal. Strict Mapping: The IHD value will only copy to the DEFAULT named Agent Settings profile. It will no longer automatically fall back to the first or top-most Agent Settings profile if DEFAULT is absent. No Profile Fallback: If a DEFAULT Agent Settings profile does not exist in the portal, the IHD value will not be applied to any alternative Agent Settings profiles. Admin Control: Administrators retain full flexibility to manually update or modify the IHD value directly within the DEFAULT portal Agent Settings at any time. If you delete the internal host detection configuration from the Default settings, make sure that you remove the internal host detection configuration here as well.

Component

Change

Internal Host Detection

During MU onboarding, the Internal Host Detection value is now strictly mapped to the DEFAULT Agent Settings profile in the portal.

Strict Mapping: The IHD value will only copy to the DEFAULT named Agent Settings profile. It will no longer automatically fall back to the first or top-most Agent Settings profile if DEFAULT is absent.
No Profile Fallback: If a DEFAULT Agent Settings profile does not exist in the portal, the IHD value will not be applied to any alternative Agent Settings profiles.
Admin Control: Administrators retain full flexibility to manually update or modify the IHD value directly within the DEFAULT portal Agent Settings at any time.

If you delete the internal host detection configuration from the Default settings, make sure that you remove the internal host detection configuration here as well.

Software and Feature Prerequisites

Prisma Access Known Issues

Prisma Access Docs

Changes to Default Behavior

Prisma Access Docs

Changes to Default Behavior

Activation and Onboarding

Next-Generation Firewalls

SASE

Cloud-Delivered Security Services

Network Security

Endpoints

Visibility & Monitoring

FedRAMP

Hardware Reference

Hardware Quick Start Guides

Virtual ION Deployment

3rd Party Integrations

Best Practices

Experts Corner