SECOPS
Phishing Campaign Blast-Radius Sweep
Webhook-triggered when an analyst confirms a phishing case; searches the Gmail tenant for other copies of the same malicious URL or sender, tallies every recipient.
How it runs
The automated pipeline, trigger to output.
- TriggerAnalyst confirms case via webhookHTTP webhook
- ActionSearch tenant mail for matching indicatorsGmail
- LogicDedupe matches into recipient roster + count
- ActionWrite incident record with affected recipientsPostgres
- ActionEscalate campaign incident over thresholdPagerDuty
- OutputPost blast-radius report to incident channelSlack
What it does
Answers the question every responder asks after one phishing report is confirmed: who else got it? Given a confirmed indicator (sender or URL), it sweeps the mail tenant for matching messages, builds the full recipient list, and delivers a blast-radius summary so containment can scale to the whole campaign instead of one inbox.
When to use it
Right after triage confirms a malicious email. Use it to size the incident, prioritize password resets, and decide whether a single report is actually a wide campaign.
How it works
- 1An analyst confirms a case, firing a webhook with the malicious sender and URL indicators.
- 2The flow queries Gmail across the tenant for all messages matching either indicator.
- 3A logic step deduplicates and aggregates the matches into a unique recipient list with timestamps.
- 4The recipient roster and indicator details are written to a Postgres incident record.
- 5If the recipient count crosses your threshold, the case is escalated in PagerDuty as a campaign-level incident.
- 6A formatted blast-radius report is posted to the incident response channel in Slack.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect GmailRead, draft, send, label.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 4Connect PagerDutyIncidents, on-call, escalations.
- 5Connect SlackChannels, DMs, threads, mentions.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More SecOps workflows
Scheduled AWS Access-Key Age Sweep and Forced Rotation
Runs daily to find IAM access keys older than your policy threshold, deactivates the stale key, issues a fresh pair, and notifies the key owner with their replacement instructions.
Correlate Datadog WAF anomaly alert with Cloudflare evidence
When Datadog fires a WAF block-rate anomaly monitor, it pulls the matching Cloudflare firewall events, builds an evidence pack of top rules and ASNs.
Exposed-Secret Incident Triage and Remediation Agent
An agent-driven workflow that investigates a reported leaked secret end to end, decides revoke-versus-escalate, executes the rotation.
Non-Rotatable Leaked Secret to PagerDuty Escalation
Catches secret-scan hits for credentials that cannot be auto-rotated, gathers blast-radius context, and pages the on-call engineer with a step-by-step manual rotation runbook.
GitHub Secret-Scan Hit to Auto-Revoke and Rotate
When GitHub secret scanning flags a leaked credential in a repo, it auto-classifies the secret type, revokes the live key at the provider, mints a replacement.
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.