Skip to main content

Cotool + CrowdStrike Falcon

Connect CrowdStrike Falcon to Cotool so agents triage Falcon detections, query Next-Gen SIEM, ingest Falcon Data Replicator logs, and contain hosts with approval.

Endpoint & Device
Updated

The short answer

With CrowdStrike Falcon connected, Cotool response agents triage Falcon detections using alert and behavior data, query CrowdStrike Next-Gen SIEM in place, store Falcon Data Replicator logs in Cotool, and propose host isolation that a person approves.[1][3][4][5]

How it connects: Cotool calls the CrowdStrike Falcon APIs with an API client ID and secret. Each Falcon API operation requires a named scope, such as Hosts: READ or Alerts: WRITE, so the client can call only what you grant.[2][8][9][10]

What Cotool uses from CrowdStrike Falcon

Falcon detections
Detections can trigger a Cotool response agent by webhook. The agent lists alerts and pulls device details before it judges an event.[3][7]
Next-Gen SIEM
Agents query CrowdStrike Next-Gen SIEM data directly from Cotool. In the Falcon API, starting an NGSIEM search needs NGSIEM: WRITE and reading its status needs NGSIEM: READ.[1][11]
Falcon Data Replicator
Cotool's managed log ingestion supports CrowdStrike Falcon Data Replicator, so raw endpoint telemetry can be stored and searched in Cotool.[1][5]
Spotlight and Falcon Shield
The CrowdStrike tool includes Spotlight vulnerability-management actions and Adaptive Shield (Falcon Shield) SaaS security support. Spotlight vulnerability queries need Vulnerabilities: READ.[1][12]

Response actions

These change state in CrowdStrike Falcon, so they are the steps teams usually gate behind approval.

Contain a host
Falcon's host action endpoint contains a host or lifts containment and needs Hosts: WRITE. Cotool shows isolation as a response action a person approves or rejects.[3][4][9]
Update alerts
Updating Falcon alerts, such as status or assignment, uses the alerts update endpoint, which needs Alerts: WRITE.[10]

Detections, hunts, and triage

Endpoint alert triageTriage
Cotool's example Endpoint Alert Responder treats Falcon alert and behavior data as the source of truth, reconstructs the full process tree before judging any single event, and escalates confirmed credential theft or C2 immediately.[3]
Isolate with approvalResponse
When an agent recommends isolation, it asks a person to approve isolating the named host in CrowdStrike before the action runs.[3][4]
Hunt across FDR telemetryHunt
With Falcon Data Replicator logs in Cotool, hunts search process and network telemetry alongside identity and cloud logs in one place.[1][5][6]

Setup and permissions

Create an API client in the Falcon console, grant only the scopes for the data and actions you want, and use its client ID and secret to authenticate.[8]

PermissionAccess
Alerts: READQuery and read Falcon alerts.[10]Read
Hosts: READSearch hosts and read device details.[9]Read
NGSIEM: READ / WRITEFalcon requires NGSIEM: WRITE to start a search and NGSIEM: READ to read its status and results.[11]Write
Vulnerabilities: READQuery Spotlight vulnerabilities.[12]Read
Hosts: WRITEContain a host or lift containment. Leave it out to keep the client read-only on endpoints.[9]Write
Alerts: WRITEUpdate alert status and assignment.[10]Write

How Cotool works with CrowdStrike Falcon

  • Cotool added the CrowdStrike Next-Gen SIEM integration in release 0.44.0 and made NG-SIEM queries more reliable in later releases.[1]
  • Response agents as code can require the crowdstrike integration and name its tools, such as crowdstrike_listDetections and crowdstrike_getDeviceDetails.[7]

FAQ

Can Cotool isolate a host in CrowdStrike without a person?
Cotool's product pages show isolation as an approval: a person approves or rejects isolating the host. Without Hosts: WRITE on the API client, Falcon refuses containment calls.[4][9]
Does Cotool need Falcon Data Replicator?
No. Agents can query Falcon alerts and Next-Gen SIEM through the API. FDR ingestion is for teams that want raw telemetry stored and searched in Cotool.[1][5]

Sources

  1. Changelog (Cotool docs) · accessed November 16, 2026
  2. Integrations (Cotool) · accessed November 16, 2026
  3. Respond to every signal (Cotool Respond) · accessed November 16, 2026
  4. AI SOC (Cotool) · accessed November 16, 2026
  5. SIEM (Cotool) · accessed November 16, 2026
  6. Threat hunting (Cotool Hunt) · accessed November 16, 2026
  7. Response agents as code (Cotool docs) · accessed November 16, 2026
  8. Authenticating to the API (FalconPy) · accessed November 16, 2026
  9. Hosts service collection (FalconPy) · accessed November 16, 2026
  10. Alerts service collection (FalconPy) · accessed November 16, 2026
  11. NGSIEM service collection (FalconPy) · accessed November 16, 2026
  12. Spotlight Vulnerabilities service collection (FalconPy) · accessed November 16, 2026

Related integrations

All integrations

Use cases with CrowdStrike Falcon

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