DPDP Comic Book - Edition 4
The 72-Hour
Breach Reporting
Clock Has Started
A breach just hit. Time is running. Does your team know what to do in the next 72 hours?
Learn how Consent Chaudhary and his team navigate the DPDP Act’s breach reporting timelines.


Why This Comic Exists
DPDP breach response cannot stay locked inside incident response documents.
Your teams need to understand what happens during a real breach: systems get compromised, timelines start shrinking, vendors get involved, boards need answers, and regulators expect action.
This comic makes breach preparedness:
Simple to understand
Easier to discuss
Harder to ignore

What You’ll Learn Inside
Through Consent Chaudhary’s world, the comic breaks down breach response situations such as:
How a breach gets detected, contained, and logged before evidence disappears
How to scope impact across systems, vendors, and data principals
What a board conversation looks like when 1.4 million records are on the line
How to notify affected individuals clearly, without making the situation worse
What the DPBI expects in a 72-hour report, and what “defensible” means in practice
Why a resigning employee’s active credentials can become a major liability

Built For Teams Preparing
for the DPDP Era
This comic is designed for:
DPOs who need a breach playbook people will actually read
CXOs who own accountability when the DPBI comes asking
Legal and compliance teams preparing for May 2027
Engineering and infosec teams managing security incidents
Teams responsible for breach response, escalation, and reporting






