SECOPS
Confirm and Block Live Phishing Clones via Cloudflare
Takes a candidate lookalike domain, fetches the live page to confirm it clones your brand, and if confirmed adds the host to a Cloudflare blocklist while alerting the team.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook receives a candidate domainHTTP webhook
- ActionBrave Search pulls cached page contextBrave Search
- ActionLoad live page and capture contentBrowserbase
- LogicConfirm clone vs. inconclusive against brand fingerprint
- ActionAdd confirmed host to Cloudflare blocklistCloudflare
- OutputSend verdict and block status to SlackSlack
What it does
Given a suspicious domain, this workflow verifies whether it is actually serving a phishing clone of your site — not just a parked or unrelated page — then pushes confirmed hosts into a Cloudflare blocklist and notifies secops, so blocking happens within minutes of confirmation.
When to use it
Run it when an analyst or upstream sweep surfaces a candidate and you need a fast confirm-then-block loop. Best for teams that front their own properties with Cloudflare and want to cut user exposure before formal takedown completes.
How it works
- 1A webhook trigger receives a candidate domain from an analyst or another workflow.
- 2A Brave Search action pulls cached snippets and indexed pages for that host to gather context.
- 3A browser action loads the live page and captures its rendered content and assets.
- 4A logic step compares logos, copy, and form fields against your real brand fingerprint to decide confirmed vs. inconclusive.
- 5If confirmed, a Cloudflare action adds the host to a managed blocklist or WAF rule.
- 6The output sends a Slack alert with the verdict, screenshot reference, and block status.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect Brave SearchWeb, news, image, video search.
- 3Connect BrowserbaseHeadless browsers, sessions, replays.
- 4Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 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.