FortiSIEM Rules

Windows Torrent Client

Rule ID


Default Status



Detects Torrent Client. Torrent is a method of file sharing over the Internet






Command And Control

MITRE ATT&CK® Techniques


Proxy: External Proxy

Adversaries may use an external proxy to act as an intermediary for network communications to a command and control server to avoid direct connections to their infrastructure. Many tools exist that enable traffic redirection through proxies or port redirection, including HTRAN, ZXProxy, and ZXPortMap. Adversaries use these types of proxies to manage command and control communications, to provide resiliency in the face of connection loss, or to ride over existing trusted communications paths to avoid suspicion. External connection proxies are used to mask the destination of C2 traffic and are typically implemented with port redirectors. Compromised systems outside of the victim environment may be used for these purposes, as well as purchased infrastructure such as cloud-based resources or virtual private servers.



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.

300 seconds

Trigger Conditions

If the following defined pattern/s occur within a 300 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 CONTAIN "FINS-Windows-" AND procName IN ("bittorrent.exe","limewire.exe","zultrax.exe","mlnet.exe","kiwialpha.exe","kceasy.exe","gnucleus.exe","amule.exe","ares.exe","warez.exe","azureus.exe","bitcomet.exe","bitspirit.exe","bittornado.exe","bitlord.exe","burst.exe","utorrent.exe","qtorrent.exe","tribler.exe","dcplusplus.exe","strongdc.exe","hydranode.exe","jubster.exe","pruna.exe","entropy.exe","bearshare.exe","cabos.exe","grokster.exe","frostwire.exe","xolox.exe","phex.exe","piolet.exe","blubster.exe","napigator.exe","overnet.exe","tvuplayer.exe","tvprunner.exe","coolstreaming.exe","tvants.exe","pplive.exe","peercast.exe","iceshare.exe","deluge.exe","vuze.exe","luckywire.exe","popcorn-time.exe")

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.reptDevName,
 user = UEBA.user,
 domain = UEBA.domain,
 procName = UEBA.procName