Tenant Isolation
How SentriScope enforces multi-tenant boundaries across data, access, integrations, and audit for SaaS customers.
Tenant Isolation
Executive Summary
SentriScope is a multi-tenant security intelligence platform. Each customer organization operates within a tenant boundary where security data, connector sessions, user access, and audit records are scoped to that tenant. Tenant isolation is an architectural foundation (implemented), not an optional configuration. This document explains the isolation model at a conceptual level without implementation or deployment detail.
Purpose
Help security evaluators, engineers, and procurement stakeholders understand how SentriScope separates customer environments and why isolation matters for SaaS security programs.
Problem Statement
Shared SaaS platforms must prevent one customer from accessing another customer's data, configuration, or operational context. Without clear tenant boundaries, connector credentials, vulnerability findings, investigations, and audit trails could leak across organizational lines—undermining trust and compliance.
Industry Context
Enterprise SaaS buyers expect logical isolation between tenants, role-governed access within each tenant, and evidence that isolation is enforced consistently across APIs, background jobs, and user interfaces. Regulatory and contractual obligations often require demonstrable separation of customer data.
SentriScope Perspective
SentriScope treats tenant isolation as mandatory (implemented). Every business record in the platform is associated with a tenant context. Analysts, connectors, intelligence correlation, and audit events operate within that scope.
Isolation applies across:
- Data plane — Canonical entities, findings, investigations, and intelligence records are tenant-scoped.
- Access plane — Users authenticate into a tenant context; cross-tenant access is not part of the product model.
- Integration plane — Connector sessions and credentials belong to a single tenant.
- Audit plane — Security-relevant actions are recorded with tenant attribution.
Enterprise deployment options may include dedicated database configurations; isolation principles remain the same regardless of hosting model.
Current Capabilities
| Capability | State | Summary |
|---|---|---|
| Tenant-scoped data model | Implemented | Business entities are created and queried within tenant context |
| Tenant-scoped connector sessions | Implemented | Ingestion credentials and sync state are per tenant |
| Tenant-scoped user membership | Implemented | Users belong to tenants through governed membership |
| Tenant-scoped audit logging | Implemented | Security-relevant actions record tenant context |
| Public host vs portal host separation | Implemented | Customer operations use separate host boundaries from the public marketing site |
Current Limitations
- This document does not describe physical infrastructure, encryption key management, or penetration-test results.
- Custom isolation attestations (for example customer-specific compliance reports) require separate engagement and are not self-service on the public website.
- Cross-tenant analytics for platform operators follow separate internal governance; customers do not browse other tenants.
- Isolation does not replace customer responsibility for identity hygiene, credential rotation, or endpoint security within their organization.
Frequently Asked Questions
Does every SentriScope customer share one database?
SentriScope supports shared and dedicated database deployment models for enterprise tenants. In all models, logical tenant isolation is enforced at the application layer.
Can a user belong to multiple tenants?
Users may hold membership in more than one tenant when invited, but each session operates in one active tenant context at a time. Switching tenants requires explicit context change—not silent cross-tenant browsing.
Is tenant isolation the same as role-based access control?
No. Isolation separates customers; RBAC governs what authorized users can do within a tenant. Both are required. See Role-Based Access Control.
Does tenant isolation guarantee compliance certifications?
Isolation is a technical control. Compliance outcomes depend on your program, contracts, and how you configure and operate the platform.