Description
This article describes how to implement Indicators Of Compromised (IOC) Automation Stitch between FortiGate, FortiAnalyzer and FortiEMS.
Pre-requisite.
Refer to the related articles section and to the document below.
Related document:
Viewing Compromised Hosts
Indicators Of Compromised (IOC) Flow.

Scope
FortiGate v6.4.4, FortiAnalyzer 6.4.5 and FortiEMS 6.4.3.
Solution
FortiGate.
Configure a firewall policy going to the Internet that has a web filter profile enabled on it. This is required for the IOC to work.
config firewall policy
edit 0
set srcintf "port3"
set dstintf "virtual-wan-link"
set srcaddr "10.115.2.52/32"
set dstaddr "all"
set action accept
set schedule "always"
set service "ALL"
set utm-status enable
set ssl-ssh-profile "certificate-inspection"
set webfilter-profile "monitor-all"
set logtraffic all
set nat enable
next
config system automation-stitch
edit "Compromised Host Quarantine"
set trigger "Compromised Host Quarantine"
set action "Compromised Host Quarantine_quarantine-forticlient"
next
end


Results.To trigger IOC logs, access http://195.22.28.198/ from the endpoint machine.





It is also possible to provide the endpoint user with a one-time access code.
The user can enter the code to access FortiClient on a quarantined endpoint, then remove the endpoint from quarantine in the FortiClient console.
Quarantining endpoints
Afterwards, it is necessary to acknowledge the logs from FortiAnalyzer to clear the compromised hosts list from FortiGate so that it can execute the Automation Stitch for the same host once triggered again.



Related articles:
Technical Tip: Configuring the root FortiGate and downstream FortiGates in Security Fabric
Technical Tip: EMS Connector setup