SECOPS

On-Demand WAF Rule Investigation with Linear Tracking

Triggered manually for a named WAF rule, this workflow builds a full investigation packet from Cloudflare and Sentry.

CategorySecOps
Enginepaperclip
Difficultyintermediate
Triggermanual
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerAnalyst manually triggers with a target rule ID
  • ActionPull rule's blocked requests from CloudflareCloudflareCloudflare
  • ActionQuery Sentry for errors on affected pathsSentrySentry
  • ActionSynthesize verdict and recommended rule changeOpenAI
  • ActionFile Linear issue with the investigation packetLinearLinear
  • OutputPost Linear link to Slack for the analystSlack

What it does

Lets an analyst kick off a deep investigation of one Cloudflare WAF rule on demand. The agent pulls the rule's recent blocks, breaks down source IPs and targeted paths, cross-references Sentry to see whether those paths served real users, then synthesizes findings into a recommendation and files a tracked Linear issue so the tuning work is owned and visible.

When to use it

Use it when someone reports a specific rule that's misbehaving and you want a thorough, documented investigation rather than a quick glance — for example during a postmortem or a customer escalation about being wrongly blocked.

How it works

  1. 1An analyst manually triggers the workflow with a target WAF rule ID.
  2. 2An action pulls the rule's recent blocked requests and metadata from Cloudflare.
  3. 3An action queries Sentry for errors and traffic on the affected paths.
  4. 4An agent step synthesizes the evidence into an attack-vs-false-positive call and a recommended rule change.
  5. 5An action files a Linear issue with the investigation packet and recommendation.
  6. 6An action posts a link to the Linear issue in Slack for the requesting analyst.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
  2. 2
    Connect SentryErrors, performance, releases.
  3. 3
    Connect LinearIssues, projects, cycles, triage.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  5. 5
    Connect OpenAIModels, embeddings, files.
  6. 6
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  7. 7
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  8. 8
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.