Configure Agent Settings for the Prisma Access Agent (Strata Cloud Manager)

1. Select ConfigurationNGFW and Prisma AccessConfiguration ScopeAccess 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. Users and groups that match the OS and User Entities criteria will receive the Prisma Access Agent app settings that you specify.

      • 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.
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—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.
     • (Not supported on Prisma Access Agent Linux) Allow with One Time Password—Users can disable the Prisma Access Agent using a one-time password (OTP). With this option enabled, you can obtain a one-time password (OTP) from the Endpoint Management page (ConfigurationEndpoint Management) and share it with the user. Prisma Access Agent will prompt the user to enter the OTP when they try to disable the agent.
     After disabling the agent, the user can switch to the GlobalProtect app. You can learn about the Prisma Access Agent behavior after disabling the agent and after switching to GlobalProtect.
   • 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
   • (Not supported on Prisma Access Agent Linux) Access Experience (ADEM, App Acceleration, End user coaching) (Windows & MAC only)—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.
   • (Not supported on Prisma Access Agent Linux) Display ADEM update notifications—Enable this setting to display notifications from ADEM when an update is available on the endpoint.
   • Gateway 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 forwarding rules.
     Gateway Session Timeout controls how long an established connection to the gateway remains valid. 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. (Default: 10 days)
     You can use gateway session timeout settings along with re-authentication timers to control how often users need to explicitly re-authenticate.
   • 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.
   • (Not supported on Prisma Access Agent Linux) Local Proxy Port—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 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—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 leave it unconfigured, the system will default to 1400 bytes. If you set a value outside this range, the text box will turn red and the Save button becomes disabled. For example:

   • (Not supported on Prisma Access Agent Linux) 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.
   • (Not supported on Prisma Access Agent Linux) 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.
   • (Not supported on Prisma Access Agent Linux) 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.
   • (Not supported on Prisma Access Agent Linux) 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.
   • (Not supported on Prisma Access Agent Linux) 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.
   • (Not supported on Prisma Access Agent Linux) Enable Pre-Logon Device Tunnel—Enable this setting to establish a pre-logon tunnel before a user logs in to their device. The pre-logon tunnel provides essential network access for managing and updating remote devices without requiring end-user authentication.
     You can configure the Post-Logon Behavior according to on your operational requirements:
     • To maintain the pre-logon tunnel until users successfully authenticate, select Persistent Pre-Logon Tunnel. This is the default post-logon behavior.
     • To maintain the pre-logon tunnel for a specified duration after OS login, select Terminate Pre-Logon Upon OS Login and set the Pre-Logon Tunnel Rename Timeout value in minutes. The range is 0-180 minutes. The default is 5 minutes.
       This setting determines how long the pre-logon tunnel will remain active before transitioning to a user-specific tunnel (when the pre-logon tunnel gets renamed to the user-specific tunnel).
       Setting the pre-logon tunnel rename timeout to 0 will disconnect the pre-logon tunnel immediately upon OS login.

   • (Not supported on Prisma Access Agent Linux) Enable Endpoint Insights to collect comprehensive troubleshooting endpoint data for analysis.
     When you enable this setting, Prisma Access Agent automatically captures diagnostic snapshots when predefined system events occur. It also collects diagnostics periodically and on-demand (through administrator-triggered diagnostic collection or user issue reporting). (Default: Disabled)
     Enable User Consent Required to display a consent dialog to the end user requesting permission to collect diagnostic data. If the user approves the request, the diagnostic collection proceeds. If the user denies the consent, the diagnostic collection fails. (Default: Disabled)

   • Show Advanced Options—Open the menu containing advanced agent settings. For example:
     • Authentication
       • Use Single Sign-on (Windows)—Select this option to prevent the embedded browser from appearing on a Windows endpoint during single sign-on with Windows Hello for Business.

       • Use Single Sign-on (Mac)—Select this option to prevent the embedded browser from appearing on a macOS endpoint during single sign-on using Platform SSO.
       • Use External Browser for Authentication—Select this option to use the default system browser on the endpoint for SAML authentication.
         Default: Unchecked (use the embedded browser for SAML authentication).
     • (Not supported on Prisma Access Agent Linux) Anti-Tamper
       Configure the Prisma Access Agent anti-tamper protection:
       • Privileged Access Protection—Select this option to enable anti-tamper protection on the endpoints that meet the Match Criteria. Enabling this option reveals the anti-tamper configuration options. (Default: Disabled)
       • Tamper Protection Auto Enable Duration (min)—Specify a time window (30-480 minutes) during which privileged commands can be executed after validation. (Default: 30 minutes)
       • Privileged Access Token—Enter and confirm an emergency access password for use in critical access scenarios. The token must have 8-16 alphanumeric characters with at least one uppercase letter, lowercase letter, number, and optionally one special character from the following set: @$!%*?&
         The Privileged Access Token is required when you enable Privileged Access Protection.
       These settings are only visible to administrators with superuser privileges through RBAC controls.
5. (Optional) If you prefer your Prisma Access Agent users not connect to Prisma Access when they are on your internal network, enable Internal Host Detection. Configuring IHD will enable Prisma Access Agent to identify whether the users are on an internal or external network. This determination enables the Prisma Access Agent to decide whether a tunnel is required and apply the appropriate security policies. If an internal network is detected, the tunnel is suppressed; if the network is external, the tunnel is established and security policies are enforced.

   1. Enter the IPv4 IP Address of a host that Prisma Access Agent can resolve from the internal network only. The IP address you specify must be compatible with the IP address type. For example, enter 198.51.100.0 for IPv4.
   2. Enter the DNS Hostname that resolves to the IP address within the internal network that you entered.

   When the user connects to a network, the Prisma Access Agent does a reverse DNS lookup using the specified IP Address to the specified Hostname. The host serves as a reference point that does not have to be reachable, but the reverse DNS lookup should be successful only when the endpoint is inside the enterprise network. If the agent finds the host, the endpoint is inside the network and the agent connects to an internal gateway, if configured, or the agent shows the connection status as internal. If the agent fails to find the internal host, the endpoint is outside the network and the agent establishes a tunnel to one of the external gateways.
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.