Resources
What India's DPDP Rules and CERT-In ask of security testing
India now has two sets of security obligations for companies that handle Indian users' personal data or run systems in India. The DPDP Rules set minimum safeguards for personal data and a 72-hour breach report. CERT-In requires six-hour incident reporting today and has published how it expects audits to run. This page sets out what each text actually says, which parts testing can evidence, and which parts it cannot.
The dates that apply
The CERT-In obligations already apply. The DPDP safeguards and breach rules apply from 13 May 2027, so an annual test that falls before then is worth scoping to Rule 6.
28 April 2022
CERT-In Directions issued: cyber incidents reported to CERT-In within six hours of noticing them, and logs of all ICT systems kept for a rolling 180 days within India.
25 July 2025
CERT-In publishes its Comprehensive Cyber Security Audit Policy Guidelines, version 1.0.
13 November 2025
DPDP Rules published in the Gazette (G.S.R. 846(E)). The Data Protection Board provisions apply from this date.
13 November 2026
Rule 4, registration and obligations of Consent Managers, comes into force.
13 May 2027
The rest come into force, eighteen months after publication: notice, security safeguards (Rule 6), breach intimation (Rule 7) and the additional duties of Significant Data Fiduciaries (Rule 13).
DPDP Rule 6, clause by clause
Rule 6 lists the minimum safeguards a Data Fiduciary must take, including for processing a Data Processor does on its behalf. Some clauses are exactly what a security test examines. Others are outside what any test can show, and we mark those plainly.
Rule 6(1)(a)
- What it asks
- Secure personal data through encryption, obfuscation, masking or tokens mapped to it.
- What testing can show
- We check whether personal data is actually protected where an attacker can reach it: in transit, in API responses, in error messages and exports, and in storage a misconfiguration exposes.
Rule 6(1)(b)
- What it asks
- Control access to the computer resources used by you and your Data Processors.
- What testing can show
- Authorization testing answers this directly. Can one customer read another customer's records? Can a support role reach an admin function? Each finding comes with the request that proves it.
Rule 6(1)(c)
- What it asks
- Keep visibility on access to personal data through logs, monitoring and review, so unauthorised access can be detected, investigated and fixed.
- What testing can show
- A test leaves a known trail: dated requests from known addresses. Comparing that trail with what your logs and alerts recorded is direct evidence of whether this clause works in practice.
Rule 6(1)(d)
- What it asks
- Keep processing going if data is compromised or access is lost, for example through backups.
- What testing can show
- Security testing does not evidence this. A restore exercise run by your operations team does, and we say so rather than implying coverage.
Rule 6(1)(e)
- What it asks
- Retain those logs and the relevant personal data for one year, unless another law requires otherwise.
- What testing can show
- A cloud configuration review can confirm the retention settings on your logging services. Whether a year of logs actually exists is shown by your own records.
Rule 6(1)(f)
- What it asks
- Put security safeguard obligations into your contracts with Data Processors.
- What testing can show
- A contract question for your counsel. Where you want a processor's systems tested, the processor has to authorise it in writing first.
Rule 6(1)(g)
- What it asks
- Take technical and organisational measures so the safeguards are actually observed.
- What testing can show
- Testing supplies the technical half: findings, reproduction steps, and fixes verified on retest. The organisational half sits with your own governance.
The 72-hour report depends on logs you already have
Under Rule 7, a Data Fiduciary tells each affected person about a breach without delay, and tells the Data Protection Board twice: once without delay, then with a detailed account within 72 hours. That account covers the events and reasons that led to the breach, any findings about who caused it, and what has been done to prevent it happening again.
None of that can be written from memory. It comes from the logs Rule 6 asks you to keep, and from knowing which weaknesses were already open. The practical preparation is to find out now whether your logs would answer those questions, which is the comparison in clause 6(1)(c) above.
Significant Data Fiduciaries carry more. Rule 13 requires a Data Protection Impact Assessment and an audit every twelve months, with a report of significant observations to the Board. Security testing evidence feeds that audit. We do not perform the impact assessment, and we do not give legal opinions on DPDP obligations; those sit with your counsel or data protection officer.
CERT-In: incident reporting now, audits once a year
The April 2022 Directions apply to service providers, intermediaries, data centres, body corporates and Government organisations. Incidents of the listed types must be reported to CERT-In within six hours of being noticed, and logs of all ICT systems kept for a rolling 180 days within India. The six-hour clock starts when you notice, so the working constraint is detection. A test whose trail never appears in your monitoring is an incident you would not have reported either.
The July 2025 audit guidelines expect auditee organisations to ensure a comprehensive audit of their ICT systems at least once a year, and let sector regulators raise that frequency. They also set out how a good audit runs. Tool-only testing is discouraged. Short lists such as the OWASP Top 10 are not treated as audit standards; the guidelines point instead to comprehensive ones, including the OWASP Application Security Verification Standard and the OWASP mobile testing guide. A follow-up audit verifies that findings were closed, and the final report is issued after that closure. Payment to the auditor should not depend on the outcome.
Two of those standards are already the published baselines for our work: OWASP ASVS for application review and the OWASP MASTG (formerly MSTG) for mobile testing. Every engagement includes a retest of reported findings.
Where we fit, and where we do not
VirtuesTech is not CERT-In empanelled, and we are not applying. The audit guidelines are written for audits carried out by organisations on CERT-In’s empanelled list. If your sector regulator, a government contract or your own policy requires an empanelled auditor, that audit and its follow-up have to come from one of them.
What we do is the testing around it. Before an audit, we test to the same standards so the issues are found and fixed before your auditor arrives. Between audits, we test the changes you ship. For DPDP, we produce the technical evidence for the Rule 6 clauses a test can reach, scoped to the systems that hold personal data. Our own position, including the certifications we do not hold, is on the trust page.
Primary sources
Everything above paraphrases these documents, read in November 2026. Where our summary and the text differ, the text governs. For the other frameworks we test against, see compliance evidence.
Working back from May 2027
Tell us which systems hold personal data and when your next audit is due, and we will plan the testing backwards from both.