Palo Alto NGFW lab 6 of 30
Security policy fundamentals
Write the depot's first real rulebase: address objects, groups and tags; allow rules built on App-ID with application-default; a deny rule placed above the allow; logging on the default rules; shadowed rules; and the tools to prove which rule matches: test security-policy-match, the session table, traffic logs and rule hit counts.
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 06 - Security policy fundamentals
- Level
- Beginner
- Time
- About 50 minutes
- Nodes need
- 5 vCPU, 7,680 MB
- Smallest plan
- Lite
The scenario
The depot firewall routes between its zones (lab 04), and an outbound NAT rule is already in place so users can reach the internet once policy allows it (you'll build NAT yourself in lab 07). Right now no security rule exists, so every interzone flow hits interzone-default and is denied. Calder's policy, agreed with the depot manager, is:
- Depot users may browse the intranet on web01 (web, HTTPS, ping).
- Only the admin workstation (Client-PC, 10.1.1.10) may SSH to the DMZ servers.
- Depot users may browse the internet (web, HTTPS, DNS, ping).
- Nobody may SSH out to the internet.
- Everything else is denied, and logged.
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
- Create address objects, an address group and tags
- Write allow and deny rules between zones with App-ID and application-default
- Order rules correctly and recognise a shadowed rule at commit
- Override the interzone default rule to log denied traffic
- Prove the matching rule with test security-policy-match, sessions, traffic logs and hit counts
The tasks
- Objects and tags
- Write the rules in the right order
- Log what the default rules deny
- A shadowed rule
- Prove which rule matches
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
06 - Security policy fundamentalsand 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.