Data breaches aren't just security events—they're compliance landmines under the DPDPA, 2023.
One of the most stringent requirements? Mandatory breach notification within 72 hours to the Data Protection Board and affected individuals (if there's likely harm).
Let's unpack what this means and how you can stay ahead.
What Triggers a Notification?
- Unauthorized access to personal data
- Accidental deletion, modification, or exposure
- Ransomware attacks or system compromise
- Any event that can reasonably cause harm to a data principal
The 72-Hour Clock Starts When?
Not from breach occurrence, but from when it's discovered.
Example:
A breach occurred on Jan 1 but discovered on Jan 4 → Deadline = Jan 7.
What Must Be Reported?
To the Data Protection Board:
- Nature and cause of the breach
- Personal data categories affected
- Number of individuals impacted
- Measures taken to mitigate damage
- Contact details of DPO or grievance officer
To Data Principals:
- Description of the breach
- What steps they should take
- Helpline or support channels
How to Prepare Your Breach Response System
Define a Breach Response SOP
→ Include detection, escalation, containment, and notification.
Form a Breach Committee
→ Include IT, Legal, DPO, and Communications.
Simulate Breaches
→ Conduct tabletop exercises every quarter.
Integrate Your Breach Module with Your CMP
→ TruConsent offers breach orchestration tools with timelines, audit logs, and action tracking.
Quick Tip: Don't Delay Disclosure
Hiding a breach may feel safe—but it's non-compliant.
Disclose transparently, mitigate fast, and document every step.
DPDPA is strict, but manageable—with the right systems in place.
TruConsent helps organizations of all sizes handle breach events with clarity, compliance, and control.
Need breach management support? Our breach orchestration tools can help you stay prepared and compliant. Book Demo