FortiManager syslog server reached without TLS
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 TLS, the FortiManager's event logs cross the network in clear text and can be read or altered on the way.
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 syslog, edit the server, set secure-connection enable (with the certificate the server expects), next, end.
Command line
FortiOS CLI
config system syslogedit <syslog-server>set secure-connection enablenextend
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 syslog <syslog-server>Values to fill in1
- <syslog-server>
- The server entry's name
Before you type it1
- Syslog over TLS needs a certificate profile the collector accepts.
How to confirm the fix
- show system syslog <server> shows secure-connection enable.
- Confirm the server still receives the FortiManager's logs.
Limits
- The syslog server has to accept TLS on the port configured.
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.