Email Collection T1114

Tactic: Collection

Adversaries may target user email to collect sensitive information. Emails may contain sensitive data, including trade secrets or personal information, that can prove valuable to adversaries. Emails may also contain details of ongoing incident response operations, which may allow adversaries to adjust their techniques in order to maintain persistence or evade defenses. Adversaries can collect or forward email from mail servers or clients.

Events covered

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

Authoring guide

Patterns shared across the 69 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 (119 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
Operation27eq 20, in 6, starts_with 2, contains 1, ends_with 1New-InboxRule, HardDelete, MailItemsAccessed, New-TransportRule, Add-MailboxFolderPermission
sourcetype21eq 21, in 3o365:management:activity, ms:o365:reporting:messagetrace, o365:reporting:messagetrace
Workload16eq 16Exchange, SecurityComplianceCenter
EventType6eq 4, in 2MailItemsAccessed, New-TransportRule, CHANGE_GMAIL_SETTING, CREATE_GMAIL_SETTING, New-InboxRule
ScriptBlockText6contains 3, in 3, eq 1*invoke-addgmailrule*, *invoke-domainharvestowa*, *invoke-globalmailsearch*, -comobject outlook.application, -filepath
EventID5eq 4, in 14104, 4103, 4688, ComplianceDLMExchange, ComplianceDLMSharePoint
data_stream.dataset5eq 5o365.audit, azure.graphactivitylogs, google_workspace.admin
m365::Workload5eq 5Exchange
CommandLine4contains 2, match 1, regex_match 1, wildcard 1$exserver=Get-ExchangeServer..., (?i)-FilePath.{1,}\.pst, *-Mailbox*-ContentFilter*, *MailboxExportRequest*, -encodedcommand
Name4eq 2, in 2BlindCopyTo, RedirectMessageTo, Email sending limit exceeded, Suspicious Email Forwarding Activity, Suspicious email sending patterns detected
Provider_Name4eq 4Exchange
event.category4eq 4process, web
m365::Parameters4contains 4forwardingsmtpaddress, forwardto, redirectto, deletemessage, forwardasattachmentto
match14ge 40
match24ge 40

Top indicator values (301 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
sourcetypeeq
o365:management:activity
2180
Workloadeq
Exchange
1220
Workloadeq
SecurityComplianceCenter
48
m365::Workloadeq
Exchange
58
Operationeq
MailItemsAccessed
44
Operationeq
HardDelete
34
Operationeq
New-InboxRule
35
Operationin
Set-TransportRule
44
Provider_Nameeq
Exchange
419
match1ge
0
44
match2ge
0
44
AppIdeq
*
33
AppIdeq
00000003-0000-0000-c000-000000000000
22
data_stream.dataseteq
o365.audit
345
event.outcomeeq
success
3251
event.typeeq
start
3606
m365::Folder.Pathin
\\Recoverable Items\\Deletions
34
m365::Folder.Pathin
\\Sent Items
34
m365::Parameterscontains
forwardingsmtpaddress
33
m365::Parameterscontains
forwardto
33
m365::Parameterscontains
redirectto
33
match3ge
0
33
process_nameeq
powershell.exe
3104
process_nameeq
pwsh.exe
362
sourcetypein
ms:o365:reporting:messagetrace
34
sourcetypein
o365:reporting:messagetrace
34
ClientAppIdeq
*
22
DistinctUserCountgt
1
22
EventIDeq
4104
2268
EventTypeeq
MailItemsAccessed
22

Exclusions (161 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.

FieldKindValueRules excluding
usercontains
devilfish-applicationaccount
2
usercontains
nt authority\\system (microsoft.exchange.servicehost)
2
usercontains
nt authority\\system (w3wp)
2
CommandLinematch
$exserver=Get-ExchangeServer ([Environment]::MachineName) -ErrorVariable...
1
EventDatacontains
gc_service.exe
1
EventDatacontains
gc_worker.exe
1
Operationin
Add-MailboxPermission
1
Operationin
Set-Mailbox
1
ParentImagecontains
gc_service.exe
1
ParentImagecontains
gc_worker.exe
1
ParentImageeq
c:\windows\system32\msiexec.exe
1
o365.audit.ClientAppIdin
00000002-0000-0000-c000-000000000000
1
o365.audit.ClientAppIdin
00000002-0000-0ff1-ce00-000000000000
1
o365.audit.ClientAppIdin
00000003-0000-0ff1-ce00-000000000000
1
o365.audit.ClientAppIdin
00000004-0000-0ff1-ce00-000000000000
1

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)

Sigma 11 rules

Elastic 13 rules

Splunk 26 rules

Kusto 16 rules

Panther 3 rules