SECOPS
Cloudflare WAF Spike Clustering with Candidate Rule Draft
On a schedule, pulls recently blocked Cloudflare requests, clusters them by shared attributes to find the dominant attack signature.
How it runs
The automated pipeline, trigger to output.
- TriggerEvery 15 minutes
- ActionFetch blocked requests from CloudflareCloudflare
- LogicCluster events by shared fingerprint, rank by volume
- ActionDraft firewall expression + rationaleOpenAI
- OutputPost candidate rule to Slack for approvalSlack
- ActionDeploy approved rule in log-only modeCloudflare
What it does
It turns a noisy spike of blocked traffic into one reviewable decision. Every interval it reads Cloudflare's blocked-request log, groups events by shared fingerprint (path, user agent, ASN, JA3), and proposes a single firewall expression that would cover the dominant cluster — then waits for a human to approve.
When to use it
When your WAF logs are too high-volume to triage by hand and you want a steady drip of pre-written, evidence-backed rule candidates instead of writing every expression from scratch during an incident.
How it works
- 1A schedule fires every 15 minutes.
- 2Pull the blocked-request sample from Cloudflare for the window.
- 3Logic clusters events by shared attributes and ranks clusters by volume and source spread.
- 4If the top cluster clears a volume threshold, an LLM step drafts a Cloudflare firewall expression plus a plain-English rationale.
- 5Post the draft rule, match count, and false-positive risk to Slack with Approve / Discard buttons.
- 6On approval, deploy the rule to Cloudflare in log-only mode for safe observation.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect OpenAIModels, embeddings, files.
- 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.