User-ID provides many different methods for mapping
IP addresses to usernames. Before you begin configuring user mapping,
consider where your users are logging in from, what services they
are accessing, and what applications and data you need to control
access to. This will inform which types of agents or integrations
would best allow you to identify your users.
Once you have your plan, you can begin configuring user mapping
using one or more of the following methods as needed to enable user-based
access and visibility to applications and resources:
If you have users with client
systems that aren’t logged in to your domain servers—for example,
users running Linux clients that don’t log in to the domain—you
IP Addresses to Usernames Using Captive Portal. Using Captive
Portal in conjunction with Authentication
Policy also ensures that all users authenticate to access
your most sensitive applications and data.
To map users as they log in to your Exchange servers, domain
controllers, eDirectory servers, or Windows clients you must configure
a User-ID agent:
While you can configure either the Windows
agent or the PAN-OS integrated User-ID agent on the firewall to
listen for authentication syslog messages from the network services,
because only the PAN-OS integrated agent supports syslog listening
over TLS, it is the preferred configuration.
A large-scale network can have hundreds of information sources
that firewalls query for user and group mapping and can have numerous
firewalls that enforce policies based on the mapping information.
You can simplify User-ID administration for such a network by aggregating
the mapping information before the User-ID agents collect it. You
can also reduce the resources that the firewalls and information
sources use in the querying process by configuring some firewalls
to redistribute the mapping information. For details, see Deploy
User-ID in a Large-Scale Network.