Law / India

RBI Payments Banks Cybersecurity Directions, Cybersecurity Policy and Testing

Reserve Bank of India (Payments Banks - Cybersecurity, Technology: Risk, Resilience and Assurance Framework) Directions 2026, paras. 3, 14, 150 and 152

In force since .

A sector security regimes rule binding private bodies.

Private right of action
No
Instrument type
a binding direction issued under an act
Obligation class
Security, Governance

What it requires

  • This binds a payments bank (reached by declaring that you are a bank).
  • Put in place a Cybersecurity Policy, approved by your Board, that sets out your approach to cyber threats and is distinct from your broader IT and information security policy (paragraph 14).
  • Conduct vulnerability assessment of critical information systems and systems in the demilitarised zone with a customer interface at least once in every six months and penetration testing at least once in 12 months, and take a risk-based approach for other systems (paragraph 150).
  • Fix identified vulnerabilities and their associated risks in a time-bound manner and keep the fixes in place so that known vulnerabilities do not recur (paragraph 152).

These lines are LexLint's reading of the law's text.

Who enforces it

Enforcement body

The Reserve Bank of India, which issues these Directions under the powers its enacting paragraph recites.

Settledness

As of

What this law does

Drafted with AI

Drafted with AI from the cited sources under the direction of UnGovr staff. UnGovr holds editorial responsibility for this page. How this site is made

Research summary

Legal information, not legal advice. This is LexLint's own research summary of a public legal source, and it creates no attorney-client relationship. For decisions that matter, consult qualified counsel in the relevant jurisdiction. About LexLint

Paragraph 3 applies the Directions to Payments Banks. Paragraph 14 requires a payments bank to put in place a Cybersecurity Policy approved by its Board. Paragraph 150 requires a payments bank to conduct vulnerability assessment of critical information systems at least once in every six months and penetration testing at least once in 12 months. Paragraph 152 requires a payments bank to fix identified vulnerabilities and associated risks in a time-bound manner. Paragraph 2 brings the Directions into force with immediate effect.

When LexLint raises it

When your app profile says your app is a bank.

Back to the example  ·  Lint your app

Page updated .