Automated Exfiltration T1020

Adversaries may exfiltrate data, such as sensitive documents, through the use of automated processing after being gathered during Collection.

Events covered

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

Authoring guide

Patterns shared across the 10 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 (12 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
CommandLine4regex_match 3, in 1(?i)\w+\.(bat|ps1|sh), *--auto-confirm*, *--config*, *--ignore-existing*
ScriptBlockText3contains 3, match 1-method "post", -method "put", -method 'post', [system.net.dns]::gethostentry, foreach
process_name3eq 1, ne 1, regex_match 1rclone.exe, (?i)\w+\.(exe)
EventID2eq 21, 4688
OriginalFileName2eq 2rclone.exe
parent_process_name2eq 1, regex_match 1(?i)\w+\.(exe), powershell.exe
AdditionalFields1ends_with 1[mArS.deiMos]::inteRaCt()"}
EventType1eq 1AmsiScriptContent
Image1in 1*atkexcomsvcres.exe, *atltracetool8.exe, *browser.ex
Type1eq 1
c_process1lt 110
signature_id1eq 14104

Top indicator values (74 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
CommandLineregex_match
(?i)\w+\.(bat|ps1|sh)
33
OriginalFileNameeq
rclone.exe
23
AdditionalFieldsends_with
[mArS.deiMos]::inteRaCt()"}
1
CommandLinein
*--auto-confirm*
1
CommandLinein
*--config*
12
CommandLinein
*--ignore-existing*
1
CommandLinein
*--multi-thread-streams*
1
CommandLinein
*--no-check-certificate*
1
CommandLinein
*--progress*
1
CommandLinein
*--transfers*
1
CommandLinein
*copy*
1
CommandLinein
*ftp*
1
CommandLinein
*mega*
1
CommandLinein
*pcloud*
1
EventIDeq
1
1232
EventIDeq
4688
1312
EventTypeeq
AmsiScriptContent
1
Imagein
*atkexcomsvcres.exe
1
Imagein
*atltracetool8.exe
1
Imagein
*browser.ex
1
Imagein
*cefsub.exe
1
Imagein
*dabs.ex
1
Imagein
*facialfeaturedemo.exe
1
Imagein
*googleupdate*.exe
1
Imagein
*gup.exe
1
Imagein
*hpcustparticui.exe
1
Imagein
*install_.exe
1
Imagein
*mcsync.ex
1
Imagein
*melt_64.exe
1
Imagein
*mscorsvw.exe
1

Exclusions (1 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
Imagestarts_with
c:\\
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.

Sigma 3 rules

Splunk 6 rules

Kusto 1 rule