Is serverless compute secure enough for regulated industries like banking or healthcare?

Summary

• Serverless compute runs each workload on compute dedicated to that workload, inside a private network with no public IP addresses. The compute and its storage are securely wiped when the workload completes.
• Traffic between the user, the control plane, the compute plane and cloud services is encrypted with at least TLS 1.2, and attached storage is protected with AES-256 encryption.
• For regulated data, enable the compliance security profile on the workspace and select your standards, such as HIPAA or PCI-DSS. HIPAA also requires an active business associate agreement (BAA) before you process PHI.
• Databricks states that you are solely responsible for your own compliance with applicable laws and regulations. You add the data-level controls, such as Unity Catalog access policies, egress control and audit review.

Is serverless compute secure enough for regulated industries like banking or healthcare?

It can be, if you pair it with the controls your regulator expects. Databricks documents layered isolation for serverless compute, and the compliance security profile supports standards such as HIPAA and PCI-DSS. No platform feature makes an organization compliant on its own: the documentation says you are solely responsible for ensuring your own compliance with all applicable laws and regulations. Treat serverless compute as a secure foundation and verify the rest for your standard, region and workspace.

What security does serverless compute provide by default?

Databricks says serverless workloads are protected by multiple layers of security. The Security & Trust Center lists them:

• Dedicated, ephemeral compute: each workload runs on compute dedicated to that workload. Data is stored only temporarily, and the compute and its storage are securely wiped as soon as the workload completes.
• Network segmentation: each workload runs in a private network with no public IP addresses, isolated logically from other workloads. Lateral movement or communication between workloads is blocked and monitored.
• Encryption: attached storage uses AES-256 encryption. Traffic between the user, the control plane, the compute plane and cloud services uses at least TLS 1.2.
• Least privilege: workloads hold no privileges or credentials for systems outside their scope, and they reach data through short-lived tokens.

Serverless compute runs in a Databricks-managed serverless compute plane, created in the same AWS region as your workspace. It sits inside a network boundary for the workspace, with layers of security that isolate different customers' workspaces. The details on this page come from the Databricks on AWS documentation.

Which compliance standards cover regulated workloads?

The compliance security profile adds extra monitoring, a hardened compute image and other controls to a workspace. The docs say to enable it before you process data regulated under C5, CCCS Medium (Protected B), DoD IL5, FedRAMP High, FedRAMP Moderate, HIPAA, HITRUST, IRAP, ISMAP, K-FSI, PCI-DSS, TISAX or UK Cyber Essentials Plus.
Two details matter for banks and healthcare providers. For HIPAA, enabling the standard through the profile means you agree to the Databricks business associate agreement unless you have a separate one, and you need an active BAA before processing any PHI. Databricks doesn't support preview features for processing PHI unless the HIPAA page lists them. For PCI DSS, the workspace needs the profile enabled, and only specific preview features are supported for regulated data. Both pages include a regional support table that lists serverless jobs, notebooks, Lakeflow Pipelines and SQL warehouses. They warn that some features may be listed as available before they are released, so check your own region.

What do you still configure yourself?

Control	What it does	Status or requirement
Compliance security profile	Turns on the extra controls and standards listed above	Enable before you process regulated data
Serverless egress control	Network policies manage outbound connections. Restricted access allows only Unity Catalog external locations and destinations you list	Enterprise tier; test a policy in dry-run mode first
Private connectivity	Network connectivity configurations (NCCs) manage private endpoints from serverless compute to your resources	Private preview, so confirm support for your standard first
Unity Catalog access control	Privileges, row filters, column masks and attribute-based access control (ABAC) policies that act on governed tags	ABAC row filter and column mask policies are GA
Data Classification	An agentic AI system classifies and tags sensitive data in Unity Catalog tables, and the tags can drive ABAC policies	GA
Audit logs	Audit events for services such as authentication and Unity Catalog, queryable in system.access.audit	The system table is in Public Preview
Customer-managed keys	Protect managed services data with your own key. EBS-volume encryption doesn't apply because serverless disks are short-lived	Enterprise tier

FAQs

Does serverless compute meet PCI-DSS requirements?

It can support PCI-DSS workloads, because PCI-DSS is one of the standards the compliance security profile supports. Enable the profile on the workspace, check the PCI DSS regional table for the serverless features you plan to use, and remember that you remain responsible for your own PCI-DSS controls. The docs also warn against putting sensitive information in customer-defined fields, such as workspace names, job names or tags, because they can be stored or processed outside the compliance boundary.

Can I restrict what serverless workloads connect to?

Yes. Serverless egress control uses account-level network policies, and each workspace links to one policy at a time. In restricted access mode, serverless workloads reach only Unity Catalog external locations, destinations you define and a few implicitly allowed ones, such as the workspace's own S3 bucket. Traffic between the control plane and the serverless compute plane always uses the cloud network backbone, not the public internet.

How do I get the Databricks SOC 2 report?

Ask your Databricks account team for the SOC 2 Type II report. The Trust Center also offers a downloadable due diligence package that includes ISO certifications and the annual penetration test confirmation letter. SOC 2 is not on the compliance security profile's list of standards, so you don't enable it on a workspace.