SECOPS

Daily Phishing Triage Digest & Metrics Rollup

Runs every morning, rolls up the prior day's phishing-report verdicts from Postgres into top-talkers, detonation outcomes, and unresolved cases.

CategorySecOps
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule at reporting hour
  • ActionQuery prior-day triage casesPostgreSQLPostgres
  • LogicRoll up verdicts, top targets, backlog
  • ActionEmit metrics to observability dashboardsDatadogDatadog
  • OutputEmail manager-ready digest to leadershipGmailGmail

What it does

Gives security leadership a daily pulse on the phishing program. It aggregates yesterday's triage cases into counts by verdict, the most-targeted recipients, the noisiest spoofed senders, and any cases still open, then ships a clean digest by email and pushes the same numbers as metrics for trend dashboards.

When to use it

When you already run automated phishing triage and want a recurring management summary plus retained metrics, without an analyst hand-building a report each morning.

How it works

  1. 1A daily schedule fires the workflow at your chosen reporting hour.
  2. 2The flow queries the Postgres triage table for all cases from the previous 24 hours.
  3. 3A logic step rolls the rows up into verdict totals, top targeted users, repeat spoofed senders, and the unresolved-case backlog.
  4. 4The aggregated counts are emitted as gauges to Datadog for trend tracking.
  5. 5A formatted HTML digest is sent via Gmail to the security leadership distribution list.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PostgresAny Postgres URL — query, write, migrate.
  2. 2
    Connect DatadogMetrics, traces, log search.
  3. 3
    Connect GmailRead, draft, send, label.
  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.