Checklist for engineering teams

DPDP Rule 6 security safeguards checklist

Rule 6 of the DPDP Rules, 2025 lists the security safeguards a Data Fiduciary must take, at the minimum. Here is each one, quoted exactly, with engineering checks and evidence we suggest for each.

Evidence for eachDownload as CSV
Rule 6(1)

The seven safeguards

Encryption, masking and tokensRule 6(1)(a)
Access controlRule 6(1)(b)
Logs, monitoring and reviewRule 6(1)(c)
Backups and continued processingRule 6(1)(d)
One-year retention of logs and dataRule 6(1)(e)
Security terms in processor contractsRule 6(1)(f)
Making the safeguards workRule 6(1)(g)
Rule text quoted belowStarts 13 May 2027, by our count
For engineering teams

What Rule 6 says.

Rule 6 starts eighteen months after the Rules were published in the Official Gazette. The Gazette is dated 13 November 2025, so we count 13 May 2027. Some law firms count from 14 November 2025.

Rule 6(1)

“A Data Fiduciary shall protect personal data in its possession or under its control, including in respect of any processing undertaken by it or on its behalf by a Data Processor, by taking reasonable security safeguards to prevent personal data breach, which shall include, at the minimum, —”

Who it applies to

The Data Fiduciary: the person or organisation that decides, alone or with others, why and how personal data is processed. It covers processing a Data Processor does on its behalf.

How to read this checklist

The rule text is quoted exactly from the Gazette (G.S.R. 846(E)). The checks and evidence under each clause are our engineering suggestions. The Rules don’t list them, and ticking them all does not by itself prove compliance. Rule 6 sets a minimum.

This page is general information, not legal advice.

The checklist, clause by clause.

Tick what you already have; nothing is saved or sent. Download the list as a spreadsheet to track it in your own tools.

0 of 24 done
Rule 6(1)(a)

Encryption, masking and tokens

appropriate data security measures, such as securing of personal data through encryption, obfuscation, masking or the use of virtual tokens mapped to that personal data;
  • EvidenceEncryption settings for each data store, and how keys are managed.

  • EvidenceTLS settings and a recent scan of public endpoints.

  • EvidenceA list of masked or tokenised fields, and where the real values are kept.

  • EvidenceThe procedure for refreshing test data.

Rule 6(1)(b)

Access control

appropriate measures to control access to the computer resources used by such Data Fiduciary or such a Data Processor, wherever applicable;
  • EvidenceIdentity provider settings and the list of systems behind it.

  • EvidenceA role and access matrix.

  • EvidenceDated access reviews and the leaver checklist.

  • EvidenceEach processor’s security answers or reports.

Rule 6(1)(c)

Logs, monitoring and review

visibility on the accessing of such personal data, through appropriate logs, monitoring and review, for enabling detection of unauthorised access, its investigation and remediation to prevent recurrence;
  • EvidenceA list of log sources, with sample entries.

  • EvidenceThe log pipeline and who can change it.

  • EvidenceAlert rules, and one alert that was investigated.

  • EvidenceReview records and follow-up actions.

Rule 6(1)(d)

Backups and continued processing

reasonable measures for continued processing in the event of confidentiality, integrity or availability of such personal data being compromised as a result of destruction or loss of access to personal data or otherwise, such as by way of data-backups;
  • EvidenceBackup schedule and coverage for each system.

  • EvidenceDated restore tests and their results.

  • EvidenceA recovery plan with owners.

Rule 6(1)(e)

One-year retention of logs and data

for enabling the detection of unauthorised access, its investigation, remediation to prevent recurrence and continued processing in the event of such a compromise, retain such logs and personal data for a period of one year, unless compliance with any law for the time being in force requires otherwise;
  • EvidenceRetention settings for each log store.

  • EvidenceA retention schedule that shows both rules, and a note, checked with your lawyers, on how erasure requests are handled during that year.

  • EvidenceRetention terms in each processor contract.

Rule 6(1)(f)

Security terms in processor contracts

appropriate provision in the contract entered into between such Data Fiduciary and such a Data Processor, wherever applicable, for taking reasonable security safeguards; and
  • EvidenceA processor register.

  • EvidenceA contract review, with gaps flagged to your lawyers.

Rule 6(1)(g)

Making the safeguards work

appropriate technical and organisational measures to ensure effective observance of security safeguards.
  • EvidenceAn owner list.

  • EvidencePolicies and training records.

  • EvidenceTest reports and fix records.

  • EvidenceThe register, kept up to date.

Encryption, masking and tokens in your databases.

Rule 6(1)(a) names encryption, obfuscation, masking and virtual tokens as examples. It does not say which to use where. Most teams need all four, at different layers of the same database.

Encryption at rest

Disk or storage encryption protects against a lost drive or snapshot. It does not stop anyone who can log in to the database, because the database decrypts the data for them. Treat it as the floor, not the whole answer, and cover replicas, snapshots and backups too.

Field-level encryption

Encrypt the most sensitive columns in the application before they reach the database, with keys held in a key management service the database cannot reach. A leaked dump or an over-broad query then returns ciphertext. Record who can use each key, and log every use.

Masking

Show only what a screen or report needs, such as the last four digits of a phone or account number. Masking in views and APIs limits what support staff and analysts see. Static masking replaces real values in copies used for testing, analytics and AI work, so production data does not leak into them.

Tokenisation

Replace an identifier with a token everywhere except one tightly controlled vault that maps tokens back to real values. Joins and lookups work on the token, and most systems never hold the real value. A plain hash of the identifier is not a safe token if the original values can be guessed and hashed again.

Aadhaar numbers

UIDAI requires requesting entities that store full Aadhaar numbers to keep them in an Aadhaar Data Vault, with reference keys used elsewhere, and says a hash of the Aadhaar number should not be used as the reference key. Everyone else should mask to the last four digits wherever the full number is not needed.

Evidence to keep

A field list showing which columns are encrypted, masked or tokenised; the key management settings and key access logs; the masking rules for each non-production copy; and who can reach the token vault. These are our suggestions, not items the Rules list.

When a breach happens anyway.

Tell affected people

Rule 7(1): without delay, in a concise, clear and plain manner, through their user account or a mode of communication they registered with you.

Tell the Data Protection Board

Rule 7(2)(a): without delay, a description of the breach, including its nature, extent, timing, location and likely impact.

Send the Board a detailed report

Rule 7(2)(b): within 72 hours of becoming aware of the breach, or a longer period the Board allows on a written request. It covers updated details of the breach, the broad facts and reasons behind it, the measures taken or proposed to reduce risk, any findings about who caused it, the steps taken to stop it happening again, and a report on the notices sent to affected people.

CERT-In

CERT-In requires the cyber incidents on its list to be reported within 6 hours of noticing them or being told about them. We build one runbook that covers both.

DPDP Rule 6 FAQs.

What does Rule 6 of the DPDP Rules require?

Reasonable security safeguards to prevent a personal data breach, including for processing a data processor does on your behalf. At the minimum: data security measures such as encryption, masking or tokens; access control; logs, monitoring and review; measures such as backups to keep processing after a compromise; keeping those logs and personal data for one year, unless another law requires otherwise; security terms in processor contracts, where applicable; and technical and organisational measures that make the safeguards work.

When does Rule 6 start?

Eighteen months after the Rules were published in the Official Gazette. The Gazette is dated 13 November 2025, so we count 13 May 2027. Some law firms count from 14 November 2025, which makes it 14 May 2027.

Does Rule 6 apply to data processors?

Rule 6 puts the duty on the Data Fiduciary, but it covers processing that a Data Processor does on its behalf. Where it applies, the contract between them must provide for reasonable security safeguards (Rule 6(1)(f)).

What are the penalties under the DPDP Act?

Up to ₹250 crore for failing to take reasonable security safeguards to prevent a breach. Up to ₹200 crore for failing to report a breach or for breaching the duties on children's data. Other failures carry lower limits set out in the Act's Schedule.

Find out which safeguards you’re missing.

Sources: Digital Personal Data Protection Act, 2023 (Sections 2 and 8, and the Schedule). Digital Personal Data Protection Rules, 2025, Rules 1, 6, 7 and 8 (G.S.R. 846(E), Gazette of India, 13 November 2025; corrigendum G.S.R. 892(E), December 2025). CERT-In Directions, 28 April 2022. UIDAI, FAQs on Aadhaar Data Vault, version 10, 3 November 2025. Last reviewed 12 November 2026. See also our DPDP compliance page.