Enable User-ID

1. Enable User-ID on the source zones that contain the users who will send requests that require user-based access controls.
   Enable User-ID on trusted zones only. If you enable User-ID and client probing on an external untrusted zone (such as the internet), probes could be sent outside your protected network, resulting in an information disclosure of the User-ID agent service account name, domain name, and encrypted password hash, which could allow an attacker to gain unauthorized access to protected services and applications.
   1. Select NetworkZones and click the Name of the zone.
   2. Enable User Identification and click OK.
2. Create a Dedicated Service Account for the User-ID Agent.
   As a best practice, create a service account with the minimum set of permissions required to support the User-ID options you enable to reduce your attack surface in the event that the service account is compromised.

   This is required if you plan to use the Windows-based User-ID agent or the PAN-OS integrated User-ID agent to monitor domain controllers, Microsoft Exchange servers, or Windows clients for user login and logout events.
3. Map Users to Groups.
   This enables the firewall to connect to your LDAP directory and retrieve Group Mapping information so that you will be able to select usernames and group names when creating policy.
4. Map IP Addresses to Users.
   As a best practice, do not enable client probing as a user mapping method on high-security networks. Client probing can generate a large amount of network traffic and can pose a security threat when misconfigured.

   The way you do this depends on where your users are located and what types of systems they are using, and what systems on your network are collecting login and logout events for your users. You must configure one or more User-ID agents to enable User Mapping:

   • Configure User Mapping Using the Windows User-ID Agent.
   • Configure User Mapping Using the PAN-OS Integrated User-ID Agent.
   • Configure User-ID to Monitor Syslog Senders for User Mapping.
   • Configure User Mapping for Terminal Server Users.
   • Send User Mappings to User-ID Using the XML API.
   • Insert Username in HTTP Headers.
5. Specify the networks to include and exclude from user mapping.
   As a best practice, always specify which networks to include and exclude from User-ID. This allows you to ensure that only your trusted assets are probed and that unwanted user mappings are not created unexpectedly.

   The way you specify which networks to include and exclude depends on whether you are using the Windows-based User-ID agent or the PAN-OSintegrated User-ID agent.
6. Configure Authentication Policy and Captive Portal.
   The firewall uses Captive Portal to authenticate end users when they request services, applications, or URL categories that match Authentication Policy rules. Based on user information collected during authentication, the firewall creates new user mappings or updates existing mappings. The mapping information collected during authentication overrides information collected through other User-ID methods.
   1. Configure Captive Portal.
   2. Configure Authentication Policy.
7. Enable user- and group-based policy enforcement.
   Create rules based on group rather than user whenever possible. This prevents you from having to continually update your rules (which requires a commit) whenever your user base changes.

   After configuring User-ID, you will be able to choose a username or group name when defining the source or destination of a security rule:
   1. Select PoliciesSecurity and Add a new rule or click an existing rule name to edit.
   2. Select User and specify which users and groups to match in the rule in one of the following ways:
      • If you want to select specific users or groups as matching criteria, click Add in the Source User section to display a list of users and groups discovered by the firewall group mapping function. Select the users or groups to add to the rule.
      • If you want to match any user who has or has not authenticated and you don’t need to know the specific user or group name, select known-user or unknown from the drop-down above the Source User list.
   3. Configure the rest of the rule as appropriate and then click OK to save it. For details on other fields in the security rule, see Set Up a Basic Security Policy.
8. Create the Security policy rules to safely enable User-ID within your trusted zones and prevent User-ID traffic from egressing your network.
   Follow the Best Practice Internet Gateway Security Policy to ensure that the User-ID application (paloalto-userid-agent) is only allowed in the zones where your agents (both your Windows agents and your PAN-OS integrated agents) are monitoring services and distributing mappings to firewalls. Specifically:

   • Allow the paloalto-userid-agent application between the zones where your agents reside and the zones where the monitored servers reside (or even better, between the specific systems that host the agent and the monitored servers).
   • Allow the paloalto-userid-agent application between the agents and the firewalls that need the user mappings and between firewalls that are redistributing user mappings and the firewalls they are redistributing the information to.
   • Deny the paloalto-userid-agent application to any external zone, such as your internet zone.
9. Configure the firewall to obtain user IP addresses from X-Forwarded-For (XFF) headers.
   When the firewall is between the Internet and a proxy server, the IP addresses in the packets that the firewall sees are for the proxy server rather than users. To enable visibility of user IP addresses instead, configure the firewall to use the XFF headers for user mapping. With this option enabled, the firewall matches the IP addresses with usernames referenced in policy to enable control and visibility for the associated users and groups. For details, see Identify Users Connected through a Proxy Server.
   1. Select DeviceSetupContent-ID and edit the X-Forwarded-For Headers settings.
   2. Select X-Forwarded-For Header in User-ID.
      Selecting Strip-X-Forwarded-For Header doesn’t disable the use of XFF headers for user attribution in policy rules; the firewall zeroes out the XFF value only after using it for user attribution.
   3. Click OK to save your changes.
10. If you use a high availability (HA) configuration, enable synchronization.
    As a best practice, always enable the Enable Config Sync option for an HA configuration to ensure that the group mappings and user mappings are synchronized between the active and passive firewall.
    1. Select DeviceHigh AvailabilityGeneral and edit the Setup section.
    2. Select Enable HA.
    3. Select Enable Config Sync.
    4. Enter the Peer HA1 IP Address, which is the IP address of the HA1 control link on the peer firewall.
    5. (Optional) Enter a Backup Peer HA1 IP Address, which is the IP address of the backup control link on the peer firewall.
    6. Click OK.
11. Commit your changes.
    Commit your changes to activate them.
12. Verify the User-ID Configuration.
    After you configure user mapping and group mapping, verify that the configuration works properly and that you can safely enable and monitor user and group access to your applications and services.