Skip to main content
Checks that expiration dates are set for all keys in non-RBAC Azure Key Vaults.

​
About

When you connect Microsoft Azure to DSALTA, the platform retrieves the list of resources in your environment using read-only API access. DSALTA then checks whether this configuration is in place. If it is not, DSALTA activates this check so you can remediate it.

​
Why This Matters

Encryption is only as strong as the keys behind it. Keys that are never rotated or are broadly accessible can be compromised, exposing all the data they protect. Rotation and access control on keys are required by SOC 2, ISO 27001, and PCI DSS.

​
How to Fix

Before you begin
  • Ensure you have access to the Azure Key Vault.
Set key expiration / recoverability
  1. Sign in to the Azure Portal and open Key Vaults → your vault.
  2. For keys, open each key and set an expiration date (90 days recommended), then rotate before expiry.
  3. For recoverability, open Properties and confirm Soft delete and Purge protection are enabled.
Once key expiration and recoverability are configured, DSALTA retrieves the change on the next sync and sets the check status to Passing.

​
Frequently Asked Questions

This check runs automatically every 24 hours while the Microsoft Azure integration is connected. You can also trigger a manual sync from Integrations in the sidebar.
A failing check appears in your Data Library → Tests dashboard. Work through the steps above; once the underlying configuration is fixed, the status updates automatically on the next sync.
Yes. If it does not apply to your environment, mark it as Not Applicable with a justification. The exclusion is documented for auditors.
No. DSALTA uses read-only API access and never modifies, creates, or deletes resources. All remediation is performed by your team directly in Microsoft Azure.