Check ID:
Provider: Azure
Service:
Severity: HIGH
Categories:
Resource type:
databricks_workspace_cmk_encryption_enabledProvider: Azure
Service:
databricksSeverity: HIGH
Categories:
encryptionResource type:
microsoft.databricks/workspacesWhat this check verifies
Azure Databricks workspaces are evaluated for use of customer-managed keys (CMK) on at-rest encryption, based on the workspace’s managed disk encryption configuration.
Risk
Without CMK, keys are provider-controlled, degrading confidentiality and incident response.- Slower revoke/rotate during breaches
- Weaker separation of duties and audit trails
- Larger blast radius if storage or control plane is compromised
Recommendation
EnableCMK for workspace encryption via Key Vault or Managed HSM and enforce:
- Least privilege for key usage
- Regular rotation and retire old versions
- Audit logging and alerts on key ops
- Separation of duties for key vs data roles
- Deny-by-default policies limiting scope
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
az databricks workspace update —name <workspace_name> —resource-group <resource_group_name> —key-source Microsoft.Keyvault —key-name <key_name> —key-vault https://<key_vault_name>.vault.azure.net/ —key-version <key_version>
References
- https://www.trendmicro.com/cloudoneconformity/knowledge-base/azure/Databricks/enable-encryption-with-cmk.html
- https://learn.microsoft.com/en-us/azure/databricks/security/keys/customer-managed-keys
Where this check fires
This check runs on every scheduled scan against your Azure account. Findings appear at Cloud Security → Findings filterable byCheck ID = databricks_workspace_cmk_encryption_enabled. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to Azure checks