You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To address this issue at runtime use the following policies:
111
+
112
+
-[Key vaults should have deletion protection enabled](https://github.com/Azure/azure-policy/blob/master/built-in-policies/policyDefinitions/Key%20Vault/KeyVault_Recoverable_Audit.json)
To address this issue at runtime use the following policies:
110
+
111
+
-[Azure Key Vault should use RBAC permission model](https://github.com/Azure/azure-policy/blob/master/built-in-policies/policyDefinitions/Key%20Vault/AzureKeyVault_Should_Use_RBAC.json)
112
+
107
113
## NOTES
108
114
109
115
The RBAC permission model may not be suitable for all use cases.
@@ -112,11 +118,12 @@ For information about limitations see _Azure role-based access control vs. acces
-[SE:05 Identity and access management](https://learn.microsoft.com/azure/well-architected/security/identity-access)
116
122
-[What is Azure role-based access control?](https://learn.microsoft.com/azure/role-based-access-control/overview)
117
123
-[Provide access to Key Vault keys, certificates, and secrets with an Azure role-based access control](https://learn.microsoft.com/azure/key-vault/general/rbac-guide)
118
124
-[Azure role-based access control vs. access policies](https://learn.microsoft.com/azure/key-vault/general/rbac-access-policy)
119
125
-[Migrate from vault access policy to an Azure role-based access control permission model](https://learn.microsoft.com/azure/key-vault/general/rbac-migration)
-[Azure security baseline for Key Vault](https://learn.microsoft.com/security/benchmark/azure/baselines/key-vault-security-baseline)
121
128
-[IM-1: Use centralized identity and authentication system](https://learn.microsoft.com/security/benchmark/azure/baselines/key-vault-security-baseline#im-1-use-centralized-identity-and-authentication-system)
az keyvault update -n '<name>' -g '<resource_group>' --retention-days 90
98
+
```
99
+
100
+
### Configure with Azure Policy
101
+
102
+
To address this issue at runtime use the following policies:
103
+
104
+
-[Key vaults should have soft delete enabled](https://github.com/Azure/azure-policy/blob/master/built-in-policies/policyDefinitions/Key%20Vault/KeyVault_SoftDeleteMustBeEnabled_Audit.json)
"_EXPERIMENTAL_WARNING": "Symbolic name support in ARM is experimental, and should be enabled for testing purposes only. Do not enable this setting for any production usage, or you may be unexpectedly broken at any time!",
0 commit comments