SECOPS
Cluster Cloudflare WAF events and draft tuned rule exceptions for review
On a schedule, pulls recent Cloudflare firewall events, clusters them by managed-rule ID and signature.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionFetch last 24h of WAF firewall eventsCloudflare
- LogicCluster by rule ID, URI, and ASN; rank false-positive likelihood
- ActionDraft minimal skip-rule expressions and justificationsOpenAI
- OutputOpen GitHub PR with drafted exceptions for reviewGitHub
What it does
Periodically reviews Cloudflare's managed WAF firewall events, groups them into behavioral clusters (same rule, path, and client fingerprint), then drafts surgical rule exceptions for the noisiest false-positive clusters. The exceptions land as a reviewable GitHub pull request, never as a live change.
When to use it
When a Cloudflare managed ruleset is generating recurring false positives on legitimate traffic (an internal API, a webhook callback, an admin path) and you want a tuned exception drafted for you each morning rather than hand-querying the events API and writing Terraform by hand.
How it works
- 1A daily schedule fires the workflow.
- 2It queries the Cloudflare GraphQL firewall-events API for the last 24h of `block`/`challenge` actions.
- 3A logic step clusters events by rule ID + URI pattern + ASN and ranks clusters by volume and likely-benign score.
- 4For each high-volume, low-risk cluster, an OpenAI step drafts a minimal skip-rule expression and a plain-English justification.
- 5The drafts are committed to a branch and opened as a GitHub PR tagged for the secops reviewer.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 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.