A Cross-Tenant Data Leak Can Cost You the Customer.

A customer may forgive a slow page, missing feature, or delayed support ticket. They should not have to accept another company's data in their workspace or their own data appearing elsewhere.

A cross-tenant leak breaks trust, triggers security review, and can put the renewal at risk. The customer may also tell peers, affecting future deals in that market.

IBM's Cost of a Data Breach Report 2025 put the global average breach cost at USD 4.4 million, a 9% decrease from the prior year driven by faster identification and containment. IBM's 2024 report found that customer personally identifiable information was involved in 46% of breaches, more than any other record type.

Governed workspaces may hold contracts, controls, findings, personal data, supplier records, and evidence covered by GDPR, DORA, or customer contracts. A cross-tenant leak can add churn and lost deals to the incident cost.

NIST defines least privilege as restricting users and processes to the minimum access needed for assigned tasks.

Every grant beyond that minimum adds attack surface. A broad role that lets one team see another's data creates unnecessary exposure. Least privilege limits how far one mistake or misconfiguration can spread. NIST SP 800-53 treats access control as a full control family, and NIST CSF 2.0 includes identity, authentication, authorization, and managed access in its protection work.

Tenant isolation depends on several controls. SSO and RBAC decide who enters. Workspace boundaries decide what they can see. Connector scoping decides which external systems are readable. Retrieval permissions decide what AI can use. Audit logs show what happened.

NIST SP 800-207 defines zero trust around accurate, least-privilege, per-request access decisions; the same idea applies to AI retrieval. A workspace answer should use only sources the requester can access, inside the active workspace, from connectors scoped to that workspace.

Tenant separation should not depend on one optional flag. Enforce it across storage, identity, authorization, connectors, retrieval, and logging.

A workspace should have no normal path to another tenant's data. The boundary also needs tests for malformed queries, incorrect roles, and AI requests that seek material outside the active workspace. Deny cross-tenant access by default and verify the controls continuously.

In Sorena SSOT, our Single Source of Truth, each workspace is a governed container. Documents, controls, and evidence are scoped by workspace and role, with the product designed to prevent access across workspace boundaries.

Audit logs record actions inside the workspace. Together with least-privilege access, they support review of who accessed governed material and when.

AI retrieval must enforce the same workspace and user permissions as the rest of the platform. The assistant should answer only from sources available to the requester inside the active workspace.

Apply access checks before retrieval and again before returning content, then log the request and the sources used. See bring your own model, keep control for the broader model-governance case.

Integrations need the same tenant boundary as stored data and AI retrieval. Scope each connector to the intended workspace, account, and permitted sources.

Sorena Integrations brings external data into a selected workspace under its access and logging controls. The connector should not create a path to another tenant's data.

Customers hand over sensitive material because they expect you to keep it separate, scoped, and accountable. One cross-tenant leak can break that trust. Build isolation and least privilege into the platform before adding features on top.