The Act tells a Data Fiduciary to protect personal data by taking “reasonable security safeguards” to prevent a breach, and attaches its largest penalty — up to ₹250 crore — to failing to. The Rules then say what the minimum is. It is a short list, and none of it is exotic. The difficulty is in being able to show each item.
The minimum the Rules name
| Safeguard | What it means in practice | What shows you have it |
|---|---|---|
| Securing the data itself | Encryption, obfuscation, masking or tokenisation of personal data | Encryption at rest and in transit; masked fields in screens and exports |
| Access control | Controlling who can reach the systems that hold the data | Role-based access, two-factor sign-in, joiner and leaver records |
| Visibility of access | Logs, monitoring and review, so unauthorised access is detected | Audit logs that cannot be quietly edited, and evidence someone reviews them |
| Continuity | Being able to carry on if data is lost or locked, for example from backups | Backups, and a restore that has actually been tested |
| Log retention | Keeping logs and the relevant data for at least one year, to detect and investigate | A retention setting, and logs that go back that far |
| Processor contracts | Security obligations written into contracts with vendors | Signed contracts with the clause in them |
| Technical and organisational measures | Whatever else is needed to make the above effective | Policies people have read, training records, internal audits |
“Reasonable” is judged afterwards
The list is a floor. Whether your safeguards were reasonable will be asked after something has gone wrong, by a Board that can see what a business of your size and kind could have done. Having the control is half the answer. Being able to produce the record of it — on the day you are asked — is the other half.
The one-year log rule
This is the item most organisations do not already meet. Many systems keep access logs for thirty or ninety days by default. From May 2027 the expectation is at least a year, unless another law requires longer. Check the retention setting on every system that holds personal data, including the ones a vendor runs for you.
How this maps to ISO 27001
If you are certified to ISO/IEC 27001, most of this list is already in your controls: access control, cryptography, logging and monitoring, backup, supplier relationships. Certification is not a defence under the Act, but it is strong evidence that safeguards exist and are reviewed. ISO/IEC 27701 adds the privacy-specific controls on top.
Where to start
- List the systems that hold personal data. You cannot protect what you have not listed.
- For each, record whether the data is encrypted, who has access, and how long logs are kept.
- Turn on two-factor sign-in wherever it is offered.
- Test one restore from backup, and write down the date and the result.
- Fix log retention first — it is the cheapest gap to close and the easiest to be caught on.
- What are reasonable security safeguards under the DPDP Act?
- At minimum: securing data through encryption or masking, access control, logging and monitoring, backups for continuity, log retention for a year, security clauses in processor contracts, and supporting technical and organisational measures.
- How long must logs be kept under the DPDP Rules?
- At least one year, unless another law requires a longer period.
- Is encryption mandatory under the DPDP Act?
- The Rules name encryption, obfuscation, masking and tokenisation as appropriate measures for securing personal data. One or more of them is expected.
- Does ISO 27001 certification make me DPDP compliant?
- No, but it covers most of the security safeguards the Rules list and is good evidence of them. Notice, consent and individual rights are outside it.
This is a working summary for people who have to act on the law, not legal advice. Read the Act and the Rules, and take advice on your own facts.