Security

You're handing over a Cloudflare token. Here is exactly what happens to it.

Written for the person who has to approve this internally. Every claim below is one the code supports.

No autonomous writes

The model proposes. A human approves. The server executes and verifies. Every function that can change Cloudflare is reachable only after approval — there is no path from a chat tool call to a write, so prompt injection through attacker-controlled data (request paths, user agents, rule names) cannot cause one. The full pipeline.

Workspace isolation

One database per customer. One encryption key per customer, itself protected by a key the customer database never holds — so a copy of your data decrypts nothing on its own. Every request runs inside its workspace, and the data layer fails closed: a request with no bound workspace gets an error, never somebody else's data.

Credentials

Connecting Cloudflare: the three permission tiers a new token can have — Core (required), Operate and Extended — with what each one allows
The three permission tiers

Access

Create a share link: scope, label, read-only access, and an expiry of 7 days
A read-only share link, expiring within 30 days

Transport

Backups

Nightly, encrypted, kept both on and off the server, integrity-checked. The job restores its own output before it reports success, so a backup that can't be restored fails loudly rather than sitting there looking fine. Restore has been tested end to end from the off-site copy alone.

Who else touches your data

Alert channels — email, Slack, Teams, SMS, PagerDuty, webhooks — go to providers you configure with your credentials.

What the model sees

Zone names, traffic analytics, attacker IPs, probed paths, rule definitions — whatever it needs to answer the question, scoped to the zone you're working in. The server injects the zone; a question cannot reach a zone outside your active context.

Reporting a vulnerability

Email [email protected] with reproduction steps. You'll get an acknowledgement, and a fix or mitigation plan, as fast as the severity warrants. Please don't open a public issue.

  1. 01You
  2. 02Your fleet
  3. 03Fit
Who should we write back to?

Takes about two minutes.