Palo Alto NGFW lab 15 of 30
User-ID: API and syslog mapping, dynamic user groups and user-based policy
Write policy for people instead of addresses: map users to IP addresses through the XML API and a syslog listener that parses Wi-Fi controller logins, restrict the finance portal to one user, then quarantine contractors with a dynamic user group tagged through the API.
Run this lab
It needs Lite: its 4 nodes are set to 5 vCPU and 7,680 MB in total. That fits the free demo too.
In your workspace: Shared, then Palo Alto NGFW PAN-OS 11 guided labs, then 15 - User-ID - API and syslog mapping dynamic user groups and user-based policy
- Level
- Advanced
- Time
- About 55 minutes
- Nodes need
- 5 vCPU, 7,680 MB
- Smallest plan
- Lite
The scenario
Calder wants rules written for people:
- The finance portal on web01 is for the finance team only (alice).
- Contractors (bob is one) must be kept off the DMZ servers completely, whichever desk they sit at.
There is no Active Directory in this lab, so you'll feed the firewall user information the way modern networks often do:
- from an identity system through the XML API;
- from a Wi-Fi controller's syslog login messages.
Client-PC plays both the users' desktop and the Wi-Fi controller.
KEY=$(curl -sk https://10.1.1.254/api/ -d type=keygen -d user=admin --data-urlencode password=Lab-Access-1 | grep -o '<key>[^<]*' | cut -c6-)Before you start. Start all the nodes. The firewall takes 6-8 minutes to boot and comes up with this lab's starting configuration already loaded. Wait until the FW1 console shows
FW1 login:, then log in asadmin/Lab-Access-1. Until the management plane is ready it answers Login incorrect, even with the right password. The Linux hosts are ready within seconds.
What you’ll practise
- Explain the User-ID mapping sources and enable User-ID on the right zones
- Create user-to-IP mappings with the XML API
- Configure a syslog listener, parse profile and syslog sender to map users from login events
- Write security rules with source users and a custom URL category
- Tag users with the API and use a dynamic user group in policy
The tasks
- Where User-ID gets its information
- Map alice with the XML API
- Rules for the finance portal
- Map users from Wi-Fi controller logins (syslog)
- Quarantine contractors with a dynamic user group
The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.
Topology and devices
The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.
Every link, as text
- FW1
mgmtto Inside (network) - FW1
ethernet1/1to Outside (network) - FW1
ethernet1/2to Inside (network) - FW1
ethernet1/3to DMZ (network) - Client-PC
eth0to Inside (network) - web01
eth0to DMZ (network) - Internet
eth0to Outside (network)
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| FW1 | Palo Alto Networks VM-Series (PAN-OS) | paloalto-11.2.5 | 2 vCPU, 5,632 MB |
| Client-PC | EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 1,024 MB |
| web01 | EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 512 MB |
| Internet | EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 512 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
Palo Alto NGFW PAN-OS 11 guided labs.Open
15 - User-ID - API and syslog mapping dynamic user groups and user-based policyand start its nodes, then open Lab Tasks for the scenario and the steps.
The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.
More Palo Alto NGFW labs
Related labs in other courses
CloudLabBox is independent of Palo Alto Networks and Cisco. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.