Skip to main content
van_sta
Explorer III
January 22, 2026
Question

Send logs to wazuh and syslog server

  • January 22, 2026
  • 3 replies
  • 1808 views

Good morning, I'd like to be able to send the Forti logs to a Wazuh server. I'm already sending them to a syslog server, but only one log is visible through the GUI. How do I configure the other redirection (to Wazuh)? I'd like to have both options: syslog and Wazuh.

 

Thanks!!

3 replies

AEK
SuperUser
SuperUser
January 22, 2026

Hi Van

Two possible methods:

  1. On syslog you forward the received FGT logs to Wazuh (sometime the preferred method)
  2. Use FGT CLI to add a second syslog destination
    config log syslogd2 setting
    You can configure additional servers with syslog3 and syslog4.

Hope it helps.

AEK
New Member
July 16, 2026

FortiGate can send logs to multiple syslog destinations, but simply duplicating the same raw stream does not always solve the operational problem. The main challenge usually starts on the Wazuh side: different FortiOS versions and event types may produce inconsistent fields, message formats and device identifiers.

I’m currently using Bivoxy with five devices connected. In my setup, it sits between the FortiGate devices and the analysis layer, receives the raw syslog events, preserves the original device identity and normalizes fields such as source IP, destination IP, user, action, policy ID, event type and severity into a consistent structure.

This has been useful because Wazuh can receive the logs in a more predictable format instead of relying on a growing collection of custom decoders and firmware-specific field mappings. It also makes cross-device correlation easier, especially for VPN authentication failures, repeated connection attempts and policy-related events.

For this setup, I would verify the following:

  • Both syslog targets are receiving events independently.
  • FortiGate is using reliable TCP or TLS syslog where possible.
  • The original hostname, serial number or device identifier is preserved.
  • Wazuh is decoding and indexing the events, not only writing them to the archives.
  • Message size, framing and timestamp formats are consistent.
  • Events from different devices are not being merged under the same source identity.

A centralized normalization layer is not mandatory, but once you have several FortiGate devices or mixed firmware versions, it can remove a lot of decoder maintenance. Bivoxy has been working well for this in my environment, especially for keeping the event structure consistent before analysis.

henry-collins
Explorer
July 16, 2026
 

You can send FortiGate logs to both a syslog server and Wazuh at the same time. Wazuh can receive them through its syslog listener, so you just need to configure an additional syslog destination on the FortiGate pointing to the Wazuh server’s IP and listening port.

If only one log type appears in the GUI, check your FortiGate log forwarding filters and make sure the required categories (traffic, event, security, etc.) are enabled for both destinations. Also verify Wazuh is properly parsing the FortiGate logs on the receiving side.

Full-Stack Developer | SEO Strategist | Helping users with software & troubleshooting solutions.
Thought Leadership. Security Summit. Thursday, November 12th, PGA National Resort, Palm Beach Gardens, FL.
Thought Leadership. Security Summit. Thursday, October 8th. Disney's Grand Californian Hotel & SPA, Anaheim, CA.