Skip to content
VITI Security

RBI Directions 2026

RBI Cybersecurity Framework Scorecard

Check your bank, NBFC or payment operation against RBI’s cybersecurity and technology-risk expectations.

What is the RBI cyber security framework now?

On 31 July 2026 the Reserve Bank of India replaced its older cybersecurity instruments with a set of Cybersecurity, Technology: Risk, Resilience and Assurance Framework Directions, 2026, one version for each kind of regulated entity: commercial banks, small finance banks, payments banks, co-operative banks, NBFCs and others. For commercial banks, they repealed the 2016 Cyber Security Framework circular and the 2023 Master Direction on IT governance, risk, controls and assurance practices.

So if your policies still cite the 2016 framework or the 2023 Master Direction, they need updating. The NBFC version is tiered by NBFC layer and size, and several requirements in every version scale with the entity's own risk assessment.

Key requirements (commercial bank directions)

AreaWhat the directions require
GovernanceAn IT Strategy Committee of the Board, a Chief Information Security Officer, and an Information Security Committee headed from the risk management vertical.
PoliciesAn information security policy and a Board-approved cybersecurity policy.
Risk managementPeriodic review and assessment of IT and information security risks.
Security operationsA Cyber Security Operations Centre suited to the bank's risk profile.
VA and PTFor critical systems and customer-facing systems in the DMZ: vulnerability assessment at least every six months and penetration testing at least every 12 months. For other systems, frequency is risk-based. Findings must be fixed in a time-bound way, by appropriately trained and independent testers.
AccessMulti-factor authentication, mandatory for privileged users of critical information systems and critical activities.
Third partiesThe bank stays accountable for security in outsourced and partner arrangements, with due diligence and oversight of vendors (commercial banks also follow RBI's 2025 outsourcing directions).
Disaster recoveryDR drills for critical systems at least half-yearly, with major issues fixed and retested before the next drill.
Incident reportingCyber incidents reported to RBI within six hours of detection on the DAKSH platform, and to CERT-In.
Payment dataUnder RBI's April 2018 circular, all payment system data must be stored only in India.

NBFCs and co-operative banks

NBFCs follow their own 2026 directions, which set different requirements for different NBFC layers and sizes, replacing the earlier IT framework for NBFCs. Co-operative banks likewise have their own version. The themes are the same: governance, risk assessment, VAPT, monitoring, incident reporting and resilience. The frequencies and the amount of structure required differ, so check the version for your entity.

One incident, several reports

Report toWhenUnder
RBI (DAKSH)Within 6 hours of detectionRBI's 2026 directions
CERT-InWithin 6 hours of noticingCERT-In Directions, 2022
Data Protection Board and affected peopleWithout delay; detailed report to the Board within 72 hoursDPDP Rules, 2025, from 13 May 2027, if personal data is involved

A single runbook that triggers all three from one decision point is easier to get right under pressure. Our CERT-In reporting clock works out the deadlines.

How to use the scorecard above

The scorecard checks ten expectations drawn from the commercial-bank directions and the 2018 payment data circular. A "Yes" means the control exists. It cannot tell you whether it meets the required frequency or depth, so use the gaps as a starting list, not as an audit result.

FAQ

Is the 2016 RBI Cyber Security Framework still in force?

Not for commercial banks: RBI repealed it on 31 July 2026, when the new directions took over. Other entity types moved to their own 2026 versions on the same date.

How often must a bank run penetration tests?

At least every 12 months for critical systems and customer-facing systems in the DMZ, with vulnerability assessments at least every six months. Other systems follow a risk-based frequency.

How fast must a cyber incident reach RBI?

Within six hours of detection, through the DAKSH platform, and CERT-In must be informed as well.

We run the VA and PT cycle, set up monitoring and the incident runbook, and prepare the evidence your auditors and RBI inspections ask for. See VAPT services and banks and financial services.

Sources

Facts checked against the sources above on 22 October 2026. General information, not legal advice.

How this is calculated

  1. Each of the ten questions is one expectation from RBI’s cybersecurity directions; each Yes counts as one control in place.
  2. Readiness = controls in place divided by ten, rounded to a whole percentage. 80% or more is green, 50% to 79% amber, below 50% red.
  3. Every No becomes a gap note that cites the paragraph of the 2026 Directions (or the 2018 localization circular) behind it.

Constants the tool uses

Unless a value names a study, it is VITI Security's working estimate for budgeting - not taken from a statute or a dated study - so treat it as an adjustable assumption.

Weight per control
Equal (10 percentage points each)
Colour thresholds
Green from 80%, amber from 50%

Worked example

The calculator run on its default inputs:

Board-level IT Strategy Committee
No
Information security policy plus a Board-approved cybersecurity policy
No
Periodic IT and cyber risk assessment
No
Cyber Security Operations Centre (SOC) monitoring
No
VA every 6 months and PT every 12 months for critical systems
No
Cyber incidents reported to RBI within 6 hours of detection (and to CERT-In)
No
MFA for privileged users of critical systems
No
Vendor / outsourcing risk managed per RBI outsourcing directions
No
Payment system data stored only in India
No
DR drills for critical systems at least every 6 months
No

0/10 controls in place

0% ready

Controls in place
0 of 10
Gaps to close
10
Readiness
0%

All ten answers default to No, so the result is 0/10 controls in place (0% ready) with ten gaps listed. Each Yes adds 10 points; eight Yes answers reach the green band.

Sources

Sources last checked September 2026.

Limitations

The paragraph references are to the commercial-bank Directions; NBFCs, small finance banks, payments banks, co-operative banks and others have parallel directions whose details differ, and several requirements scale with the bank’s risk assessment. A yes/no answer cannot show whether a control meets the stated frequency. This is an indicative estimate for education and planning, not legal advice. Laws and published figures change, and regulators and courts apply discretion no calculator can model - confirm with a qualified legal or compliance professional before acting on a result.