Web Proxy

• Configure Explicit Proxy
  The explicit proxy method allows you to troubleshoot issues more easily, since the client browser is aware of the existence of the proxy.

  1. If you have not already done so, activate the license for web proxy.
     You must activate the web proxy license for the PA-1400 Series, PA-3400 Series, and VM-Series. Learn how to activate your subscription licenses for the PA-1400 Series and PA-3400 Series or activate the web proxy license for the VM-Series in the following step.
     1. Log in to the Customer Service Portal (CSP).
     2. Edit the deployment profile.
     3. Select Web Proxy (Promotional Offer).

     4. Click Update Deployment Profile.
     5. On the firewall, retrieve the license keys from the server.
        If the license key retrieval is not successful, restart the firewall and repeat this step before proceeding.
  2. Set up the necessary interfaces and zones.
     As a best practice, use Layer 3 (L3) for the three interfaces the web proxy uses and configure a separate zone for each interface within the same virtual routers and the same virtual systems.
     1. Configure an interface for the client traffic.
        Be sure to carefully copy the IP address for this interface and save it in a secure location because you must enter it as the Proxy IP address when you configure the web proxy.
     2. Configure an interface for the outgoing traffic to the internet.
     3. Configure a loopback interface for the proxy.
        All incoming traffic is routed through this interface to the proxy.
  3. Set up the DNS proxy for Explicit Proxy.
     1. Configure a DNS proxy object for the proxy connection.
     2. Configure a DNS Server profile with both primary and secondary DNS servers.
        You must configure both a primary and a secondary DNS server for web proxy.
     3. Specify the interface for the proxy connection.
        Specify either the traffic ingress interface or a loopback interface.
  4. To enable decryption for MITM detection, create a self-signed root CA certificate or import a certificate signed by your enterprise certificate authority (CA). For more information, refer to the best practices for administrative access.
  5. Ensure you have completed the pre-deployment steps for the authentication method you want to configure. Select only one of the following authentication methods.
     • Configure Kerberos Authentication
     • Configure SAML Authentication
     • Configure Cloud Identity Engine Authentication
  6. If you have a DNS security subscription, integrate the web proxy firewall with Explicit Proxy to sinkhole any requests that match the DNS security categories that you specify.
     1. Select PanoramaCloud ServicesConfigurationOn-Prem Proxy.
     2. Edit the settings then select the Device Group you want the web proxy firewall to use or Add a new device group.
        To integrate the web proxy firewall with Prisma Access, you must configure the web proxy firewall in a separate device group that contains no other firewalls or virtual systems. If the firewall is already a member of a device group, create a child device group as a sub-group and move the firewall to the child device group.

     3. (Optional) Select Block Settings to Add a Blocked Domain or any domains that are Exempted Domains because they are sinkholed due to matching one or more of the DNS Security categories.

     4. (Optional) Select whether you want to Log any requests made to blocked domains.
     5. Click OK.
  7. Set up the Explicit Proxy.
     1. On the firewall, select NetworkProxy then Edit the Proxy Enablement settings.
     2. Select Explicit Proxy as the Proxy Type then click OK to confirm the changes.
        If the only available option is None, verify that you have an active license for the web proxy feature.

     3. Edit the Explicit Proxy Configuration.

     4. Specify the Connect Timeout to define (in seconds) how long the proxy waits for a response from the web server. If there is no response after the specified amount of time has elapsed, the proxy closes the connection.
     5. Select the Listening Interface that contains the firewall where you want to enable the web proxy.
        Specify the ingress interface for the client traffic.
     6. Select the Upstream Interface that contains the interface with the web proxy that reroutes the traffic to the server.
        If you are using a loopback interface, specify that interface as the Upstream Interface.
     7. Specify the IP address of the listening interface as the Proxy IP.
        Enter the IP address of the interface you created in Step 2.a.
     8. Specify the DNS Proxy object you created in Step 3.a.
     9. Select Check domain in CONNECT & SNI are the same to prevent domain fronting attacks by specifying different domains between the CONNECT request and the Server Name Indication (SNI) field in the HTTP header.
     10. Select the Authentication service type you want to use (either SAML/CAS or Kerberos Single Sign On).
         Be sure to complete all necessary pre-deployment and configuration steps for the authentication method you select. Select only one of the following authentication methods:

         • Configure Kerberos Authentication
         • Configure SAML Authentication
         • Configure Cloud Identity Engine Authentication
     11. Click OK to confirm the changes
  8. Configure the necessary security policy rules to decrypt traffic and reroute applicable traffic to the proxy.
     You will need to create the following types of rules:

     • Source NAT (if applicable)
     • Decryption
     • Security
     1. Configure a decryption policy to decrypt the traffic so it can be rerouted if necessary.
        To avoid decrypting traffic twice, select the zone that contains the upstream interface as the source zone for the decryption policy.
     2. (Optional but recommended) Select ObjectsDecryption Profile and select Block sessions on SNI mismatch with Server Certificate (SAN/CN) to automatically deny any sessions where the Server Name Indication (SNI) does not match the server certificate.

     3. Configure the necessary security policy rules.
        1. Create a security policy rule to allow traffic from the client to the interface you selected as the listening interface.
        2. Configure a security policy rule to allow traffic from the zone that contains the upstream interface to the internet.
        3. Configure a security policy rule to allow traffic from the DNS proxy zone to the internet.
     4. Configure a security policy rule using the authentication profile you configured in Step 5 to route traffic to the proxy as appropriate.
• Configure Transparent Proxy
  With transparent proxy, the client browser is not aware of the proxy. Transparent proxy supports inline mode deployment and does not support web cache communication protocol (WCCP). Transparent proxy is transparent to the user without requiring additional authentication.

  1. If you have not already done so, activate the license for web proxy.
     This step is required for the PA-1400, PA-3400, and VM Series. The following steps are for the VM series; for the PA-1400 and PA-3400, follow the steps to activate subscription licenses.
     1. Log in to the Customer Service Portal (CSP).
     2. Edit the deployment profile.
     3. Select Web Proxy (Promotional Offer).

     4. Click Update Deployment Profile.
     5. On the firewall, retrieve the license keys from the server.
        If the license key retrieval is not successful, restart the firewall and repeat this step before proceeding.
  2. Set up zones and interfaces.
     As a best practice, use Layer 3 (L3) for all interfaces and configure a separate zone for each interface within the same virtual routers and the same virtual systems.
     1. Configure an interface for the client.
     2. Configure an interface for the outgoing traffic to the internet.
     3. Configure a loopback interface for the proxy.
        All incoming traffic is routed through this interface to the proxy. Be sure to carefully copy the IP address for this interface and save it in a secure location because you must enter it as the Proxy IP address when you configure the web proxy.
  3. Set up the DNS proxy for Transparent Proxy.
     1. Configure a DNS proxy object for the proxy connection.
     2. Configure a DNS Server profile with both primary and secondary DNS servers.
        You must configure both a primary and a secondary DNS server for web proxy.
     3. Specify the loopback interface for the proxy connection.
  4. To enable decryption for MITM detection, create a self-signed root CA certificate or import a certificate signed by your enterprise certificate authority (CA). For more information, refer to the best practices for administrative access.
  5. Set up the Transparent Proxy.
     1. On the firewall, select NetworkProxy then Edit the Proxy Enablement settings.
     2. Select Transparent Proxy as the Proxy Type then click OK to confirm the changes.
        If the only available option is None, verify that you have an active license for the web proxy feature.

     3. Edit the Transparent Proxy Configuration.

     4. Specify the Connect Timeout to define (in seconds) how long the proxy waits for a TCP response from the web server. If there is no response after the specified amount of time has elapsed, the proxy closes the connection.
     5. Select the Upstream Interface.
        The upstream interface must be a loopback interface that is not associated with any other subnets.
     6. Specify the IP address of the loopback interface as the Proxy IP.
        Enter the IP address of the interface you configured in Step 2.3.
     7. Specify the DNS Proxy object you created in Step 3.
        Specify the loopback interface as the Upstream Interface.
     8. Click OK to confirm the changes.
  6. Configure the destination network address translation (DNAT) policy.
     You must configure the DNAT policy rule exactly as described in the following steps for the firewall to successfully use the web proxy to route traffic. Be sure to configure the DNAT policy rule so that it precedes the source network address translation (SNAT) policy rule.
     1. Select PoliciesNAT and Add a NAT policy rule.
     2. Enter a unique Name and verify that Group Rules by Tag is None then select the NAT Type.

     3. Select Original Packet and Add a trusted zone as the Source Zone and the Destination Zone as the interface that contains the web proxy.

     4. Select Translated Packet and verify that Translation Type for Source Address Translation is None.

     5. Select Dynamic IP (with session distribution) as the Translation Type for the Destination Address Translation.
     6. Enter the IP address of the web proxy as the Translated Address.
        Enter the same IP address as the Proxy IP address specified in Step 2.3 and Step 5.6.
     7. Enter 8080 as the Translated Port.
     8. Select a Session Distribution Method (for example, Round Robin).
        The session distribution method is not applicable for web proxy.
     9. Click OK and Commit the changes.
  7. Configure a security policy to allow and route the proxy traffic.
     1. Configure a source network address translation (SNAT) policy rule after the DNAT rule.
     2. Configure a decryption policy to decrypt traffic.
        Select the zone that contains the proxy interface as the source zone.
     3. (Optional but recommended) Select ObjectsDecryption Profile and select Block sessions on SNI mismatch with Server Certificate (SAN/CN) to automatically deny any sessions where the Server Name Indication (SNI) does not match the server certificate.

     4. Configure policy rules to allow access to the DNS proxy servers for both the client and the proxy.
     5. Configure a policy rule to allow traffic from the client to the proxy.
     6. Configure a policy rule to allow traffic from the proxy to the internet.