Security and Encryption
This page summarises Ennote's security model in one place. Each section links to the detailed page. For the company-level overview, see ennote.io/security.
Encryption and keys
| Ennote built-in KMS (default) | Google Cloud KMS (customer-managed) | |
|---|---|---|
| Algorithm | Kyber post-quantum cryptography | Your symmetric key in Google Cloud KMS |
| Who manages keys | Ennote, including rotation and lifecycle | You, in your own GCP project |
| Setup | None | GCP connection + KMS setup |
With the built-in KMS, only cryptographic operations, not the keys themselves, are exposed to the application layer. With Google Cloud KMS, every encryption and decryption for your organization uses your key, and the key stays in your cloud environment. KMS options are available on the Business plan. Details: KMS overview.
Secrets are encrypted at rest and in transit, and every change creates a new version.
Sign-in and access control
- No Ennote passwords. You sign in with Google, Microsoft or GitHub, so your identity provider's MFA and policies apply. The CLI can use Personal Access Tokens that you can expire and revoke.
- Email-domain restriction. Organizations can allow sign-in only from approved email domains (organization security, Team and Business plans).
- Roles. Organizations have six roles (Admin, Editor, Viewer, Billing Admin, Auditor, Browser); shared workspaces have four roles (Admin, Editor, Viewer, Auditor).
- Private workspaces. Every user has a private workspace that only they can open, not even organization admins. No audit logs are recorded there.
Audit logs and alerts
Audit logs record activity in the organization and shared workspaces, with severity and date filters. Retention depends on your plan. Audit notifications send events to Slack or Telegram in real time.
One-time links
One-time links work once and are deleted after they are opened; they expire after the time you choose (5 minutes to 7 days). Links created with ennote share are zero-knowledge: the decryption key is in the URL fragment (#key_salt), which browsers and HTTP clients never send to the server, so Ennote stores only ciphertext it cannot decrypt.
Ennote CLI
From the CLI overview:
- Ephemeral X25519 key exchange combined with post-quantum CRYSTALS-Kyber (Kyber-1024) encapsulation.
- Secrets are decrypted only in memory; plaintext data encryption keys are wiped before functions exit. No
.envfile is written:ennote secret getinjects secrets into the child process. - Auth tokens live in the OS keyring (macOS Keychain, Windows Credential Manager, Linux Secret Service), never in plaintext config files.
- TLS 1.3 for all gRPC connections, with downgrade prevention.
- Releases ship with an SBOM and Sigstore Cosign signatures; no developer holds the signing keys.
Kubernetes agent
From agent architecture and security:
- Deployed with a bootstrap token that expires in 2 hours; the agent then generates its own Ed25519 keypair in memory.
- Outbound-only gRPC over HTTP/2 on port 443, with no listening ports and under 1 second sync.
- Runs as non-root, drops all Linux capabilities, read-only root filesystem.
- Namespace-scoped Role (not a ClusterRole), without
updateordeleteon workloads; it skips Kubernetes Secrets that Ennote did not create. - Helm and OCI releases are signed with Cosign.
FAQ
Is Ennote post-quantum secure?
Ennote's built-in KMS uses Kyber post-quantum cryptography, and the Ennote CLI combines X25519 with CRYSTALS-Kyber (Kyber-1024). Organizations on the Business plan can use their own Google Cloud KMS key instead.
Can I use my own encryption key?
Yes. On the Business plan you can connect Google Cloud and switch your organization's encryption to a key in your Google Cloud KMS. See Google Cloud KMS setup.
Can an organization admin read my private workspace?
No. Only the owner of a private workspace can open it, not even organization admins, and no audit logs are recorded for it.
Does Ennote store passwords for signing in?
No. Sign-in goes through Google, Microsoft or GitHub. For the CLI and CI/CD you can use Personal Access Tokens, which you can expire and revoke.
Need Help?
If you encounter any issues or have questions, don't hesitate to contact support. Our team is here to assist you with any challenges you might face.
GCP KMS
Encrypt your Ennote secrets with your own Google Cloud KMS key: grant the IAM roles, create a symmetric key ring and key, add it in Ennote and switch your organization's encryption to it.
Overview
The Ennote CLI fetches secrets and injects them into processes without writing plaintext .env files to disk. Install it on macOS, Linux or Windows (Homebrew, Scoop or shell script) and verify the signed release.