Data Safety

Never trust.
Always verify.

No request is trusted by default. Every interaction is authenticated, every identity re-validated, every device tracked. Traditional platforms authenticate once at login — if an attacker intercepts your session, they inherit full access. Zero trust eliminates this by design.

Every request proves itself.

Traditional platforms authenticate once at login and assume trust for the remainder of the session. TABULARUM rejects this model entirely. Every API call, every agent interaction, every data request is independently verified against your identity, your device, and your session state. A stolen cookie grants nothing — because nothing is granted without proof.

15-Minute Token Expiry

Session tokens expire and rotate every 15 minutes. Each refresh invalidates the previous token — stolen tokens become useless almost immediately.

Continuous Re-Validation

Every request re-verifies your identity against the database. Account suspended mid-session? The next request is rejected instantly.

TOTP Two-Factor Auth

Optional 2FA via any standard authenticator app. Login requires email verification plus a rotating 6-digit code. Backup codes encrypted at rest.

Device Fingerprinting

Cryptographic device fingerprint on every request. If your session appears from a different device, browser, or network — it is flagged immediately.

Per-Identity Rate Limiting

Rate limits tied to sandbox identity, not IP address. One user, one limit — regardless of VPNs or IP rotation.

Agents verify each other.

Zero trust extends beyond user-facing requests. When agents communicate internally — Gaio asking Mila to calculate a waterfall, or Lucio sending Clara a meeting brief — the same principles apply. Trust is never assumed, even between components of the same system.

Agent-to-Agent Security
HMAC-signed inter-agent communication
When Gaio asks Mila to calculate a waterfall, or Lucio sends Clara a meeting brief, the inter-agent request is HMAC-signed with a timestamp. The receiving agent verifies the signature before accepting the task. If the signature is invalid, expired, or tampered with — the request is rejected. This prevents any external system from impersonating an agent or injecting fraudulent tasks into the coordination pipeline. Even internally, trust is never assumed.

Not a feature. A foundation.

Every component assumes it is under attack and proves otherwise before proceeding. From 15-minute token rotation to per-request device fingerprinting to the HMAC-signed agent bus — zero trust is not a feature added to TABULARUM. It is the foundation.

See the full security architecture.

Encryption Sandbox Isolation