Data from Removable Media T1025

Tactic: Collection

Adversaries may search connected removable media on computers they have compromised to find files of interest. Sensitive data can be collected from any removable media (optical disk drive, USB memory, etc.) connected to the compromised system prior to Exfiltration. Interactive command shells may be in use, and common functionality within cmd may be used to gather information.

Events covered

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

Authoring guide

Patterns shared across the 5 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 (7 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
registry_path3contains 2, in 2, starts_with 1HKLM\\SOFTWARE\\Microsoft\\Windows Portable Devices\\Devices\\*, HKLM\\System\\CurrentControlSet\\Enum\\SWD\\WPDBUSENUM\\*, usbstor, hklm\\system\\currentcontrolset\\enum\\usbstor\\
registry_value_name2eq 2FriendlyName
CurrentDirectory1eq 1*
Details1contains 1:\\
EventID1eq 16416
Event_s1eq 1ONLINE
object_handle1is_not_null 1

Top indicator values (9 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
registry_pathcontains
usbstor
22
registry_pathin
HKLM\\SOFTWARE\\Microsoft\\Windows Portable Devices\\Devices\\*
22
registry_pathin
HKLM\\System\\CurrentControlSet\\Enum\\SWD\\WPDBUSENUM\\*
22
registry_value_nameeq
FriendlyName
23
CurrentDirectoryeq
*
1
Detailscontains
:\\
1
EventIDeq
6416
1
Event_seq
ONLINE
1
registry_pathstarts_with
hklm\\system\\currentcontrolset\\enum\\usbstor\\
1

Exclusions (2 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
CurrentDirectoryin
*\\sysvol\\*
1
CurrentDirectoryin
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.

Platform (all)
Domain (all)

Splunk 4 rules

Kusto 1 rule