FortiSIEM Rules

UEBA Policy detects email upload

Rule ID


Default Status



FortiSIEM UEBA Policy detects email upload







Collection consists of techniques adversaries may use to gather information and the sources information is collected from that are relevant to following through on the adversary's objectives. Frequently, the next goal after collecting data is to steal (exfiltrate) the data. Common target sources include various drive types, browsers, audio, video, and email. Common collection methods include capturing screenshots and keyboard input.

MITRE ATT&CK® Techniques


Email Collection: Local Email Collection

Adversaries may sniff network traffic to capture information about an environment, including authentication material passed over the network. Network sniffing refers to using the network interface on a system to monitor or capture information sent over a wired or wireless connection. An adversary may place a network interface into promiscuous mode to passively access data in transit over the network, or use span ports to capture a larger amount of data.



Data Source

Windows via FortiSIEM Agent with UEBA turned on



Remediation Guidance

No remediation guidance specified

Time Window

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

600 seconds

Trigger Conditions

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


SubPattern Definitions

SubPattern Name: UEBA

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 = "FINS-Windows-file-read" AND procName = "outlook.exe" AND resourceName != "svrsvc" AND (fileExt IS NULL OR fileExt != "lnk") AND resourceName NOT REGEXP "c:/temp/(.+\.tmp|msohtmlclip[0-9]/\d+/.+\.thmx|exchangeperflog_.+\.dat)"  AND user NOT REGEXP ".*\$$|dwn-.*|dwm-.*|umfd-.*|.*SYSTEM.*|.*ANONYMOUS.*"

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

 hostName = UEBA.hostName,
 domain = UEBA.domain,
 user = UEBA.user,
 procName = UEBA.procName,
 activityName = UEBA.activityName,
 resourceName = UEBA.resourceName