Configure Agent Settings for the Prisma Access Agent (Prisma Access Deployment)

Configure Agent Settings for the Prisma Access Agent (Prisma Access Deployment)

1. Navigate to the Prisma Access Agent setup.

   Expand all
   Collapse all
   • From Strata Cloud Manager:
     1. Select WorkflowsPrisma Access SetupAccess AgentPrisma Access Agent.
   • From Panorama:
     1. From the Cloud Services plugin in Panorama, select PanoramaCloud ServicesPrisma Access AgentConfigure Prisma Access Agent.
     2. Select WorkflowsPrisma Access AgentSetupPrisma Access Agent.
2. Click Add Agent Settings.

   
3. Create an app configuration rule. The configuration rule associates one or more groups of users with app settings that are specific to those users.

   1. In the Detail section, enter a Name for the rule.
   2. Specify the Match Criteria by adding User Entities. Users and groups that match the User Entities criteria will receive the Prisma Access Agent app settings that you specify.

      Expand all
      Collapse all
      • For Strata Cloud Manager Managed Prisma Access:
        • Select the endpoint OS that the app settings apply to. Selecting Match Any will apply the app settings to all supported operating systems. The default is Match Any.

          

        • To deploy the configuration to all users, set User Entities to Match any. This setting is the default.
        • To deploy the configuration to specific user groups or users, set User Entities to Match AnyAdd User and select from the list of user entities. Examples of user entities include usernames and user groups, which are available in cloud directory attributes such as Common Name (CN) and Domain Component (DC).
          Click the + sign to add another user or group. To remove a user or group, click the name of the user or group and select Remove.

          

          

          If you did not configure a security policy for a user group, you can't use the group in the Add Agent Settings page. If you select this user group, the agent configuration settings won't be pushed to the endpoints in this group.
      • For Panorama Managed Prisma Access:
        • To deploy the configuration to all users, set User Entities to Any.
        • To deploy the configuration to specific user groups or users, set User Entities to Select. Then, click Select Users to select from the list of user entities. Examples of user entities include usernames and user groups, which are available in cloud directory attributes such as Common Name (CN) and Domain Component (DC).

          
4. Configure the app settings for the Prisma Access Agent.

   

   • Connect—Specify how the Prisma Access Agent connects to Prisma Access. This setting is required.
     • Select Every time the user logs on to the machine (Always on) to automatically establish a connection to Prisma Access every time the user logs on to an endpoint.
       For Panorama Managed Prisma Access, select Always On.
     • Select Only when the user clicks Connect (On demand) to connect to Prisma Access only when the user clicks Connect (the lock icon) in the Prisma Access Agent.
       For Panorama Managed Prisma Access, select On Demand.
   • Disable Agent—(Strata Cloud Manager) Specify whether to give your users the ability to disable the Prisma Access Agent on their devices. In cases where users have the GlobalProtect app installed on their device along with the Prisma Access Agent, they can conveniently disable the Prisma Access Agent so that they can switch to the GlobalProtect app to avoid interference between the two software. Select one of the following options:
     • Disallow—Users can't disable the Prisma Access Agent using the Prisma Access Agent app. The Disable link isn't available in the settings page in the Prisma Access Agent app. This is the default.
     • Allow—Users can disable the Prisma Access Agent using the Disable link in the settings page in the Prisma Access Agent app.
     After disabling the agent, the user can switch to the GlobalProtect app. The following table shows the Prisma Access Agent behavior after disabling the agent and after switching to GlobalProtect.

     Prisma Access Agent Behavior	After Disabling Prisma Access Agent	After Switching to GlobalProtect
     Connectivity to the tunnel	No	No
     Connectivity to the server (Prisma Access Agent management plane)	Yes	Yes
     Prisma Access agent Notifications	No	No
     Prisma Access Agent enforcer	No	No, but GlobalProtect enforcer is enabled
     ADEM Access Experience status	Yes (independent of agent status)	Yes (independent of agent status)
     Troubleshooting by remote shell	Yes	Yes
     Anti-tamper feature	Yes	Yes
     PACli commands functional	Yes, but don't use pacli connect	Yes, but don't use pacli connect

   • Support Page—Enter the website that users can access for assistance when they click Support Resources in the Prisma Access Agent.
     The default support page is the website for the Prisma Access Agent documentation
   • Access Experience (ADEM, App Acceleration, End user coaching) (Windows & MAC only)—(Strata Cloud Manager) Specify whether to install the ADEM Access Experience agent during the Prisma Access Agent app installation and allow end users to enable or disable user experience tests from the app.
     • Install
     • No action (The agent state remains as is)
     • Uninstall
     For details about getting started with ADEM on Cloud Managed Prisma Access, see Get Started with Autonomous DEM.
   • Enable Digital Experience Management—(Panorama Managed Prisma Access) Enable this to install the ADEM Access Experience agent during the Prisma Access Agent app installation.
   • Display ADEM update notifications—Enable this setting to display notifications from ADEM when an update is available on the endpoint.
   • Session timeout—(Configurable only on Strata Cloud Manager) Prisma Access Agent user sessions are created when a user connects to the gateway (location) and successfully authenticates. The session is then assigned to a specific gateway that determines which traffic to tunnel based on any defined split tunnel rules. The minimum Prisma Access dataplane version must be 11.2.
     Specify the amount of time that must elapse before the session times out due to inactivity. This setting is required.
     If you're using the Nebula (10.2) dataplane in Prisma Access, the Session timeout value isn’t configurable and by default is seven days.
   • Append Local Search Domains to Tunnel DNS Suffixes (Mac only)—Enable this setting to append tunnel DNS search domains to local DNS search domains on macOS endpoints. Appending tunnel search domains to an endpoint's local DNS search domains enables users to quickly access local and remote corporate websites and servers that they visit frequently without entering the complete address.
   • Detect Proxy for Each Connection (Windows only)—Enable this setting to automatically detect the proxy at every connection. Disable this setting if you want to automatically detect the proxy for the gateway connection and use that proxy for subsequent connections to Prisma Access.
   • Set Up Tunnel Over Proxy (Windows and Mac Only)—Enable this setting to configure network traffic behavior based on Prisma Access Agent proxy use. Select Enable to require the Prisma Access Agent to use proxies. Disable this setting if you want to require the Prisma Access Agent to bypass proxies. Based on the Prisma Access Agent proxy use, endpoint OS, and tunnel type, network traffic will behave differently.
     If you disable this option, Prisma Access Agent will bypass the proxies. All HTTP or HTTPS traffic that matches the proxy or PAC file rules is required to traverse the Prisma Access Agent tunnel before reaching the intended destination. By bypassing proxies, you can prevent users from setting up a personal proxy to access web resources without going through the tunnel for inspection and policy enforcement.

   

   • Optimized MTU—(Strata Cloud Manager) The maximum transmission unit (MTU) is the largest packet size that Prisma Access Agent can send in a packet during a transmission. Enable this option to automatically determine the best MTU to use for packet transmissions.
     Prisma Access Agent connections can traverse through multiple ISPs and network hops with MTU values lower than the standard 1500 bytes. When the static agent MTU value is lower than what an ISP is offering, excessive fragmentation and additional overhead occurs, resulting in lower throughput. Dropped packets in the ISP network path also trigger retransmissions that contribute to suboptimal performance. Using Optimized MTU can help you avoid tedious manual determination and configuration of the optimal MTU value, and prevent users from experiencing poor performance that impacts their productivity.
     Optimized MTU is enabled by default. If you disable it, you can manually configure the MTU. The Configurable MTU (bytes) range is 576-1500 bytes. If you set a value outside this range, the system will default to 1400 bytes.
   • Inbound Authentication Prompts from MFA Gateways—To support multi-factor authentication (MFA), a Prisma Access Agent endpoint must receive and acknowledge UDP prompts that are inbound from the gateway. Enable this setting to allow a Prisma Access Agent endpoint to receive and acknowledge the UDP prompts. This setting is enabled by default. Disable this setting to block UDP prompts from the gateway.
   • Network Port for Inbound Authentication Prompts (UDP)—Specifies the port number a Prisma Access Agent endpoint uses to receive inbound authentication prompts from MFA gateways. The default port is 4501. To change the port, specify a number 1-65535.
   • MFA Trusted Host list—Add the hosts for firewalls or authentication gateways that a Prisma Access Agent endpoint can trust for multi-factor authentication. When an endpoint receives a UDP message on the specified network port, the Prisma Access Agent displays an authentication message only if the UDP prompt comes from a trusted gateway.
   • Inbound Authentication Messages—Customize a notification message to display when users try to access a resource that requires additional authentication.
     When users try to access a resource that requires additional authentication, Prisma Access Agent receives a UDP packet containing the inbound authentication prompt and displays this message. The UDP packet also contains the URL for the Authentication Portal page you specified when you configured multi-factor authentication. Prisma Access Agent automatically appends the URL to the message.
     For example:

     You have attempted to access a protected resource that requires additional authentication. Do you want to continue?

     The message can have 255 or fewer characters.
   • Suppress Multiple Inbound MFA Prompts (sec)—Specify the number of seconds to wait before Prisma Access Agent can suppress multiple inbound UDP prompts. The default is 180 seconds.
   • Allow user to sign out—Enable this setting to permit your users to sign out of the Prisma Access Agent. This setting is disabled by default.
5. (Optional) If you don’t require your Prisma Access Agent users to connect to Prisma Access when they are on the internal network, enable Internal Host Detection. This will enable the Prisma Access Agent to determine if it's on an internal or external network.

   

   1. Enter the IP Address (IPv4) of a host that Prisma Access Agent can resolve from the internal network only.
   2. Enter the DNS Hostname that resolves to the IP address that you entered.

   When a mobile user connects to Prisma Access, the Prisma Access Agent attempts a reverse DNS lookup on the specified address. If the lookup fails, the Prisma Access Agent determines that it's on the external network and initiates a tunnel to Prisma Access.
6. Configure external and gateway settings for the Prisma Access Agent.
7. (Optional) Select a Forwarding Profile that you configured to manage how traffic flows between the agent and Prisma Access. For example, you can set up split tunnels to exclude traffic from certain applications or destinations from the tunnel while routing all other traffic through the tunnel.

   
8. (Optional) Configure HIP data collection settings.
9. When you have finished setting up the Prisma Access Agent settings, click Save. For Panorama Managed Prisma Access, click Create.