Skip to content

Commit fc95b55

Browse files
author
Frank Hu
authored
(AzureCXP) Updating SubHeader
Changing : Server-side encryption using service-managed keys in customer-controlled hardware to : Server-side encryption using customer-managed keys in customer-controlled hardware per git issue : https://github.com/MicrosoftDocs/azure-docs/issues/38978
1 parent a5f9878 commit fc95b55

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/security/fundamentals/encryption-atrest.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -174,7 +174,7 @@ To obtain a key for use in encrypting or decrypting data at rest the service ide
174174
- Customer has full responsibility for key lifecycle management
175175
- Additional Setup & configuration overhead
176176

177-
#### Server-side encryption using service-managed keys in customer-controlled hardware
177+
#### Server-side encryption using customer-managed keys in customer-controlled hardware
178178

179179
Some Azure services enable the Host Your Own Key (HYOK) key management model. This management mode is useful in scenarios where there is a need to encrypt the data at rest and manage the keys in a proprietary repository outside of Microsoft’s control. In this model, the service must retrieve the key from an external site. Performance and availability guarantees are impacted, and configuration is more complex. Additionally, since the service does have access to the DEK during the encryption and decryption operations the overall security guarantees of this model are similar to when the keys are customer-managed in Azure Key Vault. As a result, this model is not appropriate for most organizations unless they have specific key management requirements. Due to these limitations, most Azure Services do not support server-side encryption using server-managed keys in customer-controlled hardware.
180180

0 commit comments

Comments
 (0)