API Key and Token Service  ·  View 10 of 22  ·  Act 4 · Data

Storage Zones

Grouped by what each store is authoritative for, and what losing it would actually cost.

Editable source SVG draw.io All views
Authoritative — losing it is losing the service Credential truth Credential record Spanner · RPO ≤ 5 s Scope vocabulary versioned, immutable Revocation truth Revocation log append-only · RPO 0 Tenant epoch bulk revocation cut Evidential — rebuildable from nothing, but not re-creatable Audit Audit hot tier BigQuery · 400 days Audit archive GCS · 7 years, locked Telemetry Verification events 30 days · sampled Usage counters Bigtable · lossy Derived — throw it away and it rebuilds itself Distribution artefacts Regional snapshot GCS · 60 s cadence Local projection in memory Shared projection Memorystore Never stored, anywhere, in any tier The credential secret shown once, then only its digest Digest pepper KMS/HSM only — never in a backup projected overlay tiered at 400 d Storage Zones — by what each store is authoritative for Data store Risk / gap Security / platform batch event / async A restore of every store on this page cannot revive one secret. That is a property of the digest scheme, not of access control. v 1.0 · owner Security Platform Architecture · date 2026-09

The three grades

  • Authoritative: losing it is losing the service. Credential records (RPO ≤ 5 s) and the revocation log (RPO 0, because an accepted revocation must never be undone by a restore).
  • Evidential: rebuildable from nothing, but not re-creatable. Audit and telemetry — a gap here is permanent even though nothing stops working.
  • Derived: throw it away and it rebuilds itself. Snapshots and projections carry no recovery objective at all.

The fourth box

  • The secret and the pepper are on the page specifically to say where they are not. A restore of every other store on this page cannot revive one credential.
  • That is a property of the digest scheme, not of an access-control list, which is why it survives an insider and a misconfigured backup alike.

Assumptions

  • Audit: 400 days hot, 7 years cold and immutable. Verification telemetry: 30 days. Both invented, both the kind of number a compliance review overturns first.