Set Up Forwarding Profiles to Manage Agent Traffic
Focus
Focus
Prisma Agent

Set Up Forwarding Profiles to Manage Agent Traffic

Table of Contents

Set Up Forwarding Profiles to Manage Agent Traffic

Provide consistent security for internet, SaaS, and private app access across locations, using traffic forwarding rules to optimize traffic routing and policy enforcement.
Where Can I Use This?What Do I Need?
  • Prisma Access (Managed by Strata Cloud Manager)
  • Prisma Access (Managed by Panorama)
  • NGFW (Managed by Panorama)
Forwarding profiles provide a seamless end-to-end security solution for consistent access to internet, SaaS, and private applications for your users under varying conditions. This feature enables always-on security for internet access from any location and on-demand security for private apps based on user presence (remote or on-premises).
To effectively configure and use forwarding profiles, you will need to understand several key components:
Forwarding Profiles
Forwarding profiles contain a set of rules that define how to direct traffic based on various criteria. Once you set up the forwarding profiles, you can assign them to users or user groups in the Agent Settings page. These forwarding profiles allow you to create a comprehensive traffic management strategy tailored to your organization's needs.
Traffic Forwarding Rules
Traffic forwarding rules within forwarding profiles consist of several important elements. Traffic that matches a rule is steered according to the traffic forwarding specifications.
  • (macOS, Windows, and Linux agents only) (Strata Cloud Manager Managed Prisma Access) User Location: You can specify rules based on whether users are remote or on-premises, using methods like Internal Host Detection (IHD) or source IP addresses.
    If enabled, the Internal Host Detection setting in the agent app settings takes precedence over the Internal Host Detection setting in forwarding profiles. Unlike the Internal Host Detection setting in the agent app settings, the Internal Host Detection rules in forwarding profiles don't suppress the tunnel.
  • Traffic Objects: You can define the criteria for traffic handling based on traffic objects. This includes applications, destinations, and traffic types, such as network traffic and DNS traffic. (Applications and domains do not apply to agents on iOS, Android, and ChromeOS.)
  • Connectivity Options: For each rule, you can choose how to route the traffic. Options include:
    • Direct—Allows traffic to go straight to its destination. Selecting Direct will bind the traffic to the physical adapter on the endpoint rather than the tunnel.
    • Block—Blocks traffic at the endpoint
    • Bypass—Ignores specific traffic to enabling third-party agents to handle designated connections (macOS and Windows agents only)
    • Best Available - Fail Safe—Routes traffic through the tunnel to the nearest gateway for inspection and policy enforcement but block access if the user can't connect to the tunnel or the traffic type is unsupported (macOS, Windows, and Linux agents only) Linux agents require Prisma Access Agent 26.3 or later.
    • Best Available - Fail Open—Routes traffic through the tunnel to the nearest gateway for inspection and policy enforcement but allow access even if the user can’t connect to the tunnel or the traffic type is unsupported
    You can also customize your own connectivity option to direct traffic to the tunnel, the proxy (if enabled), or fallback to Advanced DNS Security Resolver if the tunnel is down. (Proxy and ADNS Resolver support are available only for macOS and Windows agents.)
  • (macOS and Windows agents only) Fallback Behavior: For rules using custom connectivity options, you can set the fallback behavior when the primary connection is unavailable:
    • Block—Blocks all traffic when the tunnel is down or for unsupported traffic types
    • Direct—Allows traffic to go directly to its destination when the tunnel is down or for unsupported traffic types
    For agents on iOS, Android, and ChromeOS, the fallback behavior is defined by the mobile device management (MDM) configuration.
  • Predefined Rules—The system includes predefined forwarding rules for common scenarios, such as:
    • (macOS and Windows agents only) Video Streaming—Directs network traffic from video streaming apps such as YouTube and Netflix outside the tunnel (direct connectivity)
    • Default—Sends all DNS and network traffic through the tunnel to Prisma Access for inspection
How Forwarding Profiles Work
When Prisma Agent receives a connection request, it evaluates the forwarding rules in your forwarding profile in priority order. The agent matches the connection against each rule's criteria including destination addresses, source applications, traffic types, and user location. 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 subsequent rules until it finds a match or reaches the default rule.
Before you begin to configure forwarding profiles, refer to Forwarding Profiles Considerations.
On Prisma Agent and GlobalProtect coexistence tenants, Prisma Agents will use forwarding profiles to manage traffic forwarding rules, while GlobalProtect will continue to use existing split tunnel configuration on GlobalProtect gateways.