Data exfiltration detection
How an AI SOC detects exfiltration to personal cloud storage: baseline each user's uploads, flag spikes, add HR context, and tune out approved storage.
The short answer
Exfiltration detection looks for data leaving through channels that blend in, such as uploads to personal cloud storage. Cotool's example detection models each user's normal upload volume from proxy logs, flags days far above it, and joins the spikes with HR data on who is leaving.[1][4]
The problem
How an AI SOC handles it
Model each user's normal
It computes a 30-day rolling median per user and flags days more than 20 times that user's normal.[1]
Flag leavers
Spikes are joined with each user's last day from the HR system.[1]
Tune out approved storage
In version 2, the tuning agent added an exclusion for the company's own Box storage.[1]
Example
LOOKBACK = 30 # days of history per user
SPIKE = 20 # flag days this many times their normal
CATEGORY = "personal-storage"
1. Query proxy logs uploads to personal storage, 30 days
2. Model each user 30-day rolling median per user
3. Find spikes days over 20x the user's normal
4. Flag leavers join each spike with a last day
5. Exclude company Box added by the tuning agent (v2)
6. Return alerts one alert per remaining spikeThe parameters and visual workflow of the example detection on Cotool's Detect page. Adjust the lookback, spike factor, and storage category to your traffic.[1]
What people approve
How Cotool handles it
- Cotool detections are Python that runs against stored and federated sources, and each one maps to a visual workflow the whole team can read.[1]
Integrations used
Sources
- Detection engineering (Cotool Detect) · accessed November 16, 2026
- Changelog (Cotool docs) · accessed November 16, 2026
- Alerts (Cotool docs) · accessed November 16, 2026
- Exfiltration to Cloud Storage, T1567.002 (MITRE ATT&CK) · accessed November 16, 2026
- About Cloud NSS feeds (Zscaler Help) · accessed November 16, 2026


