---
title: "Security and Encryption"
description: "How Ennote protects secrets: Kyber post-quantum encryption by default or your own Google Cloud KMS key, sign-in only through Google, Microsoft or GitHub, role-based access with audit logs, zero-knowledge one-time links, and a hardened CLI and Kubernetes agent."
canonical_url: "https://docs.ennote.io/docs/security"
---
# Security and Encryption

> How Ennote protects secrets: Kyber post-quantum encryption by default or your own Google Cloud KMS key, sign-in only through Google, Microsoft or GitHub, role-based access with audit logs, zero-knowledge one-time links, and a hardened CLI and Kubernetes agent.

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](https://ennote.io/security/).

## Encryption and keys

<table>
<thead>
  <tr>
    <th>
      
    </th>
    
    <th>
      Ennote built-in KMS (default)
    </th>
    
    <th>
      Google Cloud KMS (customer-managed)
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Algorithm
    </td>
    
    <td>
      Kyber post-quantum cryptography
    </td>
    
    <td>
      Your symmetric key in Google Cloud KMS
    </td>
  </tr>
  
  <tr>
    <td>
      Who manages keys
    </td>
    
    <td>
      Ennote, including rotation and lifecycle
    </td>
    
    <td>
      You, in your own GCP project
    </td>
  </tr>
  
  <tr>
    <td>
      Setup
    </td>
    
    <td>
      None
    </td>
    
    <td>
      <a href="https://docs.ennote.io/docs/integration/connections/gcp">
        GCP connection
      </a>
      
       + <a href="https://docs.ennote.io/docs/integration/kms/gcp">
        KMS setup
      </a>
    </td>
  </tr>
</tbody>
</table>

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](https://docs.ennote.io/docs/integration/kms/overview).

Secrets are encrypted at rest and in transit, and every change creates a new [version](https://docs.ennote.io/docs/secrets/versions).

## Sign-in and access control

- **No Ennote passwords.** You sign in with [Google](https://docs.ennote.io/docs/auth/google), [Microsoft](https://docs.ennote.io/docs/auth/microsoft) or [GitHub](https://docs.ennote.io/docs/auth/github), so your identity provider's MFA and policies apply. The CLI can use [Personal Access Tokens](https://docs.ennote.io/docs/auth/user-tokens) that you can expire and revoke.
- **Email-domain restriction.** Organizations can allow sign-in only from approved email domains ([organization security](https://docs.ennote.io/docs/organization/security), Team and Business plans).
- **Roles.** Organizations have six [roles](https://docs.ennote.io/docs/organization/permissions) (Admin, Editor, Viewer, Billing Admin, Auditor, Browser); shared workspaces have four [roles](https://docs.ennote.io/docs/workspaces/permissions) (Admin, Editor, Viewer, Auditor).
- **Private workspaces.** Every user has a [private workspace](https://docs.ennote.io/docs/workspaces/overview) that only they can open, not even organization admins. No audit logs are recorded there.

## Audit logs and alerts

[Audit logs](https://docs.ennote.io/docs/organization/audit/logs) record activity in the organization and shared workspaces, with severity and date filters. Retention depends on your plan. [Audit notifications](https://docs.ennote.io/docs/organization/audit/notifications) send events to [Slack](https://docs.ennote.io/docs/integration/notification/slack) or [Telegram](https://docs.ennote.io/docs/integration/notification/telegram) in real time.

## One-time links

[One-time links](https://docs.ennote.io/docs/secrets/onetime/version) 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`](https://docs.ennote.io/cli/commands/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](https://docs.ennote.io/cli/overview#architectural-cryptography):

- 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 `.env` file is written: [`ennote secret get`](https://docs.ennote.io/cli/commands/secret/get) injects 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](https://docs.ennote.io/docs/agents/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 `update` or `delete` on 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](https://docs.ennote.io/docs/integration/kms/gcp).

### 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>



</need-help>


## Sitemap

See the full [sitemap](https://docs.ennote.io/sitemap.md) for all pages.
