SECOPS
Force extra Cloudflare review when a GitLab MR touches edge config
Detects merge requests that modify Cloudflare WAF rules, page rules, or worker routes, auto-labels them for the edge-security pool.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab MR opened or updatedGitLab
- LogicDetect Cloudflare config file changes
- ActionSnapshot live Cloudflare ruleset baselineCloudflare
- ActionLabel, assign edge pool, attach snapshot noteGitLab
- OutputAlert edge-security Slack channelSlack
What it does
Changes to edge configuration (WAF rules, firewall expressions, worker routes) carry outsized blast radius. This workflow spots MRs touching Cloudflare config paths, routes them to the edge-security reviewer pool, and attaches a live config snapshot so reviewers see exactly what is changing.
When to use it
Use it when your infrastructure-as-code repo manages Cloudflare and you want any edge-affecting MR to get specialist eyes plus a before-snapshot, not just a normal review.
How it works
- 1A GitLab webhook fires on MR open or update.
- 2A logic step inspects the changed file paths for Cloudflare config (WAF, firewall, worker route files).
- 3If matched, an action pulls the current live Cloudflare ruleset via the Cloudflare API as a baseline snapshot.
- 4An action adds the `security::edge` label, assigns the edge-security pool, and attaches the snapshot as an MR note.
- 5A Slack message alerts the edge-security channel with the diff highlights.
- 6The MR stays blocked until the pool acknowledges.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 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.