HypothesisVery high confidenceCurrent
Tenant isolation must be enforced independently at identity resolution, authorization, data access, caching, search and action execution.
Every tenant-bound resource and derived artifact needs explicit tenant scope.
Valid from2026-08-23
Last reviewed2026-08-23
Review again2026-11-21
Dataheart stanceexploring
Evidence for
Zero Trust requires per-resource policy enforcement.
NIST SP 800-207 — Zero Trust Architecture · nist.gov ↗PostgreSQL 18 — Row Security Policies · postgresql.org ↗Microsoft Fabric — OneLake table, column and row-level security · learn.microsoft.com ↗RLS and workspace controls have documented privileged bypass paths.
NIST SP 800-207 — Zero Trust Architecture · nist.gov ↗PostgreSQL 18 — Row Security Policies · postgresql.org ↗Microsoft Fabric — OneLake table, column and row-level security · learn.microsoft.com ↗Evidence against
Per-tenant physical deployments can reduce the number of logical enforcement layers required, but still retain operational and administrative cross-tenant risks.
NIST SP 800-207 — Zero Trust Architecture · nist.gov ↗PostgreSQL 18 — Row Security Policies · postgresql.org ↗Microsoft Fabric — OneLake table, column and row-level security · learn.microsoft.com ↗How this claim can fall
Replace this placeholder during human review with an observable result that would materially weaken or falsify the claim.
A published claim remains useful only while it remains possible to prove it wrong.