FortiClient communicates directly with FortiClient EMS to continuously share device status information through ZTNA telemetry.

Based on the CLI output from FortiGate:

The configuration shows the use of "type fortiems," indicating that FortiGate is set up to interact with FortiClient EMS.

The "server" field points to an IP address (10.0.1.200), which is typically the address of the FortiClient EMS server.

The configuration includes an SSL-enabled connection, which is a common setup for secure communication between FortiGate and FortiClient EMS.

Thus, the configuration indicates that FortiGate is set up to pull user groups from FortiClient EMS.

References

FortiGate Security 7.2 Study Guide, FSSO Configuration Section

Fortinet Documentation on FortiGate and FortiClient EMS Integration

Based on the Security Fabric automation settings shown in the exhibit:

The automation stitch is configured with a trigger for a "Compromised Host."

The action specified for this trigger is "Quarantine FortiClient via EMS."

This indicates that when an endpoint is detected as compromised, FortiClient EMS will quarantine the endpoint as part of the automation process.

Therefore, the action taken on compromised endpoints will be to quarantine them through EMS.

References

FortiGate Security 7.2 Study Guide, Automation Stitches and Actions Section

Fortinet Documentation on Configuring Automation Stitches and Quarantine Actions