Created on
‎08-27-2024
11:45 PM
Edited on
‎01-05-2026
02:19 AM
By
Jean-Philippe_P
| Description | This article describes how to restrict self-generating traffic from FortiGate toward FortiGuard. |
| Scope | FortiGate. |
| Solution |
In a situation where FortiGate is connected to a FortiManager, which acts as a FortiGuard server, it is necessary to block traffic sourced from FortiGate to reach the FortiGuard server.
The first solution is to put all that traffic in a Group and then create a static route for that Group to be blackholed.
config firewall address edit "FQDN-DIRECTREGISTRATION.FORTINET.COM" edit "FQDN-GLOBALPRODUCTAPI.FORTINET.NET"
The second solution is to completely block FortiGate from the cloud communication by disabling 'cloud-communication' and the 'fortitoken-cloud' under get system global.
get system global cloud-communication : enable fortitoken-cloud : enable
config system global end
It is possible to check with the diagnose debug rating:
diagnose debug rating Service : Web-filter Service : Antispam Service : Virus Outbreak Prevention
The GUI images showed self-generating traffic before and after the solutions. |
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 2026 Fortinet, Inc. All Rights Reserved.