The data encryption key is cached in memory for several read and write operations and evicted from memory at a regular interval. Personal access tokens (PAT) or other credentials used to set up Git integration with Databricks Repos.Īfter you add a customer-managed key encryption for a workspace, Databricks uses your key to control access to the key that encrypts future write operations to your workspace’s managed services data. Secrets stored by the secret manager APIs.ĭatabricks SQL queries and query history.
You can configure Databricks to store all interactive notebook results in your cloud account. By default, larger results are also stored in your workspace root bucket. Notebook results for notebooks run interactively (not as jobs) that are stored in the control plane. Notebook source in the Databricks control plane. You can add a customer-managed key for managed services to help protect and control access to the following types of encrypted data: Managed services data in the Databricks control plane is encrypted at rest. To compare them, see Customer-managed keys for encryption. Databricks has two customer-managed key features. Enforce user isolation cluster types on a workspace.įor additional control of your data, you can add your own key to protect and control access to some types of data.Audit log schemas for Capsule8 and ClamAV.Create and verify a cluster for legacy HIPAA support.Access Azure storage with Azure Active Directory.GDPR and CCPA compliance with Delta Lake.Encrypt traffic between cluster worker nodes.Customer-managed keys for workspace storage.Customer-managed keys for managed services.
0 kommentar(er)
