SECOPS

Escalate Phishing Report Spikes to On-Call

On a schedule, this counts phishing reports in the last interval, and when volume spikes above your active-campaign threshold it pages on-call and opens an incident…

CategorySecOps
Enginesim
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled interval check
  • ActionCount and cluster recent reportsPostgreSQLPostgres
  • LogicCompare volume to campaign threshold
  • ActionOpen incident with cluster summaryPagerDutyPagerDuty
  • OutputPost incident link to SOC channelSlack

What it does

Catches active campaigns by their shape, not just individual reports. On a fixed interval it tallies recent phishing reports, clusters them by shared sender or URL, and when the count crosses your threshold it treats it as an in-progress attack and escalates to on-call with the clustered evidence attached.

When to use it

Use this when a single phishing report is routine but ten in five minutes means an active blast that needs an incident commander now. It bridges the gap between per-message triage and human incident response.

How it works

  1. 1A schedule fires every few minutes.
  2. 2A Postgres query counts reports in the window and groups them by shared indicators.
  3. 3A threshold check decides whether the volume and clustering indicate an active campaign.
  4. 4If triggered, a PagerDuty incident is created with the cluster summary and top indicators.
  5. 5A heads-up with the incident link posts to the SOC Slack channel so responders converge fast.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PostgresAny Postgres URL — query, write, migrate.
  2. 2
    Connect PagerDutyIncidents, on-call, escalations.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.