Application Layer Protocol: Mail Protocols T1071.003

Tactic: Command & Control

Adversaries may communicate using application layer protocols associated with electronic mail delivery to avoid detection/network filtering by blending in with existing traffic. Commands to the remote system, and often the results of those commands, will be embedded within the protocol traffic between the client and server.

Events covered

2 catalog events are tagged with this technique by at least one rule.

ProviderEventTitle
SysmonEvent ID 3Network connection
SysmonEvent ID 22DNSEvent (DNS query)

Authoring guide

Patterns shared across the 4 rules above: which fields they filter on, what specific values they look for, and what they exclude. The catalog normalizes field names across vendors so Sigma's Image, Elastic's process.name, and Splunk's process_name collapse into one row. Each rule contributes at most once per row.

Fields filtered most (7 distinct)

The fields most rules look at when detecting this technique. The How column shows the operators authors use (eq, wildcard, regex_match, match) and how often each appears. Sample values are concrete examples to start from, not an exhaustive list.

FieldRulesHowSample values
DestinationPort3eq 2, in 121, 25, 26, 587
EventID3eq 33, 22
DestinationPortName2eq 2ftp, smtp
Protocol1eq 1tcp
QueryName1in 1*.torproject.org, www.theonionrouter.com
data_stream.dataset1in 1network_traffic.flow, zeek.smtp
event.category1in 1network, network_traffic

Top indicator values (15 distinct)

Specific (field, operator, value) combinations the rules check for, ranked by how many rules under this technique use each one. The Corpus reach column counts how many rules across the entire catalog (any technique) check the same combination. High numbers point to widely-used indicators that are likely noisy on their own; combine them with another condition for useful signal. Blank means the combination is specific to rules under this technique. Click a value to expand the rules under this technique that use it.

FieldKindValueRules (here)Corpus reach
EventIDeq
3
221
EventIDeq
22
116
DestinationPorteq
21
13
DestinationPorteq
26
1
DestinationPortin
25
13
DestinationPortin
587
12
DestinationPortNameeq
ftp
1
DestinationPortNameeq
smtp
1
Protocoleq
tcp
118
QueryNamein
*.torproject.org
1
QueryNamein
www.theonionrouter.com
1
data_stream.datasetin
network_traffic.flow
13
data_stream.datasetin
zeek.smtp
1
event.categoryin
network
115
event.categoryin
network_traffic
115

Exclusions (4 distinct)

Field/operator/value combinations excluded by rules under this technique (top-level not() clauses), sorted by how many rules exclude each. These are the false-positive paths the community has learned to filter out. A new rule that ignores the high-count entries here will likely fire on the same noisy paths. Click a value to expand the rules under this technique that exclude it.

Rules under this technique

Every rule in the catalog tagged with this technique, grouped by vendor. Click a rule title for its full predicates, exclusions, and indicators.

Platform (all)
Domain (all)

Elastic 1 rule

Splunk 3 rules