FortiGate lab 2 of 25
Administrators, profiles, backups and restore
Give a helpdesk team safe, read-only access with its own profile and trusted hosts, enforce a password policy and lockout, then back up the configuration to a TFTP server in plain and encrypted form and plan a restore and a firmware upgrade.
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 02 - Administrators profiles backups and restore
- Level
- Beginner
- Time
- About 50 minutes
- Nodes need
- 4 vCPU, 6,144 MB
- Smallest plan
- Lite
The scenario
Harbourside's FortiGate is live, and only you know the admin password, which auditors flagged. The helpdesk needs to look at the firewall to answer users' questions, but must not change anything, and only from the office LAN. The auditors also want strong admin passwords, a lockout after failed logins, and a tested backup on the server network before anyone touches the firmware.
| Device | Interface | Address | Connects to |
|---|---|---|---|
| FGT1 | port1 (ISP-A) | 203.0.113.1/24 | INET (ISP gateway .254) |
| FGT1 | port2 (LAN) | 10.1.10.1/24 | PC1 10.1.10.10 |
| FGT1 | port3 (SERVERS) | 10.1.30.1/24 | SRV1 10.1.30.10 (TFTP server, files in /srv/tftp) |
Topology: FGT1 in the middle; PC1 on the LAN, SRV1 on the server network, INET upstream.
What you’ll practise
- Explain administrator profiles and build a read-only profile
- Create an administrator restricted to trusted hosts
- Enforce an administrator password policy and a login lockout
- Back up the configuration to TFTP, plain and encrypted, and read what a backup contains
- Describe the restore and firmware-upgrade procedures and their risks
The tasks
- Start the lab
- A read-only administrator profile
- A helpdesk administrator with trusted hosts
- Password policy and lockout
- Back up the configuration
- Plan a restore and a firmware upgrade (walk-through)
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 PC1eth0 - 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 |
| 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
02 - Administrators profiles backups and restoreand 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
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.