Detection tuning
How an AI SOC tunes detections from triage verdicts: propose exclusions from closed false positives, backtest them, and ship the change for review.
The short answer
Detection tuning cuts false positives without losing real detections. In Cotool, agents investigate every alert and each verdict feeds back into the detection that fired it, so a tuning agent proposes changes from false positives closed in triage.[1]
The problem
How an AI SOC handles it
Propose a change
A tuning agent reads the closed false positives and proposes a code change, such as excluding OAuth apps on the security team's approved register.[1]
Keep library updates
Customized library detections still pick up new library versions through auto-tuning, and new tunings keep changes approved earlier.[7]
Example
alerts = grants.where(scope__in=SENSITIVE_SCOPES)
# Security's register of approved OAuth apps
trusted = notion.query("Approved apps")["Client ID"]
alerts = alerts.exclude(client_id__in=trusted)The tuning a Cotool tuning agent proposed on the Detect page, built from false positives closed in triage: sensitive-scope grants still alert unless the app is on the approved register.[1]
What people approve
- Tunings go through review, as a pull request approval or Send for review, before they apply.[1]
How Cotool handles it
- Cotool's detection library covers common log sources, maps to MITRE ATT&CK, and is tuned to your environment by agents.[1]
Integrations used
Sources
- Detection engineering (Cotool Detect) · accessed November 16, 2026
- Pattern-based detection with agents (Cotool docs) · accessed November 16, 2026
- Splunk integration (Cotool docs) · accessed November 16, 2026
- Alerts (Cotool docs) · accessed November 16, 2026
- A SIEM built for AI-native security operations (Cotool SIEM) · accessed November 16, 2026
- GitHub integration (Cotool docs) · accessed November 16, 2026
- Changelog (Cotool docs) · accessed November 16, 2026
- Search endpoint descriptions (Splunk REST API Reference) · accessed November 16, 2026



