Updated: 14 May 2026
An honest evaluation for Indian IT and security teams navigating the 2026 compliance landscape
The best MFA solution for Indian enterprises in 2026 depends on one factor above all others: the breadth of your authentication surface.
There is no single best MFA solution for Indian enterprises. There is a best solution for your environment — and that distinction is doing a lot of work. This piece covers the leading enterprise MFA platforms available in India, how they differ, what the Indian regulatory landscape requires, and the framework for making the decision that fits your organisation specifically. It is written to be useful to an IT head or CISO who has moved past "should we deploy MFA" and is now asking "which one, and why."
Four regulatory deadlines have converged in a narrow window that transforms MFA from a best-practice recommendation into a compliance requirement for most Indian enterprises.
RBI Authentication Mechanisms Directions 2025, effective 1 April 2026. The RBI now mandates flexible multi-factor authentication for digital payment transactions and formally acknowledges authenticator apps, hardware tokens, and FIDO2 cryptographic methods as alternatives to SMS OTP. This applies to banks, NBFCs, and payment system operators and covers both customer-facing payment authentication and internal employee access to critical banking systems.
SEBI Cybersecurity and Cyber Resilience Framework (CSCRF). SEBI's CSCRF mandates MFA for privileged access to market infrastructure systems. Compliance deadlines ran from January to April 2025 by entity category. Brokers, asset managers, custodians, and depository participants that have not yet deployed MFA for privileged access are already outside the compliance window.
CERT-In mandatory audit guidelines, effective July 2025. CERT-In's information security audit framework for private sector entities lists MFA for privileged accounts as an expected control. Auditors will ask for evidence of individual accountability for system access — shared accounts fail this test regardless of whether MFA is deployed on top of them.
DPDP Act, full compliance deadline 13 May 2027. India's Digital Personal Data Protection Act 2023 does not mandate MFA by name but requires "reasonable security safeguards" for personal data — a standard that, in 2026, every credible legal interpretation includes MFA for systems that store, process, or transmit personal data. Organisations that suffer a breach without MFA controls will face significant difficulty demonstrating compliance with this standard to the Data Protection Board.
Four data points that contextualise the urgency:
Best suited for: Mixed-vendor Indian enterprise environments — organisations running Cisco VPN, legacy on-premises ERP, Linux servers, OT or SCADA systems, and non-Microsoft SaaS alongside Microsoft workloads. Manufacturing organisations with plant floor workers needing hardware TOTP tokens. IT/ITeS companies and GCCs requiring coverage across both Indian regulatory requirements and parent-company security mandates. Any organisation where the authentication surface extends beyond the Microsoft perimeter.
Cisco Duo is a purpose-built identity security platform acquired by Cisco in 2018 and now operating as the company's primary zero trust access and identity offering. Its architectural distinction is universality: Duo integrates with virtually any application, system, or infrastructure component without requiring those systems to be cloud-native, Microsoft-native, or modernised. It deploys a cloud service alongside an on-premises Authentication Proxy that bridges the gap between Active Directory environments and Duo's cloud — covering legacy VPN via RADIUS, on-premises ERP, Linux servers, network infrastructure, and OT/SCADA systems in industrial environments.
Cisco Duo Essentials is priced at $3 per user per month and covers MFA for unlimited application integrations, SSO, and passwordless authentication. Duo Advantage, at $6 per user per month, adds device health checks, posture management, risk-based adaptive authentication, and Cisco Identity Intelligence for cross-identity analytics and threat detection. Duo Premier, at $9 per user per month, adds VPN-less remote access via Duo Network Gateway and advanced risk scoring.
Duo operates a Mumbai data centre for Indian tenants. Indian customer identity data is processed and stored in India. The Mumbai instance is certified to ISO 27001 and SOC 2, and carries a 99.999% availability SLA. This has been operational since May 2022 — making Duo the longest-established enterprise MFA platform with India data residency.
The phishing-resistant MFA story matters specifically for Indian enterprises. Duo's Verified Push feature requires users to enter a number displayed on their login screen into the Duo mobile app before the push is approved. This defeats MFA fatigue attacks — the push bombing technique behind the 2022 Uber breach and the 2023 MGM Resorts incident — by requiring a real-time number match that a remote attacker cannot complete. Duo also supports FIDO2 hardware security keys and passkeys natively across all tiers. RBI's 2026 framework explicitly points Indian financial institutions toward phishing-resistant authentication methods, and Duo's entire tier structure satisfies this requirement without premium add-ons.
For Indian manufacturing deployments specifically — a context covered in detail in our [MFA for Manufacturing white paper] — Duo's hardware TOTP token support, Authentication Proxy architecture for legacy SCADA systems, and shift-based session management address the plant floor deployment reality that no other enterprise MFA platform has purpose-built for. India is the world's second most attacked country in manufacturing, with over 2,100 attacks per organisation per week (Check Point Research 2024). The entry point in the majority of ransomware cases is a credential — often a shared one, or a vendor account nobody deactivated.
Best suited for: Organisations that are genuinely Microsoft-native — Azure, Intune, M365 E3/E5 end-to-end, with minimal non-Microsoft infrastructure. Cloud-first organisations with modern infrastructure that does not require RADIUS proxies or legacy application integrations. Environments where the licensing cost of Duo is not justified because the authentication surface gap between Microsoft's coverage and Duo's is small.
Microsoft Authenticator is the mobile app component of Microsoft Entra ID. Its capabilities depend entirely on licensing tier. Security Defaults — included at most Microsoft 365 tiers — provides basic MFA that works adequately as a floor but is a blunt instrument: one policy for all users, limited factor configuration, no adaptive controls, no device posture enforcement.
The sophisticated controls most enterprises need — risk-based Conditional Access, device compliance enforcement, phishing-resistant authentication — require Entra ID P1 or P2 licensing, typically obtained through Microsoft 365 E3 or E5. For organisations already on those tiers for other reasons (Teams, Office applications, Intune), MFA is genuinely included at no extra cost. For those who are not, the additional licensing cost deserves honest scrutiny before treating Microsoft as the free option.
When properly licensed and configured, Microsoft Entra ID with Conditional Access is a formidable identity platform. Policies can enforce MFA based on user location, device compliance state, sign-in risk score, and application sensitivity. At P2, Identity Protection adds machine learning-driven risk scoring. This is enterprise-grade identity security. It is not a toy, and treating it as one would be inaccurate.
The question is not whether Microsoft's MFA is good. It is. The question is scope. Entra ID Conditional Access protects the Microsoft perimeter well. For Indian enterprises running Cisco VPN, legacy on-premises applications, Linux infrastructure, or OT systems — which describes the majority of mid-market organisations with more than five years of infrastructure history — it does not protect the rest. Attackers do not target the most protected application. They find the one not covered by the primary MFA policy.
One India-specific data residency note: Microsoft does not operate dedicated India Entra ID data centres for identity data. Indian customer identity data may be processed in Microsoft's global infrastructure. This is a consideration for organisations interpreting the DPDP Act's data localisation expectations, particularly in the BFSI sector where RBI has historically emphasised data residency.
Best suited for: Large Indian enterprises (typically 2,000+ users) with complex, multi-cloud SaaS estates requiring comprehensive identity governance beyond MFA. GCCs with parent-company Okta standardisation where extending to the Indian entity is the path of least friction. Organisations where CIAM (Customer Identity and Access Management) is also required alongside workforce identity.
Okta is an independent identity platform with one of the broadest pre-built integration catalogues in the market — over 7,000 applications. Its strength is full identity lifecycle management: provisioning, deprovisioning, identity governance, and MFA across a large, heterogeneous SaaS estate. As a vendor-neutral platform, it works across Microsoft and non-Microsoft applications without the ecosystem dependency that Entra ID carries.
Okta announced Indian data residency in January 2026, with in-country platform tenants hosted on AWS in India — directly addressing DPDP Act data localisation considerations. New and existing Okta customers can deploy with India-region tenants. This is a meaningful development for regulated Indian sectors that had previously raised data residency as an objection to Okta adoption.
Okta's pricing is typically perceived as enterprise-tier — base workforce identity products start at $2+ per user per month, escalating with add-ons for advanced governance and lifecycle management. For Indian mid-market organisations comparing MFA platforms on cost, Okta is typically the most expensive option in the mainstream set.
One honest limitation: as of early 2026, Okta has no India-specific content, no Indian customer case studies, and no sector-specific guidance for BFSI, manufacturing, or GCCs. Its India strategy has been announcement-driven rather than content-driven. For Indian IT teams doing due diligence, support for the Indian regulatory and infrastructure context will need to come from implementation partners rather than from Okta's own documentation.
Best suited for: SME and lower mid-market Indian organisations — typically up to 500–1,000 users — where cost is a primary driver, on-premises deployment is preferred, and the infrastructure is not highly complex. Organisations wanting India-based support with IST business hours and a vendor that natively positions its product against Indian compliance frameworks.
ManageEngine, the IT management division of Zoho Corporation, is an Indian-headquartered company with a strong mid-market presence across India. ADSelfService Plus is an identity security platform providing MFA, self-service password reset, and single sign-on, with both cloud and on-premises deployment options.
ManageEngine is notably the only mainstream MFA vendor that natively positions its product against Indian compliance frameworks — CERT-In, RBI, and DPDP — in its own product documentation and marketing. For Indian buyers who want compliance mapping from the vendor rather than relying on a third-party partner to interpret regulatory requirements, this is a meaningful differentiator.
Pricing is significantly lower than the global platforms, and the on-premises deployment option addresses data residency concerns for smaller organisations without requiring a cloud commitment. Support is India-based with IST business hours.
The limitation at enterprise scale: ADSelfService Plus's risk-based adaptive authentication, identity threat detection, and zero trust access capabilities are less mature than Cisco Duo Advantage or Okta at the large enterprise level. For organisations below 500 users with straightforward Active Directory environments, this gap is often irrelevant. For larger enterprises with sophisticated security requirements or multiple geographic locations, it matters.
Best suited for: Similar to ManageEngine — SME and lower mid-market, cost-sensitive environments where India-based support and simpler deployment are priorities. Organisations needing a broad integration catalogue at a lower price point than the global platforms.
miniOrange is an Indian MFA and identity security vendor offering both SaaS and on-premises deployment. It provides a wide integration catalogue and competitive pricing for the Indian market, with support for standard MFA factors, SSO, and Active Directory integration. Like ManageEngine, it positions its product against Indian compliance requirements and provides India-based support.
miniOrange's enterprise feature depth is comparable to ManageEngine's at the SME and lower mid-market level — adequate for standard MFA use cases, less comprehensive for risk-based authentication, device trust enforcement, and zero trust access architecture at scale. It remains a viable and cost-effective option for smaller Indian organisations where the global platforms are over-engineered for the requirement.
Side-by-side: Enterprise MFA solutions for Indian organisations
| Criteria | India relevance | Cisco Duo | Microsoft Entra ID | Okta | ManageEngine |
|---|---|---|---|---|---|
| Best environment fit | Most Indian mid-market enterprises have mixed infrastructure | Mixed/multi-vendor — Cisco VPN, Linux, legacy apps, OT | Microsoft-native — Azure, M365 E3/E5 end-to-end | Large enterprise, multi-cloud SaaS estate | SME/mid-market, on-premises AD environments |
| MFA for legacy apps | Critical — most Indian enterprises have pre-cloud infrastructure | Yes — via RADIUS proxy, no app changes needed | Limited — requires modern authentication support | Limited — RADIUS integration available but not primary | Yes — strong AD integration for on-prem legacy |
| Phishing-resistant MFA | RBI and CERT-In both reference phishing-resistant methods | Verified Push + FIDO2 across all tiers | FIDO2 supported; Verified Push not available | FIDO2 supported; push notification standard | TOTP and push; Verified Push not available |
| Data stored in India | DPDP Act "reasonable safeguards"; RBI data localisation expectations | Yes — Mumbai DC, ISO 27001, SOC 2, since May 2022 | Limited — global infrastructure; India residency not guaranteed for identity data | Yes — India data residency announced January 2026 | Yes — on-premises deployment option; Zoho India-headquartered |
| OT/manufacturing environments | India is the world's second most attacked country in manufacturing | Supported — hardware tokens, RADIUS, shared workstations | Not suited for OT/shop-floor environments | Not suited for OT environments | Limited — AD-focused, not designed for OT |
| Pricing entry point | Cost per user per month for 500+ user Indian enterprise | $3/user/month — Essentials, unlimited apps | Included in E3/E5; P1/P2 add-on if not on those tiers | $2+/user/month base, add-ons for full governance | Significantly lower than global platforms — contact for INR pricing |
| RBI/DPDP audit logging | RBI examiners request granular auth logs; DPDP breach investigations require documented access controls | Granular, exportable, available on all tiers | Comprehensive at P2; limited at lower tiers | Comprehensive across tiers | Available; less granular than global platforms |
| India-native compliance mapping | Reduces burden on implementation partner for regulatory interpretation | Via Proactive — India-specific deployment expertise | No India-specific regulatory documentation | No India-specific regulatory documentation | Yes — CERT-In, RBI, DPDP cited in product documentation |
| Deployment speed | Urgency driven by regulatory deadlines and audit windows | Same-day for simple use cases; 4–8 weeks for full enterprise | Variable — complex environments require significant configuration | Weeks to months for full deployment | Faster for on-prem AD environments; varies for cloud |
| Zero trust access | Both RBI and CERT-In reference zero trust architecture | Native — Duo Network Gateway (Premier tier) | Via Microsoft Entra Private Access (separate licensing) | Native ZTNA capabilities | Limited zero trust capabilities |
Most MFA buying decisions go wrong, not because organisations pick the wrong product but because they answer the wrong question. They ask "which product has better features," when the question that actually determines outcomes is: what does your complete authentication surface look like?
Before evaluating any vendor, map your environment honestly across three dimensions.
Your application and system inventory. Every application that holds sensitive data or provides privileged access. Every system — cloud, on-premises, legacy, network infrastructure, OT. Every access point where authentication currently occurs without a second factor. Be specific about the applications that authenticate via RADIUS or LDAP against on-premises Active Directory — this is where Microsoft's coverage typically ends, and Duo's universality matters most.
Your user population. Full-time employees, contractors, remote workers, and third-party vendors with system access. For each population: do they have smartphones? Are they in glove-based or device-prohibited environments? Are their accounts formally decommissioned when engagements end? The answers determine which factors are viable and whether your credential inventory is clean enough to deploy MFA into.
Your regulatory obligations. Which regulations apply to your sector and what specifically do they require? The RBI mandate covers banks and NBFCs. SEBI CSCRF covers registered market intermediaries. CERT-In audits cover all significant private sector entities. The DPDP Act covers any organisation handling personal data of Indian residents. Multiple regulations may apply simultaneously — an IT services company handling client financial data may be subject to RBI, CERT-In, and DPDP requirements at the same time.
Once that map exists, the vendor choice typically follows without ambiguity:
If your map is predominantly Microsoft: Entra ID Conditional Access on E3/E5 is your natural starting point. You are not paying extra, your IT team knows the tooling, and the coverage gap is manageable.
If your map includes significant non-Microsoft territory: Cisco Duo is typically the right choice. It was designed to protect everything, not just one vendor's ecosystem.
If your requirement extends to full identity lifecycle governance across a large, heterogeneous SaaS estate: Okta is worth a structured evaluation, with the understanding that India-specific deployment support will come from implementation partners rather than Okta's own documentation.
If cost is the binding constraint and your environment is not highly complex: ManageEngine ADSelfService Plus is a credible, India-built option that delivers adequate MFA for straightforward use cases with native Indian compliance documentation.
One factor that must inform every decision in the Indian context: phishing-resistant MFA is no longer aspirational. It is the direction RBI's 2026 framework points, it is what CERT-In auditors increasingly expect for privileged access, and it is the specific control that defeats the attack technique — MFA fatigue — that has compromised organisations with mature security programmes globally. Before selecting any platform, confirm that phishing-resistant methods (Verified Push or FIDO2 hardware keys) are available at the tier you are evaluating, not a premium add-on.
Quick answers to common questions about this topic.
We'll get back to you shortly.