No scheduled backup of the FortiManager
At a glance
Base severity
Area
Platform
Evidence level
Benchmark reference
Reads the export, not the device
ConfigProof reads a configuration export. This control is evaluated against the objects in that file, and it reports what the file says. It does not connect to the device and sees no traffic, so a finding here describes the configuration, not what the firewall is doing right now.
Why it matters
Without a scheduled backup, a failed or wiped FortiManager loses its ADOMs, policy packages, objects and revision history for every managed FortiGate.
How to fix it
Web interface
The steps below are written for the web interface. A finding raised on your own export carries the same steps with your object names filled in.
- On the FortiManager CLI: config system backup all-settings, set status enable, set server, set protocol sftp (or scp), set user, set passwd, set directory, set time and set week_days, end.
Command line
FortiOS CLI
config system backup all-settingsset status enableset server <backup-server>set protocol sftpset time 02:00:00set week_days monday tuesday wednesday thursday friday saturday sundayend
An example. Values in angle brackets are yours to supply; a finding on your own export fills in the names it read. FortiOS saves a change when you type next or end, with no separate commit. Read every line first.
Read it back
show system backup all-settingsValues to fill in1
- <backup-server>
- The server's address
Before you type it1
- Secrets are never generated here. Set the key yourself, on both ends.
How to confirm the fix
- show system backup all-settings shows status enable.
- Confirm a backup file arrives on the server after the scheduled time.
Limits
- The configuration shows that a backup is scheduled, not that the last backup succeeded.
Compliance references
No benchmark recommendation is mapped to this control in this version.
More in System and Metadata
- FGT-SEC-020Strong cryptography is disabled
- FGT-SW-001Software version is out of vendor support
- FMG-SEC-008FortiManager clock is not synchronized
- FMG-MGT-001Managed FortiGate out of sync with the FortiManager
- FMG-MGT-002Changes on the FortiManager not installed on a FortiGate
- FMG-MGT-003Managed FortiGate disconnected from the FortiManager
- FMG-MGT-006FortiGate runs a newer FortiOS than its ADOM
- FMG-SW-001FortiManager software version is out of vendor support
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.