SECOPS
Phishing Campaign Clustering and Escalation
Groups recent phishing reports by shared sender, domain, or URL pattern, and when a coordinated campaign crosses a report threshold it raises a PagerDuty incident and alerts…
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled campaign scan
- ActionCluster reports by shared indicators
- ActionEnrich top clusters via reputation APIHTTP webhook
- LogicCheck clusters against campaign threshold
- ActionOpen PagerDuty incident for active campaignPagerDuty
- OutputPost campaign breakdown to SOC channelSlack
What it does
Detects when many individual phishing reports are actually one coordinated campaign. It clusters recent reports by common indicators and, when a cluster grows large enough to signal an active attack, escalates to PagerDuty so the on-call responder engages immediately.
When to use it
Use this when single-report triage isn't enough and you need to catch volume-based attacks — a credential-harvesting wave hitting dozens of employees at once. It turns scattered tickets into one actionable incident with severity.
How it works
- 1A scheduled trigger fires and loads phishing reports from the recent window.
- 2A clustering step groups reports sharing a sender domain, URL host, or subject fingerprint.
- 3The largest clusters are enriched against a reputation API over HTTP to confirm maliciousness.
- 4A logic step checks each confirmed cluster against the campaign threshold (e.g. 5+ reports).
- 5For clusters over threshold, a PagerDuty incident is opened with affected-recipient counts and IOCs.
- 6A campaign alert with the cluster breakdown is posted to the SOC Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More SecOps workflows
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
Page on-call when a WAF rule mass-blocks legitimate traffic
On demand or every few minutes, it detects a single Cloudflare WAF rule suddenly blocking a broad spread of ASNs and paths (a likely false-positive storm).
PII Content Scan on New Dropbox External Share
When a file gets an external Dropbox link, it reads the file content, uses an AI classifier to detect PII or secrets.
Compile a weekly WAF tuning review with trends to Confluence
Every week an agent rolls up Cloudflare WAF block clusters by rule and ASN, compares them to prior weeks for trend direction.
Sensitive Dropbox Link Owner Remediation Loop
When a newly created Dropbox shared link points to a sensitive file, this workflow DMs the file owner, gives them a deadline to justify or revoke it.
GitLab Push Secret Detection to Block and History Purge
On a GitLab push that contains a detected secret, it revokes the exposed credential, opens a tracking issue with git-history purge instructions.
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.