Network detection triage
How an AI SOC triages network alerts such as DNS beaconing: tie traffic to a device, process, and user, check the destination, and block with approval.
The short answer
Network detection triage explains suspicious traffic, such as periodic DNS queries or connections to a new domain, by tying it to a device, a process, and a user. Cotool's example Network Egress Responder takes SIEM detections and traced periodic DNS queries to a telemetry agent.[1]
The problem
How an AI SOC handles it
Read the detection
The alert names the domain or IP and the pattern, such as queries at regular intervals.[1]
Example
dataSource.name='SentinelOne' dataSource.category='security' event.type=*
| group ct=count() by event.type
| sort -ct
| limit 50A SentinelOne PowerQuery to start from. Narrow the filter to the host and window in the alert to find the process behind the traffic.[8]
What people approve
- Blocklist changes and host containment are state-changing actions that can require approval in the app or in Slack.[4]
How Cotool handles it
- Cotool syncs Zscaler ZIA policy rules into its detection-rule repository weekly, and a Zscaler trigger turns Cloud NSS or ZIA alert-rule webhooks into Cotool alerts.[3]
Integrations used
Sources
- Respond to every signal (Cotool Respond) · accessed November 16, 2026
- Changelog (Cotool docs) · accessed November 16, 2026
- Zscaler integration (Cotool docs) · accessed November 16, 2026
- AI SOC (Cotool) · accessed November 16, 2026
- Application Layer Protocol: DNS, T1071.004 (MITRE ATT&CK) · accessed November 16, 2026
- Gateway activity logs (Cloudflare docs) · accessed November 16, 2026
- VirusTotal API v3 overview (VirusTotal docs) · accessed November 16, 2026
- LRQ API reference (SentinelOne ai-siem) · accessed November 16, 2026


