หมายเหตุ
การเข้าถึงหน้านี้ต้องได้รับการอนุญาต คุณสามารถลอง ลงชื่อเข้าใช้หรือเปลี่ยนไดเรกทอรีได้
การเข้าถึงหน้านี้ต้องได้รับการอนุญาต คุณสามารถลองเปลี่ยนไดเรกทอรีได้
Lakebase Postgres provides data protection features to help secure your databases and control access to critical data. These features enable you to protect production environments and establish secure network connectivity between your applications and databases.
Data protection features
| Feature | Description |
|---|---|
| Customer-managed keys | Manage your own encryption keys to protect Lakebase project data at rest in your cloud KMS. |
| Protected branches | Configure branch protection rules to prevent accidental modifications or deletions of critical branches, ensuring the integrity of your production and staging data. |
| Private Link for Lakebase | If your workspace uses Private Link, Lakebase requires inbound Private Link. Postgres clients connecting from outside the workspace also require inbound Private Link for performance-intensive services. |
Compliance
Lakebase is enabled by default for workspaces with the compliance security profile when the compliance standard is set to HIPAA, PCI-DSS, HITRUST, C5, TISAX, ISMAP, or None.
The following compliance standards are supported only in specific Azure regions:
- IRAP:
australiaeast - UK Cyber Essentials Plus:
uksouth,ukwest
Other compliance standards are not supported.
Lakebase is SOC 2 Type 2 compliant. For our SOC reports, please ask your Databricks account team.
For per-region feature availability under a compliance standard, see the Regional support for features table on the standard's page, such as PCI-DSS or HITRUST.
For more about processing protected health information (PHI) under HIPAA, see HIPAA compliance for Lakebase.