Published 19 November 2026 · Rathish Kumar, Invitty

RBI's Master Direction on Information Technology Governance, Risk, Controls and Assurance Practices, issued on 7 November 2023 and in force since 1 April 2024, makes multi-factor authentication mandatory in two places: for privileged users of critical information systems and critical activities (clause 19(c)), and for remote enterprise access to critical systems (clause 20(b)). If your admins or remote staff can reach a core system with only a password, that is an audit finding waiting to happen.

What the direction actually says

The access-control and teleworking clauses are short, so it is worth reading them exactly as RBI wrote them rather than through a vendor summary.

RBI Master Direction, 7 Nov 2023: access-related clauses
ClauseRequirement (RBI wording, abridged)What an auditor will ask for
19(a)Access only where a valid business need exists, under documented, approved proceduresThe access policy, and evidence that requests are approved
19(b)Personnel with elevated access closely supervised, with all activity logged and periodically reviewedAdmin activity logs and records of periodic review
19(c)MFA for privileged users of critical information systems and for critical activities, based on risk assessmentThe list of critical systems, the privileged users, and proof MFA is enforced for them
20(b)MFA for enterprise (logical) access to critical systems when teleworkingVPN and remote access configuration showing MFA on every route in

Who has to comply

The direction applies to scheduled commercial banks (excluding regional rural banks), small finance banks, payments banks, applicable NBFCs, credit information companies and all-India financial institutions including EXIM Bank, NABARD, NaBFID, NHB and SIDBI. Fintechs and service providers that run systems for these entities usually inherit the same expectations through contracts and vendor audits.

Where most entities fall short

  • Shared admin accounts. If three people use the same domain admin password, MFA on that account proves nothing about who acted. Give each admin a named account first.
  • Back doors without MFA. Jump servers, database consoles, firewall management pages and vendor support accounts are often left on passwords alone.
  • Remote access gaps. The main VPN has MFA, but a second remote tool or a legacy RDP route does not. Clause 20(b) covers every route.
  • No review trail. Logs exist but nobody signs off a periodic review, which clause 19(b) expects.

Choosing the MFA method

RBI does not prescribe a method, but the choice matters. SMS codes can be intercepted, and push approvals can be tapped by a tired user who did not start the login. For privileged users, phishing-resistant methods are the safer default: FIDO2 security keys such as YubiKeys, or passkeys and hardware authenticators through a platform such as RSA ID Plus. Keep a tested fallback for when a key is lost, so MFA never becomes the reason a critical fix is delayed.

A 60-day plan to close the gap

  1. Weeks 1 to 2: list critical information systems and critical activities, and every privileged account on them, including vendor and service accounts.
  2. Weeks 2 to 4: replace shared admin accounts with named ones, and put MFA on the admin and remote access paths first.
  3. Weeks 4 to 6: extend MFA to the remaining critical systems and close unused remote access routes.
  4. Weeks 6 to 8: set up logging and a monthly privileged access review with a named reviewer, using an identity governance tool such as RSA Governance & Lifecycle if manual reviews will not scale.

Next step

Send us your entity type, critical systems and current remote access set-up, and we will map them against clauses 19 and 20 and propose the MFA and access review design. Invitty is an RSA partner, so we can deliver RSA ID Plus and Governance & Lifecycle end to end. See RSA ID Plus, SecurID and Governance & Lifecycle or CyberArk for privileged access management.

Frequently asked questions

Which entities does the RBI IT governance direction apply to?
The Master Direction applies to scheduled commercial banks (excluding regional rural banks), small finance banks, payments banks, NBFCs in the applicable layers, credit information companies and all-India financial institutions such as EXIM Bank, NABARD, NaBFID, NHB and SIDBI. Check the applicability section for your NBFC layer.
Does RBI require MFA for every employee?
Not in this direction. Clause 19(c) requires MFA for privileged users of critical information systems and for critical activities, based on your risk assessment, and clause 20(b) requires MFA for remote enterprise access to critical systems. Many entities extend MFA further because it is simpler to run one policy.
Is SMS OTP enough to meet the RBI MFA requirement?
The direction does not name a method. SMS and app push codes can be phished or approved by mistake, so for privileged users most security teams now prefer phishing-resistant methods such as FIDO2 security keys or passkeys. Agree the method with your auditor and record the risk reasoning.
When did the RBI direction come into effect?
The Master Direction was issued on 7 November 2023 and came into effect on 1 April 2024, so it already applies in inspections and audits.

Sources

Facts in this guide come from these pages, checked on 19 November 2026.