SECOPS
Page on unapproved Cloudflare WAF rule deletions
Diffs the latest Cloudflare WAF snapshot against an approved-baseline file in GitLab, and if a rule was deleted or weakened without a matching merged MR.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule: every 15 minutes
- ActionFetch current Cloudflare WAF rulesetsCloudflare
- ActionRead approved baseline + merged MRsGitLab
- ActionDiff and classify each rule changeShell
- LogicBranch: deletion/weakening without approval?
- OutputRaise PagerDuty incident with detailsPagerDuty
What it does
This workflow distinguishes approved WAF changes from rogue ones. It compares the current ruleset to the approved baseline committed in GitLab, then checks GitLab for a recently merged MR that accounts for the change. A deletion or action-downgrade with no matching approval is treated as unauthorized and pages on-call.
When to use it
Use it on production zones where loosening the WAF is a security event in its own right. It filters out the noise of legitimate, reviewed edits and only escalates genuinely unapproved or risky changes.
How it works
- 1A scheduled trigger fires (e.g. every 15 minutes).
- 2A Cloudflare action fetches the current WAF rulesets.
- 3A GitLab action reads the approved baseline file and recent merged MRs.
- 4A shell step diffs current vs baseline and classifies each change.
- 5A logic branch checks for deletions or weakened actions lacking an approval.
- 6A PagerDuty output raises an incident with the offending rule and actor.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 3Connect ShellRun sandboxed commands inside the workspace.
- 4Connect PagerDutyIncidents, on-call, escalations.
- 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.