Skip to content

Add explanation to dual-layer encryption #22210

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
sunxiaoguang wants to merge 4 commits into
base: release-8.5
Choose a base branch
from
+13 −1
Open

Add explanation to dual-layer encryption #22210

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
805a462
Add explanation to dual-layer encryption
sunxiaoguang Dec 20, 2025
2ba2b73
Update tidb-cloud/security-concepts.md
sunxiaoguang Dec 20, 2025
33f6616
Update tidb-cloud/security-concepts.md
sunxiaoguang Dec 20, 2025
3f75ac5
Apply suggestions from code review
lilin90 Dec 22, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 13 additions & 1 deletion tidb-cloud/security-concepts.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -221,6 +221,18 @@ TiDB Cloud safeguards static data with advanced encryption capabilities, ensurin

- For TiDB Cloud Dedicated clusters without CMEK, TiDB Cloud uses escrow keys; {{{ .starter }}} and {{{ .essential }}} clusters rely exclusively on escrow keys.

**Dual-layer encryption**

- Dual-layer encryption protects data with two or more independent layers of encryption. This method provides enhanced security by protecting against the compromise of any single encryption layer.
Copy link
Collaborator

@qiancai qiancai Dec 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if we need to remove "or more" here as there are only two layers in the context of this doc


- The cloud provider where your cluster is running encrypts all persisted data at rest using its native tools.

- With dual-layer encryption enabled, TiDB Cloud adds a second layer of security by automatically encrypting data at rest using either CMEK or escrow keys.

- Dual-layer encryption is disabled by default for {{{ .starter }}} clusters and enabled by default for {{{ .essential }}} clusters.

- Dual-layer encryption is mandatory for TiDB Cloud Dedicated clusters.
Copy link
Member

@lilin90 lilin90 Dec 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nicole-yc PTAL

Copy link
Collaborator

@qiancai qiancai Dec 22, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This sentence is ambiguous and can be interpreted in two different ways:

  • Dual-layer encryption is enabled by default for TiDB Cloud Dedicated clusters, and users should not disable it.
  • Dual-layer encryption is enabled by default for TiDB Cloud Dedicated clusters, and users cannot disable it.


**Best practices:**

- Regularly rotate CMEK keys to enhance security and meet compliance standards.
Expand Down Expand Up @@ -255,4 +267,4 @@ Records detailed database operations, including executed SQL statements and user

- Use logs for compliance reporting and forensic analysis.

For more information, see [Console Audit Logging](/tidb-cloud/tidb-cloud-console-auditing.md) and [Database Audit Logging](/tidb-cloud/tidb-cloud-auditing.md).
For more information, see [Console Audit Logging](/tidb-cloud/tidb-cloud-console-auditing.md) and [Database Audit Logging](/tidb-cloud/tidb-cloud-auditing.md).