Skip to content
Enclessa
Get started

Glossary · Platform

Tenant isolation

All termsHow Enclessa secures data

Tenant isolation is the guarantee that no request made by one customer organisation can read or change any data belonging to another, enforced by the system rather than by convention.

Open betaThe platform is being built in the open, so parts of it are not there yet, behaviour changes between releases, and no availability figure is committed while it is in beta. What is still being built.

What Tenant isolation means

Isolation is the one property of a multi-tenant system that cannot be partially true. A platform with one leaking endpoint out of six hundred is not mostly isolated; it is not isolated, because an attacker only has to find the one. This makes it unusual among security properties: it can, in principle, be tested exhaustively.

Exhaustive testing means driving every operation the API offers, as one organisation, against objects belonging to another, and asserting that all of them refuse. Because the operation list can be generated from the API description rather than written by hand, the test cannot silently fall behind as endpoints are added — a new operation that nobody thought to probe shows up as a gap.

A detail that matters more than it appears to: the refusal should be a not-found rather than a forbidden. A forbidden response confirms that the object exists, which turns an access check into an existence oracle and lets an attacker enumerate another organisation’s identifiers without ever reading a row.

How Enclessa uses it

Enclessa asserts the organisation at one choke point and answers not-found for another organisation’s object. A probe suite generated from the OpenAPI document drives every operation across the boundary — 286 operations driven, 286 refused — and it runs in continuous integration, so a regression fails the build rather than reaching production. Files, audit records, metrics and log lines all carry the organisation they belong to.

Related terms

Multi-tenancyMulti-tenancy is an architecture in which one running installation of an application serves many independent customer organisations, each of which sees only its own data.Read the entryAudit logAn audit log is an append-only record of who did what, to which object, and when — kept separately from application logs so that it can be relied on as evidence rather than read as debugging output.Read the entryData residencyData residency is the requirement that data be stored and processed within a named geographic territory, usually a country or an economic area such as the European Union.Read the entryManaged channelA managed channel is a room whose contents the server can read, which is what allows server-side search, retention rules, audit trails and organisation-wide export to operate on it.Read the entrySCIMSCIM is an open standard, published as RFC 7643 and RFC 7644, that lets an identity provider create, update and deactivate user accounts in another application automatically over a REST API.Read the entry

Read further

The security page explains how Enclessa protects data and which certifications it does not hold. The trust centre covers the processing agreement, the subprocessors and the residency position. The FAQ answers the questions buyers ask most often.

Encrypted collaboration, hosted in Europe.

Create a workspace in a couple of minutes. It is yours at your-team.enclessa.app, hosted in the European Union, with encrypted direct messages from the first one you send.

Create your workspaceSee pricing

Open beta. Free plan, no payment card to start.