SECOPS
Archive WAF events to Snowflake and rebuild monthly rule baselines
Daily, exports Cloudflare firewall events to Snowflake for retention, then monthly recomputes per-rule false-positive baselines from the warehouse and posts the updated…
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionPull day's firewall eventsCloudflare
- ActionLoad events into Snowflake history tableSnowflake
- LogicOn month start, recompute per-rule baselines and thresholds
- ActionWrite refreshed baselines to Snowflake reference tableSnowflake
- OutputPost changed thresholds to SlackSlack
What it does
Keeps a durable, queryable history of Cloudflare WAF activity in Snowflake and uses it to keep tuning math honest. Each day it appends new firewall events; each month it recomputes per-rule baselines and benign-rate thresholds from the accumulated history and reports the changes.
When to use it
When short Cloudflare retention isn't enough for trend analysis and your spike-detection and tuning workflows need stable, history-derived baselines rather than a rolling few days. Also useful for audit and compliance retention of firewall decisions.
How it works
- 1A daily schedule triggers the export.
- 2It pulls the day's Cloudflare firewall events and loads them into a Snowflake events table.
- 3On the first run of each month, a logic step recomputes per-rule volume baselines and benign-rate thresholds from the full history.
- 4It writes the refreshed baselines back to a Snowflake reference table for other workflows to consume.
- 5A summary of changed thresholds is posted to the secops Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect SnowflakeWarehouses, queries, shares.
- 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
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.