Skip to content
TrustOS

DPDP Act guide

Reasonable security safeguards under the DPDP Act and Rules

Section 8(5) of the DPDP Act requires every Data Fiduciary to protect the personal data it holds by taking reasonable security safeguards to prevent a personal data breach, including where a processor handles the data. The Rules list the minimum measures. Failing this duty carries the highest penalty in the Act, up to 250 crore rupees.

The law as of October 2026.

In shortAs of October 2026

  1. Every Data Fiduciary must take reasonable security safeguards, including for processing by processors.
  2. The Rules list minimum measures: encryption or masking, access control, logs and monitoring, backups and processor contracts.
  3. Logs and personal data are to be kept for a year for detection and investigation, unless a law requires otherwise.
  4. Failing this duty can attract up to 250 crore rupees.

What the Act asks

The duty covers all personal data in your possession or under your control, including processing carried out by a Data Processor on your behalf. The Act does not prescribe a particular standard or certification. What counts as reasonable depends on the data, the risk and the measures the Rules set out.

The minimum measures in the Rules

The DPDP Rules list measures that reasonable security safeguards should include, at a minimum.

  • Securing personal data through encryption, obfuscation, masking or the use of virtual tokens
  • Controlling access to the computer resources used for processing
  • Visibility of access through logs, monitoring and review, so unauthorised access can be detected and investigated
  • Measures for continued processing if confidentiality, integrity or availability is compromised, such as backups
  • Keeping logs and personal data for one year to support detection, investigation and remediation, unless a law requires otherwise
  • Appropriate provisions in contracts with processors for taking reasonable security safeguards
  • Technical and organisational measures to make sure the safeguards are actually observed

What this means for a typical organisation

For a hospital chain, it may mean encrypting the patient database, masking Aadhaar and phone numbers in the reports front desk staff see, removing access for staff who move to other branches, and keeping access logs for the lab system for a year. For a D2C brand, it may mean tokenising payment details, limiting who can export the customer list from the CRM and reviewing that export log each month.

Processors are part of your perimeter

Many breaches start at a vendor: a call centre, a courier partner, a marketing agency with CRM access. The Rules expect your contracts with processors to cover security safeguards. You remain responsible under section 8(1) for what they do with your data.

Timing and penalties

The security safeguards duty applies in Phase 3, around 13 May 2027 as notified, unless amended. Failing to take reasonable security safeguards to prevent a personal data breach can attract a penalty of up to 250 crore rupees. Failing to notify a breach is a separate head with a maximum of up to 200 crore rupees.

How TrustOS helps

TrustOS maps each Rules measure to the systems and processors in your inventory, assigns an owner to each control, and stores the evidence as you go: encryption settings, access reviews, log retention, backup tests and processor contract clauses. When the Board or an auditor asks what was in place on a given date, the record is ready.

TrustOS does not run your security tools and does not decide whether a safeguard is reasonable. That judgement belongs to your security lead and counsel, and TrustOS does not replace legal advice.

Free toolPenalty exposure and readiness scoreSee which heads of the Schedule apply to you, their ceilings, and the controls to close first.

Official sources

This guide explains the law in plain words as of October 2026. It is not legal advice. Dates that depend on notifications can change, so check the official text before you rely on them.

Questions

Common questions

Does ISO 27001 certification mean we comply?

The Act does not name a certification. A certified programme helps, but you still need to show that the measures in the Rules cover the systems holding personal data.

Do we have to encrypt everything?

The Rules list encryption, obfuscation, masking or virtual tokens as ways to secure data. Choose the method that suits each system and its risk, and record why.

Why keep logs for a year if we are meant to minimise data?

The Rules ask for logs and personal data to be kept for one year to help detect and investigate unauthorised access, unless a law requires otherwise. Keep them secured and access controlled.

See it with your data

Show us where your personal data lives. We will show you TrustOS running on it.

A 30 minute walkthrough on Google Meet with someone who knows the Act and the product. You leave with a view of your first phase, the owners and the effort.

Or get a rollout proposal in two minutes
  1. Step 1A 30 minute demo on Google MeetWith someone who knows the Act and the product.
  2. Step 2Your systems and purposesWe walk one product's personal data through TrustOS.
  3. Step 3A first phase you can planModules, owners and effort, written down for you to keep.