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

Try it free for 30 minutesRun it on Lite from £3 a day

The free demo needs no card and no email. Every lab plan includes every guided lab.

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 as admin / 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

  1. The log types
  2. A syslog server profile and a service route
  3. A log forwarding profile on every rule
  4. System and configuration logs
  5. Generate events and watch them arrive
  6. 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.

Topology of Logging log forwarding syslog and reports4 nodes and 3 networks, 7 links. Every link is listed as text below the diagram.FW1Client-PCweb01InternetInsideOutsideDMZeth0ethernet1/3eth0mgmtethernet1/2eth0ethernet1/1
4 nodes and 3 networks, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Nodes in Logging, log forwarding, syslog and reports, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
FW1Palo Alto Networks VM-Series (PAN-OS)paloalto-11.2.52 vCPU, 5,632 MB
Client-PCEVE-NG GUI server (Docker)eve-gui-server:latest1 vCPU, 1,024 MB
web01EVE-NG GUI server (Docker)eve-gui-server:latest1 vCPU, 512 MB
InternetEVE-NG GUI server (Docker)eve-gui-server:latest1 vCPU, 512 MB

How to open this lab

  1. Sign in to your workspace at lab.cloudlabbox.com.

  2. In File Manager, open Shared, then the folder Palo Alto NGFW PAN-OS 11 guided labs.

  3. Open 16 - Logging log forwarding syslog and reports and 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

All 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.