Supersecret security overview
SuperSecret is where the internal tools your people build with AI get an identity, approved connections, isolated execution, and an audit trail. This page is the architecture, at the level your review needs.
Identity and access
Authentication is delegated to your identity provider over OIDC or SAML 2.0. SuperSecret issues no passwords and stores no password hashes. Users and groups sync from your directory via SCIM 2.0, so every authorization decision is evaluated against the groups you already maintain. Deprovisioning a user in your directory removes their access here in the same operation.
Tenancy and data location
Each customer runs in a logically isolated tenant. Data is encrypted in transit with TLS 1.3 and at rest with AES-256. The primary region is in the EU, and customer data is not replicated outside it.
Model providers and what they receive
Apps reach model providers through a gateway rather than calling them directly. Only the prompt and the data an app explicitly passes ever leaves the tenant. Provider accounts are configured for zero retention, with no training on inputs. The gateway records the destination, token count and calling app for every request. It does not record the payload.
Connections and authorization
An app has no data or network access until a connection is approved. Connections are OAuth-scoped to a named system, granted per app rather than per user, and carry an owner and a stated purpose. The scopes are visible at approval time and at any point afterwards. Revoking a connection takes effect immediately and affects only the app it was granted to.
Secrets
Credentials are held in a managed secret store and injected into the runtime at execution. They are not written into application source, not stored in app configuration, and never included in a prompt sent to a model provider. Rotation happens in one place and applies to every app using that connection.
Execution and egress
Apps run in isolated containers with no ambient credentials. Outbound network access is denied by default and permitted only to the hosts an approved connection requires. An app cannot reach another app’s data, secrets or connections.
Inventory
Every app is registered at creation with an owner, the connections it holds, its data sources, creation and last-run timestamps, and usage counts. The registry is queryable and exportable through the API. There is no path for an app to exist outside it.
Audit logging
Logged events include authentication, app create, modify and delete, connection grant and revoke, secret access, app execution, and permission changes. Each record carries actor, timestamp, target and source IP. Logs are retained for twelve months and can be streamed to your SIEM.
Lifecycle
When a user is deprovisioned, the apps they own are reassigned to a named administrator rather than deleted or orphaned. Their own access ends at the same time. The apps keep running under the new owner.
Revocation
Any app, connection or user can be disabled immediately by an administrator, with no vendor involvement. Disabling an app halts execution and drops its connections.
Compliance
Our sub-processor list, data flow diagram and DPA are available on request. Ask for the security pack and we will send the current set rather than a summary.
Request the security pack