Skip to content

Commit 069d0e2

Browse files
committed
update
1 parent b5e6af7 commit 069d0e2

2 files changed

Lines changed: 1 addition & 1 deletion

File tree

learn-pr/wwl-data-ai/implement-data-security-compliance/includes/2-design-implement-data-encryption.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ Always Encrypted takes a different approach by keeping encryption keys outside t
1818

1919
Always Encrypted protects sensitive data by ensuring the database engine never processes plaintext values. Client applications hold the encryption keys and perform all encryption and decryption operations. This separation means that even users with administrative access to the database can't view the protected data.
2020

21-
:::image type="content" source="../media/ae-data-flow.png" alt-text="Diagram showing the data flow for Always Encrypted, where client applications encrypt and decrypt data while the database engine only processes ciphertext.":::
21+
:::image type="content" source="../media/sql-data-flow.png" alt-text="Diagram showing the data flow for Always Encrypted, where client applications encrypt and decrypt data while the database engine only processes ciphertext.":::
2222

2323
To implement Always Encrypted, you first create a column master key (CMK) that protects the column encryption keys. Store the CMK in a secure key store such as Azure Key Vault, Windows Certificate Store, or a hardware security module.
2424

learn-pr/wwl-data-ai/implement-data-security-compliance/media/ae-data-flow.png renamed to learn-pr/wwl-data-ai/implement-data-security-compliance/media/sql-data-flow.png

File renamed without changes.

0 commit comments

Comments
 (0)