ATT&CK coverage › Technique

Application Layer Protocol: Mail Protocols T1071.003

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.

ProviderEvent IDTitle
Sysmon3Network connection
Sysmon22DNSEvent (DNS query)

Authoring guide

Patterns shared across the 3 rules above: which fields they filter on, what specific values they look for, and what they exclude. Field names are normalized 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 (4 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
EventID3eq 33, 22
DestinationPortName2eq 2"ftp", "smtp"
DestinationPort2eq 1, in 121, 25, 587
QueryName1in 1"*.torproject.org", "www.theonionrouter.com"

Top indicator values (9 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.

FieldKindValueRules (here)Corpus reach
EventIDeq324
DestinationPortNameeq"ftp"1
DestinationPorteq211
DestinationPortin251
DestinationPortNameeq"smtp"1
DestinationPortin5871
EventIDeq22115
QueryNamein"*.torproject.org"1
QueryNamein"www.theonionrouter.com"1

Common exclusions (4 distinct)

Field/operator/value combinations that rules under this technique routinely exclude (top-level not() clauses). 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.

FieldKindValueRules excluding
Imagein"C:\\Windows\\System32\\*"2
Imagein"C:\\Program Files \(x86\)\\*"2
Imagein"C:\\Program Files\\*"2
Imagein"C:\\Windows\\SysWOW64\\*"2

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.

Splunk 3 rules