Skip to content

Commit 198bed1

Browse files
authored
Update customer-managed keys section in documentation
Added information about customer-managed keys storage and compliance.
1 parent d03b171 commit 198bed1

1 file changed

Lines changed: 3 additions & 1 deletion

File tree

learn-pr/wwl-azure/configure-storage-security/includes/6-create-customer-managed-keys.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,8 @@ Consider the following characteristics of customer-managed keys.
1212

1313
- Customer-managed keys can be used with Azure Storage encryption. You can use a new key or an existing key vault and key. The Azure storage account and the key vault must be in the same region, but they can be in different subscriptions.
1414

15+
- Customer-managed keys are stored in a customer-owned Azure Key Vault or Azure Key Vault Managed HSM. Managed HSM provides FIPS 140-2 Level 3 validation for organizations with the highest compliance requirements.
16+
1517
## Configure customer-managed keys
1618

1719
In the Azure portal, you can configure customer-managed encryption keys. You can create your own keys, or you can have the keys managed by Microsoft. Consider how you might use Azure Key Vault to create your own customer-managed encryption keys.
@@ -24,4 +26,4 @@ In the Azure portal, you can configure customer-managed encryption keys. You can
2426

2527

2628
> [!TIP]
27-
> Expand your understanding of storage security in the [*Plan and implement security for storage*](/training/modules/security-storage/) training module.
29+
> Expand your understanding of storage security in the [*Plan and implement security for storage*](/training/modules/security-storage/) training module.

0 commit comments

Comments
 (0)