FortiGate lab 5 of 25
Firewall policies and objects
Replace an empty rule base with least-privilege policies built from address, FQDN, service and schedule objects, then fix a shadowed rule by moving it and prove which policy matches with the session table and the policy lookup.
Run this lab
It needs Lite: its 5 nodes are set to 5 vCPU and 6,656 MB in total. That fits the free demo too.
In your workspace: Shared, then FortiGate NSE 4 guided labs, then 05 - Firewall policies and objects
- Level
- Intermediate
- Time
- About 70 minutes
- Nodes need
- 5 vCPU, 6,656 MB
- Smallest plan
- Lite
The scenario
After an audit, Harbourside's old "any to any" rule was deleted, and right now FGT1 has no policies at all: nothing passes. You are to rebuild the rule base on least privilege. Staff may use DNS and two approved web sites, and reach the intranet server SRV1 on web ports. The admin workstation PC1 may reach SRV1 on anything. Everything else to the internet is denied and logged.
| Device | Interface | Address | Role |
|---|---|---|---|
| FGT1 | port1 (ISP-A) | 203.0.113.1/24 | WAN, gateway 203.0.113.254 |
| FGT1 | port2 (LAN) | 10.1.10.1/24 | PC1 10.1.10.10 (admin), H1 by DHCP |
| FGT1 | port3 (SERVERS) | 10.1.30.1/24 | SRV1 10.1.30.10 (intranet web) |
| INET | — | 198.51.100.0/24 | public DNS .53, www.example.com .10, news.example.net .11, files.example.com .13 |
What you’ll practise
- Build subnet, host and FQDN address objects and groups
- Use predefined and custom services, service groups and schedules
- Write least-privilege policies, including DNS, and an explicit deny that logs
- Explain top-down first-match ordering, find a shadowed policy and move it
- Prove which policy matched with hit counts, the session table and the policy lookup
The tasks
- Start the lab
- Address objects and groups
- Services and schedules
- Least-privilege policies
- A shadowed policy
- Prove which policy matched
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
- FGT1
port1to INETeth0 - FGT1
port2to LAN (network) - PC1
eth0to LAN (network) - H1
eth0to LAN (network) - FGT1
port3to SRV1eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| FGT1 | Fortinet FortiGate | fortinet-FGT-v7.0.17.M-build0682 | 1 vCPU, 2,048 MB |
| INET | EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 1,024 MB |
| PC1 | EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 2,048 MB |
| H1 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| SRV1 | EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 1,024 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
FortiGate NSE 4 guided labs.Open
05 - Firewall policies and objectsand 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 FortiGate labs
Related labs in other courses
CloudLabBox is independent of Fortinet. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.