Quick answer
Under Rule 7 of the DPDP Rules, a Data Fiduciary that becomes aware of any personal data breach must inform each affected Data Principal and the Data Protection Board without delay, then give the Board a detailed report within 72 hours. There is no materiality threshold. Specified cyber incidents must also be reported to CERT-In within 6 hours of noticing. This playbook sequences both clocks.
- Every personal data breach is reportable under Rule 7; there is no risk or size threshold.
- The Board gets an initial description without delay and a detailed report within 72 hours of awareness.
- Affected individuals must be told without delay, through their user account or registered contact mode.
- CERT-In's 6-hour reporting clock for specified cyber incidents runs in parallel and is shorter.
- Failure to notify a breach can attract a penalty of up to ₹200 crore; inadequate security up to ₹250 crore.
- Prepare templates, roles and evidence capture before an incident, not during one.
Who this is for: CISOs and security operations teams, Incident commanders and on-call engineers, Legal and compliance leads, Customer communications teams, Founders of startups without a security team
What counts as a personal data breach?
The DPDP Act defines a personal data breach broadly: any unauthorised processing of personal data, or accidental disclosure, acquisition, sharing, use, alteration, destruction or loss of access to personal data, that compromises its confidentiality, integrity or availability.
That covers far more than hacking:
- An S3 bucket or Elasticsearch index left publicly readable.
- An email with a customer spreadsheet sent to the wrong recipient.
- Ransomware that encrypts a customer database, even if nothing is exfiltrated, because availability is lost.
- A support agent looking up records without a business reason.
- A bug that shows one user another user's order history.
- A processor's compromise affecting your data.
No threshold
Unlike GDPR, which requires notification to the authority only where there is a risk, Rule 7 contains no materiality filter. Every personal data breach must be intimated to the Board and to each affected Data Principal. Your playbook's first decision is therefore not whether to notify but how quickly you can establish the facts.
Section 8(6) of the Act creates the duty; Rule 7 sets the content and timing from 13 May 2027.
The two clocks: CERT-In and DPDP
Indian organisations face two overlapping reporting regimes with different triggers.
| CERT-In Directions (28 April 2022) | DPDP Rule 7 | |
|---|---|---|
| Trigger | Specified types of cyber incident | Any personal data breach |
| Starts | On noticing the incident | On becoming aware of the breach |
| Deadline | Within 6 hours | Without delay; detail within 72 hours |
| Recipient | CERT-In | Data Protection Board and each affected person |
| Personal data needed? | No | Yes |
A ransomware attack on a customer database typically triggers both. A misdirected email with personal data may trigger only DPDP. A DDoS with no data impact may trigger only CERT-In.
Run them as two parallel workstreams under one incident commander. The CERT-In report is usually filed first, with what is known at hour 6; the DPDP report builds on the same facts. Keep wording consistent across both, because inconsistent accounts to two authorities create avoidable questions.
More: CERT-In rules for AI systems and the 72-hour breach notification rule.
Hours 0–6: detect, contain, decide
Hour 0: awareness. Record the exact time the organisation became aware, who raised it and how. This timestamp anchors the 72-hour deadline. Open an incident ticket and a dedicated, access-controlled channel.
Hour 0–1: assemble. Incident commander, security lead, engineering owner of the affected system, legal or compliance, and communications. Name a scribe to keep a timeline.
Hour 1–3: contain. Revoke exposed credentials and keys, close public access, isolate affected hosts, disable compromised accounts, and preserve evidence before wiping anything. Snapshot disks and export logs. Rule 6(1)(c) logs and the one-year retention in Rule 6(1)(e) are what make this step possible.
Hour 2–4: scope first pass. Which systems, which data categories, roughly how many Data Principals, which time window, whether data left your control.
Hour 4–6: CERT-In. If the incident is a reportable type, file with CERT-In within 6 hours of noticing, with the facts available.
By hour 6: DPDP initial intimation decision. Rule 7(2)(a) requires a description of the breach to the Board without delay, covering nature, extent, timing, location and likely impact. Prepare it now from the first-pass scope; you will update it in the detailed report.
Hours 6–24: notify people and keep investigating
Intimation to Data Principals (Rule 7(1))
Each affected Data Principal must be informed, to the best of the fiduciary's knowledge, concisely, clearly and plainly, without delay, through her user account or any mode of communication she has registered. The message must contain:
- A description of the breach, including its nature, extent and timing.
- The consequences relevant to her that are likely to arise.
- Measures implemented and being implemented to mitigate risk.
- Safety measures she can take to protect her interests.
- Business contact information of a person who can respond to her queries.
Practical template
Subject: Important: a security incident affecting your
[Company] account
On [date], we found that [what happened] between [start]
and [end]. Your [data types] may have been [accessed /
exposed / lost].
This could mean [likely consequences, e.g. phishing calls
using your name and order details].
We have [contained the issue, reset tokens, etc.] and are
[ongoing actions].
You should [change your password, watch for calls asking
for OTPs, etc.].
Questions: [name/role], [email], [phone].
Send in-app and by the registered channel. Do not wait for forensic perfection if people need to protect themselves now.
Hours 24–72: the detailed Board report
Within 72 hours of becoming aware, or a longer period if the Board allows it on a written request, Rule 7(2)(b) requires the Board to receive:
| Item | What to include |
|---|---|
| (i) Updated and detailed description | Revised scope, data categories, number of people and records, systems |
| (ii) Broad facts on events, circumstances and reasons | Root cause as understood: misconfiguration, credential theft, insider, vendor |
| (iii) Mitigation measures implemented or proposed | Containment, resets, monitoring, user support |
| (iv) Findings about the person who caused the breach | Attacker indicators, insider identity if established, vendor involved |
| (v) Remedial measures to prevent recurrence | Control changes, timelines, owners |
| (vi) Report on intimations to Data Principals | How many notified, channels, dates, failures and follow-up |
Extension requests
If the investigation genuinely cannot produce the detail in time, request a longer period from the Board in writing before the deadline, explaining what is outstanding and when you expect it. Do not let the deadline lapse silently.
Processors
If the breach is at a vendor, your contract should already oblige it to supply this information quickly. See the DPA clauses template.
After 72 hours: close-out and lessons
The report is not the end of the incident.
- Keep updating. Send supplementary information to the Board as material facts emerge, and correct anything that turns out to be wrong.
- Support users. Staff the contact point named in the intimation, track queries and escalate patterns such as fraud attempts using leaked data.
- Preserve evidence. Keep the incident timeline, logs, forensic images and communications. The Board may open an inquiry, which Rule 19(9) requires to be completed within six months of receipt, extendable by up to three months at a time.
- Post-incident review. Within two weeks, run a blameless review: what failed, what detection missed, how long each phase took against the playbook.
- Fix the controls. Map remediation to Rule 6 items: encryption, access control, logging, backups, contract clauses.
Penalty exposure
Two penalty heads are relevant. Failure to take reasonable security safeguards can attract up to ₹250 crore; failure to notify the Board or affected individuals up to ₹200 crore. The Board weighs mitigation, so prompt, honest notification and visible remediation matter. A voluntary undertaking under section 32 is also available.
What to prepare before 13 May 2027
- Write the playbook with named roles, deputies and phone trees.
- Draft templates for the Board initial intimation, the 72-hour report, the CERT-In report and Data Principal messages in your main languages.
- Build contact capability: confirm you can message every user through her account or registered channel at scale.
- Instrument logs for access to personal data and retain them for one year as Rule 6(1)(e) requires.
- Map data to systems so scoping takes hours, not days. See data mapping.
- Update vendor contracts with short breach notice windows.
- Synchronise clocks to NIC or NPL NTP servers, as CERT-In requires, so timelines are defensible.
- Run a tabletop exercise with a realistic scenario and measure time to each milestone.
- Agree decision rights: who can approve a Board filing and user messages at 2 a.m. on a Sunday, and who deputises.
- Pre-approve holding statements for media and social channels, consistent with what users and the Board will be told.
The playbook is only as good as the last rehearsal. Re-run it after major architecture changes, new vendors or reorganisations, and record each exercise as evidence of the technical and organisational measures Rule 6(1)(g) expects.
Further reading on suhasbhairav.com
- BlogIncident response for AI failures in production
- BlogSecurity integration tests for cross-tenant data breach scenarios in production systems
- BlogSecurity-by-design with AI agents: production-grade security
- AI SkillsIncident Response AGENTS.md Template for Architecture and Orchestration
- AI AgentsAI Agents for Incident Response in Cybersecurity
Before 13 May 2027
Compliance checklist
Record the time of awareness
Log exactly when and how the organisation became aware of the breach.
Rule 7(2)(b)
Contain and preserve evidence
Revoke access, isolate systems and snapshot logs before remediation changes them.
Rule 6(1)(c)
File with CERT-In within 6 hours if applicable
Report specified cyber incidents to CERT-In within 6 hours of noticing.
CERT-In Directions, 28 April 2022
Send the initial intimation to the Board
Describe nature, extent, timing, location and likely impact without delay.
Rule 7(2)(a)
Notify each affected Data Principal
Use the user account or registered channel and include all five required elements.
Rule 7(1)
Submit the detailed report within 72 hours
Cover the six items in Rule 7(2)(b), or request an extension in writing.
Rule 7(2)(b)
Report on intimations made
Tell the Board how and when affected individuals were informed.
Rule 7(2)(b)(vi)
Run a post-incident review
Identify control failures and map remediation to Rule 6 items.
Rule 6
Test the playbook with a tabletop
Rehearse at least once before 13 May 2027 and after major system changes.
Section 8(5)
Answers
Frequently asked questions
Do I have to report every data breach under DPDP?
Do I have to report every data breach under DPDP?
Yes. Rule 7 applies to any personal data breach and contains no threshold based on risk, size or sensitivity. Each affected Data Principal and the Data Protection Board must be informed without delay, and the Board must receive a detailed report within 72 hours of the fiduciary becoming aware.
When does the 72-hour DPDP clock start?
When does the 72-hour DPDP clock start?
It starts when the Data Fiduciary becomes aware of the breach, under Rule 7(2)(b). Record that moment precisely. The Board may allow a longer period if you request it in writing. The initial description to the Board, and the notice to affected people, must go without delay, which can be well before 72 hours.
What is the difference between CERT-In and DPDP breach reporting?
What is the difference between CERT-In and DPDP breach reporting?
CERT-In's directions require specified cyber incidents to be reported to CERT-In within 6 hours of noticing, whether or not personal data is involved. DPDP Rule 7 requires any personal data breach to be reported to the Data Protection Board and affected individuals. Many incidents trigger both, so run them in parallel.
What must the message to affected users contain?
What must the message to affected users contain?
Rule 7(1) requires five elements: a description of the breach including nature, extent and timing; likely consequences for her; mitigation measures taken or under way; safety steps she can take; and business contact details of a person who can answer her questions. It must be concise, clear and sent through her account or registered channel.
Can I delay telling users until the investigation is finished?
Can I delay telling users until the investigation is finished?
No. Rule 7(1) requires intimation without delay, to the best of the fiduciary's knowledge at the time. Send what you know, especially protective steps, and follow up with updates. Waiting for complete forensics risks both harm to users and a penalty of up to ₹200 crore for failing to notify.
What if the breach happened at our vendor?
What if the breach happened at our vendor?
You remain responsible as the Data Fiduciary under section 8(1), and the reporting duty under Rule 7 is yours. Your contract should require the vendor to notify you within hours and supply the facts you need. Your awareness may depend on that notice, so a short contractual window is essential.
Legal references and sources
- Digital Personal Data Protection Rules, 2025 — Rule 7 (official text)
- Digital Personal Data Protection Act, 2023 — Section 8(6) (official text)
- Digital Personal Data Protection Rules, 2025 — Rule 6(1)(c) and 6(1)(e) (official text)
- CERT-In Directions under section 70B(6), IT Act — Directions of 28 April 2022 (official text)
This guide explains the law for engineering and business teams. It is not legal advice; confirm how it applies to your organisation with qualified counsel, and check the Gazette for later notifications or amendments.
About the author

Suhas Bhairav
Systems architect and applied AI practitioner who designs production AI systems for Indian and global companies, with a focus on privacy-by-design under the DPDP Act and the EU AI Act.
Related guides
- DPDP Rules 2025DPDP Data Breach Notification: The 72-Hour Rule ExplainedRule 7 requires every personal data breach to be reported to affected individuals and the Data Protection Board, with a detailed Board report within 72 hours. No materiality threshold applies.
- India AI & sector rulesCERT-In Rules for AI Systems: Incident Reporting & LogsHow CERT-In's April 2022 directions on 6-hour incident reporting, 180-day logs in India and clock sync apply to LLM gateways, model APIs and AI agents, and how they meet DPDP.
- DPDP Rules 2025DPDP Reasonable Security Safeguards Under Rule 6Rule 6 lists the minimum security safeguards every Data Fiduciary must take from 13 May 2027. Failure can attract a penalty of up to ₹250 crore, the highest in the DPDP Act.
- Templates & playbooksDPDP Data Processing Agreement Clauses TemplateCopy-ready data processing agreement clauses for India, mapped to DPDP section 8(2), Rule 6(1)(f), Rule 7 breach timelines and Rule 8(3) one-year retention.
- DPDP Act 2023DPDP Penalties Explained: What a Data Breach CostsThe full DPDP Act penalty schedule, from ₹10,000 to ₹250 crore per instance, the section 33(2) factors the Board weighs, and how penalties are imposed and appealed.
- Templates & playbooksDPDP Audit Checklist: 60 Controls to TestSixty testable DPDP controls grouped by governance, notice and consent, children, security, breach, retention, rights and vendors, each mapped to the Act or the 2025 Rules.