Under India's DPDP Act, any personal data breach must be reported. There is no "risk of harm" threshold like the GDPR's. Rule 7 of the DPDP Rules sets out how. Combined with CERT-In's six-hour reporting direction, an Indian organisation can face two clocks running at once. This playbook shows how to handle both.
What counts as a personal data breach
The Act defines it broadly: any unauthorised processing, or accidental disclosure, acquisition, sharing, use, alteration, destruction or loss of access to personal data, that compromises its confidentiality, integrity or availability.
That includes ransomware that encrypts customer records (loss of availability), an email sent to the wrong list, and a misconfigured storage bucket even if you can't prove anyone downloaded the data.
The obligations in Rule 7
To each affected Data Principal, without delay, in clear language, through their user account or registered contact:
- what happened, including the extent, timing and location of the breach;
- the likely consequences for them;
- what you have done and are doing to reduce the harm;
- what they can do to protect themselves, such as changing passwords or watching for fraud;
- who they can contact about it.
To the Data Protection Board, in two steps:
- Without delay: an intimation describing the breach, its nature, extent, timing and location, and its likely impact.
- Within 72 hours of becoming aware (or longer if the Board allows on request): an updated report with the facts and circumstances, the cause, mitigation, any findings about who was responsible, remedial measures to prevent recurrence, and a report on the notices sent to individuals.
The second clock: CERT-In
CERT-In's April 2022 directions require service providers, intermediaries, data centres and body corporates to report certain cyber incidents to CERT-In within six hours of noticing them. The list includes data breaches and data leaks, unauthorised access and ransomware. The two regimes are separate: reporting to CERT-In does not satisfy the DPDP Act, or the other way round. See our guide to the CERT-In six-hour rule.
Hour-by-hour playbook
Hour 0–2: confirm and contain
- Confirm that something happened, and record the time you became aware. That timestamp starts both clocks.
- Contain the incident: isolate systems, revoke credentials and preserve evidence (logs, images). Don't wipe and rebuild before you have captured what you need.
- Open an incident record and appoint an incident lead and a decision owner for notifications.
Hour 2–6: first reports
- CERT-In (if in scope): report with what you know by hour 6. Incomplete is fine; late is not.
- Board intimation: send the initial intimation as soon as you can describe the nature and likely impact. Don't wait for the full investigation.
- Start drafting the notice to individuals. Legal, communications and the incident lead should agree it together.
Hour 6–24: scope
- Work out which records and individuals are affected and what data fields were exposed. The data inventory you built for compliance pays off here.
- Identify any processors involved and invoke their contractual duty to cooperate.
- Decide on mitigations you can offer individuals, such as forced password resets, card reissue or fraud monitoring.
Hour 24–48: tell people
- Send the notices to affected individuals through their account or registered contact.
- Prepare support staff with a script and a frequently-asked-questions sheet.
- Track delivery: you will report on the notices to the Board.
Hour 48–72: detailed report
- Complete the Board's 72-hour report: cause, timeline, data and people affected, mitigation, remediation, and the status of individual notices.
- If you can't complete the investigation in time, ask the Board for more time in writing and give the reasons.
Prepare before it happens
- Templates: Board intimation, 72-hour report, individual notice and CERT-In form, with gaps to fill.
- Contacts: who in legal, security, communications and leadership must be reachable at 3 a.m.
- Decision rights: who signs off a notification. Don't let it wait for a meeting.
- Processor terms: contracts that require vendors to tell you quickly (for example within 24 hours) and to cooperate.
- Rehearsal: a yearly tabletop exercise with a realistic breach scenario.
- Logs: Rule 8 requires processing logs to be kept for at least a year, which is also what you need to scope a breach.
Penalties
Failing to notify the Board or affected individuals can draw a penalty of up to ₹200 crore. Failing to take reasonable security safeguards in the first place can draw up to ₹250 crore.
Breach response is one of the four modules in our free Data Protection & Privacy Fundamentals course, which ends with a final exam and certificate.
Written and reviewed by the DigiTrust Asia editorial team. How we research, review and correct articles.
General information, not legal advice. Laws and official guidance change; check the current text before acting.
Learn privacy properly
Data Protection & Privacy Fundamentals is a free, law-neutral course with a final exam and certificate.
Create a free account