Loading interactive filters…
1200KM / detection
T1030 Data Transfer Size Limits — Detection Rules
Detection workspace for T1030 Data Transfer Size Limits: 2 Sigma sources, 1 Atlas concepts and 1 anomaly models. No live detection validation.
Source-backed rule directory
Atlas deterministic concepts
T1030 Data Transfer Size Limits
COUNT(outbound_transfers_with_similar_small_size BY source AND destination, 30m) >= threshold -> ALERT
Anomaly models
Transfers deliberately limited to evade controls — T1030 Data Transfer Size Limits
Comparison unit: repeated source-destination transfers.
Expected behavior: transfer sizes and inter-arrival times vary with ordinary usage.
Deviation: persistent repeated small transfers, unusual periodicity, or changed autocorrelation.
ATT&CK analytic guidance
Adversary uses a process to establish outbound connections that transmit uniform packet sizes at a consistent interval, avoiding threshold-based network alerts.
Outbound connections from non-network-facing processes repeatedly send similarly sized payloads within uniform time intervals.
Processes on macOS initiate external connections that consistently transmit data in fixed sizes using LaunchAgents or unexpected users.
Connected ecosystem references
Threat actor context
These are explicit actor-to-technique associations in the existing Threat Matrix snapshot, not attribution of an event or proof that a detector identifies the actor. No tool-to-actor relationship is inferred.
Pinned research references. No browser attack runner, live simulation result or validated detector is asserted. Source mappings and validation limits are preserved. ATT&CK / Atomic provenance · Detection provenance.