2.1 Ensure that IP addresses are mapped to usernames - Zones

Information

Configure appropriate settings to map IP addresses to usernames. Mapping userids to IP addresses is what permits the firewall to create rules based on userids and groups rather than IP addresses and subnets, as well as log events by userids rather than IP addresses or DNS names. The specifics of how to achieve IP-to-username mapping is highly dependent on the environment. It can be enabled by integrating the firewall with a domain controller, Exchange server, captive portal, Terminal Server, User-ID Agent, XML API, or syslog data from a variety of devices.
Rationale:
Understanding which user is involved in a security incident allows appropriate personnel to move quickly between the detection and reaction phases of incident response. In environments with either short DHCP lease times, or where users may move frequently between systems, the ability to analyze or report, or alert on events based on user accounts or user groups is a tremendous advantage. For forensics tasks when DHCP lease information may not be available, the Source User information may be the only way to tie together related data.

NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.

Solution

To Set User-ID Agents
Navigate to Device > User-ID Agents
Set the Name, IP Address and Port of the User-ID Agent

Enable User Identification for each monitored zone that will have user accounts:
Navigate to Network > Zone, for each relevant zone enable User Identification

To Set Terminal Services Agents
Navigate to Device > Terminal Services Agents
Set the Name, IP Address and Port of the Terminal Services Agent

Enable User Identification for each monitored zone that will have Terminal Servers:
Navigate to Network > Zone, enable User Identification

See Also

https://workbench.cisecurity.org/files/1780

Item Details

Category: CONFIGURATION MANAGEMENT

References: 800-53|CM-6b., CSCv6|6.5

Plugin: Palo_Alto

Control ID: 7430e1f9e4bdea2234c98c6ef9e99c6428715ccb0fb20f2030b2b3c540d88039