SECOPS

Block Dropbox links hit from Tor exits and hosting ASNs

Flags Cloudflare hits on public Dropbox links that originate from Tor exit nodes, anonymizing VPNs, or datacenter ASNs, revokes the link.

CategorySecOps
Enginesim
Difficultyintermediate
Triggerevent
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerCloudflare access log event receivedCloudflareCloudflare
  • ActionEnrich request with ASN and Tor/VPN classification in AxiomAxiom
  • LogicFlag Tor exit, VPN, or datacenter ASN sources
  • ActionRevoke public access on the flagged Dropbox linkDropboxDropbox
  • ActionAppend event to Axiom audit datasetAxiom
  • OutputOpen GitLab issue for analyst confirmationGitLabGitLab

What it does

Inspects the network source of every Cloudflare hit against a public Dropbox link. Legitimate recipients almost never browse from Tor exits, anonymizing VPNs, or hosting-provider ASNs — so requests from those sources are treated as exfiltration attempts. The matching link is revoked and the event is logged.

When to use it

Use this when your Dropbox shares are meant for residential or corporate users and any access from anonymizing infrastructure should be assumed hostile. It complements geo-based detection by catching attackers who hide their true country.

How it works

  1. 1A Cloudflare access log event triggers the run.
  2. 2Axiom enriches each request with ASN, network type, and Tor/VPN classification.
  3. 3A logic step flags hits sourced from Tor exits, anonymizing VPNs, or datacenter ASNs.
  4. 4Dropbox revokes public access on the flagged share link.
  5. 5The anonymized-source event is appended to an Axiom audit dataset.
  6. 6A GitLab issue is opened so an analyst can confirm and close the case.

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 DropboxFiles and folders.
  4. 4
    Connect GitLabRepos, MRs, pipelines, registry.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.