SECOPS

Page on access bursts against a single Dropbox share link

Detects a sudden spike in Cloudflare requests against one public Dropbox link within a short window, expires the link.

CategorySecOps
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWindowed Axiom query over recent Cloudflare logs runsAxiom
  • ActionCompute per-link request counts vs rolling baselineCloudflareCloudflare
  • LogicFlag links exceeding the spike threshold
  • ActionSet flagged Dropbox link to expire immediatelyDropboxDropbox
  • ActionPage on-call via PagerDuty with rate and baselinePagerDutyPagerDuty
  • OutputFile GitLab issue for post-incident reviewGitLabGitLab

What it does

Watches request volume per Dropbox share link in Cloudflare logs. When a single link's hit rate spikes far above its baseline inside a short window — the signature of a scraper or a link forwarded to a wide audience — it expires the link and escalates to on-call.

When to use it

Use this for links that should see low, steady traffic from a known recipient. A burst means the URL has been shared beyond its intended audience or is being harvested. Pairs well with the inventory sync and geo-anomaly workflows for layered defense.

How it works

  1. 1A windowed Axiom query runs on a short cadence over recent Cloudflare logs.
  2. 2It computes per-link request counts and compares each to its rolling baseline.
  3. 3A logic step flags any link exceeding the spike threshold.
  4. 4Dropbox sets the flagged link to expire immediately, cutting off access.
  5. 5PagerDuty pages the on-call engineer with the link ID, rate, and baseline.
  6. 6A GitLab issue is filed to track the post-incident review.

Set it up

What you configure once, before turning it on.

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