> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/command/security/enterprise-controlled-encryption.md).

# Enterprise Controlled Encryption

Enable customer-managed encryption keys for maximum data security

Enterprise Controlled Encryption (ECE) provides the highest level of data security by allowing your organization to manage its own encryption keys. With ECE enabled, only your organization can decrypt your data—Verkada cannot access it.

{% hint style="warning" %}
ECE requires OIDC-based SSO with Google Workspace, Microsoft Entra ID, or Okta. SAML-only providers are not supported.
{% endhint %}

***

## How ECE works

ECE uses your identity provider to generate and manage encryption keys. When enabled:

* All data at rest is encrypted with keys derived from your IdP
* Verkada cannot decrypt your data without your IdP's authorization
* Losing access to your IdP means losing access to your encrypted data

***

## Setup and recovery

{% content-ref url="/pages/sqdqy4fJFDe0NUIV1iiG" %}
[Enable Enterprise Controlled Encryption](/command/security/enterprise-controlled-encryption/enable-enterprise-controlled-encryption.md)
{% endcontent-ref %}

{% content-ref url="/pages/umUW5ykuZAchQIipp6m7" %}
[Enterprise Controlled Encryption Account Recovery](/command/security/enterprise-controlled-encryption/ece-account-recovery.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.verkada.com/command/security/enterprise-controlled-encryption.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.