Skip to main content
DPDP-AID Readiness Checkby

Breach handling

A personal data breach has to be reported to the Data Protection Board and to affected people. Detection, a response plan and a register are what make that possible in practice.

Reviewed 16 September 2026Educational self-assessment content, not legal advice

Requirements
6
Must-do
4
Penalty ceiling
Up to ₹200 crore

Failure to notify the Board or affected people of a breach. This is a statutory maximum the Data Protection Board applies case by case, never a predicted fine. 2 of these requirements are in the quick check. A must-do gap left at not started in this area caps your readiness band.

What we assess in this area

  1. MustIn the quick checkBRH-01

    A breach response plan with named roles

    When a personal data breach happens, you must inform the Board and affected people. A written plan with named roles helps you contain the breach and meet these duties quickly.

    What good looks like

    A breach response plan covers detection, containment, assessment, notification and review. Named people and backups own each step. Staff know how to report a suspected breach, and the plan is tested yearly.

    How to get there

    Write a short breach plan with clear steps. Name an incident lead, a legal contact and a communications contact. Share a simple reporting route with staff. Run a tabletop exercise.

  2. MustIn the quick checkBRH-02

    The Board is informed without delay, with a detailed report within 72 hours

    On becoming aware of a personal data breach, you must inform the Board without delay. The Rules also require a detailed report within 72 hours, covering facts, causes, harm, mitigation and people informed.

    What good looks like

    Your plan has a ready template for the first Board intimation and the 72-hour report. A named person files them, and the clock starts from the moment you become aware of the breach.

    How to get there

    Prepare templates for the initial intimation and the detailed report. Name who files them and who approves. Record the time of awareness for every incident. Practise the timeline in a drill.

  3. MustBRH-03

    Affected people are informed without delay in plain language

    You must tell each affected person about a breach without delay. The message should explain what happened, the likely impact, what you are doing and what they can do to protect themselves.

    What good looks like

    Plain-language notice templates are ready for email, SMS and in-app use. You can quickly find the contact details of affected people and send notices, with a contact point for their questions.

    How to get there

    Draft breach notice templates in plain language. Confirm you can pull affected people's contact details quickly. Decide which channels to use. Set up a helpline or email for questions.

  4. MustBRH-04

    DPDP reporting is aligned with CERT-In's 6-hour reporting

    Many cyber incidents must be reported to CERT-In within 6 hours. A personal data breach may also need reporting to the Board and affected people. Both duties can apply to the same incident.

    What good looks like

    One incident process covers CERT-In, the Board and affected people. It shows which reports apply, who files each one and the deadline, so no report is missed or delayed.

    How to get there

    Compare your CERT-In process with your breach plan. Merge them into one incident flow. Add a checklist of reports and deadlines. Name the person who files each report.

  5. ShouldBRH-05

    A breach register and post-incident review

    Keeping a record of every breach helps you show what happened and how you responded. Reviewing each incident afterwards helps you fix the cause and prevent it from happening again.

    What good looks like

    Every breach and near miss is logged with dates, data affected, people affected, reports made and actions taken. Each one gets a post-incident review, and fixes are tracked to closure.

    How to get there

    Create a breach register with standard fields. Log past incidents you know about. Hold a review within two weeks of each incident. Track agreed fixes with owners and dates.

  6. ShouldBRH-06

    Breaches can be detected, not just reported

    You can only report a breach you know about. Reasonable safeguards include the ability to spot unauthorised access, loss or leaks of personal data quickly.

    What good looks like

    Monitoring covers the systems that hold personal data. Alerts reach a named team that can act at any time. Detection is tested, and the time to detect incidents is tracked.

    How to get there

    Identify which systems holding personal data are monitored today. Add alerts for unusual access and large data exports. Set up an on-call contact. Test detection with a simulated incident.

Other areas we assess

All 13 areas

Check this area against your own business

The free assessment scores this area with the rest and shows you where it ranks against your other gaps.

The DPDP-AID Readiness Check is a free self-assessment tool for educational and self-learning purposes. It is not legal advice. Disclaimer

A free self-assessment tool for educational use. Not legal advice.