Q-Cyber Magazine
RBI's 2026 cybersecurity directions for commercial banks
On 31 July 2026 the Reserve Bank issued a consolidated Cybersecurity, Technology: Risk, Resilience and Assurance Framework for commercial banks, effective immediately, with a distinct cybersecurity policy, an independent CISO, a 24x7 CSOC, and six-hour incident reporting on DAKSH.

The Reserve Bank has replaced a scattered set of technology instructions with a single, immediately effective framework for commercial banks. The centre of gravity is governance: the Board, a distinct cybersecurity policy, an independent CISO, and a continuously staffed operations centre.
Governance before tools
The directions open with the Board. Policies and strategies are to be reviewed at least annually, with material amendments reserved for the Board even where review is delegated to the IT Strategy Committee. The Information Security Policy must set ownership, structure, exceptions and consequences for non-compliance. The Cybersecurity Policy must be distinct from the broader IT or information-security policy, so that cyber threats and the measures to meet them are not lost inside a general technology document.
The CISO is defined with unusual precision. The officer should preferably be at General Manager or equivalent rank, must have a technical background, a reasonable minimum term, and an adequately staffed office. The CISO reports directly to the Executive Director or equivalent overseeing risk, is a permanent invitee to the IT Strategy and IT Steering Committees, and must place a cybersecurity review before the Board, the Risk Management Committee of the Board, or the IT Strategy Committee at least quarterly. The CISO's office manages the SOC and cybersecurity projects. Independence is not a slogan here; it is a reporting line.
Exhibit 1
Selected mandatory features of the 2026 commercial-bank directions
| Requirement | What the directions specify |
|---|---|
| Instrument and start date | RBI/DoS/2026-27/410, 31 July 2026, updated 1 October 2026; effective immediately on issuance |
| Scope of this text | Commercial banks |
| Policies | Board-approved Information Security Policy, and a distinct Board-approved Cybersecurity Policy |
| Board committee | IT Strategy Committee; Information Security Committee under its oversight |
| CISO | No direct reporting to the Head of IT; no business targets; reports to the ED or equivalent overseeing risk; quarterly Board-level review |
| Baseline controls | Chapter V, domains A to EE, from asset inventory through forensics |
| CSOC | Continuous surveillance; staffing mechanisms for 24x7 monitoring |
| Incident reporting | Within six hours of detection on DAKSH (https://daksh.rbi.org.in), and notification to CERT-In |
Source: Reserve Bank of India (Commercial Banks – Cybersecurity, Technology: Risk, Resilience and Assurance Framework) Directions, 2026, official text at rbi.org.in.
Operations and assurance
Chapter V is a catalogue of baseline controls, including inventory, data-leak prevention, secure configuration, application security, privileged access, third-party arrangements, cryptographic controls, vulnerability assessment and penetration testing, red teaming, business continuity, incident response, customer authentication, and forensics. Chapter VI then requires a CSOC commensurate with the bank's risk and complexity, and asks the bank to plan for continuous 24x7 monitoring, whether in-house or through a managed service, with training, retention and performance metrics.
Incident reporting is aligned, in timing, with CERT-In's six-hour clock, but the channel to the supervisor is specific: DAKSH, with a parallel notice to CERT-In. The directions also expect participation in drills under CERT-In and IDRBT, and information-sharing with peers, IDRBT, RBI and CERT-In. These are operating conditions, not optional community activities.
The Reserve Bank issued parallel 2026 frameworks for other classes of regulated entity, including small finance banks, payments banks and NBFCs. A group should not assume that the commercial-bank text applies unchanged to every licence it holds.
Implications
- Separate the cybersecurity policy from the general IT policy, and keep it Board-owned.
- Protect CISO independence in reporting line, tenure, staff and the absence of business targets.
- Treat the CSOC as a 24x7 capability, with a tested six-hour path to DAKSH and CERT-In.
- Use Chapter V as an assurance map, including cryptography, third parties and forensics, not only as a policy checklist.
What this means for BFSI
For commercial banks, the 2026 directions are already in force. The first test of seriousness is whether the CISO can reach the Board with an unfiltered quarterly view, and whether the bank can report a detected incident on DAKSH within six hours. Everything else in the framework supports those two proofs.


