Name | [Preview]: Key Vault secrets should have an expiration date Azure Portal |
||||||||||||
Id | 98728c90-32c7-4049-8429-847dc0f4fe37 | ||||||||||||
Version | 1.0.1-preview details on versioning |
||||||||||||
Category | Key Vault Microsoft docs |
||||||||||||
Description | Secrets should have a defined expiration date and not be permanent. Secrets that are valid forever provide a potential attacker with more time to compromise them. It is a recommended security practice to set expiration dates on secrets. | ||||||||||||
Mode | Microsoft.KeyVault.Data | ||||||||||||
Type | BuiltIn | ||||||||||||
Preview | True | ||||||||||||
Deprecated | FALSE | ||||||||||||
Effect | Default: Audit Allowed: (Audit, Deny, Disabled) |
||||||||||||
Used RBAC Role | none | ||||||||||||
History |
|
||||||||||||
Used in Initiatives |
|
||||||||||||
JSON Changes |
|
||||||||||||
Json |
|