When an endpoint has a Zero Trust tag applied and EMS is operating as part of a Fortinet Security Fabric, the FortiGate that the endpoint's FortiClient gateway points to receives the endpoint's resolved IP or MAC address (hereafter referred to as "host tag") from EMS.
If your EMS is operating as part of a Security Fabric with multiple FortiGates, you may want to configure EMS to send the host tag to other FortiGates in the Fabric, in addition to the FortiGate that the endpoint's FortiClient gateway points to. You can configure this as follows.
The following illustrates the topology in this example:
The following is true for this scenario:
- Both FortiGates are connected to EMS as part of a Security Fabric.
- FortiClient is registered to EMS.
- The FortiClient gateway points to the first floor FortiGate.
- The FortiClient endpoint has the TAG_ANTIVIRUS_ON Zero Trust tag applied.
- The host tag of the FortiClient endpoint with TAG_ANTIVIRUS_ON applied is 10.100.91.100.
By default in this example, the core FortiGate does not retrieve the host tag information for TAG_ANTIVIRUS_ON. This is because the FortiClient device gateway is 10.100.91.1, which does not match the core FortiGate.
You can configure the core FortiGate to retrieve the host tag for TAG_ANTIVIRUS_ON by allowing the host tag to sync from FortiClient endpoints connected to the first floor FortiGate to the core FortiGate.
- Go to Administration > Fabric Devices.
- Select the serial number associated with the core FortiGate. In this example, it is FGVM02TM21011924. By default, Send tag info from all FortiClients is disabled.
- Click Edit.
- Enable Share tag info from FortiClients connected to additional FortiGates.
- From the dropdown list, select the serial number of the FortiGate on the first floor. In this example, it is FGVM02TM21011669. This change triggers EMS to resynchronize tag information to the first floor FortiGate.
- Click Save.
- Reselect the core FortiGate. It now displays that it receives host tag information from the first floor FortiGate.
- Verify that the core FortiGate is receiving the tag information: