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.
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]
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]
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]
| Permission | Access | Why |
|---|---|---|
| Alerts: READQuery and read Falcon alerts.[10] | Read | Query and read Falcon alerts.[10] |
| Hosts: READSearch hosts and read device details.[9] | Read | Search hosts and read device details.[9] |
| NGSIEM: READ / WRITEFalcon requires NGSIEM: WRITE to start a search and NGSIEM: READ to read its status and results.[11] | Write | Falcon requires NGSIEM: WRITE to start a search and NGSIEM: READ to read its status and results.[11] |
| Vulnerabilities: READQuery Spotlight vulnerabilities.[12] | Read | Query Spotlight vulnerabilities.[12] |
| Hosts: WRITEContain a host or lift containment. Leave it out to keep the client read-only on endpoints.[9] | Write | Contain a host or lift containment. Leave it out to keep the client read-only on endpoints.[9] |
| Alerts: WRITEUpdate alert status and assignment.[10] | Write | Update alert status and assignment.[10] |
How Cotool works with CrowdStrike Falcon
FAQ
Sources
- Changelog (Cotool docs) · accessed November 16, 2026
- Integrations (Cotool) · accessed November 16, 2026
- Respond to every signal (Cotool Respond) · accessed November 16, 2026
- AI SOC (Cotool) · accessed November 16, 2026
- SIEM (Cotool) · accessed November 16, 2026
- Threat hunting (Cotool Hunt) · accessed November 16, 2026
- Response agents as code (Cotool docs) · accessed November 16, 2026
- Authenticating to the API (FalconPy) · accessed November 16, 2026
- Hosts service collection (FalconPy) · accessed November 16, 2026
- Alerts service collection (FalconPy) · accessed November 16, 2026
- NGSIEM service collection (FalconPy) · accessed November 16, 2026
- Spotlight Vulnerabilities service collection (FalconPy) · accessed November 16, 2026

