Insights
DPDP Rules 2025: The Rule 6 Security Safeguards Checklist Before the 13 May 2027 Deadline
Where the Clock Stands in November 2026
The Digital Personal Data Protection Rules, 2025 were notified in November 2025 (Gazette notification dated 13 November 2025) and switched on in phases. The definitions and Data Protection Board provisions applied straight away. The consent manager rule (Rule 4) carried a 12-month runway, which ran out on 13 November 2026. The bulk of the obligations that land on ordinary businesses, including notice, security safeguards, breach intimation, retention and erasure, and the extra duties of Significant Data Fiduciaries, sit in the 18-month tranche that comes into force on 13 May 2027.
That leaves under six months. For most organisations the hardest part to compress is not the privacy notice, it is the security work under Rule 6, because it touches every system that holds personal data and because it has to be demonstrable, not just written down. Reports have suggested the government was discussing a shorter timeline with industry; nothing we have seen changes the May 2027 date, so plan against it unless a fresh notification says otherwise.
What Rule 6 Actually Asks For
Section 8(5) of the DPDP Act 2023 requires every Data Fiduciary to take reasonable security safeguards to prevent a personal data breach. Rule 6 turns that into a minimum list. In plain terms, you need to be able to show:
- Protection of the data itself through encryption, obfuscation, masking or tokenisation (virtual tokens mapped to the real data).
- Access control over the computer resources that process personal data.
- Visibility into who accessed personal data, through logs, monitoring and review, so that unauthorised access can be detected, investigated and fixed.
- Continuity of processing if confidentiality, integrity or availability is compromised, including backups.
- Contractual flow-down: your contracts with Data Processors must require them to take reasonable security safeguards too.
- Organisational and technical measures that keep the safeguards in force, rather than a one-off project.
Separately, Rule 8 expects personal data, associated traffic data and processing logs to be retained for at least one year from processing for the purposes listed in its schedule, then erased unless another law needs them kept. That makes log retention a concrete design requirement for your SIEM and application logging, not a nice-to-have.
A Six-Month Readiness Plan
- Month 1: map the data. List every application, database, SaaS tool and vendor that holds personal data of individuals in India. Rule 6 obligations follow the data, so a system that is missing from the inventory is a system with no evidence.
- Month 2: close the obvious gaps. Encryption at rest and in transit, MFA on admin and remote access, removal of shared accounts, and log forwarding from the systems in your inventory into a central store with at least a year of retention.
- Month 3: test it. Run a VAPT scoped to the systems that hold personal data, including APIs and cloud configuration. The report is your evidence that the safeguards hold up against an attacker, not just that they are configured.
- Month 4: fix and retest. Remediate critical and high findings and get them retested, so the evidence pack shows closure rather than an open list.
- Month 5: processors and breach drill. Update vendor contracts with security flow-down clauses, and rehearse the Rule 7 breach process end to end. The Board expects an initial intimation without delay and a detailed report within 72 hours of becoming aware of the breach, and affected Data Principals must be told without delay.
- Month 6: assemble the evidence pack. Policies, the data inventory, the VAPT report and retest, log-retention configuration, vendor contracts and the breach drill record, in one place, owned by a named person.
Why the Stakes Are High
The Schedule to the Act sets the heaviest penalty, up to ₹250 crore, for failing to take reasonable security safeguards to prevent a personal data breach. A breach that has already happened is exactly when the Board will ask what safeguards were in place. Organisations notified as Significant Data Fiduciaries carry more: a Data Protection Impact Assessment and an independent audit once every twelve months under Rule 13, so the evidence you build now becomes the baseline for that annual cycle.
Sector regulators add their own layer on top. If you are a regulated entity, map Rule 6 against what you already report under SEBI CSCRF or RBI directions, so one test programme produces evidence for both.
Common Mistakes We See
- Treating DPDP as a legal-only project. The privacy notice gets drafted and the security evidence is left for later. Rule 6 is where the technical team is on the hook.
- Scoping VAPT around the website only. Personal data usually lives in the CRM, HR system, mobile app backend and cloud storage. Scope by data, not by domain name.
- Logs that exist but cannot be searched. A year of logs that nobody can query will not help you investigate a breach or answer the Board.
- Forgetting the processors. A payroll provider or marketing platform leaking your customers' data is still your problem as the Data Fiduciary.
This article is a practical security reading of the Rules, not legal advice; confirm obligations specific to your organisation with your counsel. eNeoteric runs VAPT engagements and security services scoped around the systems that hold personal data, and can help you build the Rule 6 evidence pack before May 2027. Email [email protected] or talk to our team.
Explore all ← Back to Insights