Data Staged: Remote Data Staging T1074.002

Tactic: Collection

Adversaries may stage data collected from multiple systems in a central location or directory on one system prior to Exfiltration. Data may be kept in separate files or combined into one file through techniques such as Archive Collected Data. Interactive command shells may be used, and common functionality within cmd and bash may be used to copy data into a staging location.

Events covered

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

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 (11 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
EventType2eq 1, in 1CREATE_DATA_TRANSFER_REQUEST, CUSTOMER_TAKEOUT_CREATED, RestoreDBInstanceFromDBSnapshot, RestoreDBInstanceFromS3
data_stream.dataset2eq 2aws.cloudtrail, google_workspace.admin
CommandLine1contains 1, wildcard 1 copy, cp , move
EventID1eq 1CREATE_DATA_TRANSFER_REQUEST
Provider_Name1eq 1rds.amazonaws.com
event.outcome1eq 1success
event.type1eq 1start
gws::admin_application_name1starts_with 1Drive
process_name1eq 1cmd.exe, powershell.exe
security_result.category_details1eq 1USER_SETTINGS
user.id1ne 1S-1-5-18

Top indicator values (20 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
CommandLinecontains
copy
1
CommandLinecontains
cp
18
CommandLinecontains
move
1
CommandLinecontains
mv
14
CommandLinewildcard
*\\*\*$*
1
EventIDeq
CREATE_DATA_TRANSFER_REQUEST
1
EventTypeeq
CREATE_DATA_TRANSFER_REQUEST
1
EventTypeeq
CUSTOMER_TAKEOUT_CREATED
1
EventTypein
RestoreDBInstanceFromDBSnapshot
1
EventTypein
RestoreDBInstanceFromS3
1
Provider_Nameeq
rds.amazonaws.com
19
data_stream.dataseteq
aws.cloudtrail
1141
data_stream.dataseteq
google_workspace.admin
118
event.outcomeeq
success
1251
event.typeeq
start
1606
gws::admin_application_namestarts_with
Drive
1
process_nameeq
cmd.exe
177
process_nameeq
powershell.exe
1104
security_result.category_detailseq
USER_SETTINGS
12
user.idne
S-1-5-18
18

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 3 rules

YARA-L 1 rule