Skip to main content

Foundation Model APIs compliance and security

This article describes the compliance standards and security profile support for Databricks Foundation Model APIs.

Databricks Foundation Model APIs support various compliance standards to meet enterprise security and regulatory requirements. The availability of these standards can vary by region and deployment mode: pay-per-token or provisioned throughput.

Compliance standards support: Pay-per-token​

Pay-per-token workloads support the full range of compliance standards available for Model Serving:

  • HIPAA compliance across all regions.
  • Additional compliance standards (PCI-DSS, FedRAMP, IRAP, CCCS, UK Cyber Essentials Plus) in supported regions.
    • See Compliance security profile for the available compliance standards. Each standard has its own page that lists the regions and features it supports.
  • Available for customers with the Compliance Security Profile enabled, including when a compliance standard is selected.

Compliance standards support: Provisioned throughput​

Provisioned throughput workloads support the full range of compliance standards available for Model Serving:

  • HIPAA compliance across all regions.
  • Additional compliance standards (PCI-DSS, FedRAMP, IRAP, CCCS, UK Cyber Essentials Plus) in supported regions.
  • Recommended for all workloads that require compliance certifications beyond HIPAA.
note

These compliance standards require served containers to be built in the most recent 30 days. Databricks automatically rebuilds outdated containers on your behalf. However, if this automated job fails, an event log message like the following appears:

"Databricks couldn't complete a scheduled compliance check for model $servedModelName. This can happen if the system can't apply a required update. To resolve, try relogging your model. If the issue persists, contact support@databricks.com."

Data processing and residency​

The region and corresponding geography where your Foundation Model API requests are processed depends on your workspace region and the specific model being used:

  • As part of providing the Foundation Model APIs, Databricks might process your data outside of the region and cloud provider where your data originated.
  • If your workspace is in a Model Serving region but not a US or EU region, your workspace must be enabled for cross-Geo data processing. It's on by default for these workspaces unless the compliance security profile is enabled.
  • When cross-Geo data processing is on, requests can be processed outside your workspace Geo. If your workloads have data-location requirements, turn it off.
  • See Designated Services for geographic areas that process pay-per-token and provisioned throughput workloads.

Data privacy and use​

For how Databricks protects, uses, and retains the inputs and outputs of Foundation Model API requests, including partner model provider retention, see Data protection in Model Serving.

Regional model availability​

Some models are available only in certain regions. To check where each model is available and whether your region requires cross-Geo data processing, see Model availability by region. Model availability shows where you can use a model, not where requests are processed. See Data processing and residency.

Security best practices​

To restrict which Databricks-hosted foundation models your organization can invoke, see foundation model Unity Catalog permissions.

Topic

Details

Access control

  • Foundation Model API endpoints are protected by workspace-level access controls.
  • Only workspace admins can modify governance settings for Foundation Model APIs endpoints.
  • Endpoints respect networking-related ingress rules configured on the workspace.

Network security

  • Endpoints respect IP allowlists and PrivateLink configurations.
  • You can restrict outbound network access from Model Serving endpoints by configuring network policies.
  • See Manage network policies for more information.

Container security

  • Model Serving does not provide security patches to existing model images to avoid destabilization of production deployments.
  • New model images created from new model versions will contain the latest patches.
  • Containers are automatically rebuilt every 30 days for compliance requirements.

Topic

Details

Access control

  • Foundation Model API endpoints are protected by workspace-level access controls.
  • Only workspace admins can modify governance settings for Foundation Model APIs endpoints.
  • Endpoints respect networking-related ingress rules configured on the workspace.

Network security

  • Endpoints respect IP allowlists and PrivateLink configurations.
  • You can restrict outbound network access from Model Serving endpoints by configuring network policies.
  • See Manage network policies for more information.

Container security

  • Model Serving does not provide security patches to existing model images to avoid destabilization of production deployments.
  • New model images created from new model versions will contain the latest patches.
  • Containers are automatically rebuilt every 30 days for compliance requirements.

Additional resources​