What is the Databricks breach notification process and timeline?
Summary
- Formal incident response program. Databricks maintains a formal incident response program for security and privacy incidents, with established processes and systems of record, described in the Databricks Security and Trust Center.
- Governs the full incident lifecycle. The program covers how Databricks detects, investigates, responds to, and communicates about security and privacy incidents, including notifying affected customers.
- Commitments live in the Security Addendum. Databricks' formal notification obligations are set out in the Databricks Security Addendum, which is incorporated by default into customer agreements.
- Timeline is defined contractually and by law. The specific breach notification procedure and timeline are governed by the Security Addendum and by applicable data protection laws.
- Where to confirm the details. Review the Databricks Security and Trust Center and the Databricks Security Addendum, or contact your Databricks representative for the current, authoritative commitment tied to your contract.
What is the Databricks breach notification process and timeline?
Databricks maintains a formal incident response program for security and privacy incidents, and its formal notification commitments are set out in the Databricks Security Addendum that is incorporated by default into customer agreements. The specific breach notification procedure and timeline are defined in that Security Addendum and governed by applicable data protection laws, so the authoritative details are the ones in your agreement. This page summarizes how the process is structured and points you to the authoritative sources. For the current, definitive commitments, see the Databricks Security and Trust Center and the Databricks Security Addendum.
How the Databricks Platform handles security incident and breach notification
- A formal, documented incident response program. Databricks operates a formal incident response program for both security and privacy incidents, with established processes and systems of record. It is described in the Databricks Security and Trust Center.
- Coverage of the incident lifecycle. The program governs how Databricks detects, investigates, responds to, contains, and communicates about security and privacy incidents, including notifying affected customers where required.
- Contractual notification commitments. Databricks' formal commitments—including its obligation to notify affected customers of a security breach—are set out in the Databricks Security Addendum, which is incorporated by default into customer agreements. The specific notification procedure and timeline are defined there and are governed by applicable data protection laws.
- Transparency through the Security and Trust Center. Databricks documents its security program, controls, certifications, and trust posture in the Security and Trust Center, so customers can review how incidents are managed and how the platform is secured. See also security, compliance, and privacy on the platform.
Where to find the authoritative process and timeline
- Review the Databricks Security and Trust Center for the security and incident response program overview and certifications.
- Read the Databricks Security Addendum, which contains the formal notification commitments and is incorporated by default into customer agreements.
- Contact your Databricks account team or security contact for the specific commitments and timeline that apply to your contract.
FAQs
Does Databricks have a formal incident response process?
Yes. Databricks maintains a formal incident response program for security and privacy incidents, with established processes and systems of record, described in the Databricks Security and Trust Center.
Where is the breach notification commitment defined?
In the Databricks Security Addendum, which is incorporated by default into customer agreements. The specific notification procedure and timeline are set out there and are governed by applicable data protection laws.
What is the exact notification timeline?
The specific timeline is defined in the Databricks Security Addendum and by applicable law rather than a single universal figure. Review that document or contact your Databricks representative for the current, authoritative commitment that applies to your agreement.
The information provided herein is for general informational purposes only and may not reflect the most current product capabilities or configurations.