Palo Alto NGFW lab 16 of 30
Logging, log forwarding, syslog and reports
Get the firewall's logs where the SOC can use them: a syslog server profile, a service route from the DMZ interface, a log forwarding profile on every rule, system and configuration log forwarding, plus log filters, the ACC and a custom report on the box.
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 16 - Logging log forwarding syslog and reports
- Level
- Intermediate
- Time
- About 45 minutes
- Nodes need
- 5 vCPU, 7,680 MB
- Smallest plan
- Lite
The scenario
Calder's new security operations centre (SOC) collects logs over syslog. For this lab, web01 in the DMZ is the collector: every message it receives on UDP 514 is written to /var/log/calder-fw.log. The SOC wants:
- every traffic and threat log from the depot's rules;
- every system event and configuration change.
The firewall's own viewers must stay useful for the team on site.
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
- Name the PAN-OS log types and when each is written
- Configure a syslog server profile and a service route for syslog
- Build a log forwarding profile and attach it to security rules
- Forward system and configuration logs
- Filter logs in the web interface and CLI, use the ACC and create a custom report
The tasks
- The log types
- A syslog server profile and a service route
- A log forwarding profile on every rule
- System and configuration logs
- Generate events and watch them arrive
- Find things fast
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
16 - Logging log forwarding syslog and reportsand 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.