Templates & playbooksUpdated 22 November 202610 min read

DPDP Audit Checklist: 60 Controls to Test

Sixty testable DPDP controls grouped by governance, notice and consent, children, security, breach, retention, rights and vendors, each mapped to the Act or the 2025 Rules.

By Suhas Bhairav · Reviewed against the DPDP Rules, 2025 (G.S.R. 846(E), 13 Nov 2025)

Controls
60 across 7 areas
Audit mandatory?
Annually for SDFs (Rule 13(1)); voluntary for others
Core rules in force
13 May 2027
Highest penalty area
Security safeguards, up to ₹250 crore
Breach report deadline
72 hours (Rule 7(2)(b))
Grievance ceiling
90 days (Rule 14(3))

Quick answer

A DPDP audit tests whether a Data Fiduciary meets the Act and the DPDP Rules, 2025 in practice, not just on paper. This checklist sets out 60 controls across seven areas: governance and inventory, notice and consent, children, Rule 6 security, Rule 7 breach response, Rule 8 retention, and rights, contact, vendors and transfers. Each control cites its provision and should be evidenced before 13 May 2027.

  • Test operating effectiveness: sample records, run test users and inspect logs rather than reading policies.
  • Security and breach controls carry the largest penalty exposure, up to ₹250 crore and ₹200 crore respectively.
  • Rule 8(3)'s one-year retention of data, traffic data and logs is a frequent, easily tested gap.
  • Only Significant Data Fiduciaries need an annual independent audit under Rule 13; others audit voluntarily.
  • Record evidence for every control so the same pack supports Board inquiries and customer due diligence.

Who this is for: Internal audit teams, Privacy and compliance leads, External auditors and consultants, CISOs, Boards and audit committees

How to use this DPDP audit checklist

Each control below is written as a testable statement with its legal reference. For each one, record:

  • Design: does a policy, process or system exist that should achieve the control?
  • Operation: does it actually work? Test by sampling, walkthrough or technical inspection.
  • Evidence: a reference to the document, screenshot, log extract or test result.
  • Rating: met, partly met, not met, or not applicable, with a remediation owner and date.

Testing methods that work

  • Test users: create accounts, give and withdraw consent, file rights requests, and watch what the systems do.
  • Network inspection: load pages in a clean browser and inspect outbound requests before and after consent.
  • Log sampling: pick dates more than eleven months ago and confirm logs still exist, to test one-year retention.
  • Contract sampling: pull processor contracts at random and check for Rule 6(1)(f) security clauses.

Significant Data Fiduciaries, once notified, must undertake an audit every twelve months and have the auditor furnish significant observations to the Board under Rule 13. Everyone else can use this list for self-assessment ahead of 13 May 2027.

Area 1: governance and inventory (controls 1–8)

  1. A named owner is accountable for DPDP compliance, with documented authority. (s.8(1))
  2. Leadership or the board receives periodic reports on DPDP status, incidents and gaps. (s.8(1))
  3. A personal data inventory covers all production systems, with owners. (Rule 3(b)(i))
  4. Each processing activity records its purpose and lawful ground: consent or a specific section 7 use. (ss.6–7)
  5. Datasets containing children's data are identified. (s.9)
  6. Processing of non-Indian Data Principals under foreign contracts is identified, and any section 17(1)(d) reliance is documented. (s.17(1)(d))
  7. Third Schedule status (e-commerce, gaming, social media thresholds) and SDF likelihood have been assessed and recorded. (Rule 8; s.10)
  8. A release and procurement gate requires inventory updates before new data fields, purposes or vendors go live. (Rule 6(1)(g))

Test tips: pick three recent product releases and confirm the inventory reflects them. Scan for storage buckets or databases absent from the inventory.

  1. Every consent request is accompanied or preceded by a notice. (s.5)
  2. The notice is understandable independently of other information. (Rule 3(a))
  3. The notice uses clear and plain language. (Rule 3(b))
  4. The notice gives an itemised description of personal data. (Rule 3(b)(i))
  5. The notice states specified purposes and the goods, services or uses enabled. (Rule 3(b)(ii))
  6. The notice links to means to withdraw consent, exercise rights and complain to the Board. (Rule 3(c))
  7. The notice is available in English and relevant Eighth Schedule languages. (s.5(3))
  8. Consent is obtained by clear affirmative action; nothing is pre-selected. (s.6)
  9. Each purpose has a separate choice, unbundled from terms of service. (s.6)
  10. Withdrawal is possible with ease comparable to giving consent. (Rule 3(c)(i))
  11. Withdrawal stops processing, including by processors, within a defined period. (s.6)
  12. Consent and withdrawal events are recorded with notice version, channel and timestamp. (s.6)

Test tips: count the steps to give and to withdraw each consent; inspect network traffic before consent; sample 25 consent records against the notice version live at that time.

Area 3: children and lawful guardians (controls 21–26)

  1. An age gate or other age assurance identifies users under 18, calibrated to the service's risk. (s.9; Fourth Schedule, Part B, item 6)
  2. Verifiable parental consent is obtained before processing a child's personal data, outside exempt cases. (s.9(1); Rule 10)
  3. Due diligence confirms the parent is an identifiable adult using details held, details provided, or an authorised virtual token. (Rule 10(1))
  4. No tracking, behavioural monitoring or targeted advertising is directed at children, outside Fourth Schedule exemptions. (s.9(3))
  5. Any reliance on a Fourth Schedule exemption is documented, with its conditions observed. (Rule 12)
  6. Consent from a lawful guardian of a person with disability is verified against appointment by a court, designated authority or local level committee. (Rule 11)

Test tips: sign up as a 16-year-old and follow the flow; confirm ad and analytics tags are suppressed on child accounts; sample parent verification records for method and outcome.

Note that section 9(2), the bar on processing likely to cause a detrimental effect on a child's well-being, is never exempted. Include a qualitative review of features such as public leaderboards or recommendation loops aimed at minors.

Area 4: security safeguards (controls 27–38)

  1. Personal data at rest is encrypted, masked, obfuscated or tokenised as appropriate. (Rule 6(1)(a))
  2. Personal data in transit is encrypted. (Rule 6(1)(a))
  3. Identifiers are masked in user interfaces where full values are not needed. (Rule 6(1)(a))
  4. Access to computer resources uses individual accounts, SSO and MFA. (Rule 6(1)(b))
  5. Access follows least privilege and is reviewed periodically. (Rule 6(1)(b))
  6. Privileged and production access is controlled and logged. (Rule 6(1)(b)–(c))
  7. Access to personal data is logged, monitored and reviewed to detect unauthorised access. (Rule 6(1)(c))
  8. Backups exist and restores are tested. (Rule 6(1)(d))
  9. Logs and related personal data are retained for one year for detection, investigation and remediation. (Rule 6(1)(e))
  10. Processor contracts contain security safeguard provisions. (Rule 6(1)(f))
  11. Security policies, training and ownership exist and are followed. (Rule 6(1)(g))
  12. Non-production environments do not hold unmasked production personal data. (Rule 6(1)(a))

Test tips: request access logs for a date eleven months ago; restore a backup to a sandbox; review access lists of three high-risk systems for leavers.

Area 5: breach response (controls 39–45)

  1. A written breach response plan names roles, deputies and decision rights. (Rule 7)
  2. The time of becoming aware of a breach is recorded for every incident. (Rule 7(2)(b))
  3. A template exists for the Board's initial description: nature, extent, timing, location and likely impact. (Rule 7(2)(a))
  4. A template exists for the 72-hour detailed report covering all six required items. (Rule 7(2)(b))
  5. Affected Data Principals can be notified without delay through their account or registered channel, with all five required elements. (Rule 7(1))
  6. Specified cyber incidents are reported to CERT-In within 6 hours of noticing. (CERT-In Directions, 28 April 2022)
  7. The plan has been exercised in the last twelve months, with lessons tracked to closure. (Rule 6(1)(g))

Test tips: review the last three security incidents and check whether personal data impact was assessed and recorded; time a tabletop from awareness to draft Board report; confirm processors are contractually bound to notify quickly.

Remember there is no materiality threshold: every personal data breach is reportable to the Board and affected individuals.

Area 6: retention and erasure (controls 46–52)

  1. A retention schedule exists for every dataset, linked to purpose and legal requirements. (s.8(7))
  2. Personal data, associated traffic data and processing logs are retained for at least one year from processing. (Rule 8(3))
  3. After that year, data and logs are erased unless another law requires longer retention. (Rule 8(3))
  4. Data is erased when consent is withdrawn or the purpose is no longer served, unless retention is legally required. (s.8(7))
  5. Processors are instructed to erase and confirm erasure. (s.8(7))
  6. Third Schedule platforms apply the three-year inactivity erasure, with exceptions for account access and virtual tokens. (Rule 8(1); Third Schedule)
  7. Third Schedule platforms send the pre-erasure notice at least 48 hours before erasure. (Rule 8(2))

Test tips: trace one deleted test account through every system, including backups, logs, data warehouse and processors; confirm the restricted retention archive is not accessible to marketing or analytics; check deletion job run logs.

Where retention under Rule 8(3) and erasure under section 8(7) pull in different directions, the audit should confirm the organisation has a documented approach: live data erased, a restricted archive kept for the one-year period, then purged.

Area 7: rights, contact, vendors and transfers (controls 53–60)

  1. The means to make rights requests, and the identifiers needed, are published prominently. (Rule 14(1))
  2. Access, correction, completion, updating and erasure requests are fulfilled through tested workflows. (ss.11–12)
  3. A grievance response period not exceeding 90 days is published and met. (Rule 14(3); s.13)
  4. Nomination of one or more individuals is supported. (Rule 14(4); s.14)
  5. Business contact information of the DPO or contact person is published prominently and included in every rights response. (Rule 9)
  6. Every processor operates under a valid contract. (s.8(2))
  7. Processing locations are known and no transfers go to countries restricted under section 16, and any Rule 15 requirements are met. (s.16; Rule 15)
  8. If notified as an SDF, an annual DPIA and audit are completed, algorithmic due diligence is performed, and any Rule 13(4) localisation applies. (Rule 13)

Test tips: file each type of rights request as a test user and time the response; check the response includes the Rule 9 contact; compare the vendor register with accounts payable to find processors without contracts.

Further reading on suhasbhairav.com

Before 13 May 2027

Compliance checklist

  1. Confirm a complete personal data inventory

    Check every production system holding personal data is listed with an owner.

    Rule 3(b)(i)

  2. Test notice content against Rule 3

    Verify itemised data, purposes and links to withdrawal, rights and Board complaint.

    Rule 3

  3. Measure withdrawal symmetry

    Compare the steps to withdraw consent with the steps to give it.

    Rule 3(c)(i)

  4. Inspect pre-consent network traffic

    Confirm no marketing or tracking calls fire before consent.

    Section 6

  5. Test parental verification

    Sign up as a minor and verify the parent check and child-safe defaults.

    Rule 10; s.9(3)

  6. Verify encryption and access controls

    Inspect encryption settings, MFA coverage and access reviews on high-risk systems.

    Rule 6(1)(a)-(b)

  7. Sample one-year-old logs

    Retrieve access and processing logs from about eleven months ago.

    Rules 6(1)(e) and 8(3)

  8. Restore a backup

    Restore a personal data backup to a sandbox and record the result.

    Rule 6(1)(d)

  9. Time a breach tabletop

    Measure time from awareness to draft Board report and user notice.

    Rule 7

  10. Trace an erasure end to end

    Follow a deleted test account through systems, backups and processors.

    Section 8(7)

  11. File test rights requests

    Check response times, content and inclusion of the Rule 9 contact.

    Rules 9 and 14

  12. Sample processor contracts

    Confirm security safeguards, breach notice and retention clauses exist.

    Rule 6(1)(f)

Answers

Frequently asked questions

Is a DPDP audit mandatory?

Only for Significant Data Fiduciaries. Rule 13(1) requires an SDF to undertake a Data Protection Impact Assessment and an audit once in every period of twelve months from notification, and Rule 13(2) requires the auditor to furnish significant observations to the Board. Other fiduciaries are not required to audit, but regular self-assessment is good practice.

How many controls does a DPDP audit need?

There is no prescribed number. This checklist uses 60 controls because that granularity maps neatly onto the Act's sections and the Rules' sub-rules without becoming unmanageable. Smaller organisations can combine controls; larger ones may split security and rights controls further by system.

What evidence should a DPDP auditor ask for?

Inventory extracts, notice versions, consent records, network captures, access reviews, log samples older than eleven months, backup restore results, breach tabletop records, retention job logs, rights request tickets with timestamps, published contact details and processor contracts. Operating evidence is more persuasive than policy documents.

Who can perform a DPDP audit?

For SDFs, section 10(2) requires an independent data auditor. For others, internal audit, a privacy team independent of the processing, or an external firm can perform it. Independence from the teams that run the processing is the key quality, whatever the auditor's title.

When should we run the first DPDP audit?

Run a readiness assessment against these controls in early 2027, fix gaps, and repeat a full test in the weeks before 13 May 2027. After that, an annual cycle with quarterly spot checks on high-risk controls, such as security, breach and retention, keeps the programme current.

Can we use an ISO 27001 audit instead?

Partly. ISO 27001 evidence helps with many Rule 6 security controls, but it does not test notices, consent, children's data, rights, retention under Rule 8 or DPDP breach intimation. Use it as input for Area 4 and test the remaining areas specifically against the DPDP Act and Rules.

Legal references and sources

  • Digital Personal Data Protection Rules, 2025 — Rules 3, 6, 7, 8, 9, 10 and 14 (official text)
  • Digital Personal Data Protection Rules, 2025 — Rule 13 (official text)
  • Digital Personal Data Protection Act, 2023 — Sections 5 to 10 and 11 to 14 (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

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.