Name | [Preview]: Azure Key Vault Managed HSM keys should have an expiration date Azure Portal |
||||||
Id | 1d478a74-21ba-4b9f-9d8f-8e6fced0eec5 | ||||||
Version | 1.0.0-preview details on versioning |
||||||
Category | Key Vault Microsoft docs |
||||||
Description | 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. | ||||||
Mode | Microsoft.ManagedHSM.Data | ||||||
Type | BuiltIn | ||||||
Preview | True | ||||||
Deprecated | FALSE | ||||||
Effect | Default: Audit Allowed: (Audit, Deny, Disabled) |
||||||
Used RBAC Role | none | ||||||
Rule Aliases | |||||||
Rule ResourceTypes | |||||||
History |
|
||||||
Used in Initiatives | none | ||||||
JSON |
|