SECOPS
Page On-Call When a Critical Cloudflare WAF Rule Is Disabled
Hourly, checks whether any rule on the protected-critical list in the GitHub baseline has been disabled or deleted in live Cloudflare.
How it runs
The automated pipeline, trigger to output.
- TriggerHourly schedule starts the check
- ActionRead critical-rule list from GitHub baselineGitHub
- ActionFetch live state of critical Cloudflare rulesCloudflare
- LogicDetect any disabled or deleted critical rule
- LogicBranch only when a critical rule lapsed
- OutputPage on-call via PagerDutyPagerDuty
What it does
This is a focused tripwire for your most important defenses. The GitHub baseline tags certain WAF rules as critical, such as the block rule for a known exploit or a rate-limit on login. Every hour the workflow verifies those specific rules are still present and enabled in live Cloudflare, and if any is disabled or removed, it pages on-call immediately.
When to use it
Use it when a small set of WAF rules are load-bearing for security and their accidental disablement during a maintenance window would be a serious incident. Unlike a full drift report, this only fires on the failures that truly warrant a 3 a.m. page.
How it works
- 1An hourly schedule starts the check.
- 2The GitHub step reads the baseline and extracts the rules flagged as critical.
- 3Cloudflare returns the live state of those specific rules.
- 4A logic step identifies any critical rule that is now missing or disabled.
- 5A branch fires only when at least one critical rule has lapsed.
- 6PagerDuty receives an incident naming each compromised rule and its zone.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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.