SECOPS
Real-Time Cloudflare WAF Change Alert via Audit Log Webhook
Receives Cloudflare audit-log change events as they happen, checks whether the edited WAF rule matches the GitHub baseline.
How it runs
The automated pipeline, trigger to output.
- TriggerCloudflare audit-log change webhook arrivesHTTP webhook
- LogicFilter to firewall and WAF rule events
- ActionFetch baseline rule definition from GitHubGitHub
- LogicCheck if change is approved in baseline
- OutputSend urgent unapproved-change alert to SlackSlack
What it does
Instead of waiting for a daily sweep, this catches WAF changes the moment they occur. A Cloudflare audit-log webhook delivers each firewall or WAF rule edit, the workflow confirms whether the change matches an approved baseline commit in GitHub, and unapproved edits trigger an instant Slack alert naming the actor and the rule.
When to use it
Use it for high-stakes zones where an unauthorized firewall change must be noticed in minutes, not hours. It is the early-warning companion to a scheduled drift audit and is especially useful during incident windows when operators are editing rules live.
How it works
- 1A webhook trigger receives a Cloudflare audit-log change event.
- 2A filter logic step keeps only firewall and WAF rule mutations, dropping unrelated audit entries.
- 3The GitHub step fetches the current baseline definition for the affected rule.
- 4A comparison logic step decides whether the live change is already reflected in the approved baseline.
- 5If the change is unapproved, Slack receives an urgent alert with the actor, timestamp, rule name, and before/after expression.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 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.