Security
Isolation
- Between Clients. Each Client is an independent space in identity, data, and network. An account from one Client cannot see or reach another Client's resources; attempts are logged and rejected without revealing that the resource exists.
- Between labs. Each lab has its own space with a quota, a restricted network, and permissions per owner and editors. A lab does not see another lab's notebooks, volumes, or services.
- What is not isolated. The pipeline platform shares the list of pipelines and their artifacts among labs of the same Client. That is why the user guide asks you not to put confidential data in pipeline names, parameters, or metrics.
Identity and access
- No open registration: every account starts from an invitation.
- Sign-in by link, password, or corporate SSO (OIDC or SAML), with roles assigned by the administrator or by IdP attributes.
- Administration sections are verified on every request, not only in the menu.
- InferNode keys are per member, can be rotated and revoked, and each use is logged with its request identifier.
Secrets
Provider credentials are stored in a dedicated secrets store. Studio never shows a saved secret; editing a credential lets you replace it, not read it. Agents and workflows use it by reference.
Data and retention
- A lab's data lives in its volumes and is deleted with it.
- Workflow runs, messages, and traces are kept even if the agent or the workflow is deleted, for auditing, for the period the Client agrees on.
- Conversations evaluated by InferNode's content guards are logged with their category.
Auditing
Administration actions (adding and removing members, role changes, credentials, changes to models and limits in InferNode) are recorded in an audit log that the operator can query.
How secrets reach the platform
No secret is written to the deployment repository or to the platform configuration: secrets live in the Client's secrets store and are synchronized to the cluster. Rotating a key or a certificate means changing it in the store; the platform picks it up at the next synchronization. If synchronization fails, the Secret not synced alert fires and the rotation stays pending until it is resolved.
What an auditor may ask for
| Common question | Where the answer is |
|---|---|
| Who signed in and when? | Identity audit log (sign-ins, additions, and removals). |
| Who changed a credential or a role? | Administration audit log. |
| Which model processed a piece of data and at what cost? | Workflow run trace and InferNode log by X-Request-Id. |
| What left the cluster? | Inventory of the installation's external destinations (Air-gapped installation). |
| How long is it kept? | Limits and quotas > Retention. |
Security updates
Platform images are scanned in every version; critical vulnerabilities are fixed in the next version or, if no fix is available, documented with their exception and mitigation.