Response playbooks, investigation guides, and Atomic Red Team tests are Pro-only. Upgrade to unlock the full detection package for THREAT-Exfil-ArchiveSplitDLPThresholdEvasion.

Upgrade to Pro
THREAT-Exfil-ArchiveSplitDLPThresholdEvasion Sumo Logic CSE · Sumo

Detect Archive Volume-Splitting and Fixed-Chunk Transfers to Evade DLP/Network Size-Threshold Alerting in Sumo Logic CSE

Most corporate DLP appliances and egress proxies alert on a single transfer or an aggregate daily transfer that crosses a configured size threshold (commonly 10MB, 25MB, or 50MB per-connection triggers, or a daily-total cap on a per-user or per-host basis). Adversaries who know or can infer these thresholds deliberately keep every individual transfer just under the trigger point by splitting collected data into fixed-size archive volumes before exfiltration — APT28 has been observed constraining exfil chunks to stay under configured DLP alert sizes during Ukraine-focused intrusions, LuminousMoth caps individual uploads at roughly 5MB when exfiltrating over Google Drive, Threat Group-3390 (Emissary Panda/APT27) has used volume-split RAR/7-Zip archives ahead of staged transfers, and Play ransomware affiliates split staged loot into uniform archive parts before the double-extortion exfil phase that precedes encryption. Because none of these chunks individually crosses a size-based alert threshold, and because the transfers are frequently spread across a sustained window rather than sent as a single burst, this technique defeats naive 'alert on large transfer' DLP rules that do not aggregate related connections by destination or by process. Detection therefore has to correlate two signals a single-transfer DLP rule cannot see on its own: (1) command-line or file-system evidence that data was deliberately split into equal-sized volumes immediately before egress, and (2) a burst of multiple outbound transfers to the same external destination whose sizes cluster tightly around a value just below a known DLP/proxy threshold rather than exhibiting the size variability of normal user traffic.

MITRE ATT&CK

Tactic
Exfiltration

Sumo Detection Query

Sumo Logic CSE (Sumo)
sql
// Part 1: archive-splitting process events
(_sourceCategory=*windows* OR _sourceCategory=*sysmon*)
| where EventID = "1" or EventCode = "1"
| where (Image matches "*\\7z.exe" or Image matches "*\\7za.exe" or Image matches "*\\7zr.exe"
         or Image matches "*\\rar.exe" or Image matches "*\\WinRAR.exe")
  and (CommandLine matches "* -v*" or CommandLine matches "* /v*" or CommandLine matches "*-volume*")
| fields _messageTime, Computer, User, Image, CommandLine

// Part 2 — run as separate query and correlate by host:
// _sourceCategory=*proxy* OR _sourceCategory=*firewall*
// | where bytes_out > 1048576
// | timeslice 24h
// | stats count as TransferCount, min(bytes_out) as MinSent, max(bytes_out) as MaxSent by _timeslice, host, dest_ip
// | where TransferCount >= 4
// | eval SizeSpreadRatio = (MaxSent - MinSent) / MaxSent
// | where SizeSpreadRatio < 0.10
high severity medium confidence

Sumo Logic query for the archive-splitting process signal, with a companion commented query for the clustered near-threshold transfer pattern over proxy/firewall logs, to be correlated by host/destination in Sumo Logic Cloud SIEM Enterprise's rule builder — mirroring the KQL/SPL join logic.

Data Sources

Sumo Logic Continuous Intelligence PlatformWindows Event Log via Sumo Logic Installed CollectorSumo Logic Cloud SIEM Enterprise (CSE)

Required Tables

_sourceCategory=*windows*_sourceCategory=*sysmon*_sourceCategory=*proxy*_sourceCategory=*firewall*

False Positives & Tuning

  • Backup software chunking uploads at a fixed size close to but under a proxy or API limit
  • Cloud storage sync clients using fixed multipart upload block sizes
  • CI/CD artifact upload tooling with a fixed chunk size

Other platforms for THREAT-Exfil-ArchiveSplitDLPThresholdEvasion


Testing Methodology

Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Split archive into DLP-threshold-adjacent volumes and upload each below a monitored size

    Expected signal: Sysmon Event ID 1 for 7z.exe with CommandLine containing '-v9646899b'. Sysmon Event ID 11 for the .7z.001 through .7z.004 chunk files. Sysmon Event ID 3 / proxy logs for 4 outbound POST connections to the test endpoint with near-identical byte counts just under 10MB.

  2. Test 2Unix split-based chunking with repeated near-threshold curl uploads

    Expected signal: Linux auditd/Sysmon-for-Linux process events for split with '-b 24117145'. File creation events for argus_dlp_chunk_00 through argus_dlp_chunk_04. Network connection events for repeated curl POST requests with near-identical payload sizes just under 25MB to the same destination.

  3. Test 3WinRAR volume-split with delayed, spread-out uploads to avoid burst-based detection

    Expected signal: Sysmon Event ID 1 for WinRAR.exe with '-v48234291b'. Sysmon Event ID 11 for the .part1.rar through .part4.rar files. Proxy/network logs showing 4 uploads near the 50MB threshold spread across roughly 90 seconds rather than a tight burst.

Unlock playbooks & atomic tests with Pro

Get the full detection package for THREAT-Exfil-ArchiveSplitDLPThresholdEvasion — response playbook and atomic red team tests, plus investigation guidance and hunting queries.

df00tech Pro — £29/user/month

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections