Breach Incident Response

Never Miss the 72-Hour Breach Window

Log a breach. The 72-hour clock starts. We handle the rest — Board notification, principal alerts, evidence package.

Your penalty exposure
₹200Crbreach notification failure (S.8(6))

Failing to notify the Data Protection Board within 72 hours is itself a ₹200 crore violation — on top of whatever caused the breach. No grace period.

From detection to evidence package in under an hour

1
Log the breach
Enter basic incident details. The 72-hour Board notification clock starts immediately.
2
Auto-classify severity
Our classifier scores the incident (data sensitivity, affected count, category) and assigns SEV 1–4.
3
Draft Board notification
Pre-filled DPDPA S.8(6) format notification assembled from incident data. One-click send.
4
Notify affected principals
Batch notification to affected data principals with delivery receipts. Immutably logged.
5
Export evidence package
One-click export of the full regulator evidence package: incident log, notifications, timestamps.

Every tool you need inside 72 hours

Core

Auto-Severity Classifier

Score-based classification using affected count, data sensitivity, and category. SEV 1–4 scale.

72-Hour Board Notification Workflow

Prescribed DPDPA format pre-filled from incident data. Countdown timer visible at all times.

Affected Principal Notification

Batch email to affected principals with delivery receipts and immutable dispatch log.

Immutable Incident Log

All incident events stored with no UPDATE or DELETE. DB-level append-only enforcement.

Slack War-Room Webhook

Sev1/Critical incidents automatically fire a Slack alert to your security war-room channel.

Regulator Evidence Package

Export a complete PDF evidence package including incident timeline, notification records, and CERT-In format report.

72hr
Board deadline
SEV 1–4
Auto-classified
Immutable
Incident log
₹200Cr
Penalty coverage
Available from Starter plan onwards

Breach logging, severity classification, Board notification, and evidence export on all plans.

DPDPA breach obligations — answered

When exactly does the 72-hour clock start under DPDPA?+

Under DPDPA S.8(6), the 72-hour window begins the moment a Data Fiduciary "becomes aware" of a personal data breach. DPDPA Shield logs the exact UTC timestamp when you create an incident record — establishing a clear, defensible start time in your evidence trail. This timestamp is immutable and cannot be edited after the fact.

What must the Board notification contain under DPDPA S.8(6)?+

The prescribed notification format must include: (1) nature of the breach and categories of personal data affected, (2) estimated number of data principals affected, (3) likely consequences of the breach, (4) remediation and mitigation measures taken or proposed, and (5) contact details of your Data Protection Officer. DPDPA Shield pre-fills this from your incident data — you review and send in one click.

Are affected data principals also notified of a breach?+

Yes, S.8(6) also requires notifying affected data principals "in such manner as may be prescribed." DPDPA Shield handles batch email notification to all affected principals with delivery receipts stored in an immutable log. The notification content, timestamps, and delivery status are all included in your regulator evidence package.

What penalty applies if the 72-hour deadline is missed?+

Failure to notify the Data Protection Board within 72 hours carries a penalty of up to ₹200 crore under S.8(6) — separate from any penalty arising from the breach itself. There is no grace period. The DPDPA Shield countdown timer with auto-escalation and Slack war-room alerts is specifically designed to prevent this outcome.

Be ready before the next breach.

Set up breach workflows in under 15 minutes. Free trial, no credit card required.