- The mapping of IP addresses to actual user account information. This is imperative for troubleshooting and/or analyzing logged data, as IP address assignments change over time.
- The usage of user/group information within a security policy. This allows administrators to get very granular with how they enforce corporate security posture.
In most Palo Alto Networks firewall deployments, I see User-ID configured via an agent that ties into Active Directory. However, this is typically where the integration stops. It is imperative that as much user information as possible is ingested by the firewall so that logs and security policy remain consistent. User-ID provides other mechanisms by which we can tie into user account information (i.e. syslog, API, etc.). After all, active directory is only one of those ways. Specific to Ruckus Wireless, the integration happens via syslog. As users authenticate via 802.1X or captive portal with their credentials, this information is logged in the controller. We just need to share it with the firewall.
On
the Ruckus controller(s):
- Enable the Client Association option in the Debug Logs. This will allow ZoneDirector to log the client associations containing client login information and IP.
- Enable syslog forwarding in ZoneDirector to the firewall's MGT IP or User-ID agent IP.
- Enable the MGT interface to receive syslog under Device -> Setup -> Management -> Management Interface Settings.
- Navigate to Device -> User Identification -> User Mapping -> Palo Alto Networks User ID Agent Setup -> Syslog Filters -> Add.
- Create a filter to recognize the syslog messages sent from ZoneDirector.
- Name: Ruckus Wireless
- Type: Regex Identifier
- Event Regex: operation=(update|add){1}
- Username Regex: sta_name (?:=.*\\|=)([a-z]+);
- Address Regex: sta_ip=(10\.[0-9]+\.[0-9]+\.[0-9]+); ## change this to reflect your IP range
- Navigate to Device -> User Identification -> Server Monitoring -> Add
- Name: Ruckus Wireless
- Type: Syslog Sender
- Network Address: (IP of ZoneDirector)
- Filter: Ruckus Wireless
- Commit
No comments:
Post a Comment