Configure Prisma Access for Users

When you configure Prisma Access for users, you will need to define the settings to configure the portal and gateways in the cloud. For example, you will define a portal hostname, set up the IP address pool for your mobile users, and configure DNS settings for your internal domains. You may be able to leverage using existing configurations for some of the required settings, such as what authentication profile to use to authenticate mobile users. If you already have a template with your authentication profiles, certificates, certificate profiles, and server profiles, you can add that template to the predefined template stack during onboarding to simplify the setup process.
While it is not necessary to push your Security policy settings and objects to the cloud during the onboarding process, if you already have device groups and templates with the configuration objects you need (for example, Security policy, zones, User-ID configuration, and other policy objects) go ahead and add them when you onboard. This way you can to complete the zone mapping that is required to enable Prisma Access to map the zones in your policy to the appropriate interfaces and zones within the cloud. However, if you don’t have your policy set yet, you can go back later and push it to Prisma Access for users.
In addition, if you want your mobile users to be able to connect to your remote network locations, or if you have mobile users in different geographical areas who need direct access to each other’s endpoints, you must configure at least one service connection with placeholder values, even if you don’t plan to use the connection to provide access to your data center or HQ locations. The reason this is required is because, while all remote network locations are fully meshed, Prisma Access gateways (also known as
locations
) connect to the service connection in a hub-and-spoke architecture to provide access to the internal networks in your Prisma Access infrastructure.
  1. Select
    Panorama
    Cloud Services
    Configuration
    Mobile Users
    .
  2. Configure the template stack and device group hierarchy that the cloud service will push to the portal and gateway.
    1. Edit the
      Settings
      .
      prisma-access-users-edit-settings.png
    2. In the Templates section of the
      Settings
      tab,
      Add
      the template that contains the configuration you want to push to Prisma Access for users.
      Although you can add existing templates to the stack from the plugin, you cannot create a new template from the plugin. Instead, use the workflow to add a new template.
      You can
      Add
      more than one existing template to the stack and then order them appropriately using
      Move Up
      and
      Move Down
      . This is important because Panorama evaluates the templates in the stack from top to bottom and settings in templates that are higher in the stack take priority over the same settings specified in templates that are lower in the stack. You cannot move the default Mobile_User_Template from the top of the stack; this prevents you from overriding any settings that Prisma Access requires to create the network infrastructure in the cloud.
      If you want to customize the agent configuration that the Prisma Access for users pushes to clients from the portal, you must edit the GlobalProtect Portal configuration in the Mobile_User_Template to add a new agent configuration. After configuring the Agent configuration, move it above the DEFAULT agent configuration that is predefined in the template to ensure that your settings take precedence over the default settings. When editing this template, do not remove or change the External Gateway entry.
      gp-agent-default-config-1.png
    3. In the Device Group section, select the
      Parent Device Group
      that contains the configuration settings you want to push to Prisma Access for users, or leave the parent device group as
      Shared
      to use the Prisma Access device group shared hierarchy.
      You will push all of the configuration—including the address groups, Security policy, Security profiles, and other policy objects (such as application groups and objects), HIP objects and profiles and authentication policy—that Prisma Access for users needs to enforce consistent policy to your mobile users using the device group hierarchy you specify here. In addition, you must make sure that you have configured a Log Forwarding profile that forwards the desired log types to
      Panorama/Logging Service
      in a device group that gets pushed to Prisma Access for users; this is the only way that the cloud service knows which logs to forward to Cortex Data Lake.
      prisma-access-template-dg-1-6.png
  3. (
    Optional
    ) Configure Prisma Access to use the Directory Sync service to retrieve user and group information.
    You must configure Directory Sync to retrieve user and group information from your Active Directory (AD) before you enable and configure Directory Sync integration in Prisma Access using the settings in the
    Group Mapping Settings
    tab. See Get User and Group Information Using Directory Sync for details.
  4. Click
    OK
    to save the mobile user settings.
  5. Map the zones configured within the selected template stack as trusted or untrusted.
    On a Palo Alto Networks next-generation firewall, Security policy is enforced between zones, which map to physical or virtual interfaces on the firewall. However, with Prisma Access for users, the networking infrastructure is automatically set up for you, which means you no longer need to configure interfaces and associate them with zones. However, to enable consistent security policy enforcement, you must map the zones you use within your organization as trust or untrust so that Prisma Access for users can translate the policy rules you push to the cloud service to the internal zones within the networking infrastructure.
    1. Edit the Zone Mapping settings.
      By default, all of the zones in the Mobile_User_Template_Stack are classified as Untrusted Zones.
    2. For each zone you want to designate as trusted, select it and click
      Add
      to move it to the list of
      Trusted Zones
      .
      prisma-access-zone-mapping.png
    3. Click
      OK
      to save your changes.
  6. Configure the GlobalProtect portal and external gateway settings.
    You can configure Prisma Access gateways as external gateways only—not as internal gateways.
    1. In the Onboarding section, click
      Configure
      .
    2. On the
      General
      tab, specify the
      Portal Name Type
      :
      • Use Default Domain
        —If you select this option, your portal hostname uses the default domain name:
        .gpcloudservice.com
        . In this case, simply enter a
        Portal Hostname
        to append to the default domain name. Prisma Access for users will automatically create the necessary certificates and publish the hostname to public DNS servers.
        prisma-access-users-default-domain.png
        If you already have a GlobalProtect deployment with an existing portal name and you want to continue to use that portal name, add a CNAME entry that maps Prisma Access portal name to your existing portal name. For example, if you have an existing portal named portal.acme.com and you want to map the new Prisma Access portal to this same name, you would add a CNAME of gpcs2.gpcloudservice.com to the DNS entry for your existing portal.
      • Use Company Domain
        —Select this option if you want the domain in the portal hostname to match your company domain name (for example, myportal.mydomain.com). If you want to use this option, you must first obtain your own certificate and configure an SSL/TLS service profile that points to it. Then you can configure the portal name by selecting the
        SSL/TLS Service Profile
        and entering the
        Portal Hostname
        . If you use this option, you must point your internal DNS servers to the
        Portal DNS CNAME
        , which is the hostname of the portal with the
        .gpcloudservice.com
        domain. For example, if you specified a DNS hostname of acme-portal.acme.com, you would need to create a DNS CNAME entry that maps that hostname to acme-portal.gpcloudservice.com on your internal DNS servers.
      prisma-access-company-domain.png
    3. Select an
      Authentication Profile
      that specifies how Prisma Access should authenticate mobile users or create a new one.
      If you added a parent device group that contains an authentication profile configuration, you should see it on the list of available profiles. If you did not push the profile in the device group, you can create an authentication profile now.
    4. Select an
      Authentication Override Certificate
      to encrypt the secure cookies that mobile users authenticate to the portal and gateway.
      If you added a parent device group that contains the certificate you want to use to encrypt authentication cookies, you should see it on the list of available certificates. If you did not push a certificate in the device group, you can import or generate one now.
    5. (
      Optional
      ) If you do not require GlobalProtect endpoints to have tunnel connections when on the internal network, enable
      Internal Host Detection
      .
      1. Select the
        Internal Host Detection
        check box.
      2. Enter the
        IP Address
        of a host that users can reach only from the internal network.
      3. Enter the DNS
        Hostname
        for the IP address you entered. Clients that try to connect perform a reverse DNS lookup on the specified address. If the lookup fails, the client determines that it needs a tunnel connection to Prisma Access for users.
      Prisma Access copies the internal host detection settings you specify here to the settings in your GlobalProtect portal configuration (
      Network
      GlobalProtect
      Portals
      <
      portal-config
      >
      Agent
      <
      agent-config
      >
      Internal
      ). If you change your portal configuration settings through
      Network
      GlobalProtect
      Portals
      at a later time, those changes are not reflected in the settings you specify here. For this reason, Palo Alto Networks recommends that you either enter the internal host detection settings here or configure the same settings in both places.
  7. Select the
    Locations
    and the regions associated with those locations where you want to deploy your mobile users.
    The
    Locations
    tab displays a map. Highlighting the map shows the global regions (Americas, Europe, and Asia Pacific) and the locations available inside each region. Select a region, then select the locations you want to deploy in each region. Limiting your deployment to a single region provides more granular control over deployed regions and allows you to exclude regions as required by your policy or industry regulations. See List of Prisma Access Locations for the list of regions and locations. You can select a location in a region that is closest to your mobile users, or select a location as required by your policy or industry regulations.
    Specify a single region to reduce the minimum IP address pool that you need in Step 8. See Specify IP Address Pools for Mobile Users for more information.
    Prisma Access uses the Hong Kong, Netherlands Central, and US Northwest locations as fallback mobile user locations if other locations are not available. For this reason, Palo Alto Networks strongly recommends that you enable at least one of these locations during mobile user onboarding.
    1. Click the
      Locations
      tab and select a region.
      mobile-users-onboard-regions.png
    2. Select one or more Prisma Access gateways within your selected region using the map.
      Hovering your cursor over a location highlights it. White circles indicate an available location; green circles indicate that you have selected that location.
      mobile-users-onboard-locations.png
      In addition to the map view, you can view a list of regions and locations. Choose between the map and list view from the lower left corner. In the list view, the list displays regions sorted by columns, with all locations sorted by region. You can select
      All
      sites within a region (top of the dialog).
      mobile-users-onboard-locations-list-view.png
  8. Set up the IP address pools that Prisma Access for users uses to assign IP addresses to GlobalProtect endpoints by selecting the
    IP Pools
    tab and
    Add
    and IP address pool.
    prisma-access-ip-pools.png
    • Region
      —Select
      Worldwide
      to use a single IP address pool for all GlobalProtect clients using the cloud service or select an available region.
      You can use a single IP address pool for all GlobalProtect endpoints
      Worldwide
      , you can set separate pools for each region where you have mobile users, or you can specify both Worldwide and region-specific IP pools. For example, you can add an pool for a specific region and then add a
      Worldwide
      pool to use for all other regions. Prisma Access then uses the Worldwide IP addresses to scale as you onboard additional gateways in other regions to accommodate more mobile users. If you specify a pool for a region, and you exhaust the available IP addresses in that pool, Prisma Access will take IP addresses from the
      Worldwide
      pool to use in that region.
    • IP Pool
      —Enter an IP address pool to assign to the endpoints in the selected region. The addresses in this pool must not overlap with other networks you use internally or with the pools you assigned when you Enable the Service Infrastructure.
      If you deploy locations in a single region, the minimum required subnet is /23 (512 IP addresses) per location. Additional locations require a minimum /23 subnet. If you specify a Worldwide subnet, the minimum required subnet is /23 but we recommend providing enough subnets to allocate a number of IP addresses that is equal to or greater than the number of licensed mobile users so that they can log in at the same time. Do not use the 100.64.0.0/15 subnet, because Prisma Access reserves this subnet for its internal use. See how to Specify IP Address Pools for Mobile Users for more information.
      We recommend using an RFC 1918-compliant IP address pool. While we support the use of non-RFC 1918-compliant (public) IP addresses for mobile users, we do not recommend using these non-compliant IP addresses due to possible conflicts with internet public IP address space.
  9. To specify the DNS resolution settings that Prisma Access uses for mobile users, select
    Network Services
    tab and then click
    Add
    .
    GlobalProtect endpoints with an active tunnel connection use their virtual network adapters rather than their physical network adapters and therefore require separate DNS resolution settings. You can use a DNS settings for all GlobalProtect endpoints
    Worldwide
    , you can set separate pools for each geographic region where your users are located, or you can specify both a Worldwide and regional pools.
    • For
      Internal Domains
      :
      • Select a
        Region
        (
        North America & South America
        ,
        Africa, Europe & Middle East
        , or
        Asia, Australia & Japan
        ), or specify
        Worldwide
        to apply the DNS settings globally.
        You must specify at least one DNS proxy with a
        Region
        of
        Worldwide
        , or your commit will fail. You can also specify a DNS proxy for one or more regions and specify another
        Worldwide
        DNS proxy for the rest of the world. If you specify multiple proxy settings with a mix of regional and worldwide regions, Prisma Access uses the regional settings for the Locations in the region you specify; otherwise, Prisma Access uses the worldwide settings.
      • Specify the IP addresses of the
        Primary DNS
        and
        Secondary DNS
        servers that your mobile users should use to resolve internal domains.
      • (
        Optional
        ) If you want your internal DNS server to only resolve the domains you specify, enter the domains to resolve in the
        Domain List
        .
        You can use a wildcard (*) in front of the domains in the domain list, for example *.acme.local or .acme.com. You can specify a maximum of 1,024 domain entries.
    • For
      Public Domains
      :
      • Enter a
        Primary DNS
        choice.
        To use the default Prisma Access DNS server, select
        Use Cloud Default
        . To use the same server that you use to resolve internal domains, select
        Same as Internal Domains
        . To use a third-party or public DNS server, select
        Custom DNS Server
        , then specify the IP address of the DNS server.
      • Enter a
        Secondary DNS
        choice, choosing from the same options you chose for the
        Prisma DNS
        .
        dns-resolution-mobile-user-3rd-party-screenshot.png
      • (
        Optional
        )
        Add
        a
        Client DNS Suffix Search List
        to specify the suffix that the client should use locally when an unqualified hostname is entered that it cannot resolve, for example, acme.local. Do not enter a wildcard (*) character in front of the domain suffix. You can add multiple suffixes.
        You can also create a .csv file that has the list of domain suffixes and
        Import
        them, rather than manually adding them. Separate multiple entries with commas or semicolons such as
        www.example1.com,www.example2.com,www.example3.com
        . There is no limit to the number of DNS suffixes you can enter.
        dns-resolution-mobile-user-suffix-screenshot.png
  10. (
    Optional
    ) If your deployment uses Windows Internet Name Service (WINS) based, you can specify WINS servers to resolve NetBIOS name-to-IP address mapping by selecting
    WINS Configuration
    ; selecting a region for the WINS server or selecting Worldwide to apply the WINS configuration worldwide, then specifying a
    Primary WINS
    and, optionally,
    Secondary WINS
    server address.
    After you enable WINS, Prisma Access can push WINS configuration to mobile users’ endpoints over GlobalProtect.
    configure-wins-for-mobile-users.png
  11. (
    Optional
    ) If you allow your mobile users to manually select gateways from the GlobalProtect app, select the
    Manual Gateway Locations
    that the users can view from their GlobalProtect app.
    Choosing a subset of onboarded locations reduces the number of available gateways that mobile users can view in their GlobalProtect app for manual gateway selection.
    If you do not select manual gateways in this tab, Prisma Access selects the following list of gateways by default.
    • Australia Southeast
    • Belgium
    • Brazil South
    • Canada East
    • Finland
    • France North
    • Germany Central
    • Hong Kong
    • India West
    • Ireland
    • Israel
    • Japan Central
    • Netherlands Central
    • Saudi Arabia
    • Singapore
    • South Africa Central
    • South Korea
    • Taiwan
    • UK
    • US East
    • US West
    Prisma Access lets you select only gateways that you have onboarded. For example, if you don’t choose
    UK
    when you select locations, you cannot select
    UK
    as a manual gateway (the location is grayed out).
    mobile-users-onboarding-manual-gateway-locations.png
    If you allow users to manually choose more than 25 gateways, we recommend using version 5.0.3 or later of the GlobalProtect app for the best end user experience.
  12. Click
    OK
    to save the Onboarding settings.
  13. To secure traffic for your mobile users, you must create security policy rules.
    1. Select the
      Device Group
      in which to add policy rules. You can select the Mobile_User_Device_Group or the parent device group that you selected when setting up Prisma Access for mobile users.
    2. Create security policy rules. Make sure that you do not define security policy rules to allow traffic from any zone to any zone. In the security policy rules, use the zones that you defined in the template stack you are pushing to the cloud service.
  14. Configure logs to forward to Cortex Data Lake.
    The Cloud Services plugin automatically adds the following Log Settings (
    Device
    Log Settings
    ) after a new installation or when removing non-Prisma Access templates from a Prisma Access template stack:
    • Log Settings for System logs (
      system-gpcs-default
      ), User-ID logs (
      userid-gpcs-default
      ), HIP Match logs (
      hipmatch-gpcs-default
      ), and GlobalProtect logs (
      gp-prismaaccess-default
      ) are added to the Mobile_User_Template.
    • Log Settings for System logs (
      system-gpcs-default
      ), User-ID logs (
      userid-gpcs-default
      ), and GlobalProtect logs (
      gp-prismaaccess-default
      ) are added to the Remote_Network_Template.
    • Log Settings for System logs (
      system-gpcs-default
      ) and GlobalProtect logs (
      gp-prismaaccess-default
      ) are added to the Service_Conn_Template.
    These Log Setting configurations automatically forward System, User-ID, and HIP Match logs to Cortex Data Lake.
  15. (
    Optional
    ) Forward logs for other log types to Cortex Data Lake.
    To do this, you must create and attach a log forwarding profile to each policy rule for which you want to forward logs. See the Cortex Data Lake Getting Started Guide for more information.
    1. Select the
      Device Group
      in which you added the policy rules.
    2. Select
      Objects
      Log Forwarding
      and
      Add
      a profile. In the Log Forwarding Profile Match List,
      Add
      each log type that you want to forward.
      The following example enables forwarding of Traffic, Threat Prevention, WildFire Submission, URL Filtering, Data Filtering, and Authentication logs.
    3. Select
      Panorama/Logging Service
      as the Forward Method. When you select Panorama, the logs are forwarded to Cortex Data Lake. You will be able to monitor the logs and generate reports from Panorama. Cortex Data Lake provides a seamless integration to store logs without backhauling them to your Panorama at the corporate headquarters, and Panorama can query Cortex Data Lake as needed.
      prisma-access-users-log-forwarding.png
    4. Select
      Policies
      Security
      and edit the policy rule. In
      Actions
      , select the Log Forwarding profile you created.
  16. Commit all your changes to Panorama and push the configuration changes to Prisma Access.
    1. Click
      Commit
      Commit to Panorama
      .
    2. Click
      Commit
      Push to Devices
      and click
      Edit Selections
      .
    3. On the
      Prisma Access
      tab, make sure
      Prisma Access for users
      is selected and then click
      OK
      .
    4. Click
      Push
      .
  17. To verify that Prisma Access for users is deployed and active, select
    Panorama
    Cloud Services
    Status
    Status
    .
    After the provisioning completes, the mobile users
    Status
    and
    Config Status
    should show
    OK
    .
    The
    Deployment Status
    area allows you to view the progress of onboarding and deployment jobs before they complete, as well as see more information about the status of completed jobs. See Deployment Progress and Status for details.
    prisma-access-users-status-1-7.png
    To view the number of unique users who are currently logged in, or to log out a logged in user, click the hyperlinked number next to
    Current Users
    . See View Logged In User Information and Log Out Current Users for details.
    mobile-users-user-status-information.png
    To view historical information of previously-logged in users for a 90-day time period, click the number next to
    Users (Last 90 days)
    .
    To export the list of users to a csv file, select
    Export to CSV
    . Note that a maximum of 45,000 users can be exported to a CSV file.
    mobile-users-user-status-information-last-90-days.png
    To display a map that shows the locations of Prisma Access portals and gateways running in the regions you have selected, select
    Monitor
    ; then, select
    Mobile Users
    .
    mobile-users-service-stats-by-region.png
    Select a region to get more detail about that region.
    mobile-users-service-stats-by-location.png
  18. If you chose to
    Use Company Domain
    for your portal hostname, you must add a DNS entry on your internal DNS servers to map the portal hostname you defined to the Portal DNS CNAME displayed on the
    Cloud Services
    Configuration
    Mobile Users
    Onboarding
    General
    tab (for example,
    <
    portal_hostname
    >.gpcloudservice.com
    ).
  19. Deploy the GlobalProtect app software to your end users.
    For Mac OS or Windows users, you can direct users to the Prisma Access portal address, where they can download the GlobalProtect app from the portal.
    Prisma Access manages the version of the GlobalProtect app on the portal and this is not configurable; however, you can Manage Upgrade Options for the GlobalProtect App in Panorama to control the availability of an app version and control the ability of users to download it.
    Alternatively, you can host GlobalProtect app software on a web server for your Mac OS and Windows users. Prisma Access is compatible with any GlobalProtect app versions that are not listed as end of life.
    Mobile app users can download and install the GlobalProtect mobile app from the appropriate app store for their operating systems.

Recommended For You