Skip to main content
Nur
Staff
Staff
June 16, 2026

Technical Tip: FortiGate unable to sending log to FortiAnalyzer when FIPS-CC enable

  • June 16, 2026
  • 0 replies
  • 29 views

Description

This article describes the case where, when FIPS-CC mode is enabled on the FortiGate, the device is unable to send logs to FortiAnalyzer.

Scope

FortiAnalyzer, FortiGate, FIPS-CC.

Solution

When FortiGate enables FIPS-CC mode, the OFTP is unable to establish. From FortiGate, the connection status is UP.

0dc770dd.png


While from FortiAnalyzer, there is no authorized device pop-up notification. The packet capture showed that the FortiGate reset the connection.

ae9c4020.png


To successfully send logs from a FIPS-CC-enabled FortiGate to FortiAnalyzer using OFTP, both devices must use custom certificates signed by the same Certificate Authority (CA).

config system certificate oftp
set mode custom 
set certificate <PEM format>
set private key <PEM private key>
end


However, there is another option that can be done from FortiAnalyzer, which is to enable the FIPS-CC mode. To enable the FIPS-CC mode:

config system fips
set status enable
set entropy-token enable
end


Enabling the FIPS-CC mode would delete all the config and logs; the command must be run at the console. Once the FIPS-CC has been enabled from the FortiAnalyzer side, the new FortiGate needs to be authorized to enable the FIPS-CC mode.