Prisma Access
Set Up Explicit Proxy
Table of Contents
Expand All
|
Collapse All
Prisma Access Docs
-
- Prisma Access China
- 4.0 & Later
- 3.2 Preferred and Innovation
- 3.1 Preferred and Innovation
- 3.0 Preferred and Innovation
- 2.2 Preferred
-
-
-
- 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
- 3.1 Preferred and Innovation
- 3.0 Preferred and Innovation
- 2.2 Preferred
Set Up Explicit Proxy
Set up
Prisma Access
Explicit Proxy. Where Can I Use
This? | What Do I Need? |
---|---|
If you'd like to enable Private Source IP based visibility
and enforcement on Explicit Proxy in your Prisma Access environment,
get in touch with your account team to learn more. |
|
Use Explicit Proxy to secure mobile users by redirecting browser traffic to
Prisma Access
. Onboarding Guidelines
—Use the following guidelines when you license and onboard
your Explicit Proxy deployment: - Explicit Proxy supports a subset ofPrisma Accesslocations.
- You cannot add locations that are denoted with two asterisks; these are Local Zones and are not supported withPrisma Access.
- If you have a Local or Evaluation license forPrisma Accessfor Users and you have a Mobile Users—GlobalProtect deployment as well as a Mobile Users—Explicit Proxy deployment, you can deploy a maximum of five locations for each (five locations maximum for Mobile Users—GlobalProtect and five locations maximum for Mobile Users—Explicit Proxy). If you have a Worldwide license, there are no restrictions for the maximum number of locations.
- Explicit Proxy supports multitenancy under the following conditions: if you have an existingPrisma Accessnon-multitenant deployment and convert it to a multitenant deployment, only the first tenant (the tenant you migrated) supports Explicit Proxy. Any subsequent tenants you create for the multitenant deployment after the first do not support Explicit Proxy.
- When onboarding an Explicit Proxy deployment, Palo Alto Networks recommends that all the configuration be performed in a single browser. You can, however, add security policies from multiple browsers or browser sessions.
- URL filtering actions ofcontinueoroverrideare not supported and do not work with Explicit Proxy.
Learn how to set up Explicit Proxy.
Cloud Management
Cloud Management
Set up Explicit Proxy in a
Prisma Access (Managed by Strata Cloud Manager)
deployment. Set up an explicit proxy connection for mobile users; with explicit proxy, a proxy
auto-config (PAC) file on mobile user devices redirects browser traffic to
Prisma Access
.Before you begin, make sure you review the explicit proxy guidelines.
- Enable explicit proxy and allocate usersGo toto 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.ManageService SetupMobile UsersIf you're usingStrata Cloud Manager, go toto start setting up explicit proxy.WorkflowsPrisma AccessSetupMobile Users
- Add the proxy settings which mobile users will use to connect toPrisma AccessGo to theInfrastructure Settings:
- Specify an Explicit Proxy URL.By default, the name isproxyname.proxy.prismaaccess.com, whereproxynameis 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.
- (Optional) SelectEnable Agent Proxyto enable the agent-based proxy functionality.Use this feature to enablePrisma Access.
- Use forwarding rules to author a PAC file that meets your requirements or upload your own PAC file to a forwarding profile.
- Choose thePrisma Accesslocation to which your mobile users will connectAdd thePrisma Accesslocations where you want to support mobile users.The map displays thePrisma Accesslocations.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.
- Authenticate mobile usersSet upUser Authenticationso that only legitimate users have access to your services and applications.SAML and Kerberos are the supported authentication protocols.Prisma Accesssupports 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.
- Review the best practice security rules that are turned on by defaultPrisma Accessenforces 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. - Verify that the mobile users location is activeAfter you push your initial configuration toPrisma Access,Prisma Accessbegins 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 selectingand edit Infrastructure Settings to confirm a gateway is set up in each of the locations you provisioned.ManageService SetupMobile Users
- Enable decryption for explicit proxy traffic
- Set the maximum supported TLS version to 1.2.
- SetStrip ALPN(Advanced SSL Forward Proxy settings) because explicit proxy does not support native HTTP/2, and you must remove the ALPN headers.
- Download the root CA and install it on your endpoint for SSL decryption.
- Edit the PAC file content.Use Forwarding Profiles to manage PAC files.Prisma Accessbased on forwarding rules and logic from the PAC file.Go to theForwarding Rules:
- 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 wherePrisma Accesshosts the PAC file.
- Edit the PAC file using thePAC File Editormode orForwarding rules mode.
- ThePAC File Editormode is selected by default. ClickOKto edit in the PAC file edit mode.
- SelectForwarding rules modeand clickOKto edit in the forwarding rules mode. Switching to forwarding rules mode discards the existing settings.
- Specify an ExplicitProxy URLwith port to be used in the PAC file.By default, the name isproxyname.proxy.prismaaccess.com, where proxyname is the subdomain you specify, and uses port8080.
- ConfigureExclusions in Public Networkwhen your Explicit Proxy mobile users connect to Prisma Access from a public network.
- ConfigureFQDN ExclusionsandIP Address Exclusions. The excluded FQDNs and IP addresses won't be forwarded fromPrisma Access.
- Enable Exclusions in Internal Networkto configure exclusions for specific IP addresses or FQDNs when the explicit proxy mobiles users connect toPrisma Accesson the internal network.
- Specify the below exclusions to have different traffic exclusions when the user is on the internal network.
- Enter theIP Addressof a host that can be resolved from the internal network only.
- Enter theFQDNthat 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 fromPrisma Access.
- Savethe changes.
- ConfigureAdvanced Security Settings.
- If you want to forward traffic to Explicit Proxy from your branches through a secure IPSec tunnel,Enable Proxy Modeand 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 OnlyIf 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 enabledSource IP visibility and enforcement, use theSource IPfield 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, selectSource IP based visibility and enforcement.This functionality has these requirements:
- A minimumPrisma Accessdataplane of 10.2.4
- APrisma 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.
- SpecifyBlock Sources.Add any source IP address traffic that should be blocked to theBlock Source Addresslist.Specify an address, address group, or EDL.To exclude IP address list entries from enforcement,Add Exceptionand select the IP addresses to exclude from being blocked.
- SpecifyBlocked Domains.Specify the domains or domain categories for malicious websites, or for any websites that you do not want users to access.Prisma Accessprevents 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 theException 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 theDomains 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 theTrusted Source Address.
- To bypass authentication of any trusted source addresses you entered, selectSkip authentication.You can useSkip authenticationwithSource IP based visibility and enforcementto Skip authentication of headless systems that can't authenticate, set up security policies, and get visibility of the traffic onPrisma AccessExplicit Proxy.You can add either IP addresses or subnets. A maximum of 100,000 IP addresses are supported after expanding the subnets.If you selectSkip authenticationto skip authentication for an address object, and then later want to enable authentication by deselectingSkip authenticationfor 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 canUse 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 clickSavefor the XAU setting to take effect.
Set Up Explicit Proxy (Panorama)
Panorama
)Secure
Prisma Access
mobile users by creating an Explicit
Proxy and using a PAC file. To secure mobile users with an Explicit Proxy,
complete the following steps.
Before you configure Explicit Proxy, be aware of how explicit proxy works and how
explicit proxy identifies users, go through the planning checklist, and learn
how to set up the Explicit Proxy PAC
file.
- Set up authentication for Explicit Proxy.Use the following guidelines when configuring SAML authentication for the IdP and in Panorama:
- Panorama Guidelines:
- Configure aSAML Identity Providerand anAuthentication Profile, for Prisma Access. You specify the authentication profile you create in a later step.
- Be sure that you configure the authentication profile under theExplicit_Proxy_Template.
- Usemailas the user attribute in the IdP server profile and in theAuthentication Profileon Panorama.
- Explicit Proxy does not supportSign SAML Message to IdPin the SAML Identity Provider Server Profile.
- When you configure the Cloud Identity Engine to retrieve user and group mapping information, usemailoruserPrincipalNameas theSamAccountNamein Group Mapping.
- When configuringGroup Mapping Settingsduring Explicit Proxy setup, use the same Directory Attribute for Primary Username and email, orPrisma Accessdoes not accurately reflect user counts. For example, given the following user profile:sAMAccountName: muser Netbios: example userPrincipalName: muser@example.com mail: mobile.user@example.comIf, in the Cloud Identity Engine configuration, you use aPrimary UsernameofuserPrincipalNameand anE-Mailofmail, the user information thatStrata Logging Servicereturns in traffic logs and the user information that the ACS returns in authentication logs will be different. In this example, ACS sends themailattribute (mobile.user@example.com) to the authentication logs andStrata Logging Servicesends theuserPrincipalNameattribute (muser@example.com) to the traffic logs. As a result of this mismatch, your user count will not be accurate in theCurrent UsersandUsers (Last 90 days)fields when checking the Explicit Proxy status in the Status (page. For this reason, use the same directory attribute forPanoramaCloud ServicesStatusStatusPrimary UsernameandE-Mail(for example,mail) when specifyingGroup Mapping Settings.
- When using Panorama to managePrisma Access, the Cloud Identity Engine does not auto-populate user and group information in security policy rules.
- IdP Guidelines:
- Use the following URLs when configuring SAML:SAML Assertion Consumer ServiceURL:https://global.acs.prismaaccess.com/saml/acsEntity IDURL:https://global.acs.prismaaccess.com/saml/metadata
- If you use Okta as the IdP, useEmailAddressfor theName ID Formatsetting.
- Enter a single sign on URL ofhttps://global.acs.prismaaccess.com/saml/acs.
- Single Logout (SLO) is not supported.
- To troubleshoot IdP authentication issues, use the IdP’s monitoring and troubleshooting capabilities. The ACS does not log IdP authentication failures.
- When creating anAuthentication Profilefor the SAML IdP, in theAdvancedtab, selectallin theAllow Listor Explicit Proxy will not be able to retrieve group mapping.
- Configure Explicit Proxy settings.
- Selectand click the gear icon to edit Explicit ProxyPanoramaCloud ServicesConfigurationMobile Users—Explicit ProxySettings.
- In theSettingstab, edit the following settings:
- (Optional) Verify the template and template stack names.By default,Prisma Accesscreates a new template stackExplicit_Proxy_Template_Stackand a new templateExplicit_Proxy_Template. Make sure that you are using this template when you create and edit yourDevicesettings in Panorama.
- In the Device Group section, select theParent Device Groupthat contains the configuration settings you want to push for the Explicit Proxy, or leave the parent device group asSharedto use thePrisma Accessdevice group shared hierarchy. TheDevice Group Namecannot be changed.
- (Optional) If you have configured a next-generation firewall as a master device or added a Cloud Identity Engine profile to populate user and group information in security policy rules, select User-ID Master Device or Cloud Identity Engine; then, select either the Master Device or the Cloud Identity Engine profile that you created.
- In the License Allocation section, specify the number of mobile users to allocate for Explicit Proxy.
- In theGroup Mapping Settingstab,Enable Directory Sync Integration(now known as the Cloud Identity Engine) to configurePrisma Accessto use the Cloud Identity Engine to retrieve user and group information.You use the Cloud Identity Engine to populate user and group mapping information for an Explicit Proxy deployment.Entermailfor the Directory Attribute in thePrimary Usernamefield andmailfor theE-Mailfield.
- ClickOKwhen finished.
- (Optional, Innovation Deployments Starting with 3.0 Innovation Only) Configure Block Settings.Use Block Settings to block access to an internet destination at the DNS resolution stage.To restrict access to Explicit Proxy to specific source IP addresses, you can also use special objects. These Address Objects, Address Groups, and External Dynamic Lists (EDLs) that use specific names allow the IP addresses you specify for internet traffic and block any other IP addresses.
- In theAuthentication Settingstab, configure decryption, X-Authenticated-User (XAU), and authentication settings.
- Configure your settings for decrypted traffic.
- SelectDecrypt Traffic That Matches Existing Decryption rules; For Undecrypted Traffic, Allow Traffic Only From Known IPs Registered By Authenticated Usersto configure the following decryption rules:
- Traffic that matches decryption policy rules you have configured with anActiontoDecryptorDecrypt and Forwardwill be decrypted.If a user accesses an undecrypted HTTPS site, and a user has not yet authenticated to Explicit Proxy from that IP address, the user is blocked. However, the user can access a decrypted site, complete authentication, and then access undecrypted sites.
- Undecrypted traffic is allowed from IP addresses from which mobile user have already authenticated.
Explicit Proxy requires decryption to authenticate users. Enter the domains that can be decrypted in a custom URL category; then, specify those categories inIf Authentication traffic is forwarded through Explicit Proxy, specify the domains used in the authentication flow.Only add the domains that are required for authentication to the Custom URL category you specify, including all ACS and IdP FQDNs. You must add authentication URLs to the Custom URL category, even if you have added them to a decryption policy. - To allow all traffic to be decrypted, selectDecrypt All traffic (Overrides Existing Decryption Rules).If you choose this radio button, ensure that:
- You do not have exceptions in your decryption policy.
- You are applying source IP address-based restrictions in your security policy.
Failing to follow these recommendations enables the abuse of Explicit Proxy as an open proxy that can be widely misused as a forwarding service for conducting denial of service attacks.- You have at least one SSL Forward Proxy certificate specified as aForward Trust Certificate.If you do not have a forward trust certificate, create one on Panorama; then,Commit and Pushyour changes toPrisma Access. Failure to have a forward trust certificate will cause a commit error when you commit your Explicit Proxy changes.
- (Optional) Enter any IP addresses from which undecrypted HTTP or HTTP Cross-Origin Resource Sharing (CORS) traffic should be allowed to theTrusted Source Address Auth Bypass.Add the IP addresses to IP address-based Address Objects andAddthe address objects in the field.Enter a maximum of 100,000 addresses. Make sure that the address object uses IP addresses only.
- (Optional) To bypass authentication of any trusted source addresses you entered, selectAuth Bypass.You can useAuth BypasswithSource IP based visibility and enforcementto 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 selectAuth Bypassto skip authentication for an address object, and then later want to enable authentication by deselectingAuth Bypassfor 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.
- (Optional) To allow the trusted source Address IP addresses to use XAU for identity, selectUse X-Authenticated-User (XAU) header on incoming HTTP/HTTPS requests for Identity.Select this option if you if you are using proxy chaining from a third-party proxy to Explicit Proxy, users have authenticated in that proxy, and the proxy uses XAU headers.XAU headers are the only HTTP headers supported for Explicit Proxy header ingestion. X-Forwarded-For (XFF) headers are not supported.
- (Optional) Specify settings for privacy-sensitive websites by creating security policy rules for those sites, then specifying theSecurity Policyor policies for those sites in theEnforce Authentication Onlyarea.For any websites you specify in the in theSecurity Policyor policies you add, Explicit Proxy decrypts the websites based on the decryption policies, but does not inspect or log the decrypted traffic.
- (Optional) ConfigureAdvancedsettings.
- If you want to forward traffic to Explicit Proxy from your branches through a secure IPSec tunnel,Enable Proxy Modeand 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.
- (Optional) To leverage the private IP addresses of the systems in your branch locations that are forwarding traffic to Explicit Proxy, selectSource IP based visibility and enforcement.This functionality has these requirements:
- A minimumPrisma Accessdataplane of 10.2.4
- APrisma Access (Managed by Panorama)deployment with a minimum Cloud Services plugin of 4.1
- The source IP addresses only display for IP addresses from a remote network after you have configured a Remote Networks-Explicit Proxy deployment and only source addresses in Remote Network locations that are supported with Explicit Proxy.
- Proxy Mode Deployments OnlyIf 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 enabledSource IP visibility and enforcement, use theSource IPfield in Security policies in Explicit Proxy to secure the traffic. You need additional policies in the remote networks.
- ClickOK.
- ClickConfigureto configure Explicit Proxy setup.
- Specify anExplicit Proxy FQDN.By default, the name isproxyname.proxy.prismaaccess.com, whereproxynameis the subdomain you specify, and uses port 8080. If you want to use your organization’s domain name in the Explicit Proxy URL (for example, thisproxy.proxy.mycompany.com), enter a CNAME record your organization’s domain.For example, to map a proxy URL named thisproxy.prismaaccess.com to a proxy named thisproxy.proxy.mycompany.com, you would add a CNAME of thisproxy.proxy.prismaaccess.com to the CNAME record in your organization’s domain.
- (Optional) SelectUse GlobalProtect Agent to Authenticateto enable the agent-based proxy functionality.Enable this feature if you want to usePrisma Access.You also must select this check box to enableSource IP based visibility and enforcement.
- Specify anAuthentication ProfileandCookie Lifetime.
- Specify the SAMLAuthentication Profileyou used in Step 1, or add aNewauthentication profile to use withPrisma Access.You must configure SAML authentication, including configuring aSAML Identity Provider(IdP) and anAuthentication Profile, to use an Explicit Proxy.
- (Optional) Specify aCookie Lifetimefor the cookie that stores the users’ authentication credentials.Prisma Access caches the user’s credentials and stores them in the form of a cookie. To change the value, specify the length of time to use in Seconds, Minutes, Hours, or Days.To prevent issues with users not being able to download large files before the cookie lifetime expires, or the cookie expiring when users are accessing a single website for a long period of time, Palo Alto Networks recommends that you configure a Cookie Lifetime of at least one day. If Explicit Proxy users have a cookie lifetime expiration issue, they can browse to a different website to re-authenticate to ACS and refresh the ACS cookie.If you are downloading a file, and the file download takes longer than theCookie Lifetime, the file download will terminate when the lifetime value expires. For this reason, consider using a longerCookie Lifetimeif you download large files that take a long time to download.
- Select theLocationsand the regions associated with those locations where you want to deploy your Explicit Proxy for mobile users.Prisma Accessadds a proxy node into each location you select.Explicit Proxy supports a subset of allPrisma Accesslocations. See Explicit Proxy Configuration Guidelines for the list of locations.TheLocationstab 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.You should enable Explicit Proxy locations in at least two regions to ensure regional redundancy.
- Click theLocationstab and select a region.
- Select one or more Explicit Proxy locations 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.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 selectAllsites within a region (top of the dialog).
- ClickOKto add the locations.
- Configure security policy rules to enforce your organization’s security policies.To make required configuration changes and to control the URLs that mobile users can access from Explicit Proxy, use security policies. Use the following guidelines and requirements when configuring your security policies:
- Based on your business goals, create security policies for sanctioned internet and SaaS apps using App-ID and user groups that need access to those applications.
- Attach security profiles to all security policy rules so that you can prevent both known and unknown threats following the security profile best practices.
- Commit your changes to Panorama and push the configuration changes toPrisma Access.
- Click.CommitCommit and Push
- Edit Selectionsand, in thePrisma Accesstab, make sure thatExplicit Proxyis selected in thePush Scope, then clickOK.
- ClickCommit and Push.
- Select the PAC file to use with Explicit Proxy.
- Select.PanoramaCloud ServicesConfigurationMobile UsersExplicit ProxyBe sure that you enter a port of 8080 in the PAC file.
- Select theConnection Namefor the Explicit Proxy setup you just configured.
- Enter thePAC (Proxy Auto-Configuration) Fileto use for Explicit Proxy.Be sure that you understand how PAC files work and how to modify them before you upload them toPrisma Access.Browseand upload the file.Prisma Accessprovides you with a sample PAC file; you canDownload sample PAC file, change the values, and upload that file. See Set Up Your Explicit Proxy PAC File for PAC file requirements and guidelines as we as a description of the contents of the sample PAC file.