Strong cryptography is disabled
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
With strong-crypto disabled the device offers weaker ciphers on its own HTTPS, SSH and other management services.
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.
- Set strong-crypto enable under config system global.
Command line
FortiOS CLI
config system globalset strong-crypto enableend
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 globalBefore you type it2
- Written from the FortiOS CLI Reference, not yet run on a device. Read each line before typing it.
- On a device with VDOMs, type these inside the VDOM (config vdom, edit the VDOM) or inside config global for a global setting.
How to confirm the fix
- Check that management tools and peers still connect after the change.
Limits
- A setting the backup does not write is read as FortiOS's documented default for the device's release.
Compliance references
CIS FortiGate 7.4.x Benchmark v1.0.1
Covers the whole recommendation
Where a control aligns with a recommendation of the CIS FortiGate 7.4.x Benchmark v1.0.1, that recommendation is cited as a reference. Only that version was checked. A reference is not a certification.
More in System and Metadata
- FGT-SW-001Software version is out of vendor support
- FMG-SEC-008FortiManager clock is not synchronized
- FMG-SEC-011No scheduled backup of the FortiManager
- 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.