ATT&CK coverage › Technique

Data Staged: Local Data Staging T1074.001

Adversaries may stage collected data in a central location or directory on the local 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

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

ProviderEvent IDTitle
Sysmon1Process creation
Sysmon11FileCreate
Security-Auditing4688A new process has been created.
PowerShell4103Payload Context: ContextInfo User Data: UserData.
PowerShell4104Creating Scriptblock text (MessageNumber of MessageTotal).

Authoring guide

Patterns shared across the 4 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
CommandLine1match 1Compress-Archive -Path*-DestinationPath*\AppData\Local\Temp\, Compress-Archive -Path*-DestinationPath $env:TEMP, Compress-Archive -Path*-DestinationPath*:\Windows\Temp\
ContextInfo1match 1Compress-Archive -Path*-DestinationPath*\AppData\Local\Temp\, Compress-Archive -Path*-DestinationPath $env:TEMP, Compress-Archive -Path*-DestinationPath*:\Windows\Temp\
ScriptBlockText1match 1Compress-Archive -Path*-DestinationPath*\AppData\Local\Temp\, Compress-Archive -Path*-DestinationPath $env:TEMP, Compress-Archive -Path*-DestinationPath*:\Windows\Temp\
file_name1in 1"contents.json", "actionsSecrets.json", "cloud.json"

Top indicator values (14 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
CommandLinematchCompress-Archive -Path*-DestinationPath*:\Windows\Temp\1
CommandLinematchCompress-Archive -Path*-DestinationPath*\AppData\Local\Temp\1
CommandLinematchCompress-Archive -Path*-DestinationPath $env:TEMP1
ContextInfomatchCompress-Archive -Path*-DestinationPath*:\Windows\Temp\1
ContextInfomatchCompress-Archive -Path*-DestinationPath*\AppData\Local\Temp\1
ContextInfomatchCompress-Archive -Path*-DestinationPath $env:TEMP1
ScriptBlockTextmatchCompress-Archive -Path*-DestinationPath*:\Windows\Temp\1
ScriptBlockTextmatchCompress-Archive -Path*-DestinationPath*\AppData\Local\Temp\1
ScriptBlockTextmatchCompress-Archive -Path*-DestinationPath $env:TEMP1
file_namein"actionsSecrets.json"1
file_namein"cloud.json"1
file_namein"environment.json"1
file_namein"contents.json"1
file_namein"truffleSecrets.json"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 1 rule