Device > User Identification > Group Mapping Settings

To base security policies and reports on users and user groups, the firewall retrieves the list of groups and the corresponding list of members specified and maintained on your directory servers. The firewall supports a variety of LDAP directory servers, including the Microsoft Active Directory (AD), the Novell eDirectory, and the Sun ONE Directory Server.
The number of distinct user groups that each firewall or Panorama can reference across all policies varies by model:
  • VM-50, VM-100, VM-300, PA-200, PA-220, PA-500, PA-800 Series, PA-3020, and PA-3050 firewalls: 1,000 groups
  • VM-500, VM-700, PA-5020, PA-5050, PA-5060, PA-5200 Series, and PA-7000 Series firewalls, and all Panorama models: 10,000 groups
Before creating a group mapping configuration, you must configure an LDAP server profile (Device > Server Profiles > LDAP).
The complete procedure TechDocs_logo_cropped.png to map usernames to groups requires additional tasks besides creating group mapping configurations.
Click Add and complete the following fields to create a group mapping configuration. To remove a group mapping configuration, select and Delete it. If you want to disable a group mapping configuration without deleting it, edit the configuration and clear the Enabled option.
Group Mapping Settings—Server Profile
Configured In
DeviceUser IdentificationGroup Mapping Settings
Enter a name to identify the group mapping configuration (up to 31 characters). The name is case-sensitive and must be unique. Use only letters, numbers, spaces, hyphens, and underscores.
Server Profile
DeviceUser IdentificationGroup Mapping SettingsServer Profile
Select the LDAP server profile to use for group mapping on this firewall.
Update Interval
Specify the interval in seconds after which the firewall will initiate a connection with the LDAP directory server to obtain any updates that were made to the groups that firewall policies use (range is 60 to 86,400).
User Domain
By default, the User Domain field is blank: the firewall automatically detects the domain names for Active Directory servers. If you enter a value, it overrides any domain names that the firewall retrieves from the LDAP source. Your entry must be the NetBIOS name.
This field only affects the usernames and group names retrieved from the LDAP source. To override the domain associated with a username for user authentication, configure the User Domain and Username Modifier for the authentication profile you assign to that user (see Device > Authentication Profile).
Group Objects
  • Search Filter—Enter an LDAP query that specifies which groups to retrieve and track.
  • Object Class—Enter a group definition. The default is objectClass=group, which specifies that the system retrieves all objects in the directory that match the group Search Filter and have objectClass=group.
  • Group Name—Enter the attribute that specifies the group name. For example, in Active Directory, this attribute is “CN” (Common Name).
  • Group Member—Enter the attribute that contains the group members. For example in Active Directory, this attribute is “member.”
User Objects
  • Search Filter—Enter an LDAP query that specifies which users to retrieve and track.
  • Object Class—Enter a user object definition. For example in Active Directory, the objectClass is “user.”
  • User Name—Enter the attribute for the username. For example, in Active Directory, the default username attribute is “samAccountName.”
Mail Domains
When the firewall receives a WildFire™ log for a malicious email, the email recipient information in the log is matched against user mapping information from the User-ID agent. The log contains a link to the user that, when clicked, displays the ACC filtered by the user. If the email is sent to a distribution list, the ACC is filtered by the members contained in the list.
The email header and user mapping information will help you quickly track and thwart threats that arrive through email by making it easier to identify the users who received the email.
  • Mail Attributes—PAN-OS automatically populates this field based on the LDAP server type (Sun ONE, Active Directory, or Novell).
  • Domain List—Enter the email domains in your organization as a comma separated list of up to 256 characters.
Select this option to enable server profile for group mapping.
Available Groups
DeviceUser IdentificationGroup Mapping SettingsGroup Include List
Use these fields to limit the number of groups that the firewall displays when you create a security rule. Browse the LDAP tree to find the groups you want to use in rules. To include a group, select it in the Available Groups list and Add ( add_icon.png ) it. To remove a group from the list, select it in the Included Groups list and Delete (  interface_delete_icon.png  ) it.
The combined maximum for the Included Groups and Custom Group lists is 640 entries for each group mapping configuration.
Included Groups
DeviceUser IdentificationGroup Mapping SettingsCustom Group
Create custom groups based on LDAP filters so that you can base firewall policies on user attributes that don’t match existing user groups in the LDAP directory.
The User-ID service maps all the LDAP directory users who match the filter to the custom group. If you create a custom group with the same Distinguished Name (DN) as an existing Active Directory group domain name, the firewall uses the custom group in all references to that name (for example, in policies and logs). To create a custom group, click Add and configure the following fields:
  • Name—Enter a custom group name that is unique in the group mapping configuration for the current firewall or virtual system.
  • LDAP Filter—Enter a filter of up to 2,048 characters.
Use only indexed attributes in the filter to expedite LDAP searches and minimize the performance impact on the LDAP directory server; the firewall does not validate LDAP filters.
The combined maximum for the Included Groups and Custom Group lists is 640 entries.
To delete a custom group, select and Delete it. To make a copy of a custom group, select and Clone it, and edit the fields as appropriate.
After adding or cloning a custom group, you must Commit your changes before your new custom group is available in policies and objects.
LDAP Filter

Related Documentation