Quick answer
Rule 6 of the DPDP Rules, 2025 requires every Data Fiduciary, from 13 May 2027, to take reasonable security safeguards that include at minimum: encryption, obfuscation, masking or virtual tokens; access control; logs, monitoring and review; continuity measures such as backups; one-year retention of logs and personal data; security clauses in processor contracts; and technical and organisational measures. Failure can attract up to ₹250 crore.
- Rule 6(1) sets a minimum of seven safeguards, (a) to (g), that apply to the fiduciary and to processing done by its Data Processors.
- Data must be secured through encryption, obfuscation, masking or virtual tokens mapped to the personal data.
- Logs, monitoring and review must give visibility on access so unauthorised access can be detected, investigated and remediated.
- Logs and personal data must be retained for one year for detection, investigation and continuity, unless another law requires otherwise.
- Failing to take reasonable security safeguards can attract a penalty of up to ₹250 crore per instance under the Act's Schedule.
Who this is for: CISOs and security engineers, CTOs and platform teams, Cloud and DevOps teams, Data Processors and SaaS vendors, Compliance and internal audit
What security safeguards does DPDP Rule 6 require?
Section 8(5) of the DPDP Act requires a Data Fiduciary to protect personal data in its possession or under its control, including processing by Data Processors on its behalf, by taking reasonable security safeguards to prevent personal data breach. Rule 6(1) says those safeguards "shall include, at the minimum":
| Clause | Minimum safeguard |
|---|---|
| (a) | Data security measures such as encryption, obfuscation, masking or virtual tokens mapped to the personal data |
| (b) | Measures to control access to computer resources used by the fiduciary or processor |
| (c) | Visibility on access through logs, monitoring and review, to detect unauthorised access, investigate it and prevent recurrence |
| (d) | Measures for continued processing if confidentiality, integrity or availability is compromised, such as data backups |
| (e) | Retention of those logs and personal data for one year, unless another law requires otherwise |
| (f) | Contract provisions with Data Processors for reasonable security safeguards |
| (g) | Technical and organisational measures to ensure effective observance of the safeguards |
"At the minimum" is the important phrase. Meeting all seven does not automatically make your security "reasonable"; it makes it eligible to be. The Board will judge reasonableness in context, including the volume and sensitivity of data. Rule 6 applies from 13 May 2027.
Clause (a): encryption, obfuscation, masking and tokens
Clause (a) names four techniques and treats them as alternatives ("such as"). Choose by data flow, not by checklist.
| Technique | Best fit | Engineering notes |
|---|---|---|
| Encryption | Data at rest and in transit | TLS for transport; storage encryption plus field-level encryption for high-risk fields; keys in a KMS or HSM with rotation |
| Obfuscation | Test and analytics environments | Irreversible transformation so developers and analysts never see real values |
| Masking | Support and operations screens | Show partial values (e.g. last four digits) by role |
| Virtual tokens | Payments, identifiers, AI pipelines | Replace values with tokens mapped in a separate vault; only the vault can detokenise |
Practical points:
- Disk encryption alone is weak evidence. It protects against stolen drives, not against a compromised application credential. Field-level encryption or tokenisation of high-risk fields shows more.
- AI pipelines need care. Prompts, embeddings and vector stores often hold personal data in clear text. Tokenise or mask before sending data to model APIs where you can. See masking and tokenisation for AI.
- Key separation. Keys and the data they protect should not share an access path.
Clauses (b) and (c): access control and visibility
Clause (b) requires appropriate measures to control access to the computer resources used by the fiduciary or its processor. Rule 6(2) imports the IT Act definition of computer resource, which is broad: computers, systems, networks, data, databases and software.
Baseline controls:
- Single sign-on with MFA for staff and contractors.
- Role-based or attribute-based access, with least privilege for production data.
- Just-in-time elevated access with approval and expiry.
- Quarterly access reviews, with removal of leavers within a defined window.
- Separate service identities for applications, with scoped secrets.
Clause (c) requires visibility on access to personal data through appropriate logs, monitoring and review, so unauthorised access can be detected, investigated and remediated to prevent recurrence. Three verbs matter: log, monitor, review.
- Log reads and writes of personal data at the application layer, not only infrastructure events. Include who, what record, when, from where, and why where available.
- Monitor with alerting on anomalies such as bulk exports, off-hours access or access from unusual locations.
- Review logs on a schedule and after alerts, and record the review.
Logs without review fail clause (c). Many organisations collect logs but never look at them.
Clauses (d) and (e): continuity and one-year retention
Clause (d) requires reasonable measures for continued processing if confidentiality, integrity or availability is compromised, whether through destruction, loss of access or otherwise, "such as by way of data-backups". Ransomware is the obvious scenario.
Good practice:
- Immutable or offline backups that an attacker with production credentials cannot delete.
- Tested restores, with recorded recovery times.
- Backups encrypted, access-controlled and covered by the same retention rules as production.
Clause (e) requires the fiduciary, for detection, investigation, remediation and continued processing, to retain such logs and personal data for a period of one year, unless any other law requires otherwise.
This works together with Rule 8(3), which separately requires every fiduciary to retain personal data, associated traffic data and processing logs for at least one year from the date of processing for Seventh Schedule purposes. Practical effect:
- Default log retention of 30 or 90 days, common in SaaS logging tools, is too short.
- Retention must cover processors' logs too.
- Stored logs are themselves personal data and need clause (a) and (b) protection.
CERT-In's 2022 Directions separately require ICT logs to be kept for a rolling 180 days within Indian jurisdiction. The DPDP one-year period is longer, so design to the longer period. See one-year log retention.
Clauses (f) and (g): processor contracts and organisational measures
Clause (f) requires "appropriate provision" in the contract between the fiduciary and each Data Processor for taking reasonable security safeguards. Section 8(2) of the Act already says a fiduciary may engage a processor only under a valid contract, and section 8(1) keeps the fiduciary responsible for processing done on its behalf.
Contract clauses to include:
- The processor implements safeguards at least equivalent to Rule 6(1)(a) to (e).
- The processor notifies the fiduciary of any personal data breach promptly, so the fiduciary can meet Rule 7.
- The processor retains logs for at least one year, consistent with Rules 6(1)(e) and 8(3).
- Sub-processors are approved and bound by equivalent terms.
- The fiduciary has audit and information rights.
- Data is returned or erased at contract end, subject to retention duties.
Clause (g) requires technical and organisational measures to ensure effective observance of the safeguards. This is the governance layer:
- A written security policy approved by senior management.
- Named owners for each control.
- Training for staff who handle personal data.
- Periodic internal or external testing, such as vulnerability assessments and penetration tests.
- Evidence collection so you can show the Board what you did, not just what you intended.
See the DPA clauses template.
Penalties and common mistakes
Breach of the duty to take reasonable security safeguards under section 8(5) carries the highest penalty in the Act's Schedule: up to ₹250 crore per instance. The Board decides the amount after an inquiry, considering the nature, gravity and duration of the breach, the type and nature of personal data affected, repetition, any gain or loss avoided, mitigation, proportionality and impact.
The penalty is tied to failing to take safeguards, not to suffering a breach. A fiduciary with strong, documented controls that is still breached is in a different position from one whose breach exposed missing basics.
Mistakes that will be hard to defend:
- Clear-text personal data in logs, analytics or AI prompts, which bypasses clause (a) entirely.
- Shared admin accounts, which defeat both access control and attribution.
- Logs kept for 30 days, which fail clause (e).
- Backups never restored in a test, which undermines clause (d).
- Vendor contracts with no security schedule, which fail clause (f).
- No evidence. Policies without logs, tickets and reports showing they operate.
Rule 6 replaces section 43A of the IT Act and the SPDI Rules on 13 May 2027. If your programme was built on ISO 27001 for SPDI purposes, map those controls to clauses (a) to (g) and close gaps, especially around application-level access logging and one-year retention.
Further reading on suhasbhairav.com
Before 13 May 2027
Compliance checklist
Encrypt or tokenise high-risk fields
Apply field-level encryption, tokenisation or masking to identifiers, financial, health and authentication data.
Rule 6(1)(a)
Enforce MFA and least privilege
Require SSO with MFA and role-based access to systems holding personal data, with quarterly reviews.
Rule 6(1)(b)
Log application-level access to personal data
Record who accessed which records, when and from where, and alert on anomalies.
Rule 6(1)(c)
Schedule and record log reviews
Review access logs periodically and after alerts, and keep evidence of each review.
Rule 6(1)(c)
Test backup restores
Keep immutable backups and run restore tests with documented recovery times.
Rule 6(1)(d)
Extend log retention to one year
Retain logs and relevant personal data for one year, including at processors.
Rule 6(1)(e)
Add a security schedule to every processor contract
Require equivalent safeguards, breach notice, log retention and audit rights.
Rule 6(1)(f)
Approve a security policy and assign owners
Get senior approval for the policy, name control owners and train staff.
Rule 6(1)(g)
Key dates
Rule 6 safeguards apply; IT Act section 43A omitted
Answers
Frequently asked questions
What are reasonable security safeguards under the DPDP Act?
What are reasonable security safeguards under the DPDP Act?
Under Rule 6, they include at minimum: encryption, obfuscation, masking or virtual tokens; access control to computer resources; logs, monitoring and review to detect unauthorised access; continuity measures such as backups; one-year retention of logs and personal data; security clauses in processor contracts; and technical and organisational measures to make the safeguards effective.
Is encryption mandatory under DPDP Rule 6?
Is encryption mandatory under DPDP Rule 6?
Not by itself. Rule 6(1)(a) requires appropriate data security measures such as encryption, obfuscation, masking or virtual tokens. These are alternatives. In practice, encryption in transit and at rest is expected, with masking or tokenisation added where data is displayed or shared.
What is the penalty for weak security under DPDP?
What is the penalty for weak security under DPDP?
Up to ₹250 crore per instance for failing to take reasonable security safeguards to prevent personal data breach, the highest amount in the DPDP Act's Schedule. The Board sets the actual amount after an inquiry, weighing gravity, duration, data type, repetition and mitigation.
How long must logs be kept under DPDP Rule 6?
How long must logs be kept under DPDP Rule 6?
One year. Rule 6(1)(e) requires logs and personal data to be retained for one year to enable detection, investigation and remediation of unauthorised access, unless another law requires otherwise. Rule 8(3) separately sets a one-year minimum for processing logs.
Do DPDP security safeguards apply to vendors?
Do DPDP security safeguards apply to vendors?
Yes, through the fiduciary. Rule 6(1) covers processing undertaken by a Data Processor on the fiduciary's behalf, and clause (f) requires security provisions in the processor contract. The fiduciary remains responsible for its processors' processing under section 8(1) of the Act.
Is ISO 27001 enough for DPDP Rule 6 compliance?
Is ISO 27001 enough for DPDP Rule 6 compliance?
It is a strong foundation but not automatically sufficient. Map ISO controls to Rule 6(1)(a) to (g) and check specifically for application-level access logging, log review evidence, one-year log retention and security clauses in every processor contract.
Legal references and sources
- Digital Personal Data Protection Rules, 2025 — Rule 6 (official text)
- Digital Personal Data Protection Act, 2023 — Section 8(5) (official text)
- Digital Personal Data Protection Act, 2023 — Schedule (penalties) (official text)
- CERT-In Directions under section 70B(6) IT Act — 28 April 2022 (official text)
This guide explains the law for engineering and business teams. It is not legal advice; confirm how it applies to your organisation with qualified counsel, and check the Gazette for later notifications or amendments.
About the author

Suhas Bhairav
Systems architect and applied AI practitioner who designs production AI systems for Indian and global companies, with a focus on privacy-by-design under the DPDP Act and the EU AI Act.
Related guides
- DPDP Rules 2025DPDP Data Breach Notification: The 72-Hour Rule ExplainedRule 7 requires every personal data breach to be reported to affected individuals and the Data Protection Board, with a detailed Board report within 72 hours. No materiality threshold applies.
- DPDP Rules 2025DPDP One-Year Log Retention: What to Keep and for How LongTwo DPDP rules require one year of retention: Rule 6(1)(e) for security logs and Rule 8(3) for personal data, traffic data and processing logs. What to keep, where, and how to protect it.
- DPDP Act 2023DPDP Penalties Explained: What a Data Breach CostsThe full DPDP Act penalty schedule, from ₹10,000 to ₹250 crore per instance, the section 33(2) factors the Board weighs, and how penalties are imposed and appealed.
- AI & personal dataEncryption, Masking and Tokenisation for AI Pipelines Under DPDPRule 6(1)(a) names encryption, obfuscation, masking and virtual tokens as minimum safeguards. Here is how to apply each one to prompts, embeddings, training sets and model gateways.
- Templates & playbooksDPDP Data Processing Agreement Clauses TemplateCopy-ready data processing agreement clauses for India, mapped to DPDP section 8(2), Rule 6(1)(f), Rule 7 breach timelines and Rule 8(3) one-year retention.
- India AI & sector rulesCERT-In Rules for AI Systems: Incident Reporting & LogsHow CERT-In's April 2022 directions on 6-hour incident reporting, 180-day logs in India and clock sync apply to LLM gateways, model APIs and AI agents, and how they meet DPDP.