Glossary

Key Management

Encryption moves the problem rather than removing it: the data is safe only as long as the keys are. Key management is everything that happens to those keys from the moment they are created to the moment they are destroyed.

General definition

Key Management is the discipline of controlling cryptographic keys across their lifecycle so that encrypted data stays both confidential and available. NIST SP 800-57 is the usual reference; it describes the phases every key passes through and the decisions attached to each one:

  • Generation from a proper random source, at the right length and algorithm (AES-256 for data, ECDSA or Ed25519 for signatures, X25519 for key agreement)
  • Storage somewhere harder to breach than the data it protects: a hardware security module (HSM), a cloud key management service (KMS), the operating system keystore on a device, or an encrypted secrets store
  • Distribution and use so that only authorised services and people can call the key, with every use logged
  • Rotation on a schedule (the cryptoperiod) and immediately after suspected exposure, see key rotation
  • Revocation and destruction when a key is retired, including proof that it no longer exists where that is required

Two patterns dominate practical systems. Envelope encryption encrypts each piece of data with its own data key, then encrypts that data key with a master key (a key encryption key) held in the KMS or HSM. The bulk data never passes through the HSM, rotation only re-wraps the small data keys, and losing one data key exposes one object. Bring your own key (BYOK) and hold your own key (HYOK) let a customer generate the master key in their own KMS and grant a provider permission to use it, so revoking the grant makes the provider’s copy of the data unreadable. Audit logs on key use, separation of duties between the people who administer keys and the people who administer data, and tested backup of keys (losing them is a data-loss event, not a security event) complete the picture.

In a chat platform the key question is custody. With server-side encryption at rest, the operator or the customer holds the keys and the server can read messages, which is what enables archiving, search, moderation and export. With end-to-end encryption, keys are generated and kept on users’ devices; the server stores ciphertext it cannot open, and key backup, device changes and account recovery become the user’s problem. Regulated deployments usually combine server-side encryption with customer-held master keys, WORM storage for archives and a data residency choice, because supervision and retention obligations require readable records.

In the Ethora ecosystem

On a dedicated or self-hosted Ethora deployment the at-rest keys live in the environment you control: the server runs inside your own AWS, DigitalOcean or other cloud account or on-premise, so disk and database encryption use your cloud provider’s KMS or your own key store, and you decide who may administer them, how they rotate and where they reside. On the managed cloud Ethora operates the keys for the shared cluster. In both cases the platform’s own credentials are short-lived by design: chat sessions use short-lived JWT tokens and server integrations use app-level API tokens that an app owner can regenerate from the admin panel.

Ethora runs a compliance archive by default, which means server-side keys and readable records for retention, audit trail, Trust and Safety moderation and per-user erasure. Optional end-to-end encrypted rooms, switched on per app since release 2610, change the custody model for those rooms only: OMEMO 2 keys are generated and stored on the users’ devices, attachments are sealed client-side with a per-file key, and the server holds no key for message bodies. The envelope covers the body only, so sender, room and reply references stay readable for routing and push. Choosing between the two models per app is itself a key management decision.

Get started

Chat and AI built for regulated industries

Ethora gives you audit trails, retention controls, a Trust & Safety layer and dedicated deployments in your own cloud. Talk to our team.

Start Free
Free tier available Enterprise SLA No vendor lock-in