FortiSIEM Rules

Outbreak: Emotet Suspicious File Hash Found on Host

Rule ID


Default Status



Emotet malware hash detected by Fortinet Products on host.







Exfiltration consists of techniques that adversaries may use to steal data from your network. Once they’ve collected data, adversaries often package it to avoid detection while removing it. This can include compression and encryption. Techniques for getting data out of a target network typically include transferring it over their command and control channel or an alternate channel and may also include putting size limits on the transmission.

MITRE ATT&CK® Techniques


Exfiltration Over C2 Channel

Adversaries may steal data by exfiltrating it over an existing command and control channel. Stolen data is encoded into the normal communications channel using the same protocol as command and control communications.



Data Source

FortiGate via Syslog



Remediation Guidance

Check if the source is patched for the CVE associated with the event. If yes then remove the host from the network and patch immediately. If host is not scanned then determine if the host is running the affected version of the application. If yes then patch immediately, else it is likely a false positive.

Time Window

If the following pattern or patterns match an ingested event within the given time window in seconds, trigger an incident.

300 seconds

Trigger Conditions

If the following defined pattern/s occur within a 300 second time window.


SubPattern Definitions

SubPattern Name: emotet

This is the named definition of the event query, this is important if multiple subpatterns are defined to distinguish them.

SubPattern Query

This is the query logic that matches incoming events

(eventType CONTAIN "FortiGate-antivirus" OR eventType CONTAIN "FortiClient-av") AND ( hashMD5 IN ("c17a1a08f40029c5134c7dfee8855c62","ea24cb1a4b92c92199eb73a1bd6d0dbc","7cf0ae7e45e7f92e668e41b104187cce")  OR  hashCode IN ("c17a1a08f40029c5134c7dfee8855c62","ea24cb1a4b92c92199eb73a1bd6d0dbc","7cf0ae7e45e7f92e668e41b104187cce") )

Group by Attributes

This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID


Aggregate Constraint

This is most typically a numerical constraint that defines when the rule should trigger an incident

COUNT(*) >= 1

Incident Attribute Mapping

This section defines which fields in matching raw events should be mapped to the incident attributes in the resulting incident.

The available raw event attributes to map are limited to the group by attributes and the aggregate event constraint fields for each subpattern