SECOPS
Cloudflare Firewall Rule Disable Approval Gate
Triggers when a Cloudflare WAF or firewall rule is disabled or deleted, posts the change to a Slack approval channel.
How it runs
The automated pipeline, trigger to output.
- TriggerReceive Cloudflare audit event via webhookHTTP webhook
- LogicKeep only firewall/WAF disable or delete actions
- ActionPost change to Slack with approve/flag buttonsSlack
- LogicWait for approval, timeout, or flag
- ActionOpen Linear ticket on timeout or flagLinear
- OutputReturn approved-or-escalated outcome
What it does
Catches one of the riskiest Cloudflare actions — disabling or deleting a WAF/firewall rule, which directly weakens your protection. When such a change lands it posts an interactive message to your secops Slack channel asking whether it was intentional. If an engineer approves, the run closes quietly. If nobody responds within the timeout window, it auto-escalates to a Linear ticket for investigation.
When to use it
Use this when firewall and WAF rules should only change with human awareness, and you want a lightweight in-the-loop confirmation rather than a hard alert on every legitimate tuning change.
How it works
- 1A webhook trigger receives Cloudflare audit events as they arrive.
- 2A filter keeps only firewall/WAF rule disable or delete actions.
- 3An action posts the change details to the secops Slack channel with approve/flag buttons.
- 4A logic step waits for a response: an approval ends the run, while a timeout or explicit flag advances it.
- 5On timeout or flag, the workflow opens a Linear ticket capturing the rule, actor, and the unanswered Slack thread link.
- 6The outcome (approved or escalated) is returned as output.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect LinearIssues, projects, cycles, triage.
- 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.