Managed FortiGate with no policy package installed
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
The FortiGate's firewall policy is managed on the device itself, so the FortiManager's central policy and its review do not cover it.
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.
- In FortiManager: Policy & Objects > the package that should govern the device > Installation Targets > add the device (and VDOM), then install it.
Command line
This analyzer version writes no command text for this control. The steps above are the remediation it offers.
How to confirm the fix
- The package's Installation Targets list the device, and Device Manager shows the package as installed.
Limits
- A device deliberately managed for its settings only (no central policy) is reported too.
Compliance references
No benchmark recommendation is mapped to this control in this version.
More in Security Policies
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.