AzPolicyAdvertizer

last sync: 2024-Nov-25 18:54:24 UTC

[Preview]: Azure Key Vault Managed HSM keys should have an expiration date

Azure BuiltIn Policy definition

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.
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)
Control Domain Control Name MetadataId Category Title Owner Requirements Description Info Policy#
op.exp.10 Cryptographic key protection op.exp.10 Cryptographic key protection 404 not found n/a n/a 53
Initiatives usage
Initiative DisplayName Initiative Id Initiative Category State Type
Enforce recommended guardrails for Azure Key Vault Enforce-Guardrails-KeyVault Key Vault GA ALZ
Spain ENS 175daf90-21e1-4fec-b745-7b4c909aa94c Regulatory Compliance GA BuiltIn
History
Date/Time (UTC ymd) (i) Change type Change detail
2023-01-13 18:06:06 change Patch, suffix remains equal (1.0.0-preview > 1.0.1-preview)
2022-05-23 08:52:47 add 1d478a74-21ba-4b9f-9d8f-8e6fced0eec5
JSON compare
compare mode: version left: version right:
JSON
api-version=2021-06-01
EPAC