[Analysis] Incident Response Plan under the DPDP Act – Six Phases | Incident Register | CERT-In and Board Notification
- Blog|Company Law|
- 12 Min Read
The incident response plan under the DPDP Act and the CERT-In Directions: incident v breach, India’s reporting clocks, the response team, six phases, the two-tier incident register and the Board.
- By Taxmann
- |
- Last Updated on 16 November, 2026
Table of Contents
- What is an incident response plan?
- Is every security incident a personal data breach?
- What are the breach reporting deadlines in India?
- Who should be on the incident response team?
- What are the six phases of incident response?
- What must the incident register record?
- How should the plan handle communication and board oversight?
- Quick answers
1. What is an incident response plan?
An incident response plan is an organisation’s prepared answer to the questions data protection law asks after a security incident: what did it do when it knew, how quickly did it act, who did it tell and when, what records did it keep, and did it have a plan before the incident or was it improvising. Abha Tiwari and Aditya Singhania treat the plan as part of the security obligation itself. From the EU General Data Protection Regulation (GDPR) to the DPDP Act, an organisation that processes personal data without a tested and operational incident response capability has not implemented appropriate technical and organisational measures, however sophisticated its other security controls.
The plan serves three purposes at once. Operationally, it lets the organisation respond with speed, discipline and coordination, limit the damage and restore normal operations. Legally, it is the framework through which detection, assessment, containment, notification and remediation are carried out within the timelines the law sets. Culturally, it shows that data protection is practised before a crisis rather than improvised within it.
The authors set five objectives for an effective plan:
- Guidance: clear steps from the moment of detection through to post-incident review.
- Accountability: defined roles and authority, so that no time is lost deciding who is in charge, who decides and who communicates.
- Compliance: meeting notification timelines, content requirements, regulatory engagement protocols and evidence preservation standards.
- Communication: clear processes for the response team, senior management and the board of directors, regulators and affected individuals.
- Improvement: structured post-incident review, so that every incident, breach or not, strengthens security and the response itself.
2. Is every security incident a personal data breach?
No. Every personal data breach is a security incident, but not every incident is a breach, and the legal consequences of a breach (notification duties, reporting timelines, potential liability to individuals) do not attach to every incident. Labelling an incident a breach before that has been properly determined is itself a governance failure that can create regulatory liability.
An incident is any event with the potential to affect the confidentiality, integrity or availability of information assets, including personal data, from failed login attempts and malware detections to system outages and physical security violations. Most incidents are not breaches. The DPDP Act defines a personal data breach, in section 2(u), 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.
| Dimension | Security incident | Personal data breach |
|---|---|---|
| Legal trigger | Not in itself a trigger for notification | Triggers mandatory notification in most frameworks |
| CERT-In | A reportable cyber security incident must be reported within 6 hours | The 6-hour reporting applies to notifiable cyber security incidents |
| DPDP Act | Internal management | Notification to the Board and to affected Data Principals under the Rules |
| Examples | A failed intrusion attempt; malware detected and quarantined; a system outage without data access | Ransomware with data exfiltration; misconfigured cloud storage exposing customer data; insider theft of customer records |
| Response | Internal containment, investigation, remediation and documentation | All of that, plus legal assessment, notification, regulatory engagement and DPO involvement |
The plan should settle this question early, because the next steps depend on it. A limited response may do for an incident; a breach brings in other teams, fixed timelines, intimation to individuals and legal requirements.
3. What are the breach reporting deadlines in India?
India’s obligations come from three overlapping sources that must be read together: the DPDP Act and the DPDP Rules; the Information Technology Act, 2000 (IT Act) with the CERT-In Directions made under it; and sector-specific frameworks of the RBI, SEBI and IRDAI.
| Who must be told | Deadline | Source |
|---|---|---|
| Each affected Data Principal | Without delay, on becoming aware of the breach | Section 8(6) of the DPDP Act with Rule 7 |
| The Board: first intimation of the breach, its nature, extent, timing, location and likely impact | Without delay | Rule 7 |
| The Board: updated and detailed report | Within 72 hours of becoming aware, or a longer period the Board allows on a written request | Rule 7 |
| CERT-In, for a reportable cyber incident | Within six hours of noticing it or being brought to notice of it | CERT-In Directions, April 2022 |
| Sector regulators | Scheduled commercial banks must report unusual cyber security incidents within two to six hours; SEBI and IRDAI frameworks set their own reporting duties | RBI Cyber Security Framework for banks; SEBI Cybersecurity and Cyber Resilience Framework; IRDAI Information and Cyber Security Guidelines |
Three features of the DPDP duty stand out. The clock runs from awareness, not from the end of the investigation, and it runs through weekends and holidays. There is no materiality threshold: unlike the GDPR, the Indian framework requires intimation to every affected individual in every case. And the Schedule to the DPDP Act provides a penalty of up to ₹200 crore for failing to give intimation of a breach, alongside up to ₹250 crore for failing to take reasonable security safeguards.
The intimation to each individual must be in concise, clear and plain language, sent through the user account or a registered mode of communication. It must describe the nature, extent, timing and location of the breach, its likely consequences, the mitigation measures taken or being taken, the safety measures the individual can take, and business contact details for someone who can answer questions. The detailed report to the Board covers the broad facts, circumstances and reasons for the breach, the measures to mitigate risk, any findings on the person who caused it, the remedial measures taken to prevent recurrence, and a report on the intimations given to Data Principals. The two Rule 7 intimations, the five elements owed to each Data Principal and when the seventy-two-hour clock starts are covered in personal data breach intimation under Rule 7.
CERT-In’s reportable incidents are listed in the Annexure to its Directions and include data breaches, ransomware, unauthorised access, and targeted scanning or probing of critical networks and systems. The Directions also require ICT logs to be kept for 180 days within India, and non-compliance attracts liability under section 70B(7) of the IT Act. Until section 43A of the IT Act is omitted on 13 May 2027, it and Rule 8 of the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011 (SPDI Rules) also matter: they impose no notification duty, but the response must be able to show that reasonable security practices were in place and followed.
The result is that, once Rule 7 is in force, a single incident affecting personal data held by a regulated financial entity starts several clocks at the same moment, and the binding operational deadline is six hours, not 72. Because there is no risk filter, the assessment period cannot be used to decide whether individuals need to be told, only how to tell them. And because the CERT-In clock is already running while the DPDP clocks become enforceable only in May 2027, the authors’ advice is to build and rehearse the full architecture without waiting for commencement, with pre-approved templates and a single decision owner.
4. Who should be on the incident response team?
A standing, pre-designated team drawn from every function the incident touches, with defined membership, clear authority and tested protocols. A ransomware attack is more than an IT problem: it creates legal risk, regulatory obligations, communication problems, financial impact and governance concerns, so no single team can handle it alone.
| Function | Role in the response |
|---|---|
| Legal and privacy team | Assesses notification obligations and the frameworks that apply, drafts regulatory communications, advises on evidence preservation |
| Data Protection Officer, where appointed | Involved in all breach-related decisions; point of contact with supervisory authorities; monitors compliance with notification obligations |
| IT and information security | Leads the technical investigation, contains the incident, preserves forensic evidence and assesses the scope of the compromise |
| CISO or information security head | Chairs the technical response, links IT and senior management, coordinates external forensic specialists |
| Human resources | Handles employee-related incidents such as insider threats and accidental disclosure, and oversees staff communications |
| PR and communications | Manages media statements, social media and customer communications |
| Customer engagement | Handles communications to affected individuals and runs the helpline or designated contact point |
| Finance | Assesses financial exposure, manages insurance claims and authorises emergency spending |
| Procurement | Manages the response of third-party vendors and invokes the breach provisions of data processing agreements |
| Internal audit | Gives an independent assessment of the response and leads the post-incident review, reporting to the Audit Committee and the board of directors |
| Business continuity and disaster recovery | Activates continuity plans and manages restoration of systems and availability |
| Facility management | Handles physical security: physical access breaches, loss of physical media and securing affected premises |
Two governance rules make the team work. A designated Team Leader holds pre-authorised authority to activate the procedure, convene the team, decide whether an incident is a personal data breach, approve regulatory notifications and authorise emergency expenditure, and the Team Leader’s determination is final if the team disagrees. Each function names a Single Point of Contact (SPOC), reachable at any hour and trained in the role, whose contact details, including out-of-hours mobile numbers, are kept in the plan and updated at every review.
The most common failure is not the absence of a plan but a plan that has never been tested. One that exists only as a document in a folder is, in the book’s phrase, a paper tiger; one exercised through tabletop simulations, red team exercises and live drills is a working capability.
5. What are the six phases of incident response?
Detection and reporting; initial assessment and triage; containment; investigation and evidence preservation; notification and regulatory compliance; and remediation and post-incident review. The phases run in sequence but often overlap, and the plan must treat all six with equal rigour.
| Phase | What happens | The rule to remember |
|---|---|---|
| 1. Detection and reporting | Alerts and reports arrive from security tools, employees, customers, processors, outside parties or CERT-In itself, through a single, round-the-clock reporting channel connected to the SPOC | Report, assess and document every potential incident, including false alarms |
| 2. Initial assessment and triage | A time-stamped assessment of seven dimensions: scope of IT impact, nature of the data at risk, timeline, business impact, risk to data subjects, probable cause, and whether the event is a breach | The decisions of the first forty-eight hours decide whether legal obligations are met |
| 3. Containment | Isolate affected systems, preserve evidence before patching, reset credentials systematically and engage external specialists early | Disconnect from the network, do not power off; report to CERT-In within six hours, in parallel with containment |
| 4. Investigation and evidence preservation | Technical forensics, legal analysis and an assessment of the impact on individuals, run together; logs, memory dumps, forensic images, traffic captures and records of every action are preserved | Use forensically sound imaging, a documented chain of custody and cryptographic hashing; decide on legal professional privilege at the outset |
| 5. Notification and regulatory compliance | Authorities and affected individuals are notified, and the board of directors and senior management are kept informed at each phase | Notify before everything is known, accurately on the facts known, and update as information emerges |
| 6. Remediation and post-incident review | Fix the vulnerability, analyse the root cause, review the team’s performance, update the plan, follow up with regulators, report to the board of directors and update training | Treat the review as a legal obligation, not an administrative formality |
Notices to individuals should be direct (email, letter or SMS where possible), clear and empathetic, give a staffed contact point rather than a generic website, and be followed by updates as the investigation progresses. The book’s account of Uber’s 2016 breach shows the cost of the opposite course: the company paid the attackers to delete the data and stay silent, and the episode produced what remains the first criminal conviction of a security executive arising from the handling of a data breach. Concealment, as the authors put it, cannot be treated as an option in risk management.
6. What must the incident register record?
Every incident, including those that turn out not to be breaches. Recording an incident that was assessed and found not to be a breach is what evidences the assessment; a register containing only breaches looks, after the event, like one kept only when concealment was no longer possible. Article 33(5) of the GDPR makes the duty to document breaches explicit, and the authors read it as implicit in the accountability principle of the DPDP Act.
| Tier | Applies to | Minimum content |
|---|---|---|
| Tier 1 | Every incident, including those assessed as not amounting to a personal data breach | Date and time of detection; date and time of occurrence, where known; nature and description; systems and data affected; initial assessment of impact; name and role of the person who detected or reported it; actions taken; and whether it is a personal data breach, with the reasons |
| Tier 2 | In addition, every personal data breach | Categories of personal data and of data records affected; approximate numbers of individuals and of records; likely consequences for individuals; a risk rating of low, medium or high; the notification decision for the regulator and for individuals, with reasons, including reasons for not notifying; date, method and content of each notification; reference numbers issued by any regulator; remediation measures; and the date and findings of the post-incident review |
The register must be kept even for incidents assessed as not requiring notification, because the assessment and its reasons are themselves a compliance record. A regulator examining a breach notification may ask for the complete register to see whether earlier incidents should have been notified and were not.
7. How should the plan handle communication and board oversight?
With principles and templates agreed in advance. The communication principles are accuracy before speed, empathy before defensiveness, consistency across channels, a single spokesperson, and proactive rather than reactive communication. Inconsistency between a regulatory notification and a public statement is itself a compliance failure.
The plan should carry pre-drafted templates for a notification to CERT-In, a notification to the Data Protection Board, notifications to affected individuals in email, letter and SMS versions, a media statement, an internal staff communication and a briefing note for the board of directors. Templates save time under pressure, keep messages consistent and allow legal review before the incident rather than during it.
Four Indian features shape the plan:
- Dual notification. The same incident may have to be reported to CERT-In within six hours and to the Board within the period the DPDP Rules prescribe. These obligations are cumulative, to different authorities for different purposes, so the plan must say which applies to which incident, who is responsible for each, and how the two are kept consistent.
- Sector rules. Banking, insurance, securities, telecommunications and health carry sector obligations that may be more demanding, and RBI-regulated entities may face shorter reporting timelines than the DPDP framework.
- Reaching individuals at scale. Many customer records hold contact details that are stale, intermediated through agents or platforms, or shared, so the plan must provide supplementary channels such as public notice, website communication and social media.
- The board of directors. It should approve the plan, receive post-incident reports and satisfy itself that the response capability is adequate. A board first briefed at the moment of a significant breach has no basis on which to show the Data Protection Board that governance was adequate.
8. Quick answers
What is the difference between a security incident and a personal data breach?
A security incident is any event that could affect the confidentiality, integrity or availability of information assets; most are not breaches. A personal data breach, defined in section 2(u) of the DPDP Act, is unauthorised processing or accidental disclosure, acquisition, sharing, use, alteration, destruction or loss of access to personal data that compromises it.
What is the deadline to report a personal data breach under the DPDP Act?
Under section 8(6) and Rule 7, which apply from 13 May 2027, affected individuals and the Board must be told without delay, and a detailed report must reach the Board within 72 hours of becoming aware, or a longer period the Board allows on a written request. The clock runs from awareness, through weekends and holidays.
Within how many hours must a cyber incident be reported to CERT-In?
Within six hours of noticing it or being brought to notice of it, under the CERT-In Directions of April 2022. This makes six hours, not 72, the binding deadline for an incident that also involves personal data.
Must every affected individual be told of a breach under the DPDP Act?
Yes. Unlike the GDPR, the Indian framework has no materiality threshold, so every affected Data Principal must receive intimation in every case.
What are the six phases of incident response?
Detection and reporting; initial assessment and triage; containment; investigation and evidence preservation; notification and regulatory compliance; and remediation and post-incident review.
Who decides whether an incident is a personal data breach?
The plan should give that decision to a designated Team Leader with pre-authorised authority. If the response team disagrees about whether to activate the procedure or whether an event is a breach, the Team Leader’s determination is final.
What is the penalty for failing to report a personal data breach?
The Schedule to the DPDP Act provides a penalty of up to ₹200 crore for failing to give intimation of a breach, and up to ₹250 crore for failing to take reasonable security safeguards.
Chapter 20 of Digital Personal Data Protection Law Practice and Compliance by Abha Tiwari and Aditya Singhania builds the incident response plan from first principles: the distinction between an incident and a breach, India’s layered reporting framework set against the GDPR and other regimes, the make-up and governance of the response team, the six-phase response, a two-tier incident register, communication in a crisis and the features of Indian law a plan must address, with enforcement cases from Equifax to British Airways.
Taxmann.com | Learning has a webinar held on 2 September 2023, “The Digital Personal Data Protection Act 2023 – Key Takeaways & Next Steps”, in which Abha Tiwari, a co-author of the book, discussed the Act with Kanishk Gaur and Lagna Panda, including the cyber security measures Data Fiduciaries must consider.
Taxmann.com | Store has the Information Technology Act 2000 with Rules – Bare Act with Section Notes, whose Rules include the Information Technology (The Indian Computer Emergency Response Team and Manner of Performing Functions and Duties) Rules, 2013, and Taxmann.com | Research carries the Digital Personal Data Protection Rules, 2025, including Rule 7, under Indian Acts & Rules.
Related reading: breach, enforcement and penalties under the DPDP Act · obligations of Data Fiduciaries · sector guidance for FinTech and BFSI · the DPDP Act and Rules timeline.
More in this series: the SPDI Rules and the DPDP Act · the Record of Processing Activities (ROPA) · data retention and erasure · the privacy notice under Rule 3 · the data processing agreement · data localisation and cross-border transfers · employee data and workplace monitoring · exemptions under the DPDP Act · legitimate uses under section 7 · the Data Protection Board of India · how a DPDP compliance audit is conducted · Significant Data Fiduciary obligations · Consent Managers under the DPDP framework · personal data breach intimation under Rule 7 · handling Data Principal rights requests · Data Fiduciary, Data Processor or both · children’s data and verifiable parental consent.
Law stated as updated till October 2026.
Disclaimer: The content/information published on the website is only for general information of the user and shall not be construed as legal advice. While the Taxmann has exercised reasonable efforts to ensure the veracity of information/content published, Taxmann shall be under no liability in any manner whatsoever for incorrect information, if any.

Taxmann Publications has a dedicated in-house Research & Editorial Team. This team consists of a team of Chartered Accountants, Company Secretaries, and Lawyers. This team works under the guidance and supervision of editor-in-chief Mr Rakesh Bhargava.
The Research and Editorial Team is responsible for developing reliable and accurate content for the readers. The team follows the six-sigma approach to achieve the benchmark of zero error in its publications and research platforms. The team ensures that the following publication guidelines are thoroughly followed while developing the content:
- The statutory material is obtained only from the authorized and reliable sources
- All the latest developments in the judicial and legislative fields are covered
- Prepare the analytical write-ups on current, controversial, and important issues to help the readers to understand the concept and its implications
- Every content published by Taxmann is complete, accurate and lucid
- All evidence-based statements are supported with proper reference to Section, Circular No., Notification No. or citations
- The golden rules of grammar, style and consistency are thoroughly followed
- Font and size that’s easy to read and remain consistent across all imprint and digital publications are applied


CA | CS | CMA