SECOPS

Daily Cloudflare Bot-ASN Threat Digest

Each morning, aggregates the prior day's Cloudflare bot activity by ASN, ranks the top suspicious networks, writes a Confluence report.

CategorySecOps
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily at workday start
  • ActionAggregate 24h Cloudflare logs by ASNAxiom
  • LogicRank ASNs and flag net-new offenders
  • ActionPublish Confluence threat reportConfluenceConfluence
  • OutputPost digest to SlackSlack

What it does

This workflow produces a once-a-day situational report rather than real-time blocking. Every morning it rolls up the previous 24 hours of Cloudflare logs, ranks ASNs by suspicious-request volume and error patterns, and notes which networks were already quarantined versus which are trending up. It publishes a formatted Confluence page for the record and drops a short digest into Slack ahead of the security standup.

When to use it

Use this when you want a recurring, human-readable pulse on bot pressure across your edge without anyone running ad hoc queries. It is ideal for standups, weekly reviews, and giving leadership a trend line.

How it works

  1. 1A daily schedule fires at the start of the workday.
  2. 2Axiom aggregates the last 24 hours of Cloudflare logs grouped by ASN with volume and error metrics.
  3. 3A logic step ranks ASNs and flags net-new offenders versus known ones.
  4. 4A Confluence page is created with the ranked table and trend notes.
  5. 5A condensed digest with the top offenders is posted to Slack.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AxiomLog streams, queries, dashboards.
  2. 2
    Connect ConfluenceSpaces, pages, blueprints.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  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.