Skip to main content

Alert deduplication

How an AI SOC handles duplicate alerts: link repeats to one canonical alert, read prior verdicts, and keep paging and case tools from multiplying an event.

Use case
Updated

The short answer

Alert deduplication keeps one event from turning into many tickets, pages, and investigations. Cotool gives response agents prior-alert context and duplicate handling, and its Duplicate status archives an alert under the canonical one.[1][2]

The problem

PagerDuty creates a new alert for every trigger event sent without a dedup_key, so repeats page again unless a stable key is sent.[4]

TheHive rejects a new alert with the same type, source, and source reference as an existing one, so integrations have to set those fields consistently.[5]

Sublime groups similar messages under a canonical_id, so a campaign sent to 100 users shows as one group instead of 100 alerts.[6]

How an AI SOC handles it

  1. Check for prior alerts

    Before investigating, the response agent searches recent alerts, including dismissed and expired ones, for the same entity and detection.[1]

  2. Link the duplicate

    If another alert is the real record, this one is marked Duplicate, archived, and linked to the canonical alert in both timelines.[2][3]

  3. Read one investigation

    Alert detail pages link to the canonical duplicate alert, so reviewers read one investigation instead of several.[1]

  4. Keep downstream tools in step

    When an escalation pages PagerDuty, a stable dedup_key per source alert keeps repeats on one alert. TheHive alerts need a consistent source reference.[4][5]

  5. Work email campaigns as groups

    For email, the agent works the Sublime message group rather than each message.[1][6]

Example

A PagerDuty trigger with a stable dedup keyjson
{
  "routing_key": "<integration key>",
  "event_action": "trigger",
  "dedup_key": "alert-<source alert id>",
  "payload": {
    "summary": "Escalated: repeated MFA push denials for one user",
    "source": "cotool",
    "severity": "error"
  }
}

An Events API v2 trigger. Sending the same dedup_key for repeats keeps them on one PagerDuty alert; severity is one of critical, error, warning, or info.[4]

What people approve

  • People can change an alert's status, and the assigned agent resumes after the change. Canonical alerts can be dismissed.[1]

How Cotool handles it

  • Cotool added a Duplicate alert status in release 0.60.0, and prior-alert context with duplicate handling for response agents in release 0.66.0.[1]

Integrations used

Sources

  1. Changelog (Cotool docs) · accessed November 16, 2026
  2. Alerts (Cotool docs) · accessed November 16, 2026
  3. Working alerts (Cotool docs) · accessed November 16, 2026
  4. Send an alert event (PagerDuty Events API v2) · accessed November 16, 2026
  5. About alerts (TheHive docs) · accessed November 16, 2026
  6. Message groups (Sublime docs) · accessed November 16, 2026

Related use cases

All use cases

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