SECOPS
Auto-draft a WAF rule-tuning proposal in Linear with evidence
Daily, an agent analyzes Cloudflare WAF block clusters, separates likely false positives from real attacks.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule
- ActionPull 24h of Cloudflare WAF blocksCloudflare
- LogicAgent clusters and classifies FP vs attack
- LogicDraft tuning proposal with confidence
- OutputOpen Linear issue with proposal and evidenceLinear
What it does
Once a day an agent reviews the last 24 hours of Cloudflare WAF blocks clustered by rule and ASN, judges which clusters look like false positives (legitimate traffic caught by an overbroad rule) versus genuine attacks, and drafts a rule-tuning proposal. It files that proposal as a Linear issue: what to change, why, the evidence sample, and a confidence score — ready for a human to approve.
When to use it
Use it to keep WAF rules from drifting into either noise or laxity. It converts raw block telemetry into a reviewable engineering task instead of leaving tuning to whenever someone remembers.
How it works
- 1A daily scheduled trigger starts the run.
- 2Cloudflare returns the day's blocked events with rule, ASN, and request context.
- 3The agent clusters and classifies each group as false positive, attack, or ambiguous.
- 4It drafts a tuning recommendation per cluster with rationale and confidence.
- 5A Linear issue is created with the proposal, evidence, and suggested rule edits.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.