>
    Changes to Default Behavior for Prisma Access 5.0 and 5.0.1
    Focus
    Download PDF
    Focus
    1. Home
    2. Prisma Access
    3. Prisma Access Release Information
    4. Changes to Default Behavior for Prisma Access 5.0 and 5.0.1
    Download PDF
    Prisma Access

    Changes to Default Behavior

    Table of Contents

    Changes to Default Behavior for
    Prisma Access
     5.0 and 5.0.1

    Where Can I Use This?
    What Do I Need?
    • Prisma Access (Managed by Strata Cloud Manager)
    • Prisma Access (Managed by Panorama)
    • Minimum Required Prisma Access Version
       5.0 Preferred or Innovation

    Changes to Default Behavior for Prisma Access 5.0

    The following table details the changes in default behavior for the Cloud Services plugin version 5.0.
    Component
    Change
    Upgrade Considerations for the PAN-OS 10.2.8 Dataplane
    If you choose to have Palo Alto Networks upgrade your dataplane to PAN-OS 10.2.8, make sure that you're aware of the following 10.2-specific changes and upgrade considerations before you schedule the upgrade:
    Upgrade Considerations for Using a PAN-OS 11.1 Panorama to Manage Prisma Access
    (
    Panorama Managed Deployments Only
    ) Starting with Release 5.0, you can use a Panorama running PAN-OS 11.1 to manage Prisma Access. Before you upgrade your Panorama to 11.1, make sure that you're aware of the following 11.1-specific changes and upgrade considerations:
    Upgrading the Panorama that manages Prisma Access to 11.1 does not unlock 11.1 features in Prisma Access.
    Local Zones Disabled by Default
    Local zones place compute, storage, database, and other services close to large population and industry centers and have their own compute locations; however they don't support all Prisma Access features and functionality. For this reason, local zones are not enabled by default; contact your Palo Alto Networks team to enable them.
    Configuring Multiple Portals Disabled by Default
    The ability to configure multiple portals in Prisma Access is disabled by default. Contact your Palo Alto Networks team to enable this functionality.

    Changes to Default Behavior for Prisma Access 5.0.1

    The following table details the changes in default behavior for the Cloud Services plugin version 5.0.1.
    Component
    Change
    Remapped Saudi Arabia Location
    To better optimize the performance of Prisma Access, starting with the Prisma Access 5.0.1 infrastructure upgrade, the Saudi Arabia location is remapped to the Saudi Arabia compute location.
    This remapping applies to all existing Prisma Access deployments, even if you have not installed the Cloud Services plugin 5.0. Your current compute location-to-location mapping isn't 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 Prisma Access location.
    New deployments have this mapping applied automatically.
    License Enforcement Changes for Mobile Users
    As part of the license enforcement enhancements for mobile users, Prisma Access tracks the number of unique mobile users over the last 30 days instead of 90 days (the previous setting), to ensure that you have purchased the proper license tier for your user base. Palo Alto Networks might enforce stricter policing of user licenses if continued overages occur. This change is applicable for all types of mobile user licenses.
    Username Normalization
    To better standardize usernames across your organization, all usernames in Prisma Access have been normalized.
    For example, these usernames are normalized to the username
    test.user
    :
    • test.User@abc.com
    • abc/Test.User
    • abc//Test.useR
    This functionality does not affect security policy rules based on user groups and members that you've configured using the Cloud Identity Engine.

    Recommended For You

    © 2024 Palo Alto Networks, Inc. All rights reserved.