Cloud Management

1. Enable explicit proxy and allocate users

   Go to WorkflowsPrisma Access SetupMobile Users to start setting up explicit proxy. When you enable explicit proxy, you’ll be prompted to specify the number of mobile users who will use this connection type.

2. Add the proxy settings which mobile users will use to connect to Prisma Access

   Go to the Infrastructure Settings:

   1. Specify an Explicit Proxy URL.

      By default, the name is proxyname.proxy.prismaaccess.com, where proxyname is the subdomain you specify, and uses port 8080. To use your company domain in the explicit proxy URL, add a CNAME record to your organization’s domain.

      You can use SAML or Kerberos authentication types to authenticate mobile users.
   2. (Optional) Select Enable Agent Proxy to enable the agent-based proxy functionality.

      Use this feature to enable Prisma Access.
   3. Use forwarding rules to author a PAC file that meets your requirements or upload your own PAC file to a forwarding profile.
3. Choose the Prisma Access location to which your mobile users will connect

   Add the Prisma Access locations where you want to support mobile users.

   The map displays the Prisma Access locations.

   For the best user experience, if you are limiting the number of locations, choose locations that are closest to your users or in the same country as your users. If a location is not available in the country where your mobile users reside, choose a location that is closest to your users for the best performance.

   You should enable Explicit Proxy locations in at least two regions to ensure regional redundancy.
4. Authenticate mobile users

   Set up User Authentication so that only legitimate users have access to your services and applications.

   SAML and Kerberos are the supported authentication protocols. Prisma Access supports PingOne, Azure AD, and Okta as SAML authentication providers, but you should be able to use any vendor that supports SAML 2.0 as a SAML identity provider (IdP). Learn more on how to Enable Mobile Users to Authenticate to Prisma Access.
5. Review the best practice security rules that are turned on by default

   Prisma Access enforces best practice security policy rules by default. These rules allow your users to securely browse to general internet sites. Users are:

   • Blocked from visiting known bad websites based on URL
   • Blocked from uploading or downloading files that are known to be malicious
   • Protected from unknown, never-before-seen threats
   • Protected from viruses, spyware (command and control attacks), and vulnerabilities

   After going through the initial setup, you can review and update these default rules to meet your enterprise needs.
6. Verify that the mobile users location is active

   After you push your initial configuration to Prisma Access, Prisma Access begins provisioning your mobile user environment. This can take up to 15 minutes. When your mobile user locations are up and running, you’ll be able to verify them on the Mobile Users setup pages, the Overview, and within Insights.

   You can also validate your setup by selecting ManageService SetupMobile Users and edit Infrastructure Settings to confirm a gateway is set up in each of the locations you provisioned.
7. Enable decryption for explicit proxy traffic

   • Set the maximum supported TLS version to 1.2.
   • Set Strip ALPN (Advanced SSL Forward Proxy settings) because explicit proxy does not support native HTTP/2, and you must remove the ALPN headers.

8. Download the root CA and install it on your endpoint for SSL decryption.
9. Edit the PAC file content.

   Use Forwarding Profiles to manage PAC files.

   Edit a proxy auto-configuration (PAC) file for explicit proxy that meets your requirement. GlobalProtect app proxies traffic to Prisma Access based on forwarding rules and logic from the PAC file.

   Go to the Forwarding Rules:

   1. Download the PAC file and customize it so that it meets your needs. Then, import it again here, and we’ll give you the URL for the location where Prisma Access hosts the PAC file.
   2. Edit the PAC file using the PAC File Editor mode or Forwarding rules mode.
   3. The PAC File Editor mode is selected by default. Click OK to edit in the PAC file edit mode.
   4. Select Forwarding rules mode and click OK to edit in the forwarding rules mode. Switching to forwarding rules mode discards the existing settings.

      • Specify an Explicit Proxy URL with port to be used in the PAC file.
        By default, the name is proxyname.proxy.prismaaccess.com, where proxyname is the subdomain you specify, and uses port 8080.
      • Configure Exclusions in Public Network when your Explicit Proxy mobile users connect to Prisma Access from a public network.

        • Configure FQDN Exclusions and IP Address Exclusions. The excluded FQDNs and IP addresses won't be forwarded from Prisma Access.
      • Enable Exclusions in Internal Network to configure exclusions for specific IP addresses or FQDNs when the explicit proxy mobiles users connect to Prisma Access on the internal network.
        • Specify the below exclusions to have different traffic exclusions when the user is on the internal network.
          • Enter the IP Address of a host that can be resolved from the internal network only.
          • Enter the FQDN that resolves to the IP address you enter.
        • Configure exclusions for specific FQDNs and IP addresses. The traffic to specified FQDNs and IP addresses won't be forwarded from Prisma Access.
      • Save the changes.

10. Configure Advanced Security Settings.

    • If you want to forward traffic to Explicit Proxy from your branches through a secure IPSec tunnel, Enable Proxy Mode and retrieve anycast IP addresses if you want to use Explicit Proxy in conjunction with a .
      This solution uses anycast addresses with a remote network IPSec tunnel to allow Explicit Proxy to be used for users and devices at a remote network site or branch location.
    • Proxy Mode Deployments Only If Proxy Mode is enabled on your remote networks, add a policy to allow traffic bound to anycast and unicast IP on remote networks. If you have enabled Source IP visibility and enforcement, use the Source IP field in Security policies in Explicit Proxy to secure the traffic. You need additional policies in the remote networks.
    • (Optional) If you enable you enable proxy mode, to leverage the private IP addresses of the systems in your branch locations that are forwarding traffic to Explicit Proxy, select Source IP based visibility and enforcement.
      This functionality has these requirements:
      • A minimum Prisma Access dataplane of 10.2.4
      • A Prisma Access (Managed by Panorama) deployment with a minimum Cloud Services plugin of 4.1
      • The source IP addresses only display for Remote Network locations that are supported with Explicit Proxy.

    • Specify Block Sources.
      Add any source IP address traffic that should be blocked to the Block Source Address list.
      Specify an address, address group, or EDL.
      To exclude IP address list entries from enforcement, Add Exception and select the IP addresses to exclude from being blocked.
    • Specify Blocked Domains.
      Specify the domains or domain categories for malicious websites, or for any websites that you do not want users to access. Prisma Access prevents users from accessing the URLs and IP addresses you specify in this area when users initiate an HTTP GET (for unencrypted requests) or HTTP CONNECT (for encrypted requests). Users receive a block page when they attempt to access blocked websites.
    • If you want to exempt any domains that are included in a blocked domain category list, specify them in the Exception List.
      Any domains that are entered are exempted from being blocked, even if they appear in a domain category that you have blocked.
    • Explicit Proxy requires decryption to authenticate users. Enter the Domains used in the authentication flow.
    • Enter any IP addresses from which undecrypted HTTPS or HTTP cross-origin resource sharing (CORS) traffic can be allowed to the Trusted Source Address.
    • To bypass authentication of any trusted source addresses you entered, select Skip authentication.
      You can use Skip authentication with Source IP based visibility and enforcement to Skip authentication of headless systems that can't authenticate, set up security policies, and get visibility of the traffic on Prisma Access Explicit Proxy.
      You can add either IP addresses or subnets. A maximum of 100,000 IP addresses are supported after expanding the subnets.
      If you select Skip authentication to skip authentication for an address object, and then later want to enable authentication by deselecting Skip authentication for that address object, it can take up to 24 hours for the change to take effect after you make the change and Commit and Push your changes.

    • If you have an Explicit Proxy deployment and have added a list of trusted source IP addresses, you can Use X-Authenticated-User (XAU) headers on incoming HTTP/HTTPS requests for identity. Use this functionality to allow users that are logged in from another proxy that use XAU headers for authentication.
      You must click Save for the XAU setting to take effect.