Skip to main content

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.

Use case
Updated

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

Adversaries hide command and control in DNS because it is common and is often allowed even before network authentication completes.[5]

Cloudflare Gateway network logs include only TCP connections that were successfully established, so blocked attempts have to come from other logs.[6]

How an AI SOC handles it

  1. Read the detection

    The alert names the domain or IP and the pattern, such as queries at regular intervals.[1]

  2. Find the device and user

    The agent ties the source to a device and user through Cloudflare Zero Trust device records or Zscaler Client Connector devices.[2][3]

  3. Find the process

    On the endpoint, the agent finds the process behind the traffic in CrowdStrike or SentinelOne.[1][2]

  4. Check the destination

    The domain or IP goes to VirusTotal, and Zscaler classifies the URL.[3][7]

  5. Block with approval

    If the destination is malicious, the agent proposes a ZIA threat blocklist entry and host containment for a person to approve.[3][4]

Example

Group endpoint events by typetext
dataSource.name='SentinelOne' dataSource.category='security' event.type=*
| group ct=count() by event.type
| sort -ct
| limit 50

A 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

  1. Respond to every signal (Cotool Respond) · accessed November 16, 2026
  2. Changelog (Cotool docs) · accessed November 16, 2026
  3. Zscaler integration (Cotool docs) · accessed November 16, 2026
  4. AI SOC (Cotool) · accessed November 16, 2026
  5. Application Layer Protocol: DNS, T1071.004 (MITRE ATT&CK) · accessed November 16, 2026
  6. Gateway activity logs (Cloudflare docs) · accessed November 16, 2026
  7. VirusTotal API v3 overview (VirusTotal docs) · accessed November 16, 2026
  8. LRQ API reference (SentinelOne ai-siem) · accessed November 16, 2026

Related use cases

All use cases

Related reading

Attackers are scaling with tokens

Cotool helps defenders operate at machine speed. See how security teams are scaling Detection & Response.

Book a demo