Databricks sql warehouse has Serverless compute as a public preview.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-29-2024 12:42 PM
There is a risk form infosec as it is processed in the control plane shared with other azure clients. s there any control to mitigate the risk?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-30-2024 04:40 AM
You can find more information on that topic here.
"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"