SECOPS
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.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionPull the week's Cloudflare firewall eventsCloudflare
- LogicAgent clusters and computes week-over-week trends
- ActionPublish tuning-review report to ConfluenceConfluence
- OutputPost Confluence link to SlackSlack
What it does
Weekly, an agent aggregates the period's WAF blocks by rule and ASN, computes week-over-week trends (which rules are getting noisier, which ASNs are emerging), and writes a structured tuning-review report. It publishes that report to Confluence as the team's running record and drops a short Slack note linking to it, so the security review meeting starts from evidence instead of anecdotes.
When to use it
Use it to run a disciplined weekly WAF tuning cadence. It gives reviewers a consistent, comparable artifact and a prioritized change backlog without anyone manually exporting analytics.
How it works
- 1A weekly scheduled trigger starts the run.
- 2Cloudflare returns the week's firewall events for the zones in scope.
- 3The agent clusters by rule and ASN and compares against the previous weeks' baselines for trend direction.
- 4It drafts a prioritized tuning backlog with evidence and trend callouts.
- 5The report is published to Confluence, then a Slack message links to the new page.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 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
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.
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.