Set Up Forwarding Profiles (Panorama Managed Deployments)

1. Navigate to the Prisma Agent setup.

   • Prisma Access (Managed by Panorama)
     From the Cloud Services plugin in Panorama, select PanoramaCloud ServicesPrisma Access AgentLaunch Prisma Access Agent.
   • NGFW (Managed by Panorama)
     Log in to Strata Cloud Manager as the administrator.
2. Select ConfigurationForwarding Profiles.

3. (macOS, Windows, and Linux agents only) Set up Source Applications if you want to steer traffic based on the application name.

   1. Select Source ApplicationsAdd Source Application.

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

      You will select these applications when setting up the forwarding rules in a forwarding profile. To exclude application traffic, select Direct connectivity when configuring the forwarding rule. Prisma Agent sends these applications through the physical adapter on the endpoints rather than the tunnel (the virtual adapter). If you choose to include application traffic, select the Best Available - Fail Safe (macOS, Windows, and Linux agents only), Best Available - Fail Open, or your own configured connectivity option when configuring the forwarding rule.

      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

      Wildcard Character Support

      (macOS, Windows, and Linux agents only) For applications with dynamic installation locations, you can use the asterisk (*) as a wildcard character to replace exactly one directory component in the path. You can include multiple wildcards throughout the path to handle various scenarios such as version-specific directories, user-specific installations, or architecture-dependent locations. To account for changing version numbers or user directories, you can place wildcards in the middle or end of a path (when you need to match any executable within a specific directory).

      Each wildcard must be a single asterisk (*) that occupies an entire directory component; double asterisks (**) are not supported. A wildcard cannot be combined with other characters within the same component. The path must begin with a valid root directory on macOS or Linux, or a drive letter on Windows, so you cannot start the path with a wildcard character.

      Valid Examples

      • /abc/v1/app
      • /*/bin/curl
      • /opt/*/Cellar/*/*/bin/wget
      • C:\Windows\System32\*
      • C:\Users\*\AppData\Roaming\Zoom\bin\*

      Invalid Examples

      • C:\Users\xyz\AppData\Roaming\Zoom\bin\zoom* — wildcard combined with other characters in the same component
      • */bin/curl — path starts with a wildcard
      • C:\Users\**\AppData\Roaming\Zoom\bin\zoom.exe — double asterisk (**) is not a valid wildcard pattern
      • /abc/**/xyz/app — double asterisk (**) is not a valid wildcard pattern

      If any path in the list is invalid — including paths that use unsupported wildcard patterns such as ** — the agent rejects the rule and traffic falls through to the Default profile, even if other paths in the list are valid.

      Wildcard support for source application paths is not available on Arch Linux ARM64. On Arch Linux ARM64, Prisma Agent cannot identify which application generated a given traffic flow, so source application rules — including those that use wildcards — do not apply. Use destination-based rules on Arch Linux ARM64 endpoints. Wildcard support for source application paths works as expected on Arch Linux x86_64 endpoints.

      Wildcard support for source application paths on Linux requires Prisma Agent 26.2.2 or later. On Linux endpoints running 26.2.1, source application rules require the complete real path of the application and wildcard characters are not supported — use destination-based rules for applications with variable paths on those endpoints.
   4. Create the source application.
   5. Repeat these steps to add more source applications.
4. Set up Destinations if you want to create a split tunnel based on the destination domain or access routes.

   Prisma Agent cannot steer UDP traffic based on destination criteria on Windows endpoints. Any rule that uses the Destination object will not apply to UDP traffic on Windows endpoints.

   1. Select DestinationsAdd Destination.

      Prisma Agent also offers predefined destination domains, such as Okta SAML Authentication Domains, Azure SAML Authentication Domains, Microsoft Client Authentication Domains, and Video Traffic so that you can easily create forwarding rules for these destination domains.
   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.

      • (macOS, Windows, and Linux agents only) 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 don't 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.
        You can enter alphanumeric characters for the FQDN. You can also specify a wildcard domain by including a wildcard character (*) in the FQDN. However, the wildcard must appear only once and must be the first character of the string, and a period must follow the wildcard.

        The following are valid FQDN examples:

        • example.com (exact domain)
        • *.local (wildcard domain)

        The following FQDN examples are not valid:

        • .example.com (missing characters before the first period)
        • *example.com (missing period after the wildcard)
        • my*.example.* (only one wildcard allowed and it must appear at the start of the string)
        • *.example.*.com (wildcard not allowed in middle of string)

        Prisma Agent will check whether your FQDN entry is valid or not. For invalid domain inputs, the "Invalid FQDN format" message appears.

        If you add a port, the port can only contain positive numbers. The range is 1-65535.
        You will select these destinations when setting up the forwarding rules in a forwarding profile. To exclude traffic based on the domain name, select Direct connectivity when configuring the forwarding rule. Prisma Agent will send traffic from the domain 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, select the Best Available - Fail Safe (macOS, Windows, and Linux agents only), Best Available - Fail Open, or your own configured connectivity option when configuring the forwarding rule. Traffic from the domain is routed to Prisma Access, even if it meets the excluded 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.
        (macOS, Windows, and iOS agents only) For IPv6 addresses, you can enter:

        • Single IPv6 addresses using standard notation (for example, 2001:0db8:85a3::)
        • IPv6 subnets using CIDR notation (for example, 2001:0db8:85a3::/48)
        For IPv4 addresses, you can a wildcard character (*) in the IP address, but the wildcard must not appear in the middle of the IP address. Once a wildcard is used, all the following octets must also be wildcards.

        The following are some examples of valid IPv4 addresses:

        • 1.2.3.4 (exact IP address)
        • 1.4.3.* (wildcard IP address)
        • 1.*.*.*
        • *.*.*.* (full wildcard IP address)
        • 1.2.3.4/32 (exact IP address followed by CIDR)

        The following are examples of an invalid IPv4 address:

        • 1.2.3.300 (each byte must be 0-255)
        • 3.3.3.3/255.255.255.256 (invalid subnet mask)

        Prisma Agent will check whether your IP address entry is valid or not. For invalid inputs, a message appears indicating that the IP address is not valid.

        In some cases (such as 1.2.*.4 and 7.7.7.7/33), the configuration validator will allow the entry, but the agent will ultimately reject it because the entry does not adhere to a supported format. In this case, the agent will reject the forwarding profile rule and fall back to the fail-safe mode, forwarding all traffic to the tunnel.
        If you don't 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), Prisma Agent sends these routes 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 Best Available - Fail Safe (macOS, Windows, and Linux agents only), Best Available - Fail Open, or your own configured connectivity option 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 exclude routes that are more specific than include routes; otherwise, you might exclude more traffic than intended. For example:

   4. Create the destinations.
   5. Repeat these steps to add more destinations.
5. Set up Connectivity options to direct traffic based on the connectivity method.

   1. In the Forwarding Profiles Setup page, select ConnectivityAdd Connectivity.

      Prisma Agent also offers predefined connectivity options when users are using the best available location but the tunnel and proxy (if enabled) are not available or the traffic type is unsupported (such is IPv6 traffic).

      • (macOS, Windows, and Linux agents only) Best Available - Fail Safe—Connect to the nearest gateway or Prisma Access location but block access if the user can’t connect to the tunnel and proxy (when enabled) or the traffic type is unsupported, such as proxy-only UDP traffic. Linux agents require Prisma Access Agent 26.3 or later.
      • Best Available - Fail Open—Connect to the nearest gateway or Prisma Access location but allow direct access even if the user can’t connect to the tunnel and proxy (when enabled) or the traffic type is unsupported, such as proxy-only UDP traffic.
   2. Enter a meaningful Name for the connectivity option you want to add.
   3. Configure the Connectivity Methods. By default, only the Tunnel connectivity method is enabled, but you can also send traffic to a proxy by enabling Proxy (macOS and Windows agents only).

      • To direct internet traffic only through the tunnel, enable Tunnel and disable Proxy.
      • To direct internet traffic only to the proxy, disable Tunnel and enable Proxy.
      • To direct internet traffic to the proxy only when the tunnel is disconnected or unavailable, enable both Tunnel and Proxy. Prisma Agent will send traffic through the tunnel, and if the tunnel becomes disconnected, will send traffic to the proxy.
   4. (macOS and Windows agents only) Select a Fallback behavior if the user isn’t connected using the specified connectivity method. You can prevent access (Block) or allow access (Direct). The default is Direct.

   5. Create your connectivity settings.
   6. Repeat these steps to add more connectivity settings.
6. Create a forwarding profile that allows or excludes traffic based on the source applications, destination, or connectivity options that you defined.

   1. From the Forwarding Profiles page, select Forwarding ProfilesAdd Forwarding Profile.

   2. Enter a meaningful Name for the forwarding profile.
   3. Click Add Rule to add one or more forwarding rules.

      The Forwarding Rules table shows the rules that make up the forwarding profile. By default, all forwarding profiles contain the following rules:

      • (macOS and Windows agents only) The Video Streaming forwarding rule, which sends all network traffic from video streaming apps outside the tunnel (direct connectivity). By excluding lower risk video streaming traffic (such as YouTube and Netflix) from the tunnel, you can decrease bandwidth consumption on the gateway.
      • 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 can’t delete or move the default forwarding rule, but you can disable it or change its Connectivity setting.
      • An implicit forwarding rule for basic endpoint connectivity that allows traffic such as DHCP, loopback, Prisma Agent management plane, ADEM, and Remote Browser Isolation (RBI) traffic. The implicit forwarding rule isn’t displayed and can’t be changed.

      The traffic forwarding rules are applied from the top down in the forwarding profile. This means that when Prisma Agent receives a connection request, it evaluates the forwarding rules from the top to the bottom of the Forwarding Rules table. The agent matches the connection against each rule's criteria. When all criteria in a rule match, the agent applies that rule's connectivity method to route the traffic. If a rule does not match, the agent continues evaluating the next rule in the table until it finds a match or reaches the default rule. Therefore, configure the forwarding profile in a top-down manner, such as configuring the most specific rules first and the least specific rules last.

      Traffic forwarding rules are applied from the top down in the forwarding profile. Therefore, configure the forwarding profile in a top-down manner, such as configuring the most specific rules first and the least specific rules last.
   4. Enter the specifications for the forwarding rule.

      1. Enter a Name for the rule.
      2. Select a 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 specified source application makes the connection.
      3. Select a Destination. 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.
         Prisma Agent cannot steer UDP traffic based on destination criteria on Windows endpoints. Any rule that uses the Destination object will not apply to UDP traffic on Windows endpoints.
      4. Select a Connectivity option that you configured, or select one of the following predefined connectivity options:
         • 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.
         • Block—Blocks traffic at the endpoint.
         • (macOS and Windows agents only) Bypass— Bypasses the matching traffic to allow third-party agents on endpoints to process the connections if they are active and configured to handle the designated traffic. If no third-party agent is present or configured to handle the traffic, the system sends the traffic to the tunnel (if present) or directly to its destination if the tunnel is not present.
         • (macOS and Windows agents only) Best Available - Fail Safe—Connects to the nearest gateway or Prisma Access location but blocks all traffic when the tunnel is down or for unsupported traffic types.
         • Best Available - Fail Open—Connects to the nearest gateway or Prisma Access location but allows traffic to go directly to its destination when the tunnel is down or for unsupported traffic types. This is the default.
      5. 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—Includes or excludes rules that are applied only to DNS traffic and not to network application traffic. All network application traffic goes through the tunnel regardless of the split tunnel based on the destination domain that you specified for inclusions or exclusions.
         • 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. This is the default.
         • 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 source 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. Click Add to save the forwarding rule.
   6. In the Forwarding Rules table, adjust the priority of the rules in a top-down manner, such that the most specific rules go first and the least specific rules go last in the table. You can select the checkbox next to a rule and select Move Up or Move Down.
7. (macOS and Windows agents only) Configure the Traffic Enforcement options to determine how you want traffic to be enforced.

   • Block outbound LAN access when connected to the tunnel—When enabled, the agent 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 Agent. The default setting is disabled.
   • Block inbound access when connected to the tunnel—When enabled, the agent blocks all inbound connections from the tunnel. The default setting is disabled.
8. Create your forwarding profile.
9. Push the configuration by selecting Push ConfigPush. This action will make your forwarding profile available for selection in the Prisma Agent Setup page.