Skip to content

Commit be71c6a

Browse files
committed
removing the general recommendation that would need to be expanded to make sense in the context of key vault
1 parent 1c601be commit be71c6a

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

articles/key-vault/security-recommendations.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: barclayn
66
manager: rkarlin
77
ms.service: key-vault
88
ms.topic: article
9-
ms.date: 09/18/2019
9+
ms.date: 09/19/2019
1010
ms.author: barclayn
1111
ms.custom: security-recommendations
1212

@@ -25,7 +25,6 @@ Some of the recommendations included in this article can be automatically monito
2525

2626
| Category | Recommendation | Comments | Security Center |
2727
|-|-|----|--|
28-
| General | Stay up-to-date | Use the latest versions of supported platforms, programming languages, protocols, and frameworks. | - |
2928
| Data protection |Enable soft delete | [Soft delete](key-vault-ovw-soft-delete.md) allows you to recover deleted vaults and vault objects | - |
3029
| Data protection | Limit access to vault data | Follow the principle of least privilege and limit which members of your organization have access to vault data | - |
3130
| Identity and access management | Limit the number of users with contributor access | If a user has Contributor permissions to a key vault management plane, the user can grant themselves access to the data plane by setting a Key Vault access policy. You should tightly control who has Contributor role access to your key vaults. Ensure that only those with a need for access authorized persons can access and manage your vaults. You can read [Secure access to a key vault](key-vault-secure-your-key-vault.md) | - |

0 commit comments

Comments
 (0)