SECOPS
Daily Cloudflare WAF Drift Audit Against Git Baseline
Every morning, pulls the live Cloudflare firewall and WAF custom rules, diffs them against the approved baseline stored in GitHub.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires the audit
- ActionList live Cloudflare WAF and firewall rulesCloudflare
- ActionFetch approved baseline JSON from GitHubGitHub
- LogicDiff live rules against baseline
- LogicBranch on whether drift was detected
- OutputPost drift report or all-clear to SlackSlack
What it does
This workflow keeps your Cloudflare Web Application Firewall honest. Once a day it reads every active custom firewall and WAF rule across your configured zones, compares them line by line against the approved baseline checked into a GitHub repo, and reports any drift to Slack so on-call can react.
When to use it
Run this when your WAF rules are change-managed through Git but operators can still hot-edit them in the Cloudflare dashboard during incidents. It surfaces the gap between what was approved and what is actually live, before an unreviewed rule weakens your perimeter.
How it works
- 1A daily schedule fires the audit at a quiet hour.
- 2The Cloudflare step lists all custom firewall and WAF rules for each zone, capturing expression, action, and enabled state.
- 3The GitHub step fetches the committed baseline JSON for the same zones.
- 4A diff logic step computes rules that were added, removed, or modified versus baseline.
- 5A branch checks whether any drift exists.
- 6If drift is found, Slack receives a formatted report listing each delta with the rule name and what changed; a clean run posts a short all-clear.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 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.