SECOPS
Confirmed Phishing Containment Actions
When an analyst confirms a phishing report is malicious, this workflow blocks the sender, pages on-call if the campaign is widespread.
How it runs
The automated pipeline, trigger to output.
- TriggerAnalyst confirms malicious via Slack actionHTTP webhook
- LogicBranch on recipient blast radius
- ActionBlock sender domain and URLsCloudflare
- ActionPage on-call for widespread campaignPagerDuty
- OutputAppend containment actions to audit casePostgres
What it does
Drives the response side once a verdict is in. On a confirmed-malicious decision it executes containment: submits the sender domain and URLs to the blocklist, notifies affected recipients, escalates to on-call when the blast radius is large, and logs every action taken.
When to use it
Use this after triage and enrichment, when you want consistent, fast containment instead of ad-hoc manual steps. Ideal for teams that need an auditable record of exactly what was blocked and when.
How it works
- 1A Slack approval interaction (analyst marks a case 'confirmed malicious') fires the trigger via webhook.
- 2A branch checks recipient count: campaigns above the threshold escalate, smaller ones proceed to standard containment.
- 3Containment actions submit the malicious domain and URLs to Cloudflare for blocking.
- 4For widespread campaigns an incident is opened in PagerDuty to page the on-call responder.
- 5The full set of actions and timestamps is appended to the audit case record in Postgres.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 4Connect PostgresAny Postgres URL — query, write, migrate.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More SecOps workflows
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.
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
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.
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.
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.