SECOPS
Investigate a WAF false-positive cluster and file a Linear tuning ticket
An agent-driven workflow that takes a flagged Cloudflare rule cluster, investigates it across the events API and web context, decides whether tuning is warranted.
How it runs
The automated pipeline, trigger to output.
- TriggerFlagged cluster ID received via webhookHTTP webhook
- ActionFetch full event detail for the clusterCloudflare
- ActionResearch ASNs, user agents, and paths for legitimacyExa
- LogicDecide tune, monitor, or dismiss from evidence
- OutputOpen Linear ticket with proposed exception and risk noteLinear
What it does
Runs an investigation agent over a single suspected false-positive WAF cluster. The agent pulls the cluster's events, researches the source ASNs and URL patterns for legitimacy, weighs attack risk, and decides whether to recommend a tuning change — filing a Linear ticket with a concrete proposed exception only when the evidence supports it.
When to use it
When a cluster needs judgment rather than a fixed rule — ambiguous sources, partial signatures, or paths that could be either a partner integration or a probe. Use it to offload the investigative legwork while keeping the decision auditable.
How it works
- 1A flagged cluster ID arrives via webhook from an upstream detector.
- 2The agent fetches the cluster's full firewall-event detail from Cloudflare.
- 3It researches the involved ASNs, user agents, and paths using web search to gauge legitimacy.
- 4A decision step weighs benign evidence against attack risk and chooses tune, monitor, or dismiss.
- 5If tuning is warranted, the agent drafts a scoped exception and acceptance criteria.
- 6It opens a Linear ticket with the findings, proposed rule, and risk note.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect ExaNeural search across the web.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Connect HTTP webhookTrigger any URL on agent actions.
- 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
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.