> 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/ja/sekyuriti/enterprise-controlled-encryption.md).

# Enterprise Controlled Encryption

最大限のデータセキュリティのために、顧客管理の暗号化キーを有効にします

Enterprise Controlled Encryption (ECE) は、オーガナイゼーション' が独自の暗号鍵を管理できるようにすることで、最高レベルのデータセキュリティを提供します。ECE を有効にすると、データを復号できるのはオーガナイゼーション' のみで、Verkada はアクセスできません。

{% hint style="warning" %}
ECE には、Google Workspace、Microsoft Entra ID、または Okta を使用した OIDC ベースの SSO が必要です。SAML のみのプロバイダはサポートされていません。
{% endhint %}

***

## ECE の仕組み

ECE は、暗号鍵の生成と管理に IDプロバイダを使用します。有効にすると:

* 保存時のすべてのデータは、IDプロバイダから派生した鍵で暗号化されます
* IDプロバイダの認可がなければ、Verkada はデータを復号できません
* IDプロバイダにアクセスできなくなると、暗号化されたデータにもアクセスできなくなります

***

## セットアップと復旧

{% content-ref url="/pages/186f9f0f5721b7c49ceaad5244cb53fc2657f955" %}
[Enterprise Controlled Encryptionを有効にする](/command/ja/sekyuriti/enterprise-controlled-encryption/enable-enterprise-controlled-encryption.md)
{% endcontent-ref %}

{% content-ref url="/pages/bda116ceb86deb8337d292ee571593fb03b41b90" %}
[Enterprise Controlled Encryptionアカウントの復旧](/command/ja/sekyuriti/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/ja/sekyuriti/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.