India now has two clocks that can start ticking on the same breach. One is CERT-In's six-hour incident report. The other is the duty under the Digital Personal Data Protection framework to tell the Data Protection Board and every affected person. They ask for different things, go to different authorities and carry different consequences. This guide sets out the DPDP side, based on the official text of the Act and the Rules, and gives you a breach-day runbook that covers both. It is practical guidance, not legal advice.
What does the DPDP Act say about breaches?
The Digital Personal Data Protection Act, 2023 creates two separate obligations that matter on a breach day:
- Section 8(5): a data fiduciary must protect personal data in its possession or under its control, including processing done by a data processor on its behalf, by taking reasonable security safeguards to prevent a personal data breach.
- Section 8(6): in the event of a personal data breach, the data fiduciary must give the Board and each affected data principal intimation of the breach, in the form and manner prescribed (DPDP Act, 2023).
The Schedule to the Act links each to a maximum penalty: up to Rs 250 crore for failing to take reasonable security safeguards, and up to Rs 200 crore for failing to notify the Board or affected people of a breach. These are separate items, so a breach caused by weak security and then not reported can expose a company on both counts.
What counts as a personal data breach?
The Act defines a personal data breach as "any unauthorised processing of personal data or accidental disclosure, acquisition, sharing, use, alteration, destruction or loss of access to personal data, that compromises the confidentiality, integrity or availability of personal data". That is wider than many teams assume. It covers a hacker copying a database, but also an employee emailing a customer list to the wrong address, a misconfigured storage bucket, and ransomware that makes records unavailable even if nothing was copied. Loss of access counts. If your incident response plan only says "data theft", update the definition before you need it.
What exactly does Rule 7 require?
Rule 7 of the DPDP Rules, 2025 sets out the "form and manner" (DPDP Rules, 2025).
To each affected person: without delay
On becoming aware of a breach, the fiduciary must, to the best of its knowledge, inform each affected data principal "in a concise, clear and plain manner and without delay", through their user account or a registered mode of communication. The message must cover:
- a description of the breach, including its nature, extent and timing;
- the consequences likely to arise for that person;
- the measures taken or being taken to mitigate risk;
- safety measures the person can take; and
- business contact details of someone who can answer their questions.
To the Data Protection Board: two stages
| When | What the Board must receive |
|---|---|
| Without delay | A description of the breach: nature, extent, timing and location of occurrence, and likely impact |
| Within 72 hours of becoming aware (or longer if the Board allows on a written request) | Updated, detailed information; broad facts on the events, circumstances and reasons; mitigation measures; any findings about who caused it; remedial steps to prevent recurrence; a report on the intimations given to affected people |
Two points stand out. First, there is no threshold of "likely harm" in the rule text: the duty attaches to a personal data breach as defined in the Act. Second, the 72-hour report includes a report on the notices you sent to individuals, so those notices cannot wait for the investigation to finish.
When does this apply?
The Rules were notified on 13 November 2025. Rule 1 sets a phased start: rules on the Board took effect on publication, consent manager registration one year later, and Rules 3 and 5 to 16 (which include notice, security safeguards and breach intimation in Rule 7) eighteen months after publication. Bar & Bench reads that date as 13 May 2027 (Bar & Bench). The CERT-In Directions do not wait for that date, and in January 2026 MeitY sought industry views on cutting the 18-month window to 12 months (Storyboard18), so check the current position with counsel. Practically, build the process now: a breach runbook takes months to embed.
How does DPDP reporting fit with CERT-In?
| CERT-In Directions, 2022 | DPDP Act and Rules | |
|---|---|---|
| Trigger | Any of 20 listed cyber incidents, including data breach and data leak | A personal data breach |
| Who to tell | CERT-In | Data Protection Board and each affected person |
| Timeline | Within 6 hours of noticing | Without delay; detailed Board report within 72 hours |
| Supporting duty | 180-day log retention in India | Logs and monitoring as security safeguards; one-year retention of logs under Rule 6 |
A ransomware attack that encrypts and copies a customer database will typically require both. The CERT-In requirements are set out in the Directions of 28 April 2022 (CERT-In Directions).
Breach-day runbook
Hour 0 to 6
- Contain: isolate affected systems, revoke compromised credentials, preserve logs.
- Open an incident log with timestamps. Record the moment you became aware; both clocks run from awareness.
- Send the initial CERT-In report.
- Brief legal counsel and the person responsible for data protection.
Hour 6 to 24
- Establish what personal data was involved: whose, which fields, how many records, whether it was encrypted.
- Send the first intimation to the Board describing nature, extent, timing, location and likely impact.
- Draft the notice to affected people in plain language, in the languages your customers use. Include concrete safety steps, such as changing passwords or watching for fraudulent calls.
Hour 24 to 72
- Send notices to affected people through their account or registered contact details.
- Prepare the detailed Board report: facts and reasons, mitigation, findings about the cause, remediation, and the report on notices sent.
- If you cannot complete it in 72 hours, request an extension in writing before the deadline.
- Check contracts: clients and partners may have their own notification clauses.
After 72 hours
- Complete root-cause fixes and keep evidence of them.
- Review whether security safeguards under Rule 6 were adequate: encryption, access control, logging, backups and processor contracts.
- Update the runbook with what slowed you down.
What should you prepare before any breach?
- A data inventory, so you can answer "whose data, which fields" in hours, not weeks.
- Pre-approved notice templates for individuals and for the Board.
- A working way to reach every customer: verified email or mobile, or an in-app message.
- Processor contracts that require your vendors to tell you about breaches immediately.
- A named decision-maker who can approve notices at midnight.
How Cehpoint can help
Cehpoint's DPDP Act compliance service builds the breach runbook, notice templates, data inventory and processor clauses, and rehearses them with your team. When a breach happens, our digital forensics team establishes what data was accessed, which is the foundation of an accurate Board report.