CloudLabBox
Try the free demo

FortiGate lab 14 of 25

Antivirus scanning

Stop a test virus downloaded over the web: compare flow-based and proxy-based antivirus, handle archives and oversized files with protocol options, and read the antivirus logs, using the industry-standard EICAR test file.

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 14 - Antivirus scanning

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

The scenario

A Harbourside user downloaded an "invoice" that turned out to be malware, and the firewall let it straight through because no security profiles were applied. You'll switch on antivirus scanning for web and FTP downloads and prove it works. Never use real malware for this: the EICAR test file is a harmless 68-byte string that every antivirus product detects as if it were a virus. The test sites serve it at /eicar.com, and zipped at /eicar.zip.

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

Evaluation licence. There are no FortiGuard updates on these VMs: the antivirus engine uses the signatures built into the firmware, which include the EICAR test signature. On a licensed unit, FortiGuard updates the database many times a day.

What you’ll practise

  • Explain flow-based and proxy-based antivirus and when to choose each
  • Build antivirus profiles and apply them to a policy in the matching inspection mode
  • Use protocol options for ports, archives and oversized files
  • Read antivirus logs and recognise common antivirus issues

The tasks

  1. Start the lab
  2. Prove there is no protection
  3. Flow-based antivirus
  4. Proxy-based antivirus and archives
  5. Protocol options: ports and oversized files
  6. Logs and common issues

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 Antivirus scanning4 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 Antivirus scanning, 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 14 - Antivirus scanning 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

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.