Skip to main content

Vulnerability exposure hunting

How an AI SOC hunts exposure to new vulnerabilities: match intel to your assets, confirm the vulnerable setup, look for exploitation, and ship a detection.

Use case
Updated

The short answer

Vulnerability exposure hunting starts from a new vulnerability or campaign and asks whether you run the affected software, whether it is reachable, and whether anyone has exploited it. Cotool Hunt ingests intel, assesses relevance and exposure, and opens a Hunt alert when something is actionable.[1]

The problem

Exploiting internet-facing systems, from web servers and databases to network device management, is a direct path to initial access.[5]

Answering "are we exposed?" takes the affected versions, your configuration, and your logs together, as in Cotool's example of an Envoy CVE checked against GKE ingress workloads.[2]

How an AI SOC handles it

  1. Ingest intel

    Hunt pulls intel from built-in sources, your RSS, MISP, and TAXII sources, and the /hunt-intel chat command.[1]

  2. Assess relevance

    Hunt decides whether the threat applies to your environment, such as whether the affected software runs in your workloads.[1][2]

  3. Check exposure

    The agent confirms vulnerable versions and configuration, using sources such as CrowdStrike Spotlight vulnerability data.[3][6]

  4. Look for exploitation

    Stored logs and federated sources such as Splunk are searched for compromise signals. If the needed telemetry is missing, the threat is marked Blocked rather than Clear.[1][4]

  5. Open follow-up work

    Actionable results become a Hunt alert, with proposed detection rules and fixes such as pull requests.[1][2]

Example

Hunt threat statusestext
Hunting      a Hunt assessment is running
Active       Hunt created an open alert
Blocked      required telemetry was missing
Monitoring   residual exposure is being watched
Covered      an existing detection covers the threat
Clear        no meaningful exposure found
Resolved     the Hunt alert was investigated and closed
Not relevant the threat does not apply to your environment

The statuses a threat moves through in Cotool Hunt. Blocked marks a visibility gap, not a clean result.[1]

What people approve

  • A person decides whether to patch, mitigate, or accept the risk. Residual exposure is tracked as Monitoring, and users can dismiss a threat.[1]

How Cotool handles it

  • Cotool's Hunt settings set minimum exposure thresholds and compromise signal overrides for when it creates alerts.[3]

Integrations used

Sources

  1. Hunt (Cotool docs) · accessed November 16, 2026
  2. Threat hunting (Cotool Hunt) · accessed November 16, 2026
  3. Changelog (Cotool docs) · accessed November 16, 2026
  4. A SIEM built for AI-native security operations (Cotool SIEM) · accessed November 16, 2026
  5. Exploit Public-Facing Application, T1190 (MITRE ATT&CK) · accessed November 16, 2026
  6. Spotlight Vulnerabilities (FalconPy) · 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