Security model

This page describes how we protect your data and your account: how requests are authenticated and authorized, how projects are kept apart, how secrets and stored data are handled, and what the audit log records. Read it before you decide what to put on Etorm. The things we do not do are listed together at the end, under Limits.

Authentication

Every request to the API is authenticated. The only things you can reach without a credential are the health probes and the version endpoint. A request with a missing, expired or revoked credential gets 401.

CredentialUsed byNotes
API tokenService accounts, scripts, CIBearer secret etorm.<cluster>.<name>.<secret>. Expires (90 days by default, 365 at most below platform level). Tied to the identity it was issued for: recreating a service account under the same name does not revive old tokens.
Personal tokenPeople using kubectlCreated by etorm login or the console for your own identity only. Same rights as you, nothing more. At most 20 per person. 30 days by default from the CLI, 365 at most.
Sign-in token (OIDC)The consoleOne-hour access token from the sign-in service, signed with ES256. The API checks signature, issuer, audience and expiry. No refresh tokens: the sign-in session renews silently.

Sign-in

Two-step verification

Each person can turn on two-step verification for themselves. It uses a six-digit code from an authenticator app (RFC 6238) and ten single-use recovery codes, which we store only as hashes. Once it is on, a correct password does not create a session until the code is accepted too, and each code works only once.

Turning it on or off ends your other sign-in sessions. Tokens that were already issued keep working until they expire. See Protect your account with two-step verification.

Getting credentials

People get credentials with Sign in and get kubectl access. Automation gets them with Automate with a service account. For anything that runs unattended, use a service account rather than a person's token.

Authorization

Everything is denied unless a role allows it.

The built-in roles are listed in the Reference. The guide Give a teammate access shows the ones you will use most.

Tenancy

A project is a logical cluster with its own hostname. Its objects, roles, bindings, tokens and audit log are separate from every other project's. A caller who is not a member gets 403 and an empty list, never another tenant's data.

Private networks are isolated by tunnel id, so two projects can use the same addresses without seeing each other. Object storage uses separate keys for each bucket, as described below.

Secrets

Encryption at rest

Audit log

Every successful change, and every refusal of an authenticated caller, is recorded in the project where it happened. An entry holds the time, principal, verb, resource, name and result, and for a refusal the message as well. The log leaves out reads, request contents and unauthenticated requests.

Owners can read the log of their projects. It keeps the most recent 5 000 changes and 1 000 refusals, and nothing older than 90 days. See Give a teammate access and Find out why something stays Pending.

Network isolation basics

There are no firewall or security group resources. What can be reached inside a VPC depends on what you attach to it.

Limits