SECOPS
Cloudflare Alert Webhook Triage and Block Agent
Receives a Cloudflare security-event webhook, enriches the source ASN with reputation and geo context, decides whether to block or watch.
How it runs
The automated pipeline, trigger to output.
- TriggerCloudflare security-event webhookHTTP webhook
- ActionEnrich ASN with recent log contextAxiom
- LogicAgent decides block, watch, or ignore
- ActionAdd ASN to Cloudflare block listCloudflare
- OutputPost decision summary to TeamsMicrosoft Teams
What it does
Instead of polling, this workflow reacts the instant Cloudflare emits a security event webhook. An agent enriches the firing ASN with reputation lookups and recent log context, weighs whether the signal is a real threat or noise, and either pushes the ASN into a Cloudflare block list or files it on a watchlist for monitoring. Every decision, with its reasoning, is posted to a Microsoft Teams channel so the team has an auditable trail.
When to use it
Use this when you already have Cloudflare alerting configured and want an intelligent first responder that triages each event rather than blindly blocking. The agent's judgment reduces the false-positive blocks that pure-threshold rules produce.
How it works
- 1A Cloudflare security-event webhook fires the workflow.
- 2The agent queries Axiom for recent traffic from the firing ASN to gauge scope.
- 3It reasons over volume, error ratio, and ASN type to choose block, watch, or ignore.
- 4On a block decision, Cloudflare adds the ASN to the managed block list.
- 5A summary of the decision and evidence is posted to Microsoft Teams.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect AxiomLog streams, queries, dashboards.
- 3Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 4Connect Microsoft TeamsChannels, chats, files.
- 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
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.