> 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/es/seguridad/enterprise-controlled-encryption.md).

# Cifrado controlado por la empresa

Habilita claves de cifrado administradas por el cliente para máxima seguridad de los datos

El cifrado controlado por la empresa (ECE) proporciona el nivel más alto de seguridad de los datos al permitir que su organización gestione sus propias claves de cifrado. Con ECE habilitado, solo su organización puede descifrar sus datos—Verkada no puede acceder a ellos.

{% hint style="warning" %}
ECE requiere SSO basado en OIDC con Google Workspace, Microsoft Entra ID u Okta. Los proveedores solo con SAML no son compatibles.
{% endhint %}

***

## Cómo funciona ECE

ECE utiliza su proveedor de identidades para generar y gestionar las claves de cifrado. Cuando está habilitado:

* Todos los datos en reposo se cifran con claves derivadas de su proveedor de identidades
* Verkada no puede descifrar sus datos sin la autorización de su proveedor de identidades
* Perder el acceso a su proveedor de identidades significa perder el acceso a sus datos cifrados

***

## Configuración y recuperación

{% content-ref url="/pages/faea7cf0fe50442a7814a6a871cfbc3371dfbb95" %}
[Habilitar el cifrado controlado por la empresa](/command/es/seguridad/enterprise-controlled-encryption/enable-enterprise-controlled-encryption.md)
{% endcontent-ref %}

{% content-ref url="/pages/fb5dce4cfb3ec0d96bee9b48d44cada18bc2f876" %}
[Recuperación de cuenta de cifrado controlado por la empresa](/command/es/seguridad/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/es/seguridad/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.