SECOPS
Auto-Open a GitHub PR to Reconcile Cloudflare WAF Drift
When live Cloudflare WAF rules diverge from the baseline, this captures the live state and opens a GitHub pull request updating the baseline file.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled reconciliation run
- ActionExport normalized live Cloudflare WAF rulesetCloudflare
- ActionRead current baseline file from GitHubGitHub
- LogicDiff live state against baseline
- ActionCommit live snapshot to a new branchGitHub
- OutputOpen pull request summarizing the driftGitHub
What it does
This treats your live Cloudflare WAF configuration as the proposal and your Git baseline as the source of truth. On a schedule it exports the current ruleset, and if it differs from the committed baseline, it writes the live state to a branch and opens a GitHub pull request. Reviewers then merge to bless the change or close it to flag a rollback.
When to use it
Use it when you want every firewall change to converge back into version control through review rather than drift silently. It is ideal for GitOps-style teams who would rather adjudicate drift in a PR diff than chase it in a dashboard.
How it works
- 1A schedule starts the reconciliation run.
- 2Cloudflare returns the full live WAF and firewall ruleset, normalized to the baseline format.
- 3GitHub provides the current baseline file from the main branch.
- 4A diff logic step determines whether the live state differs from baseline.
- 5If it differs, a GitHub step commits the live snapshot to a new branch.
- 6The output step opens a pull request with a summary of every changed rule for human review.
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.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.