[Analysis] DPDP Compliance Audit – Scope | Evidence Framework | 57 Common Findings | Gap Assessment
- Blog|Company Law|
- 20 Min Read
How a DPDP compliance audit is conducted: who must appoint an independent data auditor, what the evidence framework must produce, the 49 testable requirements in the Consolidated Requirements Register, and the 57 findings that recur in practice.
- By Taxmann
- |
- Last Updated on 16 November, 2026
Table of Contents
- What is a DPDP compliance audit?
- Is a data audit compulsory, and for whom?
- Who may act as an independent data auditor?
- What is the scope of the audit?
- What does demonstrable compliance mean, and what evidence does it need?
- What will the auditor test, obligation by obligation?
- Which findings recur, and what causes them?
- How is a gap assessment run before the audit?
- What should be in place in the first ninety days?
- Does an existing ISO 27001 or SOC 2 report cover this?
- How does the audit connect to a Board inquiry?
- Quick answers
1. What is a DPDP compliance audit?
It is an evaluation of whether the organisation observes the Digital Personal Data Protection Act, 2023 and the Digital Personal Data Protection Rules, 2025 in practice, evidenced by artefacts the organisation can produce on demand. Section 10(2)(b) puts it in those terms for Significant Data Fiduciaries: the independent data auditor shall evaluate the compliance of the Significant Data Fiduciary in accordance with the provisions of the Act (para 10.3).
The distinction that matters is between compliance and demonstrable compliance. Taxmann’s Digital Personal Data Protection frames the audit question as whether the organisation can show, rather than assert, that each obligation has been met. Its summary is blunt: an undocumented assumption will rarely provide the same assurance as a reasoned decision supported by reliable evidence (Conclusion).
That is why the book treats the audit not as a separate exercise bolted on at the end, but as a design constraint on the compliance programme itself. Every one of the twelve obligation chapters closes with an Audit Considerations section that identifies what an auditor will test, what evidence should be ready, and the most common findings observed in practice. Those sections are addressed equally to the organisation preparing for an audit and to the auditor conducting one (How to use this book).
2. Is a data audit compulsory, and for whom?
Two different answers, depending on designation.
For a Significant Data Fiduciary, yes, annually. Section 10(2)(b) requires the appointment of an independent data auditor to carry out a data audit. Rule 13(1) supplies the periodicity: the Significant Data Fiduciary shall, once in every period of twelve months from the date on which it is notified as such or is included in the class of Data Fiduciaries notified as such, undertake a Data Protection Impact Assessment and an audit to ensure effective observance of the provisions of the Act and the rules made thereunder (para 10.3).
Rule 13(2) then requires the Significant Data Fiduciary to cause the person carrying out the Data Protection Impact Assessment and audit to furnish to the Board a report containing significant observations. The book notes that the obligation to furnish the report rests on the Significant Data Fiduciary, not on the auditor directly, and that the content is limited to significant observations, not the entirety of the audit findings. What constitutes a significant observation requires professional judgement, informed by the materiality of the finding, the number of Data Principals affected, the severity of the risk to Data Principal rights, and whether the finding indicates a systemic rather than isolated compliance gap (para 10.3).
The designation itself is not self-assessed. Section 10(1) provides that the Central Government may notify any Data Fiduciary or class of Data Fiduciaries as a Significant Data Fiduciary on the basis of an assessment of relevant factors, and enumerates six: the volume and sensitivity of personal data processed, risk to the rights of Data Principals, potential impact on the sovereignty and integrity of India, risk to electoral democracy, security of the State, and public order (para 10.1).
For every other Data Fiduciary, there is no statutory audit requirement, and the evidentiary standard applies anyway. The book’s reasoning here is the most useful single idea in this area. The DPDP Act does not use the word “demonstrate” in the manner of GDPR Article 5(2). But section 6(10) establishes that the Data Fiduciary bears the burden of proving that notice was given and consent was obtained in accordance with the Act and the Rules when a question arises in a proceeding. That burden-of-proof provision, combined with the Board’s power to inquire into the affairs of any person for ascertaining compliance under section 28(5), creates an effective obligation of demonstrable compliance: the Data Fiduciary must comply with the Act and must be able to produce evidence of compliance on demand (para 12.2.4).
An organisation that is not a Significant Data Fiduciary therefore has no auditor to satisfy and the same file to build.
3. Who may act as an independent data auditor?
The independence requirement in section 10(2)(b) is stated without elaboration, and the Act does not define the criteria. The book fills the gap by drawing on established audit standards, including those under the Companies Act, 2013 for statutory auditors, the ICAI’s standards on auditing for independence, and the ISACA framework for information systems audit. On that basis, independence of the data auditor would ordinarily require that the auditor (para 10.3):
| Independence criterion | What it excludes |
|---|---|
| No financial interest in the Significant Data Fiduciary other than the audit engagement | Shareholdings, revenue dependence, other commercial arrangements |
| No consulting or implementation services to the same entity in respect of the same subject matter being audited | An auditor that designed the very controls it is now auditing |
| Not a current or recent employee of the entity | Internal staff presented as an independent auditor |
| Exercises professional judgment without direction or influence from the entity’s management | Engagements where management scopes out inconvenient areas |
The book’s warning is specific: an auditor that has designed the very controls it is now auditing, or that receives a material portion of its revenue from the entity being audited, would face legitimate questions about independence in a Board proceeding (para 10.3).
The engagement itself should follow a structured process: define the audit scope, identify and evaluate potential auditors against independence and competence criteria, and conclude with a formal engagement letter specifying the scope, the applicable standards and methodology, the deliverables including the report of significant observations to be furnished to the Board under Rule 13(2), the timeline, and the terms of access to the organisation’s systems, records and personnel (para 10.7.2).
The independence assessment should itself be documented and retained as part of the compliance record, because the Board may scrutinise the auditor’s independence in the course of reviewing the audit report, and a finding that the auditor lacked independence could undermine the credibility of the entire audit and the organisation’s compliance position (para 10.7.2).
4. What is the scope of the audit?
The scope is the full set of obligations arising from the Act and the Rules. Appendix A to the book, the Consolidated Requirements Register, consolidates every compliance obligation into a single reference: 49 consolidated entries, each stated as a testable statement in formal language, each with its legal reference and an audit evidence column identifying the tangible artefacts an organisation should maintain to demonstrate compliance (Appendix A).
The register is organised into fifteen subject areas:
| # | Subject area |
|---|---|
| 1 | Scope, applicability and roles |
| 2 | Notice and consent |
| 3 | Children’s data and persons with disability |
| 4 | Data Principal rights and request handling |
| 5 | Security safeguards |
| 6 | Breach response and notification |
| 7 | Retention and deletion |
| 8 | Data Processor and vendor management |
| 9 | Cross-border transfer |
| 10 | Grievance redressal |
| 11 | Governance, accountability and Significant Data Fiduciary obligations |
| 12 | Consent Manager obligations |
| 13 | Exemptions |
| 14 | Enforcement, penalties and dispute resolution |
| 15 | Commencement timelines |
Two drafting conventions in the register are worth knowing before using it. Where the Rules expand, clarify or operationalise an obligation under the Act, the requirement is merged into a single entry with both references cited, so the reader is not left reconciling an Act duty against a Rule duty. And obligations applicable only to Significant Data Fiduciaries are identified as such within the requirement text, while obligations applicable only to Consent Managers are grouped separately in section 12 (Appendix A, Notes).
The register’s purpose is explicitly operational. For each requirement, the organisation should determine whether it has produced each of the listed evidence artefacts, whether the artefact is current and accurate, and whether it is stored in a retrievable format. It is not a substitute for the organisation’s own compliance records; it is a structured checklist that ensures no obligation is overlooked in the preparation for a Board inquiry or an independent data audit under section 10(2)(b) (para 12.2.4).
A single entry shows the level of granularity. For the breach notification obligation under section 8(6) and Rule 7(2), the register lists seven evidence items: the Board intimation template covering all prescribed elements; the breach register with Board notification timeline tracking for both the initial and the seventy-two-hour submissions; a copy of the initial intimation with timestamp; a copy of the detailed seventy-two-hour report; the written request for extension, if applicable, with the Board’s response; the internal breach assessment and investigation report; and root cause analysis documentation (Appendix A, section 6). The Act, the Rules and the notifications the register cites are on Taxmann.com | Research under Indian Acts and Rules.
5. What does demonstrable compliance mean, and what evidence does it need?
The book calls the answer the evidence framework, and defines it as the architecture through which demonstrable compliance is achieved. It comprises every artefact the organisation maintains for the purpose of showing that a specific obligation has been discharged (para 12.2.4):
| Component | What it is |
|---|---|
| Policy | The document that governs the obligation |
| Process document | The description of how the policy is implemented |
| Records and logs | The capture of the process actually executing |
| Technical configurations | The settings that enforce the controls |
| Governance artefacts | The documentation of oversight and accountability |
| Testing proof | The verification that the controls work as intended |
Each obligation should be mapped to its corresponding evidence artefacts, and the resulting matrix serves as the audit-readiness backbone of the compliance programme (para 12.2.4).
Policy is the layer organisations most often get wrong, in both directions. The Act and Rules do not prescribe a specific set of policies that every Data Fiduciary must maintain; the obligations are stated in terms of outcomes rather than documents. But the obligations cannot be operationalised at organisational scale without documented policies that translate statutory requirements into internal standards, assign responsibilities, and create a basis for training, monitoring and audit. The book’s minimum policy architecture, derived from the obligation chapters, is eight policies (para 12.2.2):
| Policy | What it must govern |
|---|---|
| Data protection policy | The overarching commitment to compliance and the assignment of accountability |
| Notice and consent policy | Drafting, review, approval, multi-language translation and version management of notices; design, deployment and maintenance of consent collection and withdrawal mechanisms |
| Data retention and deletion policy | Retention periods per data category, legal retention requirements, the Third Schedule deemed cessation periods where applicable, and the Rule 8(2) pre-deletion notification |
| Security safeguards policy | The seven minimum requirements of Rule 6(1) and any additional measures appropriate to the risk profile |
| Breach response policy | Detection, classification, investigation, notification and remediation, with templates for Board and Data Principal intimation under Rule 7 |
| Data Principal rights policy | Intake, verification, processing and response for access, correction, completion, updating, erasure and nomination requests |
| Grievance redressal policy | The mechanism, response timelines, escalation paths and record-keeping under section 13 and Rule 14(3) |
| Vendor and Data Processor management policy | Assessment, contracting, monitoring and termination of Data Processor engagements under section 8(2) and Rule 6(1)(f) |
Training sits inside the evidence framework too, and not as a nicety. The technical and organisational measures required by section 8(4) and Rule 6(1)(g) include the capability of the organisation’s personnel to understand and discharge their data protection responsibilities. The book’s formulation is that a security safeguard is only as effective as the person who operates it, a consent mechanism only as compliant as the developer who builds it and the business user who configures it, and a grievance mechanism only as responsive as the handler who receives the complaint. Training is the mechanism through which organisational capability is built, and its absence is a gap in the technical and organisational measures that the Act requires (para 12.2.3).
The programme should run in two tiers: general awareness training for all personnel who handle personal data, and role-specific training for personnel with specialised responsibilities, covering legal teams on notice drafting and consent compliance, IT teams on security safeguard implementation and log management, customer service teams on rights fulfilment and grievance handling, HR teams on employee data processing under section 7(i), and procurement teams on Data Processor assessment and contract negotiation. Training completion should be recorded and the records retained as evidence of the organisational measures implemented under section 8(4) (para 12.2.3). Role-specific sessions of this kind, live or recorded, run on Taxmann.com | Learning, and can be arranged for an organisation.
6. What will the auditor test, obligation by obligation?
The book answers this at the end of each obligation chapter. Consolidated, the test programme and the evidence it calls for look like this:
| Obligation area | What the auditor will test | Key evidence |
|---|---|---|
| Lawful basis (para 3.8) | Whether every processing activity has a documented lawful basis, whether section 7 grounds were assessed before defaulting to consent, and whether the register has been reviewed | Lawful basis register; the specific section 7 clause relied on; the notice version in effect at the time of consent; evidence of periodic review with reviewer identity |
| Notice and consent (para 4.10) | Whether the notice is standalone and understandable independently under Rule 3(a), whether each purpose links to specific goods, services or uses under Rule 3(b)(ii), whether consent records carry the notice version, and whether withdrawal is of comparable ease | Current notice; version control log with effective dates; immutable consent records; withdrawal mechanism documentation and a step-count comparison |
| General obligations (para 5.8) | Whether the governance structure and role assignments are documented, whether every Data Processor engagement is under a valid contract with Rule 6(1)(f) security provisions, and whether the grievance response period is published and met | Governance charter; Data Processor register with contract status; sample Data Processing Agreements with security clauses; grievance log with receipt and resolution dates |
| Security safeguards and breach (para 6.5) | Each of the seven Rule 6(1) requirements separately, plus whether a documented breach response plan exists, has been tested by tabletop exercise, and whether notification templates are pre-drafted | Encryption configuration; access control matrix with last review date; log retention configuration; breach response plan with version history; tabletop exercise reports |
| Children’s data (para 7.8) | Whether age-gating operates beyond self-declaration, whether parental verification records record the Rule 10(1) method, and whether section 9(3) prohibitions are enforced at system level rather than by policy directive | Age-gating design specification; parental consent verification records; advertising and analytics platform configuration showing child-account exclusion; Fourth Schedule exemption register |
| Retention, deletion and cross-border (para 8.10) | Whether data that has reached retention expiry has actually been erased, comparing the schedule against actual database records; whether Data Processor erasure is evidenced; whether transfers are registered | Retention schedule with legal references; deletion logs correlated to the schedule; Data Processor erasure instructions and written confirmations; cross-border transfer register |
| Rights and grievance (para 9.8) | Whether the rights mechanism is prominently published under Rule 14(1), whether identification requirements are no more burdensome than terms of service, and whether declined erasures are documented and deferred erasures tracked | Screenshots of the published mechanism and grievance period; rights request log from intake to closure; register of declined erasure requests with legal retention references |
| Significant Data Fiduciary (para 10.8) | Whether the DPO is appointed, based in India and reports to the governing body; whether the DPIA was done within the Rule 13(1) twelve-month cycle; whether the auditor was independent; whether the Rule 13(2) report reached the Board | DPO appointment letter or board resolution and terms of reference; current and prior DPIA with remediation tracking; auditor engagement letter with independence declaration; evidence of Board submission |
| Exemptions (para 11.7) | Whether each claimed exemption is documented with the section 17 clause, the factual basis and the conditions satisfied, and whether provisions that remain in force, particularly sections 8(1) and 8(5), are actually observed | Exemption register with clause, basis and conditions; evidence of continued observance of the preserved obligations; Second Schedule compliance assessment for research processing |
| Compliance programme (para 12.3) | Whether the governance structure has defined accountability, whether the eight-policy architecture is covered, whether training completion records exist, and whether the programme has a periodic review mechanism rather than being a one-time project | Governance documentation; the policy set; training completion records; the Appendix A artefacts per requirement; regulatory interaction mapping for the sector |
| Sector specific (para 13.10) | Whether a regulatory interaction matrix maps DPDP obligations against sectoral requirements, and whether the more restrictive requirement is applied where both frameworks address the same obligation | Regulatory interaction matrix; banking retention reconciled with KYC periods; healthcare Fourth Schedule conditions; SaaS processor contracts covering cross-border flows and tenant-level residency |
| Enforcement readiness (para 14.9) | Whether a Board inquiry response protocol exists and has been communicated, whether the evidence framework is maintained in a state of readiness, and whether at least one inquiry simulation has been conducted | Response protocol and SOP; the evidence framework itself; simulation exercise records; a section 33(2) penalty calibration assessment for the organisation’s risk profile |
Two of these deserve emphasis because they are where the audit most often turns from a paper review into a real test. On retention, the auditor compares the retention schedule against actual database records, which means a schedule that has never been executed is worse than no schedule, because it evidences a known and unmet commitment. On children’s data, the auditor looks for configuration evidence in the advertising and analytics platforms, not a memo to the marketing team.
7. Which findings recur, and what causes them?
The book reports 57 findings across its twelve Audit Considerations sections. They are not random. Read together, almost all of them fall into one of four patterns, and recognising the pattern is faster than memorising the list.
Pattern one: the artefact exists but was never executed. A retention schedule exists on paper but no automated deletion process runs, so data remains indefinitely (para 8.10). A breach response plan exists but has never been tested through a tabletop exercise (para 6.5). A lawful basis register has not been reviewed since it was created (para 3.8). A grievance mechanism is published but no grievances are recorded, which suggests the mechanism is either inaccessible or non-functional (para 9.8).
Pattern two: the control is a policy directive rather than a system setting. Section 9(3) compliance is an instruction to the advertising team with no system-level enforcement (para 7.8). Access control lists have not been reviewed since initial configuration, leaving stale permissions for departed or reassigned employees (para 6.5). Encryption is applied to production databases but not to backup media or test environments containing real personal data (para 6.5).
Pattern three: the record cannot be linked to the thing it is supposed to prove. Consent records are not linked to notice versions, which is fatal because section 6(10) requires proof both that notice was given and that consent was obtained (para 4.10). Deletion logs are not maintained, making it impossible to prove that erasure occurred (para 8.10). Erasure requests are declined without documenting the specific legal basis for retention (para 9.8). A DPIA was completed but the Rule 13(2) Board reporting step was omitted (para 10.8).
Pattern four: an assumption stands in for an assessment. Exemptions are claimed without documentation, the organisation simply assuming an exemption applies without recording the basis (para 11.7). Security safeguards are relaxed for exempt processing on the assumption that the exemption removes all obligations, when section 17(1) expressly preserves sections 8(1) and 8(5) (para 11.7). An algorithmic risk assessment is not conducted because the organisation did not recognise its recommendation engine or fraud scoring model as falling within Rule 13(3) (para 10.8). SaaS providers treat themselves as having no DPDP obligations because they are Data Processors, overlooking the security safeguard, contractual and erasure obligations that do apply to Data Processors (para 13.10).
A selection of the findings, in the book’s own terms, with the structural cause:
| Area | Finding | Why it happens |
|---|---|---|
| Lawful basis | Processing activities without any documented lawful basis | Legacy processing predating the programme, vendor processing under informal arrangements, and ad hoc processing started by business units without privacy team involvement (para 3.8) |
| Lawful basis | Over-reliance on consent where a legitimate use applies | Defaulting to consent without assessing section 7, which creates withdrawal risk the organisation need not have carried (para 3.8) |
| Notice | Notice not standalone, referencing terms of service for key details | Treating the notice as a privacy policy rather than the self-contained document Rule 3(a) requires (para 4.10) |
| Consent | Withdrawal mechanism requires more steps than consent | Consent is built by the growth team and withdrawal by the support team (para 4.10) |
| Processors | Data Processor engagements without written contracts, particularly with legacy vendors | Vendor management treated as a procurement function rather than a compliance function (paras 5.8 and 5.7.1) |
| Security | Logs retained for less than one year due to storage cost constraints | Rule 6(1)(e) and Rule 8(3) were never translated into a storage budget line (para 6.5) |
| Breach | No pre-drafted Board notification template, so the team would draft from scratch under seventy-two-hour pressure | The timeline was read as a reporting deadline rather than a drafting constraint (para 6.5) |
| Rights | No structured log, with requests handled through ad hoc email exchanges without tracking | An unstructured inbox cannot produce the dates a Board proceeding will ask for (paras 9.8 and 9.7.2) |
| Rights | Deferred erasures not tracked, so data is retained beyond the expiry of the legal retention period | The refusal was legitimate when made and no review mechanism exists to trigger the deferred erasure (paras 9.8 and 9.7.3) |
| Significant Data Fiduciary | DPIA conducted but limited to a policy review, with no data flow mapping, no risk register and no algorithmic assessment | The DPIA was scoped as a document exercise rather than a risk assessment (para 10.8) |
| Programme | Training conducted for legal and IT teams but not for customer-facing staff who handle rights requests and grievances | Training budget follows the project team rather than the obligation (para 12.3) |
| Enforcement | Appeal timeline of sixty days not tracked | No one owns the post-order calendar (para 14.9) |
8. How is a gap assessment run before the audit?
As a mapping exercise at the level of systems and processes, not at the level of the organisation. The book’s method, set out for security safeguards and applicable throughout, is to map existing controls against each requirement, identifying where controls exist, where they are partially implemented, and where they are absent, and to conduct the assessment at the level of each system and process that handles personal data rather than at the organisational level, because security postures vary significantly across systems. Its illustration is familiar to anyone who has done this work: a production database may be well-encrypted and access-controlled while a legacy reporting system operates with minimal safeguards (para 6.3.1).
The assessment should produce a remediation plan with prioritised actions, estimated timelines and assigned ownership for each gap, approved at the appropriate level of management (para 6.3.1).
The book sequences the whole programme in three phases against the 13 May 2027 enforcement date: discovery and assessment first, then design and implementation, and testing and validation in the final two to three months (para 12.1.1). The phases, and the readiness checklist that goes with them, are set out in the DPDP Act compliance checklist for businesses.
Where that remediation has to be built rather than listed, including compliance SOPs and automation of compliances, Taxmann Advisory provides implementation support.
9. What should be in place in the first ninety days?
The foundational artefacts. By the end of the first ninety days the organisation should have a documented data inventory, a preliminary lawful basis register, an initial gap analysis identifying the highest-priority remediation areas, a programme plan with milestones and resource requirements, and a governance structure with defined roles and accountabilities. These artefacts ensure the programme proceeds from a foundation of fact rather than assumption (para 12.1.2).
Figure 12.1, the book’s Compliance Readiness Checklist for those ninety days, and the three-tier governance structure behind it are set out in the DPDP Act compliance checklist for businesses.
10. Does an existing ISO 27001 or SOC 2 report cover this?
No, and the book is direct about why. An organisation that assumes its existing ISO 27001 certification or SOC 2 report satisfies the DPDP Act’s requirements will discover gaps in precisely those areas where the Act goes beyond information security into data protection governance, transparency and individual rights. The existing frameworks are a foundation for the DPDP compliance programme, not a substitute for it (para 12.3).
That assumption appears in the book’s list of recurring findings in exactly that form: an existing ISO 27001 or SOC 2 framework treated as sufficient for DPDP compliance without addressing the data protection-specific gaps of notice, consent, rights and retention (para 12.3).
The encouraging half of the same point is that the disciplines are not new. The book’s note for compliance professionals observes that risk assessments, evidence-based assurance, control documentation, audit trails, exception management and governance reporting have long been established features of financial reporting, internal audit and assurance frameworks. A Data Protection Impact Assessment is, structurally, a risk assessment. A requirements register is a control matrix. A Board inquiry response file is evidence preparation for a regulatory assessment proceeding conducted through a digital interface. The subject matter is personal data rather than financial information, but the underlying disciplines are familiar (para 12.3).
One further interaction belongs in the scope discussion. The CERT-In Directions of 28 April 2022, issued under section 70B(6) of the Information Technology Act, 2000, require covered entities to maintain logs of ICT systems for a rolling period of one hundred and eighty days and to retain those logs within the territory of India, while Rule 6(1)(e) and Rule 8(3) of the DPDP Rules impose a separate requirement to retain relevant logs and associated processing records for a minimum of one year. The book treats these as cumulative rather than alternative, and recommends a single log management architecture retaining twelve months of logs within India, which is operationally simpler and satisfies both frameworks more effectively than separate retention arrangements (para 6.4).
11. How does the audit connect to a Board inquiry?
Directly, because the same file answers both.
Section 28(5) permits the Board, where it determines there are sufficient grounds, to inquire into the affairs of any person for ascertaining compliance, for recorded reasons. Rule 19(9) requires the inquiry to be completed within six months from the date of receipt of the intimation, complaint, reference or direction under section 27, extendable by the Board for recorded reasons for a further period not exceeding three months at a time. The Board conducts its proceedings as a digital office under section 28(1) and Rule 20, so submission of evidence, hearing of arguments and pronouncement of decisions are conducted online (para 12.2.5).
The book’s conclusion from those three facts is the reason the evidence framework exists at all: preparation should begin not when the inquiry is received but when the compliance programme is established, so that the production of evidence in response to a Board direction is an easier retrieval exercise rather than a stressful creation exercise (para 12.2.5).
Seen from the enforcement side, the overlap is complete. The evidence generated during breach detection, investigation and notification will be the same evidence the Board examines during its inquiry, and the organisation’s consent records, notice versions, security safeguard documentation, grievance logs and rights fulfilment records should be maintained in a state of constant readiness, because an inquiry may be initiated at any time on receipt of a complaint under section 27(1)(b) and the six-month timeline means evidence must be produced promptly once it commences (para 14.8.1).
Appendix A closes the loop. Step 3 of the book’s Board Inquiry Response Protocol, covering days seven to twenty-one after receipt, is to compile documentary evidence responsive to the inquiry, prepare a chronological narrative of the relevant events, cross-reference the evidence against the Appendix A requirements register, and identify gaps and prepare explanations for any deficiencies (para 14.8.2). The register that drives the audit is the same register that drives the inquiry response.
12. Quick answers
Is a DPDP audit mandatory?
An independent data audit is mandatory only for Significant Data Fiduciaries. Section 10(2)(b) requires the appointment of an independent data auditor, and Rule 13(1) requires a Data Protection Impact Assessment and an audit once in every period of twelve months from the date of notification as a Significant Data Fiduciary. Other Data Fiduciaries have no statutory audit obligation, but section 6(10) places the burden of proving notice and consent on them and section 28(5) empowers the Board to inquire into the affairs of any person for ascertaining compliance, which together create an effective obligation of demonstrable compliance.
Who can conduct a DPDP data audit?
Section 10(2)(b) requires an independent data auditor but does not define independence. Drawing on the Companies Act, 2013, the ICAI’s standards on auditing and the ISACA framework, independence would ordinarily require that the auditor has no financial interest other than the audit engagement, does not provide consulting or implementation services on the same subject matter being audited, is not a current or recent employee, and exercises professional judgment without direction from management. An auditor that designed the controls it is auditing would face legitimate questions about independence in a Board proceeding.
What evidence does a DPDP audit require?
Six layers for each obligation: the policy that governs it, the process document describing how the policy is implemented, the records and logs capturing execution, the technical configurations enforcing the controls, the governance artefacts documenting oversight and accountability, and the testing proof verifying that the controls work. Appendix A to Taxmann’s Digital Personal Data Protection consolidates all 49 requirements across fifteen subject areas and lists the specific evidence items for each.
How many requirements are there under the DPDP Act and Rules?
The Consolidated Requirements Register in Appendix A to Taxmann’s Digital Personal Data Protection sets out 49 consolidated entries covering all obligations under the Act and the Rules, organised into fifteen subject areas from scope and roles to commencement timelines. Where the Rules expand or operationalise an obligation under the Act, the requirement is merged into a single entry with both references cited.
What are the most common DPDP audit findings?
Taxmann’s Digital Personal Data Protection reports 57 findings across twelve obligation chapters. The recurring ones are a retention schedule that exists on paper with no automated deletion process; a breach response plan that has never been tested; consent records not linked to notice versions; Data Processor engagements without written contracts; section 9(3) children’s protections enforced by policy directive rather than system configuration; declined erasure requests without a documented legal basis; deferred erasures not tracked after the retention period expires; a DPIA limited to a policy review; and exemptions claimed without documenting the basis.
Does ISO 27001 or SOC 2 satisfy DPDP compliance?
No. Taxmann’s Digital Personal Data Protection states that an organisation assuming its existing ISO 27001 certification or SOC 2 report satisfies the DPDP Act will find gaps precisely where the Act goes beyond information security into data protection governance, transparency and individual rights. The existing frameworks are a foundation for the programme, not a substitute for it.
This article draws on Chapter 12 of Taxmann’s Digital Personal Data Protection – An Essential Guide to India’s DPDP Law by CA Narasimhan Elangovan (2026 Edition), which sets out the compliance programme framework, the evidence architecture for demonstrable compliance, the minimum policy set and the readiness checklist in Figure 12.1. It also draws on Appendix A, the Consolidated Requirements Register, which states all 49 obligations as testable requirements with their legal references and audit evidence items across fifteen subject areas, on Chapter 10 on the independent data audit and the DPIA, and on the Audit Considerations sections that close Chapters 3 to 14 with 57 recurring findings. Law stated as updated till 15 September 2026.
The DPDP Act, 2023, the DPDP Rules, 2025 and the notifications of 13 November 2025 are available on Taxmann.com | Research under Indian Acts and Rules.
Related reading: the DPDP Act compliance checklist for businesses · obligations of Data Fiduciaries under the DPDP Act · the impact on startups and SMEs · an analysis of the Act read with the Rules.
More in this series: the Data Protection Board of India · Significant Data Fiduciary obligations · Consent Managers under the DPDP framework · personal data breach intimation under Rule 7 · handling Data Principal rights requests · Data Fiduciary, Data Processor or both · children’s data and verifiable parental consent · the SPDI Rules and the DPDP Act · the Record of Processing Activities (ROPA) · the incident response plan · data retention and erasure · the privacy notice under Rule 3 · the data processing agreement · data localisation and cross-border transfers · employee data and workplace monitoring · exemptions under the DPDP Act · legitimate uses under section 7.
Disclaimer: The content/information published on the website is only for general information of the user and shall not be construed as legal advice. While the Taxmann has exercised reasonable efforts to ensure the veracity of information/content published, Taxmann shall be under no liability in any manner whatsoever for incorrect information, if any.

Taxmann Publications has a dedicated in-house Research & Editorial Team. This team consists of a team of Chartered Accountants, Company Secretaries, and Lawyers. This team works under the guidance and supervision of editor-in-chief Mr Rakesh Bhargava.
The Research and Editorial Team is responsible for developing reliable and accurate content for the readers. The team follows the six-sigma approach to achieve the benchmark of zero error in its publications and research platforms. The team ensures that the following publication guidelines are thoroughly followed while developing the content:
- The statutory material is obtained only from the authorized and reliable sources
- All the latest developments in the judicial and legislative fields are covered
- Prepare the analytical write-ups on current, controversial, and important issues to help the readers to understand the concept and its implications
- Every content published by Taxmann is complete, accurate and lucid
- All evidence-based statements are supported with proper reference to Section, Circular No., Notification No. or citations
- The golden rules of grammar, style and consistency are thoroughly followed
- Font and size that’s easy to read and remain consistent across all imprint and digital publications are applied


CA | CS | CMA