Configure Prisma Agent App Settings for Dynamic Privilege Access

1. Log in to Strata Cloud Manager as the Project Admin.
2. Select ConfigurationNGFW and Prisma AccessOverview and expand the Configuration Scope to view the Snippets.

3. Select the snippet that the Superuser admin assigned to you.

   You can also view the snippets that are not assigned to you, but you cannot interact with them, such as to change the configuration.
4. Select ObjectsDynamic Privilege Access to open the Dynamic Privilege Access settings.

5. Select the Agent Settings tab.
6. Strata Cloud Manager provides you with the default agent settings. If you don't want to use the default settings. Select Add Agent Settings.

   To edit the settings for an agent, select an agent name from the table.

7. Create an app configuration rule. The configuration rule associates one or more projects with certain settings that are specific to those projects.

   1. Enter a Name for the rule.
   2. Specify the Match Criteria by adding Projects. Users and groups that match the Project criteria will receive the app settings when they log in to the project using the Prisma Agent.

      • To deploy the configuration to all users, set Projects to Any.
      • To deploy the configuration to users who log in to specific projects, set Projects to Add Projects and select from the list of projects.

8. Configure the app settings for the Prisma Agent.

   • Connect—Specify how the Prisma 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 Agent.
   • Support Page—Enter the website that users can access for assistance when they click Support Resources in the Prisma 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)—Specify whether to install the ADEM Access Experience agent during the Prisma 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.
   • Display ADEM update notifications—Enable this setting to display notifications from ADEM when an update is available on the endpoint.
   • Gateway Session Timeout—Prisma 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)
   • Aggressive Authentication—Enable this option to force immediate re-authentication during manual gateway connection, gateway session extension, machine reboot, and user refresh token expiry.
     When disabled, re-authentication is required only when the user refresh token expires.
   • 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 Agent proxy use. Select Enable to require the Prisma Agent to use proxies. Disable this setting if you want to require the Prisma Agent to bypass proxies. Based on the Prisma Agent proxy use, endpoint OS, and tunnel type, network traffic will behave differently.
     If you disable this option, Prisma Agent will bypass the proxies. All HTTP or HTTPS traffic that matches the proxy or PAC file rules is required to traverse the Prisma 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.

   • Inbound Authentication Prompts from MFA Gateways—To support multi-factor authentication (MFA), a Prisma Agent endpoint must receive and acknowledge UDP prompts that are inbound from the gateway. Enable this setting to allow a Prisma 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 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 Agent endpoint can trust for multi-factor authentication. When an endpoint receives a UDP message on the specified network port, the Prisma 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 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 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 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 Agent. This setting is disabled by default.
9. Select a Forwarding Profile that you configured previously to manage how traffic flows between the agent and Prisma Access.

10. Configure DNS settings for Dynamic Privilege Access.
11. Configure Host Information Profile settings
12. When you have finished setting up the Prisma Agent settings, click Save.