FortiManager does not send its own logs to a syslog server
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
Administrator logins and policy installs stay only on the FortiManager, where a person who controls it can erase them.
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.
- Define the server: config system syslog, edit a name, set ip to the server, next, end.
- Send the logs to it: config system locallog syslogd setting, set status enable, set syslog-name to that entry, set severity information, end.
Command line
FortiOS CLI
config system locallog syslogd settingset status enableset syslog-name <syslog-server>set severity informationend
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 locallog syslogd settingValues to fill in1
- <syslog-server>
- The server entry's name
How to confirm the fix
- show system locallog syslogd setting shows status enable and the server's name.
- Confirm the server records a FortiManager login after the change.
Limits
- No limitation is recorded for this control beyond the one that applies to all of them: it reads a configuration export.
Compliance references
No benchmark recommendation is mapped to this control in this version.
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.