India (Reserve Bank of India)

RBI Cybersecurity Framework for Banks

228 controls. 0 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

228 controls 0 frameworks share controls with it India (Reserve Bank of India) verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

No measured overlap with another framework in the corpus.

Every control

CodeControlAlso in
RBIBANK-1Board-Approved Cybersecurity Policy, Crisis Management0
RBIBANK-2Network Security, Configuration Hardening, Application Security0
RBIBANK-3Identity Access, Authentication, Privileged Access Management0
RBIBANK-4Data Protection, Encryption, Customer Data Security0
RBIBANK-5Vulnerability Management, Patching, Threat Intelligence0
RBIBANK-6Incident Response, Reporting to RBI, CERT-In0
RBIBANK-7Third-Party Risk, Outsourcing, Cloud0
RBIBANK-8Training, Awareness, Customer Education0
1-6Paragraphs 1 to 6: commencement, applicability, foreign branch comply-or-explain, definitions0
100Para 100: track patch status for internet-connected endpoints and servers, databases, middleware0
101Para 101: configuration management and baselines for change integrity0
102Para 102: root cause of detected incidents and patching to close them0
103Para 103: periodic evaluation of access devices at VLAN, LAN/WAN, external and partner interconnections0
104Para 104: access only for a valid business need0
105Para 105: supervise, log and review elevated access0
106Para 106: secure access with data at rest and in transit protected0
107Para 107: protect credentials, tokens and access profiles against leakage and attack0
108Para 108: no local admin rights on end-user devices except time-bound need0
109Para 109: centralised authentication and authorisation with strong passwords, least privilege and SoD0
110Para 110: risk-based two-factor or multi-factor authentication; mandatory MFA for privileged users of critical systems and activities0
111Para 111: centralised management, logging and monitoring of privileged access to critical systems0
112Para 112: limit invalid logons and deactivate dormant accounts0
113Para 113: monitor abnormal logon patterns0
114Para 114: teleworking: secure remote access, MFA, remote device identification, data protection0
115Para 115: customer authentication framework with mutual verification across channels0
116Para 116: bank as identity provider for customer access to partner systems0
117Para 117: secure mail and messaging: anti-spoofing, look-alike domains, malicious content, spam; partners too0
118Para 118: email server specific controls documented and implemented0
119Para 119: restrict permissible email attachment types0
12Para 12: IT governance framework on the five focus areas0
120Para 120: DMARC for email domains; urge third parties to adopt it0
121Para 121: removable media prohibited unless authorised for defined use and duration0
122Para 122: removable media and BYOD policy with secure erasure0
123Para 123: limit media types and information transferable0
124Para 124: scan removable media before access0
125Para 125: consider centralised removable media policies via directory or endpoint tools0
126Para 126: vendor risk assessment and proportionate controls0
127Para 127: bank accountable for security risk in outsourced and partner arrangements0
128Para 128: evaluate need to outsource critical processes; select on risk assessment0
129Para 129: regular due diligence, oversight and management of vendors and partners0
13Para 13: enterprise or operational risk policy assesses IT risks periodically0
130Para 130: policies to evaluate, approve and monitor vendor risk and materiality0
131Para 131: service providers adhere to Indian legal and regulatory requirements0
132Para 132: agreements with audit right for the bank and inspection right for RBI0
133Para 133: RBI access to all information resources consumed by the bank0
134Para 134: legal requirements on infrastructure location and cross-border data movement0
135Para 135: vet vendor personnel; background checks, NDAs and security compliance agreements0
136Para 136: cyber controls enforced on ATM switch application service providers0
137Para 137: ATM switch ASP controls written into contracts and scoped to the IT ecosystem0
138Para 138: 24 baseline cyber controls mandated in ASP contracts0
139Para 139: share applicable RBI instructions with ATM switch ASPs0
14Para 14: Information Security Policy with the prescribed contents0
140Para 140: strong, non-deprecated cryptography compliant with law0
141Para 141: no manual intervention in data between processes for critical applications0
142Para 142: tested, automated, authenticated STP interfaces with audit trails0
143Para 143: set up a CSOC for continuous surveillance0
144Para 144: multi-point defence against malicious code0
145Para 145: anti-malware with behavioural detection everywhere, centrally managed0
146Para 146: whitelist internet websites and systems0
147Para 147: consider secure web gateways with HTTPS deep inspection0
148Para 148: anti-phishing and anti-rogue app takedown services0
149Para 149: periodic VA and PT for all critical and internet-facing systems0
15Para 15: Board-approved Cybersecurity Policy distinct from the IT and information security policies0
150Para 150: VA/PT of critical internet-facing applications, servers and network across the lifecycle0
151Para 151: VA every six months and PT every 12 months for critical and DMZ customer-facing systems0
152Para 152: post-implementation VA/PT on production, or documented ISC-approved deviation0
153Para 153: fix vulnerabilities on time and keep them fixed0
154Para 154: documented VA/PT approach including scoring, also for cloud-hosted systems0
155Para 155: VA/PT by trained, independent experts0
156Para 156: control over audit methodology and auditor competence when engaging VA/PT auditors0
157Para 157: reasonable assurance per area stated in VA/PT reports0
158Para 158: ongoing review of VA/PT auditor performance including missed vulnerabilities0
159Para 159: interact with auditors; follow CERT-In audit policy guidelines for empanelled auditors0
16Para 16: Board-level IT Strategy Committee0
160Para 160: close monitoring of VA/PT findings by security, IS audit and senior management0
161Para 161: quarterly VA/PT closure status to the ITSC and ISC0
163Para 163: BCP and DR policy on best practice such as ISO 22301, updated on major developments0
164Para 164: BCP and DR designed for rapid, secure recovery after cyber-attacks within RTOs0
165Para 165: DR drills half-yearly for critical systems0
166Para 166: major DR drill issues fixed and retested before next cycle0
167Para 167: DR testing runs DR as primary for at least a full working day0
168Para 168: test BCP and DR under different contingency scenarios0
169Para 169: backups taken, restore-tested, integrity preserved and secured0
17Para 17: ITSC composition: three directors, independent IT-expert chair, competent members0
170Para 170: DR architecture and procedures meet defined RTO and RPO0
171Para 171: minimal ITSC-approved RTO and near zero RPO for critical systems0
172Para 172: documented reconciliation where RPO is not zero0
173Para 173: identical configurations and patches at DC and DR0
174Para 174: BCP/DR on interconnected vendor and partner systems with collaborative testing0
175Para 175: incident response and recovery policy with eight elements0
176Para 176: specialised training for incident handlers0
177Para 177: response plans for varied scenarios with stakeholder coordination0
178Para 178: lessons learned fed into response plans0
179Para 179: documented strategies for ransomware, data destruction and DDoS0
18Para 18: ITSC meets at least quarterly0
180Para 180: contain attacks by shielding and quarantine0
181Para 181: analyse incidents for severity, impact and root cause; corrective and preventive measures0
182Para 182: report cyber incidents on DAKSH within six hours; notify CERT-In0
183Para 183: escalation and reporting plans to Board, senior management and customers0
185Para 185: external coordination and threat intelligence integration0
186Para 186: lawful systems to collect and share threat information0
187Para 187: improve response and recovery through lessons from incidents, tests and drills0
188Para 188: participate in CERT-In and IDRBT cyber drills0
189Para 189: resilient interconnected systems with collaborative testing and capacity0
19Para 19: ITSC functions: planning, strategy, governance, risk, budget, escalation, BCP/DR, capacity, access standards0
190Para 190: crisis communication tested through drills with customers and providers0
191Para 191: SOC, incident response and forensics aligned to cut downtime0
192Para 192: documented Cyber Crisis Management Plan within the Board framework0
193Para 193: CCMP covers detection, containment, response and recovery for a wide threat set0
194Para 194: comprehensive cyber metrics with KPIs and KRIs0
195Para 195: performance, recovery and resumption metrics including RPO and RTO0
196Para 196: scorecard for IT performance and maturity0
197Para 197: indicators for adequacy of and adherence to the cyber framework0
198Para 198: promote cyber resilience objectives to providers and partners and require aligned action0
199Para 199: communicate security policies and acceptable use to users, vendors and partners0
20Para 20: senior management duties for IT and cyber0
200Para 200: targeted training for key executive, operational and security administration roles0
201Para 201: encourage reporting of suspicious behaviour0
202Para 202: periodic evaluation of employee awareness0
203Para 203: continuous capacity building; mandatory for new recruits; annual for lower and middle management0
204Para 204: Board and senior management sensitised; annual IT and cyber training for all Board members and senior management0
205Para 205: improve and maintain customer cyber awareness0
206Para 206: encourage customers to report phishing and act on reports0
207Para 207: educate customers not to share credentials, OTPs and PINs0
208Para 208: promote cyber resilience objectives among customers0
209Para 209: risk-based transaction monitoring across all channels0
21Para 21: IT Steering Committee meeting at least quarterly0
210Para 210: alternate-channel alerts for payments above a customer-set value0
211Para 211: network forensics, investigation and DDoS mitigation on standby0
212Para 212: CSOC framework proportionate to risk, scale and obligations0
213Para 213: CSOC governance: Board and management briefing, dashboards, metrics and reporting0
214Para 214: proactive monitoring with tools for detection, response and analytics0
215Para 215: log collection, storage, SIEM correlation, dashboard monitoring and alerting0
216Para 216: CSOC systems: root cause, classification, investigation, behaviour analysis, IoCs, analytics, honeypots0
217Para 217: CSOC responsibilities across protect, detect, respond and recover0
218Para 218: security analytics engine with timely processing and deep packet inspection0
219Para 219: malware detection and analysis and forensic imaging tools0
22Para 22: IT Steering Committee responsibilities0
220Para 220: CSOC architecture scalable, highly available and capable across six outcomes0
221Para 221: CSOC staffing across Level 1, 2 and 30
222Para 222: differentiated hiring, management and retention for CSOC staff0
223Para 223: 24x7 staffing model, training, incentives, SOC metrics and capacity planning0
224Para 224: Audit Committee oversees IS audit0
225Para 225: ACB-approved IS audit policy reviewed annually0
226Para 226: ACB reviews critical IT and cyber issues and directs management0
227Para 227: separate, competent IS audit function; accountability for external IS audits retained0
228Para 228: risk-based IS audit planning0
23Para 23: Information Security Committee under ITSC oversight, headed from risk management0
24Para 24: appoint a senior, competent Head of IT Function0
25Para 25: Head of IT responsibilities: alignment, organisation, DR and BCP0
26Para 26: Head of IT as first line of defence over IT controls and risk0
27Para 27: senior, independent CISO with expertise, tenure, staff and budget0
28Para 28: documented CISO role: strategy, enforcement, committee invitee, SOC, reporting to risk ED, quarterly review0
29Para 29: defined project management approach for IT projects0
30Para 30: enterprise architecture methodology for new technology or stack revamp0
31Para 31: new technology adoption within risk appetite and aligned to strategy0
32Para 32: product approval and quality assurance for new IT applications0
33Para 33: IT architecture designed for security, reviewed annually by the ITSC0
34Para 34: IT service management framework for operational resilience including DR sites0
35Para 35: service level management with segregation of duties0
36Para 36: security classification of information assets by criticality0
37Para 37: avoid outdated and unsupported hardware and software; track EOS and AMC dates0
38Para 38: technology refresh plan before end of support0
39Para 39: risk policy covers IT and cyber risk, reviewed annually by RMCB with ITSC0
40Para 40: IT and information security risk management framework0
41Para 41: asset risk assessment guided by security standards or control frameworks0
42Para 42: staff and service providers comply with security and acceptable-use policies0
43Para 43: annual review of security infrastructure and policies; tackle phishing and spoofing0
44Para 44: inherent risk factors reckoned0
45Para 45: riskiness categorised low to very high including business component riskiness0
46Para 46: control evaluation factors including threat intelligence and information sharing0
47Para 47: up-to-date inventory of information assets with business criticality0
48Para 48: classify data by sensitivity0
49Para 49: enterprise data dictionary0
50Para 50: protect data inside and outside the network according to sensitivity0
51Para 51: comprehensive data loss or leakage prevention strategy0
52Para 52: similar data leakage arrangements at vendor-managed facilities0
53Para 53: protect customers' data across its lifecycle including with vendors0
54Para 54: remote manage, wipe and lock mobile devices and laptops0
55Para 55: data migration policy with integrity checks, audit trails and sign-offs0
56Para 56: inventory of authorised and unauthorised software; optional whitelisting0
57Para 57: control software installation and block unauthorised software0
58Para 58: monitor patches and advisories; expedite patches for actively exploited flaws0
59Para 59: exception policy with justification, duration, approval and senior review0
60Para 60: physical and environmental controls for DC and DR sites0
61Para 61: monitoring of environmental control breaches and access logs0
62Para 62: geographically separated DC and DR0
63Para 63: e-surveillance at DC and DR0
64Para 64: systems and infrastructure support business functions and all channels0
65Para 65: annual proactive IT capacity assessment and planning0
66Para 66: documented security baselines for all device categories through the lifecycle0
67Para 67: periodic review of critical devices' configurations and patch levels everywhere0
68Para 68: only authorised, time-limited, audited network access; responsibility with bank officials0
69Para 69: up-to-date organisation-wide network architecture diagram0
7Para 7: Board approves IT, asset, continuity, security and cyber strategies and policies0
70Para 70: centralised inventory of authorised network devices0
71Para 71: network devices configured appropriately and assessed periodically0
72Para 72: secure wireless networks and access points0
73Para 73: connect only authorised devices meeting security requirements0
74Para 74: automatically detect and block unauthorised device connections0
75Para 75: detect and remedy unusual activity on systems, servers, network devices and endpoints0
76Para 76: SOPs for all major IT activities0
77Para 77: multi-layer boundary defences with real-time traffic filtering0
78Para 78: public-facing IT infrastructure handles IPv60
79Para 79: security across all stages of the application life cycle0
8Para 8: annual Board review of the strategies and policies0
80Para 80: secure coding for internal and collaborative development0
81Para 81: security requirements specified from the start0
82Para 82: segregated development, test and production environments0
83Para 83: threat modelling, secure coding, standards-aligned testing and secure deployment0
84Para 84: address vulnerabilities per OWASP and defence in depth0
85Para 85: application security assessments beyond the OWASP top 100
86Para 86: periodic application security testing across the lifecycle in production-like environments0
87Para 87: containerised business apps on mobile devices with remote wipe0
88Para 88: new technologies evaluated before use on critical systems0
89Para 89: vendor maintenance and support enforced by agreement0
90Para 90: source code or escrow for critical applications0
92Para 92: vendor certificate that code is free of known vulnerabilities, malware and covert channels0
93Para 93: audit logging for systems touching critical or sensitive information0
94Para 94: log settings capture identifying fields and are validated periodically0
95Para 95: audit trails detailed enough for audit, forensics and non-repudiation0
96Para 96: regular monitoring of audit trails and logs0
97Para 97: stakeholders consulted on log scope, frequency and storage0
98Para 98: change and patch policy: impact assessment, timely approved changes, justification, rollback0
99Para 99: risk-based patching strategy with an inventory of patchable components0
DIRECTIONSThe 2026 Directions: what they are0
PERMISSIVEPermissive provisions (may) and cross-references folded0
STATUSStatus: what the Directions repealed, sibling directions and what is pending0

Tell me when RBI Cybersecurity Framework for Banks files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What an auditor will ask you to produce

The artefacts named on the failure modes this framework speaks to.

  • Governance framework doc
  • Board charter
  • RACI matrix
  • access control matrix
  • RBAC documentation
  • access review reports
  • Recovery test plan
  • Test reports comparing expected and actual recovery duration
  • Actions on failed tests
  • Backup strategy and life cycle policy

How programmes fail on this

Failure modes named by this framework and others. Each opens the full record.

What this page is

A control-level reference for RBI Cybersecurity Framework for Banks, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition