SECOPS
Cloudflare admin-action anomaly triage to Slack
Pulls new Cloudflare audit-log entries on a schedule, flags unusual admin actions (WAF rule deletions, API token creation, off-hours config changes).
How it runs
The automated pipeline, trigger to output.
- TriggerEvery 15 minutes (scheduled)
- ActionFetch new Cloudflare audit-log entries since last cursorCloudflare
- LogicScore actions by sensitivity and time-of-day
- LogicFilter out low-risk routine events
- OutputPost ranked anomaly queue to Slack security channelSlack
What it does
Every 15 minutes it reads the Cloudflare audit log, scores each admin action for risk, and pushes anything suspicious into a Slack triage thread with the actor, action, source IP, and a one-line reason it was flagged.
When to use it
Use it when your team manages Cloudflare zones for multiple properties and wants a lightweight, continuous check on who changed what — without anyone manually scrolling the audit UI. Ideal for catching WAF rule removals, new API tokens, DNS edits, or changes made outside business hours.
How it works
- 1A schedule fires every 15 minutes and records the last cursor it processed.
- 2The flow calls the Cloudflare audit-log API for entries since that cursor.
- 3A scoring step ranks each action by sensitivity (token/WAF/firewall changes weighted high) and time-of-day (off-hours boosted).
- 4A filter drops routine, low-score events so only genuine anomalies advance.
- 5Flagged actions are formatted into a compact review queue.
- 6The queue posts to a Slack security channel as a threaded message, one row per anomaly, ready for an analyst to ack or escalate.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect SlackChannels, DMs, threads, mentions.
- 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.