CloudLabBox
Try the free demo

FortiGate lab 4 of 25

Logging and monitoring

Follow a log from a policy to the screen and to a syslog server: choose what each policy logs, log the implicit deny, read and filter traffic and event logs in the CLI and GUI, and send everything to SRV1.

Run this lab

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

In your workspace: Shared, then FortiGate NSE 4 guided labs, then 04 - Logging and monitoring

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
Beginner
Time
About 50 minutes
Nodes need
4 vCPU, 6,144 MB
Smallest plan
Lite

The scenario

Last week a user swore a web site "just stopped working", and nobody could prove what the firewall did, because nothing was being logged. Harbourside's security lead wants every internet session logged, every blocked attempt recorded, and a copy of the logs on the syslog server (SRV1) where they can't be erased from the firewall. You set it up and prove it works.

DeviceInterfaceAddressConnects to
FGT1port1 (ISP-A)203.0.113.1/24INET, gateway 203.0.113.254
FGT1port2 (LAN)10.1.10.1/24PC1 10.1.10.10
FGT1port3 (SERVERS)10.1.30.1/24SRV1 10.1.30.10 (syslog receiver)

Policies already in place: 1 LAN-to-Internet (any service, NAT) and 2 LAN-to-Servers-Web (HTTP, HTTPS and PING to the servers). Neither logs traffic yet.

What you’ll practise

  • Describe log types, severities and where a FortiGate can store logs
  • Choose per-policy traffic logging and log the implicit deny
  • Filter and read traffic and event logs from the CLI and the GUI
  • Send logs to a syslog server and prove they arrive
  • Explain how a FortiGate registers with FortiAnalyzer and which commands check the link

The tasks

  1. Start the lab
  2. Where do logs go?
  3. Choose what each policy logs
  4. Read and filter traffic logs in the CLI
  5. Event logs and the GUI log viewer
  6. Send the logs to syslog
  7. FortiAnalyzer and monitoring (reading task)

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 and monitoring4 nodes, 3 links. Every link is listed as text below the diagram.FGT1INETPC1SRV1port1eth0port2eth0port3eth0
4 nodes, with the interface names each link uses.
Every link, as text
  • FGT1 port1 to INET eth0
  • FGT1 port2 to PC1 eth0
  • FGT1 port3 to SRV1 eth0
Nodes in Logging and monitoring, 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
SRV1EVE-NG GUI server (Docker)eve-gui-server:latest1 vCPU, 1,024 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 04 - Logging and monitoring 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.