dpdpact.co.in

This website belongs to KavachOne Solutions Pvt. Ltd., having its corporate office located in Noida, India.
Data Breach Response Under DPDP Act India: 72-Hour Notification Guide 2025 | KavachOne
Critical Compliance Obligation

Data Breach Response
Under India's
DPDP Act
The 72-Hour Guide

When a personal data breach occurs, the clock starts immediately. India's DPDP Act imposes strict notification obligations — to the Data Protection Board and to affected individuals. Without a tested response plan, organisations face both reputational catastrophe and penalties up to ₹250 crore. Be ready before it happens.

⏱ 72-Hour Response Window
72
Hours to Notify DPB
T+0 Breach detected / confirmed 🔴
T+1h Incident response team activated 📞
T+4h Containment measures applied 🛡️
T+12h Scope & impact assessment 🔍
T+24h DPB preliminary notification 📋
T+48h Data principal notifications begin 📬
T+72h Full DPB report submitted ⚠️ 🏛️
72 HrsDPB Notification Deadline
₹250 CrMax Penalty for Security Failures
₹200 CrPenalty for Breach Notification Failure
100%Affected Principals Must Be Notified
AnnualBreach Simulation Required
What Is a Breach?

What Counts as a Personal Data Breach Under DPDP?

The DPDP Act defines a personal data breach broadly — any incident that leads to accidental or unlawful destruction, loss, alteration, unauthorised disclosure, or access to personal data. These six categories are the most common triggers.

🔓
Unauthorised Access
An external attacker, insider threat, or compromised account gains access to personal data without authorisation — the most common breach type.
e.g. Hacker gains access to customer database via SQL injection; rogue employee exports customer list
☁️
Accidental Exposure
Personal data is unintentionally made accessible — a misconfigured cloud bucket, an email sent to the wrong recipient, or a publicly accessible database.
e.g. AWS S3 bucket with customer PII accidentally set to public; CSV with personal data emailed externally
🗑️
Data Loss or Destruction
Personal data is permanently lost or destroyed — whether through ransomware, hardware failure, or accidental deletion without adequate backup.
e.g. Ransomware encrypts customer database with no recoverable backup; server hardware failure destroys user records
✏️
Unauthorised Alteration
Personal data is modified without authorisation — changing user account details, manipulating health records, or altering financial data.
e.g. Database tampered to change account holders' contact details; medical records altered by unauthorised party
🤝
Third-Party Processor Breach
A data processor or vendor you share personal data with suffers a breach — you remain liable as the Data Fiduciary for the personal data processed on your behalf.
e.g. Your CRM provider suffers a breach exposing your customers' contact data; payment processor compromised
📧
Phishing & Social Engineering
Employees are tricked into revealing credentials or authorising data transfers — resulting in unauthorised access to personal data systems.
e.g. CFO phishing attack gains access to HR system with employee PII; fake IT support call obtains database passwords
6-Phase Response Playbook

The DPDP Data Breach Response Playbook

Every minute from detection to containment matters. Follow this six-phase playbook to respond correctly — and meet every DPDP notification obligation.

Phase 0
🔴 Detection & Triage — Is This a Breach?
T+0 to T+2 Hours

The moment a potential incident is identified — by monitoring systems, staff reports, or external notification — triage begins. Establish: Has personal data been exposed, lost, or altered? How? What systems and data are affected?

Acknowledge the incident and log the detection time precisely
Activate the incident response team immediately
Isolate affected systems to prevent further exposure
Classify incident severity (Critical / High / Medium)
Confirm whether personal data is involved
Preserve all logs and forensic evidence
Phase 1
🟠 Containment — Stop the Bleeding
T+2 to T+8 Hours

Prevent the breach from spreading. Apply immediate technical controls to stop ongoing unauthorised access or data exfiltration, while preserving evidence for investigation and regulatory reporting.

Revoke compromised credentials and access tokens
Block network access from attacker IP addresses
Disable or quarantine affected systems / accounts
Patch exploited vulnerabilities where possible
Notify cloud/hosting provider if infrastructure involved
Secure all forensic artefacts — logs, snapshots, emails
Phase 2
🟡 Assessment — Scope, Impact & Obligations
T+8 to T+24 Hours

Conduct a thorough assessment of the breach — identifying exactly what personal data was exposed, how many data principals are affected, and the likely harm to those individuals. This assessment drives notification decisions.

Query ROPA to identify all affected personal data types
Determine number of affected data principals
Assess risk of harm: financial loss, discrimination, identity theft
Determine breach notification obligations under DPDP
Identify affected third-party processors to notify
Prepare initial DPB preliminary notification document
Phase 3
🟢 Notification — DPB & Data Principals
T+24 to T+72 Hours ⚠

Meet the DPDP Act's notification obligations — reporting to the Data Protection Board within 72 hours and notifying affected data principals as soon as possible. Accuracy and completeness are critical — late or inaccurate notifications attract additional penalties.

File full breach notification with DPB by T+72h
Include all mandatory DPB notification fields
Notify all affected data principals via registered contact
Notification must include: what happened, data exposed, recommended actions
Notify affected third-party processors and vendors
Activate breach communication plan — PR, legal, leadership
Phase 4
🔵 Recovery — Restore & Remediate
T+72h to T+2 Weeks

Restore affected systems and data from clean backups, implement remediation measures to close the vulnerability exploited, and validate that no residual attacker presence remains in the environment.

Restore systems from pre-breach clean backups
Implement full remediation of exploited vulnerability
Reset all potentially compromised credentials
Conduct thorough penetration test post-remediation
Verify no residual attacker access or backdoors remain
Update DPB with remediation progress and timeline
Phase 5
🟣 Post-Breach Review — Learn & Improve
T+2 Weeks to T+4 Weeks

Conduct a formal post-breach review to understand root cause, assess response effectiveness, update the breach response plan, and implement systemic improvements to prevent recurrence. Document everything for the DPB.

Document full incident timeline and root cause analysis
Identify what response steps worked and what failed
Update breach response plan based on lessons learned
Implement systemic security improvements
Update ROPA and DPIA to reflect new risk knowledge
Submit final closure report to DPB
Notification Obligations

DPDP Breach Notification — What Must Be Reported

The DPDP Act imposes specific notification requirements for both the Data Protection Board and affected data principals. Here is exactly what each notification must contain.

🏛️ Data Protection Board (DPB) Notification
Required within 72 hours of breach confirmation
What
Nature of the breach — how it occurred, the attack vector or cause, and when it was detected
Scope
Data categories and volume — what personal data was exposed, how many data principals affected, and sensitivity classification
Impact
Likely consequences — assessed risk of harm to affected data principals (financial loss, identity theft, discrimination, etc.)
Action
Measures taken — containment steps already applied, ongoing remediation, and timeline for full resolution
Contact
DPO or nominated contact — name, designation, and contact details for the DPB's ongoing liaison on the incident
Basis
Reason for any delay — if notification is approaching 72 hours, document the reason for any delay in detecting or assessing the breach
👥 Data Principal Notification
Required as soon as practicable after DPB notification
What
Description of the breach — plain language explanation of what happened, in terms an ordinary person can understand
Data
Data specifically affected — which of their personal data was exposed (name, phone, financial data, health records, etc.)
Risk
Risk to them — what harm could result from the breach and the likelihood of that harm occurring to the individual
Action
Steps they should take — specific protective actions the individual can take (change passwords, freeze credit, monitor for fraud, etc.)
Contact
How to get help — dedicated helpline, email, or portal where individuals can ask questions or report harms they experience
Remediation
What you are doing — steps your organisation is taking to address the breach and prevent recurrence — reassures principals and demonstrates accountability
DPDP Breach Penalties

The Cost of Getting Breach Response Wrong

Under the DPDP Act, breach-related violations attract some of the highest penalties in the legislation.

Violation DPDP Act Section Maximum Penalty Mitigating Factor
Failure to implement adequate security safeguards §8(5) ₹250 Crore Having a tested breach plan & DPIA evidence reduces penalty
Failure to notify DPB of breach within required timeframe §8(6) ₹200 Crore Prompt notification and cooperation with DPB mitigates
Failure to notify affected data principals of breach §8(6) ₹200 Crore Timely, accurate notification to all affected principals
Children's data breach — inadequate protection §9 ₹200 Crore Separate consent controls and age-verification systems
Third-party processor breach — inadequate DPA controls §8(3) ₹150 Crore Comprehensive DPAs with security requirements evidenced
Failure to produce breach notification records on DPB request §25 ₹50 Crore Complete incident documentation maintained throughout
Breach Preparedness

Is Your Organisation Breach-Ready?

The organisations that respond best to breaches are those that prepared before one happened. This checklist covers the 18 must-have elements of DPDP breach readiness.

📋
Documented Breach Response Plan
  • Incident classification criteria defined
  • Response team roles and contacts documented
  • Escalation matrix approved by leadership
  • DPB notification templates pre-prepared
🔍
Detection & Monitoring
  • Security monitoring and SIEM deployed
  • Anomaly detection alerts configured
  • PII Scanner integrated with alerting
  • Third-party breach notification monitoring
🗺️
Complete ROPA (Data Map)
  • All personal data stores documented in ROPA
  • Data flows and third parties mapped
  • PII Scanner reconciled with ROPA
  • ROPA enables instant breach scope assessment
📬
Notification Workflows
  • DPB notification templates drafted and approved
  • Data principal notification channels confirmed
  • ConsentiQo notification automation configured
  • Dedicated breach helpline number reserved
🎭
Annual Simulation Exercise
  • Tabletop exercise conducted annually
  • Full team (IT, Legal, PR, HR) participated
  • Exercise scenario documented
  • Lessons learned actioned and plan updated
🔗
Third-Party Readiness
  • All DPAs include breach notification timelines
  • Vendor breach notification contacts maintained
  • Third-party TPRM programme active
  • Sub-processor breach obligations documented

Run a Breach Simulation Before a Real Breach Runs You

KavachOne facilitates annual DPDP breach response tabletop exercises — testing your team, your plan, and your notification workflows under realistic pressure, without the stakes of a real incident.

  • Realistic breach scenario briefed to response team
  • Team works through detection, triage, and containment decisions
  • DPB notification draft prepared under time pressure
  • Data principal notification workflow tested end-to-end
  • Facilitator debrief identifies gaps and improvement actions
  • Updated breach response plan delivered post-exercise
🎭 Book a Breach Simulation

Conducted by KavachOne's certified incident response and DPDP compliance experts.

Don't Wait for a Breach to Build Your Response Plan

KavachOne designs, documents, and tests DPDP-compliant data breach response plans for Indian organisations — integrating with your ROPA, PII Scanner, and ConsentiQo platform to ensure you can respond and notify within 72 hours, every time.

FAQs

Common Questions About DPDP Breach Response

Does the 72-hour notification clock start from when the breach occurred, or when it was detected?
The 72-hour notification window under the DPDP Act starts from when the Data Fiduciary becomes aware of the breach — i.e. from detection, not from the time the breach actually occurred. This is an important distinction: a breach that occurred three weeks ago but was only discovered today must still be reported to the DPB within 72 hours of discovery. This reinforces the need for robust monitoring to detect breaches quickly.
Do we need to notify every single data principal affected by a breach?
The DPDP Act requires notification to all data principals whose personal data has been involved in a breach — there is no minimum threshold of affected individuals below which notification can be waived. However, the DPB may issue guidance on breach categories where the risk of harm is so low that principal notification is not required. Until such guidance is issued, the safest approach is to notify all affected principals.
What if our third-party vendor/processor suffers a breach involving our customer data?
As the Data Fiduciary, you remain responsible for the personal data you have transferred to a data processor — even if that processor suffers the breach. Your DPA with the vendor should require them to notify you promptly upon discovering a breach. Once notified, your own 72-hour DPB notification clock starts. Your vendor's failure to notify you promptly does not excuse your own notification delay.
Can demonstrating a tested breach response plan reduce DPDP penalties?
Yes — significantly. The Data Protection Board's penalty assessment framework considers factors including the organisation's good-faith compliance efforts, the measures in place before the breach, and the effectiveness of the response. A documented and tested breach response plan, combined with prompt notification and full cooperation with the DPB, are the most powerful mitigating factors available in a breach enforcement proceeding.
How does KavachOne's breach response service integrate with ConsentiQo?
KavachOne's breach response framework integrates directly with ConsentiQo for data principal notification workflows. When a breach is confirmed, ConsentiQo's multi-channel notification system can send personalised breach notifications to affected data principals via email and SMS — using their registered contact details and consent record data from the platform. This ensures timely, documented, and compliant notification to every affected individual.
Data Breach Response India DPDP Act Data Breach 72-Hour Breach Notification India DPDP Breach Notification DPB Data Breach Plan India Incident Response DPDP DPDP Security Safeguards KavachOne Breach Response Data Breach Penalty India Data Protection Board Notification DPDP Compliance 2025 ConsentiQo Breach Simulation India ROPA Breach Scope DPDP Act 2023