PG-1206 Reworked intro to pg_tde #353
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Performance test results:
|
ImTheKai
reviewed
Nov 19, 2024
documentation/docs/faq.md
Outdated
|
|
||
| ## I use disk-level encryption. Why should I care about TDE? | ||
|
|
||
| Encrypting hard drive encrypts all data, system and application files that are there. However, disk encryption doesn’t protect your data after the boot-up of your system. During runtime, the files are decrypted with disk-encryption. |
There was a problem hiding this comment.
"Encrypting a hard drive..." or "Encrypting hard drives.." also "..encrypts all data, including system and..." (that is easier to read I think).
ImTheKai
approved these changes
Nov 19, 2024
nastena1606
commented
Nov 21, 2024
nastena1606
force-pushed
the
PG-1206-TDE-intro
branch
from
18a0ba8
to
443f0b1
Compare
|
|
||
| ## How does it work? | ||
|
|
||
| To encrypt the data, two types of keys are used: | ||
|
|
||
| * Database keys to encrypt user data. These are stored internally, near the data that they encrypt. | ||
| * Table encryption keys (TEK) to encrypt user data. These keys are stored internally, near the data that they encrypt. | ||
| * The principal key to encrypt database keys. It is kept separately from the database keys and is managed externally. |
There was a problem hiding this comment.
Suggested change
| * The principal key to encrypt database keys. It is kept separately from the database keys and is managed externally. | |
| * The principal key to encrypt table keys. It is kept separately from the table keys and is managed externally. |
|
|
||
| * For DBAs: | ||
|
|
||
| - Allows defining what to encrypt in the table and with what key | ||
| - Encryption on storage level is not a must to provide data safety. However, using TDE and storage-level encryption together adds another layer of data security | ||
| - Granular encryption of specific tablespaces and reducing the performance overhead that encryption brings |
There was a problem hiding this comment.
Suggested change
| - Granular encryption of specific tablespaces and reducing the performance overhead that encryption brings | |
| - Granular encryption of specific tables and reducing the performance overhead that encryption brings |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PG-1206
Description
Reworked the intro on the index page to make it more appealing.
Added a link to what's TDE.
Added some FAQ