SECOPS
Open Linear Tickets for Each Cloudflare WAF Drift Item
Audits live Cloudflare WAF rules against the GitHub baseline and opens a deduplicated Linear issue for every drifted rule, tagged by severity.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled audit run
- ActionPull live Cloudflare WAF rulesCloudflare
- ActionRead approved baseline from GitHubGitHub
- LogicDiff and score each drift item by severity
- ActionLook up existing Linear issue per ruleLinear
- OutputCreate or update Linear remediation ticketLinear
What it does
This turns WAF drift into actionable work. It compares the live Cloudflare ruleset to the approved baseline in GitHub, and for each rule that was added, removed, or modified without review, it creates a Linear issue describing the exact delta. Existing open tickets for the same rule are updated instead of duplicated.
When to use it
Use it when you want drift handled through your normal engineering queue rather than a noisy chat ping. Each finding gets an owner, a severity label, and a paper trail, which is ideal for teams under SOC 2 or PCI change-control obligations.
How it works
- 1A schedule triggers the audit run.
- 2Cloudflare returns all active firewall and WAF custom rules per zone.
- 3GitHub provides the committed baseline for comparison.
- 4A diff step produces a list of drift items, each scored by how risky the change is (a disabled block rule ranks higher than a renamed allow rule).
- 5For each drift item, a Linear lookup checks for an existing open issue keyed on the rule ID.
- 6The Linear output creates a new issue or appends a comment to the existing one, applying the computed severity label.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 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
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.
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
Exposed-Secret Incident Triage and Remediation Agent
An agent-driven workflow that investigates a reported leaked secret end to end, decides revoke-versus-escalate, executes the rotation.
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.
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.