All of our customer firewalls are logging to FortiAnalyzer for research/analytics. We've also had many of these firewalls also logging to syslog for the managed SOC. However, it seems like recently if logging to FortiAnalyzer is enabled, that syslog stops working, even though it's configured in the UI.
Perhaps I'm missing something? It's possible that it hasn't worked in a while and we just didn't notice..
Hi Team,
Could you please execute this command "diag sniffer packet any 'host a.b.c.d'" 4 0 a (where a.b.c.d is the syslog server ip)
Also please let us know where is the sys log server located
please share these logs with us
One option that you might want to investigate is to use the FAZ to forward logs to the syslog server in the managed SOC.
If the SOC syslog supports TCP, the FAZ will be able to cache the logs if there is a connectivity problem between itself and the syslog server.
You can also specify which devices the logs will be forwarded for.
User | Count |
---|---|
1930 | |
1144 | |
770 | |
447 | |
291 |
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.