by
Ruchin Kumar, VP South Asia, Futurex
Last updated: November 18, 2026
India's Digital Personal Data Protection (DPDP) Act, 2023, and Digital Personal Data Protection Rules, 2025, introduce requirements for the handling of covered digital personal data. Implementation is phased.
As of November 17, 2026, the Data Protection Board of India has been established, but most core processing, security, breach-notification, and penalty provisions are scheduled to take effect on May 13, 2027.
For enterprise security and privacy leaders, the immediate priority is to identify affected data flows, assign accountability, and test whether existing safeguards support the obligations that will become applicable. The law does not prescribe a particular HSM, tokenization product, or FIPS certification.
These 10 priorities distinguish the law, practical implementation decisions, and where Futurex data protection technology may help.
1. Understand the Phased DPDP Timeline and Scope
The DPDP Act adds a national framework for covered digital personal data. It does not completely replace the Information Technology Act, 2000, or every existing sector-specific requirement. Its scope includes digital personal data collected in India, whether in digital form or later digitized. It can also cover processing outside India connected with offering goods or services to people in India. Statutory exclusions apply.
Commencement matters. The November 13, 2025 notification brought institutional and certain other provisions into force immediately. Consent Manager registration provisions took effect one year later, on November 13, 2026. The principal obligations in sections 3 through 17, including section 8 safeguards and breach notification, are scheduled for May 13, 2027. Prepare against the relevant effective dates, not the Act's 2023 enactment date alone.
2. Define Data Fiduciary and Processor Responsibilities
A Data Fiduciary determines the purpose and means of processing personal data. Section 8 makes the Data Fiduciary responsible for compliance with respect to processing it undertakes itself or through a Data Processor. Processing on its behalf requires a valid contract; Rule 6 also addresses appropriate security provisions in those contracts. These duties are scheduled to take effect in May 2027.
Boards should oversee ownership, investment, incident response, and risk acceptance. Do not claim that every processor failure automatically creates personal liability for each director. The Act places obligations on specified entities and establishes its own inquiry and penalty process.
3. Understand the Penalty Framework Without Overstating Exposure
The Schedule to the Act sets maximum penalties for specific breaches, subject to the applicable provisions and the Board's statutory process. Examples include:
• Up to INR 250 crore for breach of the duty to take reasonable security safeguards under section 8.
• Up to INR 200 crore for breach of the duty to notify the Board or affected Data Principals of a personal data breach under section 8.
• Up to INR 150 crore for breach of additional obligations that apply to a designated Significant Data Fiduciary under section 10.
These are separate statutory maximums, not automatic fines or a reliable forecast of total exposure after an incident. Section 33 requires a finding after inquiry and considers factors such as severity, mitigation, and proportionality. The main penalty provisions are scheduled to begin on May 13, 2027.
4. Translate Rule 6 Into Specific Control Requirements
Rule 6 of the 2025 Rules describes minimum categories of reasonable safeguards, which are scheduled to take effect on May 13, 2027. The text allows appropriate measures suited to the data and processing context. Its requirements include:
• Protection of data: Appropriate measures such as encryption, obfuscation, masking, or virtual tokens mapped to personal data.
• Access: Appropriate controls over computer resources used by the Data Fiduciary or its Data Processor, where applicable. Rule 6 does not impose universal multi-factor authentication.
• Detection and evidence: Logs, monitoring, and review to detect unauthorized access, investigate it, and prevent recurrence. Rule 6(e) specifies one-year retention of relevant logs and personal data for stated purposes, unless another law requires otherwise.
• Continuity and governance: Reasonable recovery measures, such as backups; suitable processor-contract provisions; and supporting technical and organizational measures.
Rule 7 adds a separate breach-notification process: inform affected Data Principals and provide an initial notice to the Board without delay, then provide specified details to the Board within 72 hours unless the Board permits a longer period. Treat these as future DPDP requirements while planning now.
5. Evaluate Software-Managed Cryptographic Key Risk
The relevant question is where keys are generated, stored, used, recovered, and administered, and what happens if an application host or privileged account is compromised.
Software-managed keys can be protected by operating-system, cloud, application, and access controls, but may share attack surfaces with the workloads they protect. Assess exposure to host compromise, memory access, administrator privileges, key export, and insufficient separation of duties. The DPDP Act and Rules do not declare software encryption inadequate in every deployment.
A hardware security module (HSM) can provide a distinct, tamper-resistant boundary for supported cryptographic keys and operations. That can be useful for higher-assurance workloads, but the DPDP Rules do not require FIPS 140-2 or FIPS 140-3 Level 3 compliance, nor does such certification itself establish DPDP compliance.
6. Know Where HSM-Backed Protection Adds Value
Compare the trust boundary and operating model, not a claim that all software encryption is insecure. The table below highlights questions to test during an architecture review.
|
Evaluation point |
Software-managed cryptography |
HSM-backed cryptography |
|
Key protection boundary |
Varies by OS, cloud service, and configuration |
Dedicated hardware boundary for supported keys and operations |
|
Exposure to host compromise |
Review host privileges, key export, and memory exposure |
Review HSM permissions, client access, and integration boundary |
|
Logging and auditability |
Depends on configured logging and independent retention |
Depends on configured HSM/service logging and independent retention |
|
Deployment tradeoffs |
May reduce dedicated hardware needs; assess shared controls |
Adds a separate cryptographic trust boundary and operational dependencies |
|
DPDP status |
Not categorically prohibited |
Not required by DPDP Rule 6 |
For key-intensive or higher-risk workloads, Futurex Excrypt HSMs provide a hardware cryptographic foundation. CryptoHub manages supported cryptographic services, key lifecycles, policies, and integrations. Evaluate the specific release, deployment model, interfaces, and operating responsibilities before making a product selection.
7. Separate DPDP Obligations From RBI Requirements
Financial institutions may face DPDP obligations alongside distinct Reserve Bank of India (RBI) directions. The rules differ by regulated entity. Do not treat the RBI requirements for non-bank payment system operators (PSOs) as universally applicable to banks, non-banking financial companies (NBFCs), and insurers.
For authorized non-bank PSOs, the RBI issued consolidated Cyber Resilience and Digital Payment Security Controls Master Directions on November 5, 2026. The following commencement dates apply to those directions:
• Large non-bank PSOs: in force from publication in November 2026.
• Medium non-bank PSOs: in force from publication in November 2026.
• Small non-bank PSOs: scheduled to take effect April 1, 2028.
These directions address governance, access controls, data protection, incident response, and other safeguards for covered PSOs. For example, the directions specify multi-factor authentication for certain electronic debit transactions, subject to exceptions. That is an RBI requirement for its defined scope, not a blanket mandate under DPDP Rule 6.
8. Map and Protect Personal Data in Legacy Systems
Legacy applications may contain personal data in fields, logs, file exports, backups, and interfaces that were not designed for modern privacy controls. The first task is to locate those data flows and determine which systems genuinely need the original values.
Tokenization can replace selected sensitive values with tokens before they reach downstream applications. Futurex CryptoHub supports vaultless and vault-based tokenization for supported use cases. Design work must account for token format, retrieval needs, access controls, integration paths, and where the original data is processed.
The potential benefits depend on the architecture:
• Data minimization in downstream systems: Tokenization can limit the exposure of original values where applications do not require them.
• Operational fit: Format-preserving approaches may reduce changes to systems that expect a fixed field shape. Performance and throughput must be measured against the actual workload; no zero-latency result is implied.
• Audit boundaries: Tokenization may change the scope of certain controls, but PCI DSS scoping and DPDP obligations require separate assessments. Point-to-point encryption is a distinct control and does not automatically accompany tokenization.
9. Assess Startup Obligations and Possible Exemptions
A startup is not automatically excluded from the DPDP Act because it is small or early-stage. Applicability depends on processing activities and statutory exclusions. Section 17(3) permits the government to notify certain classes of Data Fiduciaries, including startups, for limited exemptions from specified provisions. Do not assume an exemption without the relevant notification.
SaaS, fintech, health technology, and education technology teams should establish data inventories, processing purposes, vendor roles, retention rules, and incident ownership before choosing controls. The most useful investment depends on the data involved and the risk posed by the processing.
Ask five concrete questions: Which personal data do we process? Why do we need it? Which systems and vendors receive it? Who can access the originals and the keys? How would we identify, contain, and report a breach?
10. Build a Practical Four-Step DPDP Readiness Plan
Treat these steps as a readiness approach, not a regulator-prescribed certification process.
Step 1: Assign Accountability
Identify the Data Fiduciary, processors, affected business units, legal owners, and security owners. Record which DPDP provisions and other sector rules apply and when they take effect.
Step 2: Discover the Data
Map digital personal data, collection purposes, application flows, third parties, retention, backups, and key custody. Identify systems that store or transmit values they do not need.
Step 3: Assess Controls
Compare present controls with applicable requirements for notice and consent, access, protection methods, logs, incident response, recovery, contracts, and data rights. Prioritize gaps by consequence and deployment effort.
Step 4: Implement and Test
Apply targeted safeguards, test access and recovery, exercise breach response, document processor responsibilities, and preserve evidence. Use HSM-backed key management or tokenization where the risk assessment and technical requirements justify them.
Complete the highest-risk changes before the applicable commencement dates. A purchased tool, completed assessment, or HSM deployment does not itself constitute legal compliance.
Conclusion
The DPDP transition is a governance and implementation challenge, not a single encryption purchase. Organizations need a current inventory, defensible processing purposes, appropriate security controls, clear processor responsibilities, and tested response procedures.
The most useful next step is to identify which sensitive data flows need stronger protection and which cryptographic controls will make a measurable difference.
Review Futurex data protection and key management solutions, including HSM-backed cryptography and tokenization. See how Futurex solutions can support your data protection needs: https://www.futurex.com/solutions/data-protection
What does DPDP readiness involve?
DPDP readiness involves checking applicable processing activities, notice and consent or other lawful grounds, data rights, retention, processor arrangements, security safeguards, and breach response against the Act and Rules. The obligations do not all become effective on the same date.
Does the DPDP Act require encryption or HSMs?
Rule 6 lists appropriate measures such as encryption, obfuscation, masking, and virtual tokens, but it does not prescribe an HSM or require encryption for every data element in every setting. Other sector-specific rules may specify additional protection measures.
Can privacy-management software replace technical controls?
No. Consent and workflow software can support governance, but the organization must also evaluate access control, protection of data, logging, recovery, incident response, vendor obligations, and key management as applicable. An HSM is an option where hardware-backed protection is justified, not a universal DPDP condition.
Is a DPDP readiness review the same as a statutory audit?
No. A readiness review is an internal or adviser-led assessment of controls and obligations. Section 10 prescribes additional auditor and assessment duties for entities formally designated as Significant Data Fiduciaries. Those duties should not be described as a universal annual DPDP audit requirement.
Sources:
[1] Digital Personal Data Protection Act, 2023 (Sections 3, 8, 10, 17, 33, and Schedule). https://www.meity.gov.in/static/uploads/2024/02/Digital-Personal-Data-Protection-Act-2023.pdf
[2] Government of India, G.S.R. 843(E), November 13, 2025 (phased commencement). https://www.meity.gov.in/static/uploads/2025/11/c56ceae6c383460ca69577428d36828b.pdf
[3] Digital Personal Data Protection Rules, 2025, G.S.R. 846(E) (Rules 1, 4, 6, 7 and 8). https://www.meity.gov.in/static/uploads/2025/11/53450e6e5dc0bfa85ebd78686cadad39.pdf
[4] RBI Master Directions on Cyber Resilience and Digital Payment Security Controls for non-bank PSOs, November 5, 2026. https://rbi.org.in/Scripts/BS_ViewMasDirections.aspx?id=13751
[5] Futurex, Tokenization. https://www.futurex.com/solutions/tokenization
[6] Futurex, Enterprise Key Management Solutions. https://www.futurex.com/solutions/key-management-solutions