Cotool + Datadog
Connect Datadog to Cotool so agents search and aggregate logs, read and triage security signals, and author, validate, and disable Cloud SIEM detection rules.
The short answer
With Datadog connected, Cotool agents search and aggregate your Datadog logs during investigations, and author Datadog detection rules with generation, validation, and the ability to disable a rule from Cotool's detection editor.[1][2]
How it connects: Cotool calls the Datadog API with an API key and an application key. Datadog lets you scope application keys so they carry only the permissions an application needs, and create them on service accounts.[2][6]
What Cotool uses from Datadog
- Logs
- Agents search Datadog logs and run aggregations with multiple groupings. Datadog's search syntax addresses attributes with
@and supports filters such asCIDR(@network.client.ip, 13.0.0.0/8).[1][8] - Environment map
- Cotool keeps a map of your Datadog environment that it refreshes from Datadog, and a failed refresh no longer overwrites the existing map.[1]
- Security signals
- Signals are what Datadog detection rules raise. Reading them needs
security_monitoring_signals_read; changing their state needssecurity_monitoring_signals_write.[5]
Response actions
These change state in Datadog, so they are the steps teams usually gate behind approval.
- Create and edit detection rules
- Cotool's Datadog detection authoring generates rules, validates them, and respects Datadog's constraint that
groupSignalsBymust be a subset ofgroupByFields, which cuts invalid attempts.[1][5] - Disable a detection rule
- Datadog detection rules can be disabled directly from Cotool's detection editor.[1]
Detections, hunts, and triage
Example query
service:okta CIDR(@network.client.ip, 203.0.113.0/24) -status:infoDatadog log search syntax: @ addresses an attribute and CIDR() matches a range. Replace the service and range with your own.[8]
Setup and permissions
Create an API key and an application key, preferably on a service account so the keys keep working when people leave, and limit the application key's scopes to the permissions listed here.[6]
| Permission | Access | Why |
|---|---|---|
logs_read_dataRead log data. Datadog also requires Logs Read Index Data to read logs.[5] | Read | Read log data. Datadog also requires Logs Read Index Data to read logs.[5] |
logs_read_configRead logs configuration, such as indexes.[5] | Read | Read logs configuration, such as indexes.[5] |
security_monitoring_rules_writeCreate and edit detection rules. Leave it out if agents should only read.[5] | Write | Create and edit detection rules. Leave it out if agents should only read.[5] |
security_monitoring_signals_writeModify security signals, for triage. Pair it with security_monitoring_signals_read.[5] | Write | Modify security signals, for triage. Pair it with security_monitoring_signals_read.[5] |
- Scoped application keys get only the scopes you select and no other permissions, and you can change their scopes later.[6]
How Cotool works with Datadog
FAQ
Sources
- Changelog (Cotool docs) · accessed November 16, 2026
- Integrations (Cotool) · accessed November 16, 2026
- Detections are code (Cotool Detect) · accessed November 16, 2026
- Respond to every signal (Cotool Respond) · accessed November 16, 2026
- Datadog role permissions (Datadog docs) · accessed November 16, 2026
- API and application keys (Datadog docs) · accessed November 16, 2026
- Detection rules (Datadog docs) · accessed November 16, 2026
- Log search syntax (Datadog docs) · accessed November 16, 2026
