SECOPS

Cloudflare Configuration-Change Webhook to Axiom Audit Trail

Receives Cloudflare audit-log change events via webhook, enriches each with actor and diff context.

CategorySecOps
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerCloudflare audit-log change webhook receivedHTTP webhook
  • LogicFilter to security-relevant resource types
  • ActionEnrich actor and before/after payload via Cloudflare APICloudflareCloudflare
  • LogicNormalize into flat audit schema
  • OutputShip structured event to AxiomAxiom

What it does

Turns raw Cloudflare configuration-change events into a clean, queryable audit stream in Axiom. Every WAF rule, firewall, or ruleset edit is captured with who changed it, what changed, and when, so security teams can investigate and set alerts.

When to use it

Use it when you need a durable, vendor-independent record of Cloudflare changes for compliance (SOC 2, ISO 27001) or incident forensics, beyond Cloudflare's own retention. Ideal as the ingestion backbone other audit workflows query.

How it works

  1. 1A Cloudflare audit-log webhook fires on any configuration change.
  2. 2The flow filters to security-relevant resource types (WAF, rulesets, firewall rules) and drops noise.
  3. 3It enriches the event by calling the Cloudflare API to resolve the actor, resource name, and the before/after rule payload.
  4. 4The record is normalized into a flat schema with stable field names.
  5. 5The normalized event is shipped to Axiom as a structured log line.
  6. 6A confirmation summary is returned to the webhook caller so the source system knows the event was captured.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
  2. 2
    Connect AxiomLog streams, queries, dashboards.
  3. 3
    Connect HTTP webhookTrigger any URL on agent actions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.