Configure Agent Settings for the Prisma Access Agent (Panorama)

1. Navigate to the Prisma Access Agent setup.

   • For Panorama Managed Prisma Access deployments:
     1. From the Cloud Services plugin in Panorama, select PanoramaCloud ServicesPrisma Access AgentLaunch Prisma Access Agent.
     2. Select WorkflowsPrisma Access AgentSetup.
   • For Panorama Managed NGFW deployments:
     1. Log in to Strata Cloud Manager as the administrator.
     2. Select WorkflowsPrisma Access AgentSetup.

2. Select Prisma Access AgentAdd Agent Settings.

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

   1. 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.

      • To deploy the configuration to all users, select Match Any.
      • To deploy the configuration to specific user groups or users, select Match Users. 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.

   You can configure the following app settings:

   • 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.
     • 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 app.
   • Disable Agent—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—Does not allow users to disable the agent. The Disable option is not available in the Prisma Access Agent app.
     • Allow—Users can disable the Prisma Access Agent using the Disable option 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

   • Allow user to sign out—Enable this setting to permit your users to sign out of the Prisma Access Agent. Default: Disabled.
   • Support Page—Enter the website that users can access for assistance when they click Support Resources in the Prisma Access Agent.
     Default: The website for the Prisma Access Agent documentation.
   • 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.
   • Optimized MTU—The maximum transmission unit (MTU) is the largest packet size that Prisma Access Agent can send in a packet during a transmission. When enabled, Prisma Access Agent will automatically determine the best MTU to use for packet transmissions.
     Default: Enabled. You can disable this option to manually configure the MTU. The Configurable MTU (bytes) range is 576-1500 bytes. If you set a value outside this range or don't specify a value, the system will default to 1400 bytes.
   • Session timeout—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.
     Specify the amount of time that elapses before the session ends. During the session, the user stays logged in as long as the gateway receives a HIP check from the endpoint. After this time, the session ends automatically. The default is 10 days. This setting is required.
     Learn how to Customize Prisma Access Agent Session Timeout Settings.
   • Notify Before Session Expires—Specify when to notify the user before a session expires. You can enter a value between 0-120 minutes. The default is 0 minutes. The value must be less than the value for Session timeout.
     For example, if you set the value to 120 minutes, the Prisma Access Agent will display the notification to the user two hours before their session expires. If you don't want any notification to be displayed, set the value to 0.
     For the notification to appear on the endpoint, PAN-OS must be at version 11.2 or later.
   • Session Timeout Expiration Message— Enter a message to display to the users when their sessions are about to expire. The maximum length for the message is 127 alphanumeric characters. The user will receive the notification as part of the system notification framework on the endpoint.
5. (Optional) Configure the Proxy settings.

   • Local Proxy Port (Optional)—Configure the local proxy port used for transparent proxy support. The Prisma Access Agent uses a local proxy to route outgoing connections to Prisma Access explicit proxy servers based on customizable forwarding profiles.
     Default: 9999. Range: 1024-65534.
     If the default port isn't available, Prisma Access Agent will try 50 other ports in the range of 9999-10009 and use the port that’s available. If none is available, Prisma Access Agent will use a random port assigned by the operating system. You can also enter your own port number within the range.
   • 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 the gateway. Default: Disabled.
6. Configure MFA settings.

   • 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.
7. Enable Endpoint Insights to collect comprehensive troubleshooting endpoint data for analysis.

8. Configure ADEM settings.

   • Access Experience (Optional)—Specify whether to install the ADEM Access Experience agent during the Prisma Access Agent app installation and to let end users enable or disable user experience tests from the app.
     • Install
     • No action (The agent state remains as is)
     • Uninstall
   • Display ADEM update notifications—Enable this setting to display notifications from ADEM when an update is available on the endpoint.
9. Enable Internal Host Detection if you don’t require your Prisma Access Agent users to connect to the gateway when they are on the internal network. This option will enable the Prisma Access Agent to determine if it's on an internal or external network.

   Default: Disabled

   After you enable this option, complete the following steps:

   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.
10. Configure external and internal gateways for the Prisma Access Agent by selecting the external and internal gateways that you configured in the Infrastructure tab.
11. (Optional) Select a Forwarding Profile that you configured previously 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.
12. (Optional) Configure HIP Data Collection Settings for the Prisma Access Agent
13. When you have finished setting up the Prisma Access Agent settings, click Create.