Home/Security
Trust & architecture
Brivas is one governed platform on an mTLS service mesh. Tenancy, audit, attestation, fraud and residency are structural properties of the stack, grounded in real platform ADRs — not a compliance page bolted on.
The pillars
Every tenant route carries X-Tenant-Id; numbers, calls, messages, CDRs and fraud signals are structurally scoped to the tenant. A cross-tenant read returns zero rows — no operator, no usage — verified by an automated pen test in CI.
Every mutation — a route change, a send decision, a fraud action, a wallet debit — is appended to a hash-chained audit log signed by Vault Transit. Tampering breaks the chain; evidence is exportable and retained seven years.
Money and usage writes carry an Idempotency-Key; a network retry double-counts nothing. Mediation also dedups on record_id, so outage replay is safe by construction.
Real ES256/X.509 PASSporT signing and verification at attestation level A/B/C, with a per-tenant policy for unsigned or failed-verification calls. Signing credentials never leave Vault (SS-05).
SIM-box, IRSF, Wangiri and CLI-spoof detection run on the same plane that carries traffic; high-impact actions require dual-control (a different approver), and every action is reversible and audited.
Tenant data is scoped to its region; recordings carry a retention class governed by SS-24 privacy, and access to a call recording is itself an audited, reason-bearing action (SS-42).
Auth model
Auth on every call is an SS-01 OIDC bearer token plus X-Tenant-Id on tenant routes; money/usage mutations add an Idempotency-Key (ADR-0039). Keys are minted from Vault (SS-05) and never leave it.
no operator, no usage — a cross-tenant read returns zero rows, verified by an automated pen test in CI