SECOPS
Instant Cloudflare WAF change alert from audit-log webhook
Triggers the moment a Cloudflare audit-log webhook reports a WAF ruleset edit, pulls the new ruleset.
How it runs
The automated pipeline, trigger to output.
- TriggerCloudflare audit-log webhook receivedHTTP webhook
- LogicFilter for WAF ruleset write events
- ActionFetch current ruleset for affected zoneCloudflare
- ActionDiff against cached prior versionShell
- OutputPost actor + diff to Slack channelSlack
What it does
Instead of polling, this workflow reacts to Cloudflare's audit-log webhook. When the webhook signals a WAF ruleset was modified, it fetches the current ruleset, builds a before/after diff against the cached previous version, and pushes a concise alert into a Slack channel with the actor, timestamp, and exact rule changes.
When to use it
Use it for high-sensitivity zones where any WAF change must be seen by on-call immediately, not on the next scheduled scan. It shrinks detection time from minutes to seconds and names who made the edit.
How it works
- 1An HTTP webhook trigger receives the Cloudflare audit-log event.
- 2A logic step filters for WAF ruleset write events and drops unrelated audit entries.
- 3A Cloudflare action fetches the full current ruleset for the affected zone.
- 4A shell step diffs it against the cached prior version and renders a readable summary.
- 5A Slack output posts the actor, change time, and rule-level diff to the security channel.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 3Connect ShellRun sandboxed commands inside the workspace.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.