← All news and guides
Data protection

DPDP Breach Response: One Playbook for CERT-In's 6 Hours and DPDP's 72 Hours

CERT-In wants a report in 6 hours. DPDP Rule 7 wants users and the Board told without delay, then a full report in 72 hours. One runbook for both.

Mono Team ·

A dark control room at night, rows of desks with blurred, unreadable screens glowing blue and amber, no people in view.

Short answer: run one incident clock, started the moment anyone in the company becomes aware, and hang both reports off it. If the incident is on CERT-In's list of reportable cyber incidents, report it to CERT-In within 6 hours of noticing it. That duty is already in force. From 13 May 2027, if personal data was involved, DPDP Rule 7 adds two more duties for the Data Fiduciary: tell each affected person without delay, and tell the Data Protection Board without delay, followed by a detailed report within 72 hours of becoming aware. The Act puts those two duties on the Data Fiduciary, not on a processor. A processor should tell its customer fast enough for the customer to meet them, and that window belongs in the contract.

This is an engineering guide, not legal advice. The legal wording of every notice should come from your counsel.

What counts as a personal data breach under the DPDP Act?

Section 2(u) of the DPDP 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 most teams expect. It is not limited to an attacker stealing a database. On the plain wording, all of these can qualify:

  • Accidental disclosure. An email with a customer export sent to the wrong address. A public storage bucket. A support agent screen-sharing the wrong record.
  • Unauthorised processing. An internal job that reads personal data for a purpose it was never meant for. A staff member browsing records without a business reason.
  • Alteration. A bad migration that overwrites addresses or bank details for a set of users.
  • Destruction or loss of access. Ransomware that encrypts a customer database. A deleted table with no working backup. A cloud account lockout that leaves you unable to reach the data.

Neither the Act nor the Rules sets a harm threshold or a minimum number of people. Section 8(6) says that "in the event of a personal data breach" the Data Fiduciary shall give the Board and each affected Data Principal intimation. Plan on the basis that every confirmed breach is reportable, and let counsel decide edge cases.

How is a CERT-In cyber incident different?

CERT-In's Directions of 28 April 2022, issued under Section 70B(6) of the IT Act, require service providers, intermediaries, data centres, body corporates and government bodies to report the incident types in Annexure I within 6 hours of noticing them or being told about them. The list has 20 items. Some involve no personal data at all. CERT-In's FAQs on the Directions (May 2022) add that you may report with the information you have at that point and send the rest later within a reasonable time.

ExampleCERT-In Annexure I?DPDP personal data breach?
Targeted scanning or probing of critical systems, nothing accessedCERT-In Annexure I?: Yes (item i)DPDP personal data breach?: Usually no
DDoS attack that takes your app offlineCERT-In Annexure I?: Yes (item viii)DPDP personal data breach?: Possibly, if it causes loss of access to personal data
Ransomware on a server holding customer recordsCERT-In Annexure I?: Yes (item v)DPDP personal data breach?: Yes: loss of access, and possibly disclosure
Database of users exfiltratedCERT-In Annexure I?: Yes (items xi and xii, data breach and data leak)DPDP personal data breach?: Yes
Customer export emailed to the wrong personCERT-In Annexure I?: Arguably item xii (data leak); confirm with counselDPDP personal data breach?: Yes: accidental disclosure
Botched migration corrupts user addressesCERT-In Annexure I?: Usually noDPDP personal data breach?: Yes: alteration affecting integrity

So triage asks two separate questions. Is it on the CERT-In list? Does it involve personal data? A yes to either starts a reporting track.

CERT-In 6 hours vs DPDP 72 hours: what are the two clocks?

CERT-In Directions (2022)DPDP Rule 7 (from 13 May 2027)
Who reportsCERT-In Directions (2022): Any service provider, intermediary, data centre, body corporate or government organisation that notices the incident or is told about itDPDP Rule 7 (from 13 May 2027): The Data Fiduciary
TriggerCERT-In Directions (2022): Noticing the incident, or being brought to noticeDPDP Rule 7 (from 13 May 2027): Becoming aware of a personal data breach
Who you tellCERT-In Directions (2022): CERT-InDPDP Rule 7 (from 13 May 2027): Each affected Data Principal, and the Data Protection Board
DeadlineCERT-In Directions (2022): Within 6 hoursDPDP Rule 7 (from 13 May 2027): People: without delay. Board: without delay, then a detailed report within 72 hours (or longer if the Board allows on a written request)
ChannelCERT-In Directions (2022): Email incident@cert-in.org.in, phone 1800-11-4949 or fax 1800-11-6969; formats on cert-in.org.inDPDP Rule 7 (from 13 May 2027): People: their user account or a contact method they registered with you. Board: as the Board specifies
LogsCERT-In Directions (2022): ICT system logs kept for a rolling 180 days within Indian jurisdiction, provided with the report or when CERT-In ordersDPDP Rule 7 (from 13 May 2027): Rule 6(1)(e): logs and personal data kept for one year, unless another law requires otherwise
Penalty for not reportingCERT-In Directions (2022): Punitive action under Section 70B(7) of the IT ActDPDP Rule 7 (from 13 May 2027): Up to ₹200 crore (Schedule, item 2)

Two practical points follow. First, "without delay" in Rule 7 has no number of hours attached, but it is not the same as 72 hours. The 72-hour mark is for the detailed Board report. The first Board intimation and the user notices are meant to go out as soon as you reasonably can. Second, the CERT-In duty falls on whoever notices the incident. CERT-In's FAQs say any entity that notices it must report, and that the duty cannot be passed to someone else by contract. So a SaaS vendor whose systems are hit has its own 6-hour CERT-In report to make, even though the DPDP reports belong to its customers, and a customer that is told about the incident should assume it has a CERT-In report of its own to make.

Is the Data Protection Board ready to receive reports?

The Board is established in law. As of November 2026, reports say its members have not yet been appointed, so it is not yet functioning. That does not move the date. Rule 7 and the other core duties start on 13 May 2027 regardless. Build the runbook so the Board report is ready in a structured form, and plug in the submission channel once the Board publishes one. For the full set of dates, see our DPDP Rules compliance calendar.

What must the DPDP breach notices contain?

Rule 7 lists the contents. These are the items, taken from the Rules as notified (G.S.R. 846(E)).

To each affected Data Principal (Rule 7(1))

"To the best of its knowledge", in a "concise, clear and plain manner and without delay", through her user account or a registered mode of communication:

  • (a) a description of the breach, including its nature, extent and the timing of its occurrence;
  • (b) the consequences relevant to her that are likely to arise from the breach;
  • (c) the measures implemented and being implemented to mitigate risk, if any;
  • (d) the safety measures she may take to protect her interests;
  • (e) business contact information of a person able to respond to her queries on the Data Fiduciary's behalf.

To the Board, without delay (Rule 7(2)(a))

  • A description of the breach, including its nature, extent, timing and location of occurrence, and the likely impact.

To the Board, within 72 hours (Rule 7(2)(b))

  • (i) updated and detailed information on that description;
  • (ii) the broad facts on the events, circumstances and reasons leading to the breach;
  • (iii) measures implemented or proposed to mitigate risk, if any;
  • (iv) any findings regarding the person who caused the breach;
  • (v) remedial measures taken to prevent recurrence;
  • (vi) a report on the intimations given to affected Data Principals.

Item (vi) is a data job: a record of which users were notified, when, by which channel, and whether delivery failed.

A red fire alarm call point mounted on a bare concrete wall in a dim corridor, lit by a single overhead strip light.

What does one combined breach runbook look like?

Use a single timestamp, T0: the moment anyone in the organisation becomes aware of a possible incident. That includes a vendor email, a customer complaint or an alert. Record it in the ticket at once. In law the CERT-In clock runs from noticing the incident, and the DPDP clock from the Data Fiduciary becoming aware of a personal data breach. Neither term is defined, and a first alert is not always awareness of a breach. Starting both from T0 is our conservative choice, not a legal rule. Counsel decides the legal start time.

TimeActionOwnerOutput
T0Action: Detect or receive report. Open incident ticket. Record T0 and source.Owner: Whoever spots it; on-call engineerOutput: Ticket with T0
T0 to T+1h (our target)Action: Triage. Contain if safe. Answer: CERT-In listed type? Personal data involved? Whose data (ours as fiduciary, or a customer's as processor)?Owner: Incident leadOutput: Classification, initial scope
By T+1h (our target)Action: Page the response group: incident lead, security, legal or DPO contact, comms, the business owner of the affected system.Owner: Incident leadOutput: Response group assembled
Before T+6h (legal deadline)Action: If CERT-In listed: send the CERT-In report with what is known. Preserve logs.Owner: CERT-In point of contactOutput: CERT-In submission, acknowledgement saved
Within the contract window (processor; we suggest well inside T+6h)Action: If the data is a customer's: notify each affected customer under the contract.Owner: Account owner plus incident leadOutput: Customer notices with timestamps
Without delay (legal duty, no fixed hours)Action: If a personal data breach is confirmed: first intimation to the Board (Rule 7(2)(a)) and notices to affected users (Rule 7(1)).Owner: DPO contact, legal, commsOutput: Board intimation; user notice batch started
T+24h to T+48h (our target)Action: Scope the affected set precisely. Identify root cause. Track notice delivery and resend failures.Owner: Security, data engineeringOutput: Affected-user list, delivery report
By T+72h (legal deadline)Action: Detailed Board report (Rule 7(2)(b)), or a written request for more time.Owner: Legal and DPO contactOutput: Detailed report, approval trail

The 1-hour triage target, the processor window, the 24 to 48 hour scoping window and the order of steps are our recommendation, not legal requirements. The only fixed numbers in law are the 6 hours and the 72 hours, and "without delay" has no number at all. Do not hold the user notices or the first Board intimation back to the 72-hour mark.

Who does what in a breach?

  • Incident lead. Owns the clock, the ticket and escalation.
  • CERT-In point of contact. The Directions require you to designate a Point of Contact and send their details to CERT-In. We suggest the same person submits the 6-hour report.
  • Legal and DPO contact. Confirms whether it is a personal data breach and approves notice wording.
  • Comms. Sends user notices and handles inbound questions.
  • Data engineering. Produces the affected-user list and the delivery report.
  • Scribe. Records every decision, who made it and when.

What evidence should you collect?

Preserve evidence before you clean up. Both reports, and any later inquiry, depend on it.

  • Timeline. T0, how awareness arose, and the time of every decision and notice. Synchronise clocks: the CERT-In Directions require ICT system clocks to sync to NIC or NPL NTP servers, or sources traceable to them.
  • Logs. Access logs for the affected systems, identity provider logs, cloud control-plane logs, database audit logs. Snapshot them to write-once storage. Our one-year log retention guide covers the settings on AWS, Azure and GCP.
  • Scope. The query used to build the affected-user list, the list itself, and which data fields each person had exposed.
  • Notice records. Copies of every notice sent, recipient lists, send times, delivery status and bounce handling.

How long do you need to keep logs for CERT-In and DPDP?

The CERT-In Directions require logs of all ICT systems to be kept securely for a rolling 180 days within Indian jurisdiction. DPDP Rule 6(1)(e) requires the logs that show access to personal data, and the personal data, to be kept for one year to enable detection, investigation and remediation, unless another law requires otherwise. If you set one policy, set the longer one for the logs Rule 6 covers. On location, the Directions say the logs shall be maintained within the Indian jurisdiction. CERT-In's FAQs (Q35) add that logs may also be stored outside India as long as you can produce them to CERT-In in a reasonable time. Keeping a copy in India is the simplest way to meet both readings. This is a CERT-In condition. The DPDP Act and Rules do not themselves require logs or personal data to stay in India. See our Rule 6 checklist for the other safeguards.

Breach notification templates: which fields do you need?

Build templates as structured records. The incident system fills the fields; counsel approves the wording once, in advance.

CERT-In report record

  • Reporting entity, point of contact name, designation, phone and email.
  • Time the incident occurred (if known) and time it was noticed.
  • Incident type, mapped to the Annexure I item.
  • Affected systems: hostnames, IPs, cloud accounts, applications.
  • Symptoms, indicators of compromise and actions taken so far.
  • Log locations available to share.

Check the current reporting format on the CERT-In website before you fix these fields. The Directions say it is published there and updated from time to time.

Data Principal notice record

  • Breach description: nature, extent, when it happened.
  • Data categories involved for this person.
  • Likely consequences for this person.
  • Mitigation done and in progress.
  • Steps the person can take, such as resetting a password or watching for phishing.
  • Contact person, with business email and phone.
  • Channel used, send time, delivery status.

Board intimation and 72-hour report record

  • Initial: description with nature, extent, timing, location of occurrence, likely impact.
  • Detailed: updated description; events, circumstances and reasons; mitigation implemented or proposed; findings on the person who caused it; remedial measures; summary of user notices sent.
  • Awareness time, submission time, and any extension request with its date.

What should processors and SaaS vendors build for?

The Act places the reporting duty on the Data Fiduciary, which stays responsible for processing done on its behalf under Section 8(1). It reaches the processor through the contract that Section 8(2) requires, and Rule 6(1)(f) asks that contract to provide for reasonable security safeguards. Expect customers to ask for these clauses. Our guide to DPDP for SaaS data processors covers the wider contract.

Clause to expectWhat you need to build
Notice to the customer within a fixed window of becoming awareWhat you need to build: On-call cover, a per-customer security contact list, and a notice workflow that fires from your incident ticket
Notice contents: what, when, which data, which usersWhat you need to build: Tenant-scoped access logs and a query that returns affected records per customer
Cooperation with the customer's Board and CERT-In reportsWhat you need to build: Exportable log bundles, retained for at least the customer's required period
No direct notice to the customer's users without consentWhat you need to build: A notice pipeline the customer can trigger or approve, not one you send on your own
Sub-processor flow-downWhat you need to build: The same notice window in your own vendor contracts

What window to agree is a commercial and legal decision. The customer's own duties start once it is told: user and Board notices without delay, and possibly a 6-hour CERT-In report of its own. So expect fiduciaries to ask for a short window, and it is sensible to offer one well inside 6 hours. If you can't meet that yet, find out before an incident, not during one. The Act and Rules do not say whether a processor's awareness counts as the fiduciary's awareness for the 72-hour clock. That is an open point of interpretation for counsel. Our suggestion is to engineer as if it does.

A long, empty emergency exit corridor with pale walls, the floor lit by low green safety lights and a closed fire door at the far end.

How do you run a tabletop drill for a breach?

Run a short tabletop exercise each quarter with the people named above.

  • Pick a realistic scenario. A public storage bucket. A stolen support laptop. A vendor emailing you at 7 pm on a Friday.
  • Start the clock for real. Record T0 and time every step against the 6-hour and 72-hour marks.
  • Produce real outputs. Fill the CERT-In record, run the affected-user query on test data, draft the user notice.
  • Inject surprises. The CERT-In contact is on leave. One system's logs only go back 30 days.
  • Track the gaps as fixes with an owner and a date.

The slow part is rarely writing the report. It is finding out who was affected. So scoped logs and a tested affected-user query are the first things to build.

What is the penalty for not notifying a breach under DPDP?

The Schedule to the Act sets a penalty of up to ₹200 crore for breaching the duty in Section 8(6) to notify the Board and affected Data Principals. Failing to take reasonable security safeguards to prevent a breach, under Section 8(5), carries up to ₹250 crore. One incident can raise both. The Board decides the amount after an inquiry, looking at factors in Section 33(2) such as the nature, gravity and duration of the breach and whether it was mitigated. No Significant Data Fiduciaries have been notified, and no DPDP penalties have been reported as of November 2026.

If you want help wiring this into your systems, our DPDP implementation service builds the logging, scoping and notice pipeline with your team.

Sources: Digital Personal Data Protection Act, 2023, Sections 2(u), 8(1), 8(2), 8(5), 8(6), 33 and the Schedule. Digital Personal Data Protection Rules, 2025, Rules 6 and 7 (G.S.R. 846(E), Gazette of India, 13 November 2025). CERT-In Directions under Section 70B(6) of the IT Act, 2000, No. 20(3)/2022-CERT-In, 28 April 2022, directions (i) to (iv) and Annexures I and II, and CERT-In's FAQs on the Directions (May 2022), Q13, Q30 and Q35. Information Technology Act, 2000, Section 70B(7). Last reviewed 19 November 2026.

FAQ

Is the DPDP breach deadline 72 hours?

Partly. DPDP Rule 7 requires the Data Fiduciary to tell each affected Data Principal and the Data Protection Board without delay. The 72 hours applies to the detailed report to the Board, counted from becoming aware of the breach, unless the Board allows a longer period on a written request. The duty starts on 13 May 2027.

Do I still need to report to CERT-In within 6 hours if I report under DPDP?

Yes. The CERT-In Directions of 28 April 2022 are a separate duty under the IT Act and are already in force. If the incident is one of the 20 types in Annexure I, report it to CERT-In within 6 hours of noticing it, whether or not personal data is involved. DPDP reporting is in addition.

What counts as a personal data breach under the DPDP Act?

Section 2(u) defines it as 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 includes a misdirected email, ransomware that locks you out of customer data, and staff viewing records without a business reason.

Does a Data Processor have to report a breach to the Data Protection Board?

The Act puts the Board and user reporting duty on the Data Fiduciary. A processor's duty reaches it through the contract required by Section 8(2), which should set a short window to notify the fiduciary. A processor that is a body corporate can still have its own 6-hour CERT-In reporting duty if it notices an incident on CERT-In's list.

What is the penalty for failing to notify a personal data breach in India?

Under the Schedule to the DPDP Act, failing to give the Board or affected Data Principals notice of a personal data breach can attract a penalty of up to ₹200 crore. Failing to take reasonable security safeguards to prevent the breach can attract up to ₹250 crore. The Board sets the amount after an inquiry.

Have your breach runbook ready before 13 May 2027.