DPDP Act guide · 3 controls
Security & Breach Response Under the DPDP Act
Security carries the largest penalties in the Act. You need reasonable safeguards, controlled and logged access, and a plan to report a personal data breach to the Data Protection Board and the people affected.
Reasonable security safeguards Sec 8(5), Rule 6
Personal data is protected with sensible safeguards such as encryption, masking, access control and tested backups.
Why it matters
Failing to take reasonable security safeguards carries the highest penalty: up to ₹250 crore.
How to close the gap
Encrypt personal data at rest and in transit, limit who can reach it, test backups, and write these down in a security policy.
Evidence that shows it's in place
- Information security policy
- Encryption standard and key management
- Backup and restore test records
Access control and logging Rule 6(1)
Only the right people can reach personal data, you review that access regularly, and you keep access logs for at least a year.
Why it matters
The Rules ask for access logs kept for a year. Without them you cannot investigate or prove a breach.
How to close the gap
Give access by role only, review access every quarter, and keep access logs for at least one year.
Evidence that shows it's in place
- Access control policy
- Periodic access review records
- Log retention configuration showing one year or more
Breach detection and notification Sec 8(6), Rule 7
You can spot a personal data breach, tell the Data Protection Board and the people affected without delay, and send the Board a detailed report within 72 hours.
Why it matters
Not reporting a personal data breach to the Board and affected people can cost up to ₹200 crore.
How to close the gap
Write a breach response plan with named roles, templates for the Board and affected people, and a 72-hour reporting clock. Practise it once a year.
Evidence that shows it's in place
- Incident response plan with DPDP notification steps
- Notification templates for the Board and data principals
- Incident drill or tabletop records
An Example
A fintech finds that a misconfigured storage bucket exposed customer KYC documents. Its team spends the first two days working out who should decide what to do. With a written breach plan, named roles and ready templates, it could have told the affected customers and the Board without delay and sent the Board's detailed report within 72 hours.
Common Mistakes
- Encrypting data in transit but not at rest, or leaving backups unencrypted.
- Shared admin accounts, so logs cannot show who accessed what.
- Keeping access logs for only a few weeks, when the Rules ask for at least a year.
- A breach plan that exists on paper but has never been practised.
- Reporting only to CERT-In and forgetting the separate DPDP duty to tell the Board and affected people.
Questions People Ask
What counts as reasonable security safeguards?
Rule 6 lists measures such as encryption, obfuscation, masking or virtual tokens, access controls, visibility of access through logs and monitoring, backups for continuity, keeping logs for a year, and security clauses in contracts with processors.
When must we report a personal data breach?
Rule 7 asks you to tell affected people without delay, and to tell the Data Protection Board without delay, followed by a detailed report within 72 hours of becoming aware of the breach.
What are the penalties?
Up to ₹250 crore for failing to take reasonable security safeguards, and up to ₹200 crore for failing to notify a breach, under the Schedule to the Act.
Last checked: , against the DPDP Act 2023 and the DPDP Rules 2025. This is general guidance, not legal advice.