Created on
08-15-2024
09:33 PM
Edited on
05-14-2025
12:21 AM
By
Jean-Philippe_P
Description | This article describes how to configure CrowdStrike FortiGate data ingestion. |
Scope | FortiGate v7.2 or later. |
Solution |
FortiGate supports the third-party log server via the syslog server. The Linux-based Syslog server can be configured in FortiGate to integrate with CrowdStrike.
config log syslogd setting set status enable set server "y.y.y.y" <----- Syslog server. set mode udp set port 514 set facility syslog set source-ip 'x.x.x.x' set format default set priority default set max-log-rate 0 set interface-select-method auto end
Users can customize the Syslog severity level by CLI:
config log syslogd filter show full
Users can choose to send all logs or customize logs by navigating under Log & Report -> Log Settings:
To troubleshoot this, run the following commands:
execute ping-options source "x.x.x.x" <------ source-ip configured on the Syslog setting. execute ping y.y.y.y <----- Syslog server IP.
If the ping works fine, run a sniffer to see if the FortiGate is sending information on port 514:
diagnose sniffer packet any 'host x.x.x.x and y.y.y.y and port 514' 4 0 l
Seeing traffic on this sniffer would mean that logs are being sent to the Syslog configured, and something on the other end needs to be checked.
Related article: Troubleshooting Tip: Syslog and log trouble shooting via CLI |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.