CloudLabBox
Try the free demo

FortiGate lab 15 of 25

Web filtering and DNS filtering

Build Harbourside's acceptable-use rules with static URL filters (simple, wildcard and regular expression, with allow, block, monitor and exempt), see how entry order and inspection mode change the result, add a DNS filter, and read what FortiGuard categories would add on a licensed unit.

Run this lab

It needs Lite: its 4 nodes are set to 4 vCPU and 5,632 MB in total. That fits the free demo too.

In your workspace: Shared, then FortiGate NSE 4 guided labs, then 15 - Web filtering and DNS filtering

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 60 minutes
Nodes need
4 vCPU, 5,632 MB
Smallest plan
Lite

The scenario

Harbourside's new acceptable-use policy says: no gaming sites; nothing under the example.net domain except the news site the marketing team relies on; no downloads from the company's own download area on www.example.com (they must go through the file portal); and log, but allow, visits to the shop. You implement it on FGT1 and prove each rule.

DeviceInterfaceAddressConnects to
FGT1port1 (ISP-A)203.0.113.1/24INET (test sites, DNS 198.51.100.53)
FGT1port2 (LAN)10.1.10.1/24PC1 10.1.10.10, H1 by DHCP

Evaluation licence. FortiGuard category ratings need a FortiGuard web filtering licence and a connection to FortiGuard, which these VMs don't have. This lab uses static URL filters and a static DNS domain filter, which work locally; Task 5 explains categories without pretending they work here.

What you’ll practise

  • Choose flow or proxy inspection for web filtering and explain the differences
  • Write static URL filters with simple, wildcard and regex entries and the four actions
  • Predict which URL filter entry matches first
  • Block domains at DNS resolution with a DNS filter profile
  • Explain FortiGuard category filtering, rating errors and local ratings
  • Read web filter and DNS filter logs and troubleshoot web filtering

The tasks

  1. Start the lab
  2. Inspection modes for web filtering
  3. A static URL filter
  4. Order matters
  5. Block at DNS with a DNS filter
  6. FortiGuard categories and rating errors (concept)
  7. Logs and troubleshooting

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 Web filtering and DNS filtering4 nodes and 1 network, 4 links. Every link is listed as text below the diagram.FGT1INETPC1H1LANport2eth0eth0port1eth0
4 nodes and 1 network, with the interface names each link uses.
Every link, as text
  • FGT1 port1 to INET eth0
  • FGT1 port2 to LAN (network)
  • PC1 eth0 to LAN (network)
  • H1 eth0 to LAN (network)
Nodes in Web filtering and DNS filtering, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
FGT1Fortinet FortiGatefortinet-FGT-v7.0.17.M-build06821 vCPU, 2,048 MB
INETEVE-NG GUI server (Docker)eve-gui-server:latest1 vCPU, 1,024 MB
PC1EVE-NG GUI server (Docker)eve-gui-server:latest1 vCPU, 2,048 MB
H1Alpine Linuxclbalpinebase-alpine-base-3-20-31 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 FortiGate NSE 4 guided labs.

  3. Open 15 - Web filtering and DNS filtering 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 FortiGate labs

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