What is tenant data isolation?
Tenant data isolation keeps each customer's data separate in a multi-tenant system, where many customers share the same application and infrastructure. It can be enforced at the database, schema, row, or application layer. The goal is that one customer can never see or change another customer's data.
What the buyer is really asking
In a multi-tenant product, what buyers really worry about is another customer seeing their data. Describe how tenants are separated (separate databases, separate schemas, or row-level controls) and how you check that the separation holds.
Other ways buyers ask it
Every one of these wants the same answer:
- “How is our data separated from other customers' data?”
- “Is your platform multi-tenant?”
- “Describe logical separation between tenants.”
- “How do you prevent cross-tenant data access?”
Evidence to have ready
- An architecture description of the tenancy model
- Tests or code review practice that cover tenant scoping
- Penetration test findings on authorization, if you have them
How Tyrvar answers this
Tyrvar treats every wording above as one question. You write the answer once, attach the evidence, and revisit it when your setup changes. Each buyer gets that approved answer no matter how their questionnaire words it. If you have not answered it yet, Tyrvar flags the question for you and does not make something up. Try it on your own questionnaire.