Security
Tenant isolation
How OSTaaS keeps every workspace's data, environments, and evidence separated from every other tenant.
OSTaaS is multi-tenant: many organizations share the platform, but no organization can see another's data. Isolation is enforced at the data layer, not just in the UI.
How isolation is enforced
- Per-query scoping. Every query that touches workspace data is filtered by the session's tenant (organization) id. A request authenticated for one workspace cannot read or write another's rows.
- Scoped tokens. Provider tokens and environment credentials are bound to the tenant that created them.
- Isolated environments. Sandbox and production environments are provisioned per tenant and never shared.
Cross-tenant access is explicit
The only way data crosses a tenant boundary is an explicit, audited cross-tenant grant. Grants are scoped, revocable, and recorded in both workspaces' audit logs.
What reviewers can verify
- Attempting to load another tenant's record returns not-found, never another tenant's data.
- Every cross-tenant grant appears in Audit logs.
- Your tenant id uniquely identifies your workspace in every support and audit context.
Related
Related documentation
- Audit logsRead the immutable record of who did what in your workspace, and how to export it for compliance.
- Cross-tenant collaborationGrant a person from another workspace scoped access to yours — safely and temporarily.
- Finding your tenant IDWhat the tenant (workspace) ID is and where to find it when support asks.