Skip to content

Commit 45cd8e0

Browse files
authored
Merge pull request #89642 from b-juche/patch-9
Update "How are encryption keys managed" in azure-netapp-files-faqs.md
2 parents d6da4f0 + 043ef77 commit 45cd8e0

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

articles/azure-netapp-files/azure-netapp-files-faqs.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.workload: storage
1313
ms.tgt_pltfrm: na
1414
ms.devlang: na
1515
ms.topic: conceptual
16-
ms.date: 05/14/2019
16+
ms.date: 09/24/2019
1717
ms.author: b-juche
1818
---
1919
# FAQs About Azure NetApp Files
@@ -53,7 +53,9 @@ All Azure NetApp Files volumes are encrypted using the FIPS 140-2 standard. All
5353

5454
### How are encryption keys managed?
5555

56-
Key management for Azure NetApp Files is handled by the service. Currently, user-managed keys (Bring Your Own Keys) are not supported.
56+
Key management for Azure NetApp Files is handled by the service. A unique XTS-AES-256 data encryption key is generated for each volume. An encryption key hierarchy is used to encrypt and protect all volume keys. These encryption keys are never displayed or reported in an unencrypted format. Encryption keys are deleted immediately when a volume is deleted.
57+
58+
Currently, user-managed keys (Bring Your Own Keys) are not supported.
5759

5860
### Can I configure the NFS export policy rules to control access to the Azure NetApp Files service mount target?
5961

0 commit comments

Comments
 (0)