Security & Trust Center
Your data security is our priority
Deploy Your Workloads Safely on Serverless Compute
With serverless, Databricks customers can access near-instant compute, with minimal management and lower TCO. This compute and its associated resources are managed by Databricks in a serverless compute plane within the customer’s Databricks account. To safeguard customer data, serverless workloads are executed within multiple layers of isolation.
First, the compute is freshly created in an unallocated pool without any customer credentials. When needed, the running compute is quickly assigned to a customer’s logical network and scaled as needed. This approach allows fast cluster deployment, typically under 30 seconds. All compute is ephemeral, dedicated exclusively to that workload and securely wiped once the workload is complete. These layers of isolation are extensively tested by both our in-house offensive security team and external penetration testing companies, to protect your data at all times.
Securing your workloads with multiple layers of protection
With Databricks, your serverless workloads are protected by multiple layers of security. These security layers form the foundation of Databricks’ commitment to providing a secure and reliable environment for even the most sensitive workloads.
They include but are not limited to:
- Dedicated compute resources
- Each workload runs on compute and encrypted storage that is dedicated to that workload
- Storage cannot be reallocated or reassigned after use
- Both the compute and the storage are securely wiped as soon as the workload completes
- Network segmentation
- Each workload operates within a private network with no public IP addresses assigned
- That network is isolated logically from other workloads
- Lateral movement or communication between workloads is blocked
- All traffic between the user, the control plane, the compute plane and cloud services is routed over the cloud provider’s global network, not the public internet
- Encryption at rest and in transit
- All attached storage is protected by industry-standard AES-256 encryption
- All traffic between the user, the control plane, the compute plane and cloud services is encrypted with at least TLS 1.2
- Principle of least privilege
- Workloads have no privileges or credentials for systems outside the scope of that workload
- Access to the data is via short-lived (1-hour) tokens
- These tokens are passed securely to each specific workload
