-
Notifications
You must be signed in to change notification settings - Fork 708
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.
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
base: release-8.5
Are you sure you want to change the base?
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -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 is where two or more independent layers of encryption are enabled to protect against compromises of any one layer of encryption. Using two layers of encryption mitigates threats that come with encrypting data. | ||||||
sunxiaoguang marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||
|
|
||||||
| - All persisted data is encrypted-at-rest using the tool of the cloud provider that your cluster is running in. | ||||||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. For better clarity and adherence to the style guide's preference for active voice (line 43), consider rephrasing this sentence. Using 'encrypted at rest' instead of 'encrypted-at-rest' would also improve consistency with other parts of the document (e.g., line 230).
Suggested change
References
|
||||||
|
|
||||||
| - With dual-layer encryption enabled, data is automatically encrypted at rest using CMEK or escrow keys. | ||||||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This sentence could be clearer about this being the second layer of encryption, building upon the cloud provider's encryption mentioned previously. The suggested phrasing makes this relationship explicit.
Suggested change
|
||||||
|
|
||||||
| - 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. | ||||||
|
|
||||||
| **Best practices:** | ||||||
|
|
||||||
| - Regularly rotate CMEK keys to enhance security and meet compliance standards. | ||||||
|
|
@@ -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). | ||||||
Uh oh!
There was an error while loading. Please reload this page.