🇮🇳DPDP Act DPDP-7Rule: DPDP-007critical

Breach Notification

Description

Data fiduciary must notify Data Protection Board + affected data principals of personal data breach.

⚠️ Risk Impact

Timely notification is required; DPDP doesn't yet have GDPR's 72-hour clock but expects 'as soon as practicable'.

🔍 How EchelonGraph Detects This

DPDP-007Automated scanner rule

EchelonGraph's Tier 1 Cloud Scanner automatically checks for this condition across all connected cloud accounts. Violations are flagged as critical-severity findings with remediation guidance.

🔧 Remediation

Documented breach response runbook. Pre-built notification templates. DPB notification authority documented.

💀 Real-World Attack Scenario

An Indian SaaS experienced a breach Tuesday; notified DPB Friday. Late notification was treated as separate violation; ₹50 crore added to underlying breach penalty.

💰 Cost of Non-Compliance

Notification delay: ₹50-₹150 crore additional.

📋 Audit Questions

  • 1.Breach response runbook?
  • 2.DPB notification template?
  • 3.Authority documented?

⚡ Common Pitfalls

  • Investigation extends past 'practicable'
  • Templates missing
  • Authority unclear

📈 Business Value

Timely notification prevents double-penalty.

⏱️ Effort Estimate

Manual

Pre-built templates + on-call

With EchelonGraph

EchelonGraph IR runbook with DPB workflow

🔗 Cross-Framework References

GDPR-Art33

Automate DPDP Act DPDP-7 compliance

EchelonGraph continuously monitors this control across all your cloud accounts.

Start Free →