| Source | Azure Portal | ||||||||||||||||||||||
| Display name | [Preview]: Azure Key Vault Managed HSM keys should have an expiration date | ||||||||||||||||||||||
| Id | 1d478a74-21ba-4b9f-9d8f-8e6fced0eec5 | ||||||||||||||||||||||
| Version | 1.0.1-preview Details on versioning |
||||||||||||||||||||||
| Versioning |
Versions supported for Versioning: 1 1.0.1-preview Built-in Versioning [Preview] |
||||||||||||||||||||||
| Category | Key Vault Microsoft Learn |
||||||||||||||||||||||
| Description | To use this policy in preview, you must first follow these instructions at https://aka.ms/mhsmgovernance. Cryptographic keys should have a defined expiration date and not be permanent. Keys that are valid forever provide a potential attacker with more time to compromise the key. It is a recommended security practice to set expiration dates on cryptographic keys. | ||||||||||||||||||||||
| Cloud environments | AzureCloud = true AzureUSGovernment = unknown AzureChinaCloud = unknown |
||||||||||||||||||||||
| Available in AzUSGov | Unknown, no evidence if Policy definition is/not available in AzureUSGovernment | ||||||||||||||||||||||
| Mode | Microsoft.ManagedHSM.Data | ||||||||||||||||||||||
| Type | BuiltIn | ||||||||||||||||||||||
| Preview | True | ||||||||||||||||||||||
| Deprecated | False | ||||||||||||||||||||||
| Effect | Default Audit Allowed Audit, Deny, Disabled |
||||||||||||||||||||||
| RBAC role(s) | none | ||||||||||||||||||||||
| Rule aliases | none | ||||||||||||||||||||||
| Rule resource types | none | ||||||||||||||||||||||
| Compliance |
The following 1 compliance controls are associated with this Policy definition '[Preview]: Azure Key Vault Managed HSM keys should have an expiration date' (1d478a74-21ba-4b9f-9d8f-8e6fced0eec5)
| ||||||||||||||||||||||
| Initiatives usage |
|
||||||||||||||||||||||
| History |
|
||||||||||||||||||||||
| JSON compare |
compare mode:
version left:
version right:
|
||||||||||||||||||||||
| JSON |
|