SECOPS
Cloudflare WAF Drift Detection Against GitHub IaC with Auto-Revert PR
Compares live Cloudflare WAF rules against the version-controlled definition in GitHub on a schedule.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled drift check
- ActionFetch live WAF ruleset from CloudflareCloudflare
- ActionFetch committed WAF definition from GitHubGitHub
- LogicDiff live vs. source and branch on drift
- ActionOpen reconciliation/revert pull requestGitHub
- OutputAlert platform team in Slack with PR linkSlack
What it does
Detects when the live Cloudflare WAF configuration has drifted from the source of truth in your GitHub IaC repo. On a mismatch it generates a corrective revert pull request and notifies the team, keeping production aligned with reviewed code.
When to use it
Use it when WAF rules are managed as code (Terraform or JSON) but emergency hotfixes or console edits happen out of band. This catches unmanaged drift before it becomes permanent and forces every change back through code review.
How it works
- 1A scheduled run triggers a drift check.
- 2The flow pulls the live WAF ruleset from the Cloudflare API and the committed definition from the GitHub repo.
- 3It diffs the two and branches on whether meaningful drift exists.
- 4If no drift, the run records a clean check and exits.
- 5If drift is found, it opens a GitHub pull request that reconciles the repo or reverts the live change, with the diff in the PR body.
- 6A Slack alert links the PR and summarizes which rules drifted so a reviewer can decide which direction to reconcile.
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.