Exfiltration Over Physical Medium T1052

Tactic: Exfiltration

Adversaries may attempt to exfiltrate data via a physical medium, such as a removable drive. In certain circumstances, such as an air-gapped network compromise, exfiltration could occur via a physical medium or device introduced by a user. Such media could be an external hard drive, USB drive, cellular phone, MP3 player, or other removable storage and processing device. The physical medium or device could be used as the final exfiltration point or to hop between otherwise disconnected systems.

Events covered

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

Authoring guide

Patterns shared across the 6 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 (18 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
EventType3eq 3, in 1FileCreated, FileDownloaded, FileRenamed, UsbDriveMounted, mount
AlertName1eq 1mass download by a single user
CloudAppEvent_EndTime1le 1Alert_TimeGenerated
DeviceFileEvent_Files1starts_with 1USB_DriveLetter
DeviceFileEvent_StartTime1ge 1Alert_TimeGenerated
Status1ne 1Resolved
TargetDriveLetter1eq 1MountedDriveLetters
TargetObject1contains 1usbstor
Type1eq 1account, ip
USB_DriveLetter1is_not_null 1
USB_TimeGenerated1ge 1Alert_TimeGenerated
event.category1eq 1registry
event.outcome1eq 1success
event.type1eq 1device
file_name1eq 1ca_filelist

Top indicator values (21 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
EventTypeeq
UsbDriveMounted
22
EventTypeeq
FileDownloaded
12
EventTypeeq
mount
1
AlertNameeq
mass download by a single user
1
CloudAppEvent_EndTimele
Alert_TimeGenerated
1
DeviceFileEvent_Filesstarts_with
USB_DriveLetter
1
DeviceFileEvent_StartTimege
Alert_TimeGenerated
1
EventTypein
FileCreated
14
EventTypein
FileRenamed
12
Statusne
Resolved
1
TargetDriveLettereq
MountedDriveLetters
1
TargetObjectcontains
usbstor
1
Typeeq
account
113
Typeeq
ip
17
USB_TimeGeneratedge
Alert_TimeGenerated
1
event.categoryeq
registry
14
event.outcomeeq
success
1251
event.typeeq
device
1
file_nameeq
ca_filelist
1
registry_value_nameeq
FriendlyName
13
volume.removableeq
true
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)

Elastic 4 rules

Kusto 2 rules