Configure Forwarding Profiles to Manage Agent Traffic for Dynamic Privilege Access Agents

1. Log in to Strata Cloud Manager as the Project Admin.
2. Select ConfigurationNGFW and Prisma AccessOverview and expand the Configuration Scope to view the Snippets.

3. Select the snippet that the Superuser admin assigned to you.

   You can also view the snippets that are not assigned to you, but you cannot interact with them, such as to change the configuration.
4. Select ObjectsDynamic Privilege Access to open the Dynamic Privilege Access settings.

5. Select Forwarding Profiles and edit the Forwarding Profiles Setup.

6. Set up Source Applications if you want to create split tunnels based on the SaaS or public cloud application name.

   1. In the Forwarding Profiles Setup page, select Source ApplicationsAdd Source Application.

   2. Enter a meaningful Name for the application that you want to add.
   3. Click + in the Applications table and enter the complete path of the application. You can add one or more applications to manage whether to exclude or include the application traffic in the tunnel.

      If you choose to exclude application traffic (by selecting Direct connectivity in the forwarding rule), traffic from these applications is sent through the physical adapter on the endpoints rather than the tunnel (the virtual adapter).

      If you choose to include application traffic (by selecting Tunnel connectivity in the forwarding rule), traffic from these applications is routed to Prisma Access, even if it meets the exclude traffic criteria.

      For example, to manage traffic from the Zoom application, add the following complete paths:

      • Windows endpoints: %AppData%\Roaming\Zoom\bin\Zoom.exe
      • macOS endpoints: /Applications/zoom.us.app/Contents/MacOS/zoom.us

      If you have a list of applications in a text file in comma-separated values format (.csv), you can Upload .csv File.
   4. Save the source application.
   5. Repeat these steps to add more source applications.
7. Set up Destinations if you want to create split tunnels based on the destination domain or access routes.

   1. In the Forwarding Profiles Setup page, select DestinationsAdd Destination.

   2. Enter a meaningful Name for the destination that you want to add.
   3. Add a destination by specifying the domain name, access route, or both.

      • To add a destination domain, click + in the FQDNs table and enter the FQDN for the destination domain. You can optionally add a port. If you do not specify a port, all ports for the specified domain are subjected to the forwarding rule. You can add one or more domains for traffic management.
        If you choose to exclude traffic based on the domain name (by selecting Direct connectivity in the forwarding rule), traffic from the domain is sent through the physical adapter on the endpoints rather than the tunnel (the virtual adapter).
        If you choose to include traffic based on the domain name (by selecting Tunnel connectivity in the forwarding rule), traffic from the domain is routed to Prisma Access, even if it meets the exclude traffic criteria.

      • To add an access route, click + in the IP Addresses table and enter a destination subnet. You can add one or more access routes for traffic management.
        Do not include wildcard characters in the IP address. Wildcards in IP addresses are not supported in forwarding profiles.
        If you do not include or exclude routes or applications, every request is routed through the tunnel (without a split tunnel). Also, all traffic is inspected and subjected to policy enforcement whenever users connect to Prisma Access.
        When you define split tunnel traffic to exclude access routes (by selecting Direct connectivity in the forwarding rule), these routes are sent through the physical adapter on the endpoint instead of being sent through the tunnel via the virtual adapter (the tunnel). By excluding split tunnel traffic by access routes, you can send latency-sensitive or high-bandwidth traffic outside of the tunnel, while all other traffic is routed through the tunnel for inspection and policy enforcement by the gateway.
        When you define split tunnel traffic to include access routes (by selecting Tunnel connectivity in the forwarding rule), the gateway pushes these routes to the remote users’ endpoints to specify what traffic these endpoints can send through the tunnel.
        Specify excluded routes that are more specific than included routes; otherwise, you might exclude more traffic than intended.
        If you have a list of IP addresses in a text file in .csv format, you can Upload .csv File.

   4. Save the destinations.
   5. Repeat these steps to add more destinations.
8. Create a forwarding profile that allows or excludes traffic based on the source applications or destinations that you configured.

   1. To add a forwarding profile, select Forwarding ProfilesAdd Forwarding ProfilePrisma Access Agent.

      To edit a forwarding profile, select the name of the profile in the Forwarding Profiles table.
   2. Enter a meaningful Name for the forwarding profile.
   3. Add a forwarding rule.

      The Forwarding Rules table shows the rules that make up the forwarding profile. All forwarding profiles contain the Default forwarding rule, which sends all DNS and network traffic through the tunnel. Any new rules that you add are placed above the default rule. You cannot delete or move the default forwarding rule, but you can change its Connectivity setting.
   4. Enter the specifications for the forwarding rule.

      1. Enable the rule.
      2. Enter a Name for the rule.
      3. Select the Source Application that you defined previously. If you select Any, the forwarding rule will apply to traffic from any source applications.
         The rule will match only if the connection is made by the specified source application.
      4. Select a User Location. If you did not set up a user location or if you allow the rule to match any user location, select Any. (Does not apply to Dynamic Privilege Access enabled agents.)
         The rule will match only if an endpoint is connected to the user location that you specify.
      5. Select a Destination that you defined previously. If you select Any, the forwarding rule will apply to traffic from any destination domain or IP address.
         The rule will match only if the connection destination matches the specified destination domain or IP address.
      6. Select the Connectivity:
         • Direct—Sends the traffic outside of the tunnel. All traffic for the selected application or destination is sent directly to the physical adapter on the endpoint without inspection.
         • Tunnel—Sends the traffic through the tunnel. All traffic going to the selected application or destination is sent through the tunnel to Prisma Access for inspection and policy enforcement.
      7. Select the Traffic Type:
         Specify whether to use split DNS to allow users to direct their DNS queries for applications and resources over the tunnel or outside the tunnel in addition to network traffic.
         • DNS + Network Traffic—Ensures that the split tunnel based on the destination domain you specified for inclusions or exclusions are applied to the DNS traffic and the associated network application traffic for that domain.
         • Network Traffic—Includes or excludes rules that are applied only to network application traffic and not to DNS traffic. All DNS traffic goes through the tunnel regardless of the split tunnel based on the destination domain that you specified for inclusions or exclusions.
         For Windows agents, the DNS + Network Traffic split tunnel option is not supported for application-based split tunnel rules. If you set up split tunneling to include or exclude traffic from the tunnel based on application names and select DNS + Network Traffic, DNS query packets for excluded and included apps will not honor the split tunnel rule.
   5. Add the forwarding rule.

      The rule is added to the Forwarding Rules table. You can add multiple rules to the forwarding profile.

9. Configure the Traffic Enforcement options to determine how you want traffic to be enforced.

   Be sure that to deselect all these options as they are not recommended for Dynamic Privilege Access.

   • Block all other unmatched outbound connections—When enabled, blocks all connections that do not match any of the forwarding rules. The traffic will not be sent through the tunnel.
   • Block outbound LAN access when connected to the tunnel—When enabled, blocks direct access to the local network when the agent is connected to the tunnel.
     Blocking access to your local network causes all traffic from being sent to the local adapter. In addition, your users won't be able to access resources on the local subnet, such as printers. Split tunnel traffic based on access route, destination domain, and application still works as expected.
     If you disable this option, your end users can access local resources without requiring them to first connect to Prisma Access using the Prisma Access Agent.
   • Block inbound access when connected to the tunnel—When enabled, blocks all inbound connections from the tunnel.
10. Save your forwarding profile.
11. Push the configuration by selecting Push ConfigPush. This action will make your forwarding profile available for selection in the Agent Settings page.