SECOPS
Real-Time Risky Cloudflare WAF Change Auto-Block and Linear Ticket
Inspects each Cloudflare WAF change as it happens, and when a change matches risky patterns (rule disabled, action weakened, or scope broadened) it immediately re-applies…
How it runs
The automated pipeline, trigger to output.
- TriggerCloudflare WAF change audit webhookHTTP webhook
- LogicClassify change vs. prior value
- LogicBranch on risky patterns (disabled/weakened/broadened)
- ActionRe-apply prior safe value via CloudflareCloudflare
- OutputFile Linear ticket with reverted diff and risk reasonLinear
What it does
Acts as an automated guardrail that reverses dangerous WAF edits the moment they land. If a change disables a protective rule, downgrades a block to log, or widens an allow scope, the flow restores the previous safe state and opens a tracked ticket explaining what was undone.
When to use it
Use it for high-sensitivity zones where certain WAF weakenings should never go live unreviewed, even briefly. Unlike an approval gate that waits, this enforces an opinionated safe-default and reverts first, then asks questions via a ticket.
How it works
- 1A Cloudflare audit webhook fires on a WAF or ruleset change.
- 2The flow compares the new rule state to the prior value to classify the change.
- 3A branch evaluates risky patterns: rule disabled, action downgraded to log/allow, or expanded IP/path scope.
- 4Safe or neutral changes are logged and pass through untouched.
- 5For a risky change, it immediately re-applies the prior safe value via the Cloudflare API.
- 6It files a Linear ticket capturing the actor, the reverted diff, and the risk reason, and tags the security team for follow-up.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect HTTP webhookTrigger any URL on agent 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.