Skip to main content

Cotool + SentinelOne

Connect SentinelOne to Cotool so agents run PowerQuery hunts, investigate threats and alerts, look up endpoints, and fetch files from agents securely.

Endpoint & Device
Updated

The short answer

With SentinelOne connected, Cotool agents run PowerQuery over your SentinelOne data, investigate threats and alerts, look up endpoints, fetch files from agents securely, and use SentinelOne's own MITRE mappings in Cotool's coverage map.[1][3]

How it connects: Cotool calls your console's management API with a service user's API token and your account or site ID. SentinelOne enforces token permissions server-side, and each endpoint lists the permissions it requires.[2][6]

What Cotool uses from SentinelOne

Threats and alerts
Agents read threats, their timelines, and their explore events. In the SentinelOne API these reads require Threats.view.[1][8]
Endpoints
Agents look up the endpoint behind an alert, including devices without a serial number. Listing agents requires Endpoints.view.[1][9]
PowerQuery
Agents hunt with PowerQuery, which requires an explicit end time in Cotool. SentinelOne runs PowerQueries through an asynchronous query API scoped to the accounts the token can reach.[1][7]
Managed log ingestion
Cotool's managed log ingestion supports SentinelOne, with threat and alert investigation actions on the ingested data.[1]

Response actions

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

Fetch files from an agent
Cotool supports secure file fetches from SentinelOne agents. SentinelOne's fetch-files action requires Endpoints.fileFetch, and fetching a threat file requires Threats.fetchThreatFile.[1][8][10]

Detections, hunts, and triage

Triage a SentinelOne alertTriage
Cotool's docs show an agent that fetches alert details from SentinelOne, searches Splunk for related activity, checks indicators in VirusTotal, decides severity, and updates the Jira ticket.[4]
Map coverage with SentinelOne's MITRE tagsDetection
Cotool generates MITRE mappings for each detection with confidence scores, and for platforms like SentinelOne that supply their own mappings it can use those directly.[3]
Hunt with PowerQueryHunt
A hunt runs PowerQuery over a bounded window, groups events by type, and pivots to the endpoints and threats behind the outliers.[1][5][7]

Example query

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

PowerQuery from SentinelOne's query API reference. Narrow it with a site or endpoint term before you hunt.[7]

Setup and permissions

Create a service user at the account or site scope you want covered, give it a role with only the permissions listed here, and copy its API token. Service user tokens do not expire with an SSO session and are not shared with a person's console use.[6][7]

PermissionAccess
Threats.viewList threats and read timelines and explore events.[8]Read
Endpoints.viewLook up agents and endpoint details.[9]Read
Endpoints.fileFetchFetch files from an agent for investigation.[10]Write
Threats.fetchThreatFileFetch the file behind a threat.[8]Write
  • On a multi-account token, the S1-Scope header does not narrow queries; the account must be set in the query request itself.[7]
  • Network disconnect needs Endpoints.disconnectFromNetwork. Leave it off the role unless you want agents to be able to propose isolation.[10]

How Cotool works with SentinelOne

  • SentinelOne PowerQuery and MITRE mapping were among Cotool's earliest integration features, in releases 0.3.0 and 0.7.0.[1]
  • Cotool's detection workflows support SentinelOne custom rules, including custom rule filters.[1]

FAQ

What role should the SentinelOne service user have?
The lowest role that grants the view permissions above, at the narrowest account or site scope. Add Endpoints.fileFetch or Threats.fetchThreatFile only if agents should fetch files.[8][9][10]

Sources

  1. Changelog (Cotool docs) · accessed November 16, 2026
  2. Integrations (Cotool) · accessed November 16, 2026
  3. MITRE ATT&CK mapping (Cotool docs) · accessed November 16, 2026
  4. Creating agents from chat (Cotool docs) · accessed November 16, 2026
  5. Threat hunting (Cotool Hunt) · accessed November 16, 2026
  6. Management Console API skill (SentinelOne ai-siem) · accessed November 16, 2026
  7. LRQ API reference (SentinelOne ai-siem) · accessed November 16, 2026
  8. Threats API reference (SentinelOne ai-siem) · accessed November 16, 2026
  9. Agents API reference (SentinelOne ai-siem) · accessed November 16, 2026
  10. Agent actions API reference (SentinelOne ai-siem) · accessed November 16, 2026

Related integrations

All integrations

Use cases with SentinelOne

Attackers are scaling with tokens

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

Book a demo