Hunting For Data Exfiltration Indicators

Hunting for Data Exfiltration Indicators

When to Use

• When hunting for data theft in compromised environments
• After detecting unusual outbound data volumes or patterns
• When investigating potential insider threat data theft
• During incident response to determine what data was stolen
• When threat intel indicates data exfiltration campaigns targeting your sector

Detection Gaps & Validation

• "Low and slow" defeats volume thresholds: T1030 size-limited transfers and T1029 scheduled exfil stay under daily-byte baselines — sum bytes-out per destination over 7–30 days and alert on cumulative volume, not single sessions.
• DNS tunneling (T1048.003): encoded data in long/high-entropy subdomains and high TXT query rates needs DNS logs (Sysmon EID 22 or resolver logs) plus entropy/length scoring — invisible if only NXDOMAIN or aggregated DNS is retained.
• Encrypted upload blind spots: HTTPS POSTs to personal cloud (T1567.002 — Drive/Dropbox/OneDrive) look like normal TLS; without CASB/DLP body inspection you only have bytes-out + destination — pivot on a high out:in byte ratio and newly-seen destinations.
• Direction matters: flag asymmetric flows where bytes_out >> bytes_in to non-corporate ASNs; many rules only watch inbound.
• Validate: run Atomic Red Team T1048 (DNS/ICMP exfil) and T1567.002 (cloud upload) and confirm the volume-anomaly and DNS-entropy searches fire with the test host/destination.
• Tune FPs: backups, cloud sync (OneDrive/Box), software updates, and video uploads create large legitimate egress — baseline per-user/per-host to sanctioned destinations and exclude known backup targets.

Prerequisites

• Network proxy/firewall logs with byte-level data transfer metrics
• DLP solution or CASB with cloud upload visibility
• DNS query logs for DNS exfiltration detection
• Email gateway logs for attachment monitoring
• SIEM with data volume anomaly detection capabilities

Workflow

1. Define Exfiltration Channels: Identify potential channels (HTTP/S uploads, DNS tunneling, email attachments, cloud storage, removable media, encrypted protocols).
2. Baseline Normal Data Flows: Establish baseline outbound data transfer volumes per user, host, and destination over a 30-day window.
3. Detect Volume Anomalies: Identify hosts or users transferring significantly more data than baseline to external destinations.
4. Analyze Transfer Destinations: Check destination domains/IPs against threat intel, identify newly registered domains, personal cloud storage, and foreign infrastructure.
5. Inspect Protocol Abuse: Look for DNS tunneling (large/frequent TXT queries), ICMP tunneling, or data hidden in allowed protocols.
6. Correlate with File Access: Link exfiltration indicators to file access events on sensitive file shares, databases, or repositories.
7. Report and Contain: Document findings with evidence, estimate data exposure, and recommend containment actions.

Key Concepts

Tools & Systems

Common Scenarios

1. Cloud Storage Exfiltration: User uploads sensitive documents to personal Google Drive or Dropbox via browser.
2. DNS Tunneling: Malware exfiltrates data encoded in DNS subdomain queries to attacker-controlled nameserver.
3. HTTPS Upload: Compromised system POSTs large data blobs to C2 server over encrypted HTTPS.
4. Email Attachment Exfiltration: Insider forwards sensitive documents to personal email accounts.
5. Staging and Compression: Adversary stages data in compressed archives before slow exfiltration to avoid detection.

Output Format

Hunt ID: TH-EXFIL-[DATE]-[SEQ]
Exfiltration Channel: [HTTP/DNS/Email/Cloud/USB]
Source: [Host/User]
Destination: [Domain/IP/Service]
Data Volume: [Bytes/MB/GB]
Time Period: [Start - End]
Protocol: [HTTPS/DNS/SMTP/SMB]
Files Involved: [Count/Types]
Risk Level: [Critical/High/Medium/Low]
Confidence: [High/Medium/Low]