SECOPS

Weekly Dropbox link exposure digest from Cloudflare logs

Once a week, summarizes which public Dropbox links saw access from new geos or anonymized sources, quantifies the riskiest links.

CategorySecOps
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly digest schedule fires
  • ActionAggregate week of Cloudflare logs joined to Dropbox inventory in AxiomAxiom
  • LogicScore each link on new geos, anonymized sources, and volume
  • ActionOpen GitLab issue for any link above review thresholdGitLabGitLab
  • OutputPost ranked exposure digest to SlackSlack

What it does

Produces a weekly rollup of how your public Dropbox links were accessed. It aggregates a week of Cloudflare logs from Axiom, ranks links by exposure risk — new geographies, anonymized sources, access volume — and surfaces the ones that warrant a closer look before they become incidents.

When to use it

Use this as a recurring hygiene review rather than a real-time tripwire. It gives owners a regular, low-noise view of which shared links are drifting toward risky access patterns so they can clean up stale or over-shared links proactively.

How it works

  1. 1A weekly schedule fires the digest run.
  2. 2Axiom aggregates the week's Cloudflare access logs joined to the Dropbox link inventory.
  3. 3A logic step scores each link on new geos, anonymized sources, and volume.
  4. 4For any link above the review threshold, a GitLab issue is opened for triage.
  5. 5A ranked digest of the top exposed links is posted to Slack for the team.

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 GitLabRepos, MRs, pipelines, registry.
  5. 5
    Connect SlackChannels, DMs, threads, mentions.
  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.