ATT&CK coverage › Technique

Data from Network Shared Drive T1039

Adversaries may search network shares on computers they have compromised to find files of interest. Sensitive data can be collected from remote systems via shared network drives (host shared directory, network file server, etc.) that are accessible from the current system prior to Exfiltration. Interactive command shells may be in use, and common functionality within cmd may be used to gather information.

Events covered

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

ProviderEvent IDTitle
Sysmon1Process creation
Security-Auditing5143A network share object was modified.
Security-Auditing5145A network share object was checked to see whether client can be granted desired access.

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 (6 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
DACLS1starts_with 1A;
EventID1eq 15143
Image1match 1, ends_with 1\pwsh.exe, \robocopy.exe, \powershell.exe
OriginalFileName1eq 1PowerShell.EXE, powershell_ise.exe, XCOPY.EXE
CommandLine1match 1copy , cpi , \Sysvol\
RelativeTargetName1ends_with 1.dmp, .kirbi, .pst

Top indicator values (36 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
DACLSstarts_withA;1
EventIDeq51431
Imagematch\powershell.exe1
Imagematch\pwsh.exe12
CommandLinematchcopy 111
CommandLinematchcopy-item14
CommandLinematchcpi 14
CommandLinematch move-item1
OriginalFileNameeqpowershell_ise.exe16
CommandLinematch mi 12
Imageends_with\robocopy.exe15
CommandLinematchmove 12
CommandLinematch\Sysvol\1
OriginalFileNameeqPowerShell.EXE164
CommandLinematch\\\\*\\*$1
CommandLinematch cp 15
OriginalFileNameeqpwsh.dll172
Imageends_with\cmd.exe192
OriginalFileNameeqrobocopy.exe14
Imageends_with\xcopy.exe15

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

Kusto Query Language 1 rule