Other Articles
- SQL Database – Enable Database Encryption
- SQL Databases – Enable Backup
- SQL Database – Monitor CPU Utilization
- SQL Database – Monitor IO Utilization
- SQL Database – Monitor Memory Utilization
- SQL Database – Protect From Direct Internet Traffic
- SQL Server – Enable SQL Defender
- SQL Server – Require Microsoft Entra-Only Authentication
- SQL Server – Block Public Firewall Rules
- SQL Server – Enable Auditing
- Storage Account – Enable Storage Encryption
- Storage Account – Disable Blob Public Access
- Storage Account – Disable Cross-Tenant Replication
- Storage Account – Disable Public Network Access
- Storage Account – Enable Microsoft Defender
- Storage Account – Enable Secure Transfer
- Storage Account – Enforce Minimum TLS Version
- Storage Account – Enforce Network Access Rule
- Storage Account – Enforce Private Endpoint Access
- Storage Account – Enable Blob Soft Delete
- Storage Account – Enable Blob Versioning
- User – Enable Azure MFA
- App Service – Disable Remote Debugging
- App Service – Enable Defender
- App Service – Enable Entra ID Registration
- App Service – Enable HTTP2
- App Service – Enforce Latest TLS Version
- App Service – Enforce Secure FTPS State
- App Service – Monitor Server Errors
- App Service – Redirect HTTP to HTTPS
- Cosmos DB – Enable Backup
- Cosmos DB – Enable Microsoft Defender
- Cosmos DB – Monitor Latency
- Cosmos DB – Ensure Private Connectivity
- Cosmos DB for PostgreSQL – Monitor CPU Utilization
- Cosmos DB for PostgreSQL – Monitor IO Utilization
- Cosmos DB for PostgreSQL – Monitor Memory Utilization
- Cosmos DB for PostgreSQL – Protect From Direct Internet Traffic
- Cosmos DB – Protect From Direct Internet Traffic
- Cosmos DB – Restrict Firewall Network Access
- Virtual Machine – Enable Defender
- Virtual Machine – Protect From Direct Internet Traffic
- Key Vault – Enable Defender
- Key Vault – Ensure Vault Recoverable
- Key Vault – Require Private Endpoint Access
- Key Vault – Enable Purge Protection
- Key Vault – Use Azure RBAC Authorization
- MySQL Flexible Server – Enable Audit Log Events Connection
- MySQL Flexible Server – Enable Audit Logs
- MySQL Flexible Server – Enforce Minimum TLS Version
- PostgreSQL Flexible Server – Configure Log File Retention
- PostgreSQL Flexible Server – Enable Connection Logging
- PostgreSQL Flexible Server – Enable Connection Throttling
- PostgreSQL Flexible Server – Enable Disconnection Logging
- PostgreSQL Flexible Server – Enable Log Checkpoints
- Network Security Group – Ensure Flow Logs Captured
- General – Enable Auto Provisioning Log Analytics
- General – Enable Security Notifications
- General – Set Additional Email Address
- Cosmos DB – Enforce Minimum TLS Version
- PostgreSQL Flexible Server – Enforce Minimum TLS Version
- Container Instance – Enforce Use of Private Virtual Networks
- Container Instance – Enforce Managed Identity Usage
Key Vault – Enforce Keys Expiration
Secure Configuration Checks > Azure
This check ensures that every key in an Azure Key Vault has an expiration date. Setting an expiration date forces keys to be rotated regularly, which limits how long a leaked or old key can be used.
Check Details
- Resource: Key Vault
- Check: Enforce Keys Expiration
- Risk: Keys without an expiration date stay valid indefinitely. If a key is exposed, it can be misused for as long as it exists, and there is no prompt to rotate it.
Remediation via Azure Portal
-
Log in to the Azure Portal.
-
Navigate to Key vaults and select the affected key vault.
-
In the left menu, click on Keys under Objects.
- Select the key that has no expiration date, then select its current version.
- Select Set expiration date and choose a date and time.
- Click Save to apply the changes.
- Repeat these steps for every key and key version that has no expiration date. For new keys, select Set expiration date on the Create a key page.
Remediation via Azure CLI
-
Open Azure Cloud Shell from the Azure Portal or use a local
terminal with Azure CLI installed.
-
Run the following command to list the keys in the vault:
az keyvault key list \ --vault-name <key-vault-name> \ --output table
-
Run the following command to set an expiration date on a key:
az keyvault key set-attributes \ --vault-name <key-vault-name> \ --name <key-name> \ --expires <expiration-date>
Replace
<key-vault-name>,<key-name>and<expiration-date>with your actual values. The date must be in UTC format, for example2027-12-31T00:00:00Z. Repeat the command for each key.
Updated on 04 November, 2026