SigmaTrust Docs · Security Model & Tenant Isolation
Security Model & Tenant Isolation
How the platform isolates tenants, protects secrets and records activity.
Tenant isolation by construction
Every data model carries an organisation scope enforced by a global data-access plugin — queries are tenant-filtered at the ORM layer, not per-endpoint. Cross-tenant isolation is verified by automated tests as part of the platform test suite, and a pre-commit safety check blocks code that would bypass the tenant layer with raw database access.
Secrets and credentials
Third-party integration credentials are stored encrypted at rest and decrypted only at the point of use. Platform access for the hosted Outlook add-in uses per-user tokens with explicit mailbox-access assertions — a public key cannot read another user’s mailbox.
Authentication options
Password sign-in with configurable policy, plus native passkey (WebAuthn) support for passwordless login. Sessions and privileged operations are recorded in audit logs.
Audit trail
Administrative and data-changing actions write to an append-oriented audit log, giving compliance teams the who/what/when their own auditors ask for.
Availability and recovery
Automated database backups run on schedule and restores are tested — recovery is a practised procedure, not an assumption.
FAQ
How is customer data separated between tenants?
Through organisation-scoped data access enforced globally at the ORM layer, verified by automated cross-tenant isolation tests — not by per-route filters that can be forgotten.
Can CyberSigma staff see our data?
Access follows role-based controls and is logged. Administrative access is restricted to operational need and recorded in the audit trail.