RBI Cybersecurity Framework for Banks
The Reserve Bank of India's 2026 Directions on cybersecurity, technology risk, resilience and assurance for commercial banks, which replaced the 2016 Cyber Security Framework in Banks and the 2023 IT governance Master Direction: Board and committee governance (IT Strategy Committee, Information Security Committee, an independent CISO reporting to risk), IT and cyber risk management, some 160 baseline controls from asset inventory to DMARC, VA/PT and half-yearly full-day DR switchovers, third-party and ATM switch provider controls, incident reporting on DAKSH within six hours, a Cyber Security Operations Centre and IS audit.
RBI Cybersecurity Framework for Banks is a compliance framework from India (Reserve Bank of India) with 16 domains and 216 controls. The largest domains are Chapter V L to P: access control, teleworking, customer authentication, mail and removable media – RBI Cybersecurity Framework for Banks (22 controls), Chapter V R to X: cryptography, straight through processing, surveillance, threat defence, anti-phishing and VA/PT – RBI Cybersecurity Framework for Banks (22 controls), Chapter V A to G: assets, data leakage, migration, software, physical, capacity and configuration – RBI Cybersecurity Framework for Banks (21 controls). Every control below carries what it requires and what an assessor expects to see.
Framework summaries on this platform are interpretations grounded in the published source, for educational and compliance planning purposes. They do not reproduce or replace the official standards. Refer to the authoritative source for the definitive text. Framework names and trademarks belong to their respective organisations.
Framework Domains (16)
Chapter III C to G: IT Strategy Committee, senior management, committees, Head of IT and CISO – RBI Cybersecurity Framework for Banks
| Code | Title |
|---|---|
| rbi-cybersecurity-framework-for-banks::16 | Para 16: Board-level IT Strategy Committee |
| rbi-cybersecurity-framework-for-banks::17 | Para 17: ITSC composition: three directors, independent IT-expert chair, competent members |
| rbi-cybersecurity-framework-for-banks::18 | Para 18: ITSC meets at least quarterly |
| rbi-cybersecurity-framework-for-banks::19 | Para 19: ITSC functions: planning, strategy, governance, risk, budget, escalation, BCP/DR, capacity, access standards |
| rbi-cybersecurity-framework-for-banks::20 | Para 20: senior management duties for IT and cyber |
| rbi-cybersecurity-framework-for-banks::21 | Para 21: IT Steering Committee meeting at least quarterly |
| rbi-cybersecurity-framework-for-banks::22 | Para 22: IT Steering Committee responsibilities |
| rbi-cybersecurity-framework-for-banks::23 | Para 23: Information Security Committee under ITSC oversight, headed from risk management |
| rbi-cybersecurity-framework-for-banks::24 | Para 24: appoint a senior, competent Head of IT Function |
| rbi-cybersecurity-framework-for-banks::25 | Para 25: Head of IT responsibilities: alignment, organisation, DR and BCP |
| rbi-cybersecurity-framework-for-banks::26 | Para 26: Head of IT as first line of defence over IT controls and risk |
| rbi-cybersecurity-framework-for-banks::27 | Para 27: senior, independent CISO with expertise, tenure, staff and budget |
| rbi-cybersecurity-framework-for-banks::28 | Para 28: documented CISO role: strategy, enforcement, committee invitee, SOC, reporting to risk ED, quarterly review |
Chapter III H to J: IT projects, architecture and IT service management – RBI Cybersecurity Framework for Banks
| Code | Title |
|---|---|
| rbi-cybersecurity-framework-for-banks::29 | Para 29: defined project management approach for IT projects |
| rbi-cybersecurity-framework-for-banks::30 | Para 30: enterprise architecture methodology for new technology or stack revamp |
| rbi-cybersecurity-framework-for-banks::31 | Para 31: new technology adoption within risk appetite and aligned to strategy |
| rbi-cybersecurity-framework-for-banks::32 | Para 32: product approval and quality assurance for new IT applications |
| rbi-cybersecurity-framework-for-banks::33 | Para 33: IT architecture designed for security, reviewed annually by the ITSC |
| rbi-cybersecurity-framework-for-banks::34 | Para 34: IT service management framework for operational resilience including DR sites |
| rbi-cybersecurity-framework-for-banks::35 | Para 35: service level management with segregation of duties |
| rbi-cybersecurity-framework-for-banks::36 | Para 36: security classification of information assets by criticality |
| rbi-cybersecurity-framework-for-banks::37 | Para 37: avoid outdated and unsupported hardware and software; track EOS and AMC dates |
| rbi-cybersecurity-framework-for-banks::38 | Para 38: technology refresh plan before end of support |
Chapter IV: IT and information security risk management – RBI Cybersecurity Framework for Banks
| Code | Title |
|---|---|
| rbi-cybersecurity-framework-for-banks::39 | Para 39: risk policy covers IT and cyber risk, reviewed annually by RMCB with ITSC |
| rbi-cybersecurity-framework-for-banks::40 | Para 40: IT and information security risk management framework |
| rbi-cybersecurity-framework-for-banks::41 | Para 41: asset risk assessment guided by security standards or control frameworks |
| rbi-cybersecurity-framework-for-banks::42 | Para 42: staff and service providers comply with security and acceptable-use policies |
| rbi-cybersecurity-framework-for-banks::43 | Para 43: annual review of security infrastructure and policies; tackle phishing and spoofing |
| rbi-cybersecurity-framework-for-banks::44 | Para 44: inherent risk factors reckoned |
| rbi-cybersecurity-framework-for-banks::45 | Para 45: riskiness categorised low to very high including business component riskiness |
| rbi-cybersecurity-framework-for-banks::46 | Para 46: control evaluation factors including threat intelligence and information sharing |
Chapter V A to G: assets, data leakage, migration, software, physical, capacity and configuration – RBI Cybersecurity Framework for Banks
| Code | Title |
|---|---|
| rbi-cybersecurity-framework-for-banks::47 | Para 47: up-to-date inventory of information assets with business criticality |
| rbi-cybersecurity-framework-for-banks::48 | Para 48: classify data by sensitivity |
| rbi-cybersecurity-framework-for-banks::49 | Para 49: enterprise data dictionary |
| rbi-cybersecurity-framework-for-banks::50 | Para 50: protect data inside and outside the network according to sensitivity |
| rbi-cybersecurity-framework-for-banks::51 | Para 51: comprehensive data loss or leakage prevention strategy |
| rbi-cybersecurity-framework-for-banks::52 | Para 52: similar data leakage arrangements at vendor-managed facilities |
| rbi-cybersecurity-framework-for-banks::53 | Para 53: protect customers' data across its lifecycle including with vendors |
| rbi-cybersecurity-framework-for-banks::54 | Para 54: remote manage, wipe and lock mobile devices and laptops |
| rbi-cybersecurity-framework-for-banks::55 | Para 55: data migration policy with integrity checks, audit trails and sign-offs |
| rbi-cybersecurity-framework-for-banks::56 | Para 56: inventory of authorised and unauthorised software; optional whitelisting |
| rbi-cybersecurity-framework-for-banks::57 | Para 57: control software installation and block unauthorised software |
| rbi-cybersecurity-framework-for-banks::58 | Para 58: monitor patches and advisories; expedite patches for actively exploited flaws |
| rbi-cybersecurity-framework-for-banks::59 | Para 59: exception policy with justification, duration, approval and senior review |
| rbi-cybersecurity-framework-for-banks::60 | Para 60: physical and environmental controls for DC and DR sites |
| rbi-cybersecurity-framework-for-banks::61 | Para 61: monitoring of environmental control breaches and access logs |
| rbi-cybersecurity-framework-for-banks::62 | Para 62: geographically separated DC and DR |
| rbi-cybersecurity-framework-for-banks::63 | Para 63: e-surveillance at DC and DR |
| rbi-cybersecurity-framework-for-banks::64 | Para 64: systems and infrastructure support business functions and all channels |
| rbi-cybersecurity-framework-for-banks::65 | Para 65: annual proactive IT capacity assessment and planning |
| rbi-cybersecurity-framework-for-banks::66 | Para 66: documented security baselines for all device categories through the lifecycle |
| rbi-cybersecurity-framework-for-banks::67 | Para 67: periodic review of critical devices' configurations and patch levels everywhere |
Chapter V AA to EE: metrics, awareness, customer education, transaction monitoring and forensics – RBI Cybersecurity Framework for Banks
| Code | Title |
|---|---|
| rbi-cybersecurity-framework-for-banks::194 | Para 194: comprehensive cyber metrics with KPIs and KRIs |
| rbi-cybersecurity-framework-for-banks::195 | Para 195: performance, recovery and resumption metrics including RPO and RTO |
| rbi-cybersecurity-framework-for-banks::196 | Para 196: scorecard for IT performance and maturity |
| rbi-cybersecurity-framework-for-banks::197 | Para 197: indicators for adequacy of and adherence to the cyber framework |
| rbi-cybersecurity-framework-for-banks::198 | Para 198: promote cyber resilience objectives to providers and partners and require aligned action |
| rbi-cybersecurity-framework-for-banks::199 | Para 199: communicate security policies and acceptable use to users, vendors and partners |
| rbi-cybersecurity-framework-for-banks::200 | Para 200: targeted training for key executive, operational and security administration roles |
| rbi-cybersecurity-framework-for-banks::201 | Para 201: encourage reporting of suspicious behaviour |
| rbi-cybersecurity-framework-for-banks::202 | Para 202: periodic evaluation of employee awareness |
| rbi-cybersecurity-framework-for-banks::203 | Para 203: continuous capacity building; mandatory for new recruits; annual for lower and middle management |
| rbi-cybersecurity-framework-for-banks::204 | Para 204: Board and senior management sensitised; annual IT and cyber training for all Board members and senior management |
| rbi-cybersecurity-framework-for-banks::205 | Para 205: improve and maintain customer cyber awareness |
| rbi-cybersecurity-framework-for-banks::206 | Para 206: encourage customers to report phishing and act on reports |
| rbi-cybersecurity-framework-for-banks::207 | Para 207: educate customers not to share credentials, OTPs and PINs |
| rbi-cybersecurity-framework-for-banks::208 | Para 208: promote cyber resilience objectives among customers |
| rbi-cybersecurity-framework-for-banks::209 | Para 209: risk-based transaction monitoring across all channels |
| rbi-cybersecurity-framework-for-banks::210 | Para 210: alternate-channel alerts for payments above a customer-set value |
| rbi-cybersecurity-framework-for-banks::211 | Para 211: network forensics, investigation and DDoS mitigation on standby |
Chapter V H: network management and security – RBI Cybersecurity Framework for Banks
| Code | Title |
|---|---|
| rbi-cybersecurity-framework-for-banks::68 | Para 68: only authorised, time-limited, audited network access; responsibility with bank officials |
| rbi-cybersecurity-framework-for-banks::69 | Para 69: up-to-date organisation-wide network architecture diagram |
| rbi-cybersecurity-framework-for-banks::70 | Para 70: centralised inventory of authorised network devices |
| rbi-cybersecurity-framework-for-banks::71 | Para 71: network devices configured appropriately and assessed periodically |
| rbi-cybersecurity-framework-for-banks::72 | Para 72: secure wireless networks and access points |
| rbi-cybersecurity-framework-for-banks::73 | Para 73: connect only authorised devices meeting security requirements |
| rbi-cybersecurity-framework-for-banks::74 | Para 74: automatically detect and block unauthorised device connections |
| rbi-cybersecurity-framework-for-banks::75 | Para 75: detect and remedy unusual activity on systems, servers, network devices and endpoints |
| rbi-cybersecurity-framework-for-banks::76 | Para 76: SOPs for all major IT activities |
| rbi-cybersecurity-framework-for-banks::77 | Para 77: multi-layer boundary defences with real-time traffic filtering |
| rbi-cybersecurity-framework-for-banks::78 | Para 78: public-facing IT infrastructure handles IPv6 |
Chapter V I: application security life cycle – RBI Cybersecurity Framework for Banks
| Code | Title |
|---|---|
| rbi-cybersecurity-framework-for-banks::79 | Para 79: security across all stages of the application life cycle |
| rbi-cybersecurity-framework-for-banks::80 | Para 80: secure coding for internal and collaborative development |
| rbi-cybersecurity-framework-for-banks::81 | Para 81: security requirements specified from the start |
| rbi-cybersecurity-framework-for-banks::82 | Para 82: segregated development, test and production environments |
| rbi-cybersecurity-framework-for-banks::83 | Para 83: threat modelling, secure coding, standards-aligned testing and secure deployment |
| rbi-cybersecurity-framework-for-banks::84 | Para 84: address vulnerabilities per OWASP and defence in depth |
| rbi-cybersecurity-framework-for-banks::85 | Para 85: application security assessments beyond the OWASP top 10 |
| rbi-cybersecurity-framework-for-banks::86 | Para 86: periodic application security testing across the lifecycle in production-like environments |
| rbi-cybersecurity-framework-for-banks::87 | Para 87: containerised business apps on mobile devices with remote wipe |
| rbi-cybersecurity-framework-for-banks::88 | Para 88: new technologies evaluated before use on critical systems |
| rbi-cybersecurity-framework-for-banks::89 | Para 89: vendor maintenance and support enforced by agreement |
| rbi-cybersecurity-framework-for-banks::90 | Para 90: source code or escrow for critical applications |
| rbi-cybersecurity-framework-for-banks::92 | Para 92: vendor certificate that code is free of known vulnerabilities, malware and covert channels |
Chapter V J and K: audit logs, patch, vulnerability and change management – RBI Cybersecurity Framework for Banks
| Code | Title |
|---|---|
| rbi-cybersecurity-framework-for-banks::100 | Para 100: track patch status for internet-connected endpoints and servers, databases, middleware |
| rbi-cybersecurity-framework-for-banks::101 | Para 101: configuration management and baselines for change integrity |
| rbi-cybersecurity-framework-for-banks::102 | Para 102: root cause of detected incidents and patching to close them |
| rbi-cybersecurity-framework-for-banks::103 | Para 103: periodic evaluation of access devices at VLAN, LAN/WAN, external and partner interconnections |
| rbi-cybersecurity-framework-for-banks::93 | Para 93: audit logging for systems touching critical or sensitive information |
| rbi-cybersecurity-framework-for-banks::94 | Para 94: log settings capture identifying fields and are validated periodically |
| rbi-cybersecurity-framework-for-banks::95 | Para 95: audit trails detailed enough for audit, forensics and non-repudiation |
| rbi-cybersecurity-framework-for-banks::96 | Para 96: regular monitoring of audit trails and logs |
| rbi-cybersecurity-framework-for-banks::97 | Para 97: stakeholders consulted on log scope, frequency and storage |
| rbi-cybersecurity-framework-for-banks::98 | Para 98: change and patch policy: impact assessment, timely approved changes, justification, rollback |
| rbi-cybersecurity-framework-for-banks::99 | Para 99: risk-based patching strategy with an inventory of patchable components |
Chapter V L to P: access control, teleworking, customer authentication, mail and removable media – RBI Cybersecurity Framework for Banks
| Code | Title |
|---|---|
| rbi-cybersecurity-framework-for-banks::104 | Para 104: access only for a valid business need |
| rbi-cybersecurity-framework-for-banks::105 | Para 105: supervise, log and review elevated access |
| rbi-cybersecurity-framework-for-banks::106 | Para 106: secure access with data at rest and in transit protected |
| rbi-cybersecurity-framework-for-banks::107 | Para 107: protect credentials, tokens and access profiles against leakage and attack |
| rbi-cybersecurity-framework-for-banks::108 | Para 108: no local admin rights on end-user devices except time-bound need |
| rbi-cybersecurity-framework-for-banks::109 | Para 109: centralised authentication and authorisation with strong passwords, least privilege and SoD |
| rbi-cybersecurity-framework-for-banks::110 | Para 110: risk-based two-factor or multi-factor authentication; mandatory MFA for privileged users of critical systems and activities |
| rbi-cybersecurity-framework-for-banks::111 | Para 111: centralised management, logging and monitoring of privileged access to critical systems |
| rbi-cybersecurity-framework-for-banks::112 | Para 112: limit invalid logons and deactivate dormant accounts |
| rbi-cybersecurity-framework-for-banks::113 | Para 113: monitor abnormal logon patterns |
| rbi-cybersecurity-framework-for-banks::114 | Para 114: teleworking: secure remote access, MFA, remote device identification, data protection |
| rbi-cybersecurity-framework-for-banks::115 | Para 115: customer authentication framework with mutual verification across channels |
| rbi-cybersecurity-framework-for-banks::116 | Para 116: bank as identity provider for customer access to partner systems |
| rbi-cybersecurity-framework-for-banks::117 | Para 117: secure mail and messaging: anti-spoofing, look-alike domains, malicious content, spam; partners too |
| rbi-cybersecurity-framework-for-banks::118 | Para 118: email server specific controls documented and implemented |
| rbi-cybersecurity-framework-for-banks::119 | Para 119: restrict permissible email attachment types |
| rbi-cybersecurity-framework-for-banks::120 | Para 120: DMARC for email domains; urge third parties to adopt it |
| rbi-cybersecurity-framework-for-banks::121 | Para 121: removable media prohibited unless authorised for defined use and duration |
| rbi-cybersecurity-framework-for-banks::122 | Para 122: removable media and BYOD policy with secure erasure |
| rbi-cybersecurity-framework-for-banks::123 | Para 123: limit media types and information transferable |
| rbi-cybersecurity-framework-for-banks::124 | Para 124: scan removable media before access |
| rbi-cybersecurity-framework-for-banks::125 | Para 125: consider centralised removable media policies via directory or endpoint tools |
Chapter V Q: third-party arrangements and ATM switch service providers – RBI Cybersecurity Framework for Banks
| Code | Title |
|---|---|
| rbi-cybersecurity-framework-for-banks::126 | Para 126: vendor risk assessment and proportionate controls |
| rbi-cybersecurity-framework-for-banks::127 | Para 127: bank accountable for security risk in outsourced and partner arrangements |
| rbi-cybersecurity-framework-for-banks::128 | Para 128: evaluate need to outsource critical processes; select on risk assessment |
| rbi-cybersecurity-framework-for-banks::129 | Para 129: regular due diligence, oversight and management of vendors and partners |
| rbi-cybersecurity-framework-for-banks::130 | Para 130: policies to evaluate, approve and monitor vendor risk and materiality |
| rbi-cybersecurity-framework-for-banks::131 | Para 131: service providers adhere to Indian legal and regulatory requirements |
| rbi-cybersecurity-framework-for-banks::132 | Para 132: agreements with audit right for the bank and inspection right for RBI |
| rbi-cybersecurity-framework-for-banks::133 | Para 133: RBI access to all information resources consumed by the bank |
| rbi-cybersecurity-framework-for-banks::134 | Para 134: legal requirements on infrastructure location and cross-border data movement |
| rbi-cybersecurity-framework-for-banks::135 | Para 135: vet vendor personnel; background checks, NDAs and security compliance agreements |
| rbi-cybersecurity-framework-for-banks::136 | Para 136: cyber controls enforced on ATM switch application service providers |
| rbi-cybersecurity-framework-for-banks::137 | Para 137: ATM switch ASP controls written into contracts and scoped to the IT ecosystem |
| rbi-cybersecurity-framework-for-banks::138 | Para 138: 24 baseline cyber controls mandated in ASP contracts |
| rbi-cybersecurity-framework-for-banks::139 | Para 139: share applicable RBI instructions with ATM switch ASPs |
Chapter V R to X: cryptography, straight through processing, surveillance, threat defence, anti-phishing and VA/PT – RBI Cybersecurity Framework for Banks
| Code | Title |
|---|---|
| rbi-cybersecurity-framework-for-banks::140 | Para 140: strong, non-deprecated cryptography compliant with law |
| rbi-cybersecurity-framework-for-banks::141 | Para 141: no manual intervention in data between processes for critical applications |
| rbi-cybersecurity-framework-for-banks::142 | Para 142: tested, automated, authenticated STP interfaces with audit trails |
| rbi-cybersecurity-framework-for-banks::143 | Para 143: set up a CSOC for continuous surveillance |
| rbi-cybersecurity-framework-for-banks::144 | Para 144: multi-point defence against malicious code |
| rbi-cybersecurity-framework-for-banks::145 | Para 145: anti-malware with behavioural detection everywhere, centrally managed |
| rbi-cybersecurity-framework-for-banks::146 | Para 146: whitelist internet websites and systems |
| rbi-cybersecurity-framework-for-banks::147 | Para 147: consider secure web gateways with HTTPS deep inspection |
| rbi-cybersecurity-framework-for-banks::148 | Para 148: anti-phishing and anti-rogue app takedown services |
| rbi-cybersecurity-framework-for-banks::149 | Para 149: periodic VA and PT for all critical and internet-facing systems |
| rbi-cybersecurity-framework-for-banks::150 | Para 150: VA/PT of critical internet-facing applications, servers and network across the lifecycle |
| rbi-cybersecurity-framework-for-banks::151 | Para 151: VA every six months and PT every 12 months for critical and DMZ customer-facing systems |
| rbi-cybersecurity-framework-for-banks::152 | Para 152: post-implementation VA/PT on production, or documented ISC-approved deviation |
| rbi-cybersecurity-framework-for-banks::153 | Para 153: fix vulnerabilities on time and keep them fixed |
| rbi-cybersecurity-framework-for-banks::154 | Para 154: documented VA/PT approach including scoring, also for cloud-hosted systems |
| rbi-cybersecurity-framework-for-banks::155 | Para 155: VA/PT by trained, independent experts |
| rbi-cybersecurity-framework-for-banks::156 | Para 156: control over audit methodology and auditor competence when engaging VA/PT auditors |
| rbi-cybersecurity-framework-for-banks::157 | Para 157: reasonable assurance per area stated in VA/PT reports |
| rbi-cybersecurity-framework-for-banks::158 | Para 158: ongoing review of VA/PT auditor performance including missed vulnerabilities |
| rbi-cybersecurity-framework-for-banks::159 | Para 159: interact with auditors; follow CERT-In audit policy guidelines for empanelled auditors |
| rbi-cybersecurity-framework-for-banks::160 | Para 160: close monitoring of VA/PT findings by security, IS audit and senior management |
| rbi-cybersecurity-framework-for-banks::161 | Para 161: quarterly VA/PT closure status to the ITSC and ISC |
Chapter V Y: business continuity and disaster recovery – RBI Cybersecurity Framework for Banks
| Code | Title |
|---|---|
| rbi-cybersecurity-framework-for-banks::163 | Para 163: BCP and DR policy on best practice such as ISO 22301, updated on major developments |
| rbi-cybersecurity-framework-for-banks::164 | Para 164: BCP and DR designed for rapid, secure recovery after cyber-attacks within RTOs |
| rbi-cybersecurity-framework-for-banks::165 | Para 165: DR drills half-yearly for critical systems |
| rbi-cybersecurity-framework-for-banks::166 | Para 166: major DR drill issues fixed and retested before next cycle |
| rbi-cybersecurity-framework-for-banks::167 | Para 167: DR testing runs DR as primary for at least a full working day |
| rbi-cybersecurity-framework-for-banks::168 | Para 168: test BCP and DR under different contingency scenarios |
| rbi-cybersecurity-framework-for-banks::169 | Para 169: backups taken, restore-tested, integrity preserved and secured |
| rbi-cybersecurity-framework-for-banks::170 | Para 170: DR architecture and procedures meet defined RTO and RPO |
| rbi-cybersecurity-framework-for-banks::171 | Para 171: minimal ITSC-approved RTO and near zero RPO for critical systems |
| rbi-cybersecurity-framework-for-banks::172 | Para 172: documented reconciliation where RPO is not zero |
| rbi-cybersecurity-framework-for-banks::173 | Para 173: identical configurations and patches at DC and DR |
| rbi-cybersecurity-framework-for-banks::174 | Para 174: BCP/DR on interconnected vendor and partner systems with collaborative testing |
Chapter V Z: cyber incident response, recovery and crisis management – RBI Cybersecurity Framework for Banks
| Code | Title |
|---|---|
| rbi-cybersecurity-framework-for-banks::175 | Para 175: incident response and recovery policy with eight elements |
| rbi-cybersecurity-framework-for-banks::176 | Para 176: specialised training for incident handlers |
| rbi-cybersecurity-framework-for-banks::177 | Para 177: response plans for varied scenarios with stakeholder coordination |
| rbi-cybersecurity-framework-for-banks::178 | Para 178: lessons learned fed into response plans |
| rbi-cybersecurity-framework-for-banks::179 | Para 179: documented strategies for ransomware, data destruction and DDoS |
| rbi-cybersecurity-framework-for-banks::180 | Para 180: contain attacks by shielding and quarantine |
| rbi-cybersecurity-framework-for-banks::181 | Para 181: analyse incidents for severity, impact and root cause; corrective and preventive measures |
| rbi-cybersecurity-framework-for-banks::182 | Para 182: report cyber incidents on DAKSH within six hours; notify CERT-In |
| rbi-cybersecurity-framework-for-banks::183 | Para 183: escalation and reporting plans to Board, senior management and customers |
| rbi-cybersecurity-framework-for-banks::185 | Para 185: external coordination and threat intelligence integration |
| rbi-cybersecurity-framework-for-banks::186 | Para 186: lawful systems to collect and share threat information |
| rbi-cybersecurity-framework-for-banks::187 | Para 187: improve response and recovery through lessons from incidents, tests and drills |
| rbi-cybersecurity-framework-for-banks::188 | Para 188: participate in CERT-In and IDRBT cyber drills |
| rbi-cybersecurity-framework-for-banks::189 | Para 189: resilient interconnected systems with collaborative testing and capacity |
| rbi-cybersecurity-framework-for-banks::190 | Para 190: crisis communication tested through drills with customers and providers |
| rbi-cybersecurity-framework-for-banks::191 | Para 191: SOC, incident response and forensics aligned to cut downtime |
| rbi-cybersecurity-framework-for-banks::192 | Para 192: documented Cyber Crisis Management Plan within the Board framework |
| rbi-cybersecurity-framework-for-banks::193 | Para 193: CCMP covers detection, containment, response and recovery for a wide threat set |
Chapter VI: Cyber Security Operations Centre – RBI Cybersecurity Framework for Banks
| Code | Title |
|---|---|
| rbi-cybersecurity-framework-for-banks::212 | Para 212: CSOC framework proportionate to risk, scale and obligations |
| rbi-cybersecurity-framework-for-banks::213 | Para 213: CSOC governance: Board and management briefing, dashboards, metrics and reporting |
| rbi-cybersecurity-framework-for-banks::214 | Para 214: proactive monitoring with tools for detection, response and analytics |
| rbi-cybersecurity-framework-for-banks::215 | Para 215: log collection, storage, SIEM correlation, dashboard monitoring and alerting |
| rbi-cybersecurity-framework-for-banks::216 | Para 216: CSOC systems: root cause, classification, investigation, behaviour analysis, IoCs, analytics, honeypots |
| rbi-cybersecurity-framework-for-banks::217 | Para 217: CSOC responsibilities across protect, detect, respond and recover |
| rbi-cybersecurity-framework-for-banks::218 | Para 218: security analytics engine with timely processing and deep packet inspection |
| rbi-cybersecurity-framework-for-banks::219 | Para 219: malware detection and analysis and forensic imaging tools |
| rbi-cybersecurity-framework-for-banks::220 | Para 220: CSOC architecture scalable, highly available and capable across six outcomes |
| rbi-cybersecurity-framework-for-banks::221 | Para 221: CSOC staffing across Level 1, 2 and 3 |
| rbi-cybersecurity-framework-for-banks::222 | Para 222: differentiated hiring, management and retention for CSOC staff |
| rbi-cybersecurity-framework-for-banks::223 | Para 223: 24x7 staffing model, training, incentives, SOC metrics and capacity planning |
Chapter VII: Information systems audit – RBI Cybersecurity Framework for Banks
| Code | Title |
|---|---|
| rbi-cybersecurity-framework-for-banks::224 | Para 224: Audit Committee oversees IS audit |
| rbi-cybersecurity-framework-for-banks::225 | Para 225: ACB-approved IS audit policy reviewed annually |
| rbi-cybersecurity-framework-for-banks::226 | Para 226: ACB reviews critical IT and cyber issues and directs management |
| rbi-cybersecurity-framework-for-banks::227 | Para 227: separate, competent IS audit function; accountability for external IS audits retained |
| rbi-cybersecurity-framework-for-banks::228 | Para 228: risk-based IS audit planning |
Chapters II and III A to B: Board, IT governance framework and security policies – RBI Cybersecurity Framework for Banks
| Code | Title |
|---|---|
| rbi-cybersecurity-framework-for-banks::12 | Para 12: IT governance framework on the five focus areas |
| rbi-cybersecurity-framework-for-banks::13 | Para 13: enterprise or operational risk policy assesses IT risks periodically |
| rbi-cybersecurity-framework-for-banks::14 | Para 14: Information Security Policy with the prescribed contents |
| rbi-cybersecurity-framework-for-banks::15 | Para 15: Board-approved Cybersecurity Policy distinct from the IT and information security policies |
| rbi-cybersecurity-framework-for-banks::7 | Para 7: Board approves IT, asset, continuity, security and cyber strategies and policies |
| rbi-cybersecurity-framework-for-banks::8 | Para 8: annual Board review of the strategies and policies |
What is RBI Cybersecurity Framework for Banks and who does it apply to?
RBI Cybersecurity Framework for Banks is a compliance framework from India (Reserve Bank of India) with 16 domains and 216 controls. The Reserve Bank of India's 2026 Directions on cybersecurity, technology risk, resilience and assurance for commercial banks, which replaced the 2016 Cyber Security Framework in Banks and the 2023 IT governance Master Direction: Board and committee governance (IT Strategy Committee, Information Security Committee, an independent CISO reporting to risk), IT and cyber risk management, some 160 baseline controls from asset inventory to DMARC, VA/PT and half-yearly full-day DR switchovers, third-party and ATM switch provider controls, incident reporting on DAKSH within six hours, a Cyber Security Operations Centre and IS audit. It is used by organisations to establish and maintain compliance with industry standards and regulatory requirements.
What does RBI Cybersecurity Framework for Banks actually require?
RBI Cybersecurity Framework for Banks has 216 controls organised across 16 domains. The largest domains are Chapter V L to P: access control, teleworking, customer authentication, mail and removable media – RBI Cybersecurity Framework for Banks (22 controls), Chapter V R to X: cryptography, straight through processing, surveillance, threat defence, anti-phishing and VA/PT – RBI Cybersecurity Framework for Banks (22 controls), Chapter V A to G: assets, data leakage, migration, software, physical, capacity and configuration – RBI Cybersecurity Framework for Banks (21 controls). Each control defines specific requirements that organisations must implement to achieve compliance.
If I already comply with another framework, how much of RBI Cybersecurity Framework for Banks do I already cover?
RBI Cybersecurity Framework for Banks does not currently have cross-framework mappings in our system. Check back as we continuously expand our mapping database.
How do I implement RBI Cybersecurity Framework for Banks?
Start your RBI Cybersecurity Framework for Banks compliance journey by running a self-assessment on our platform to identify your current compliance posture. Our AI advisory can answer specific questions about RBI Cybersecurity Framework for Banks requirements, and cross-framework mapping helps you leverage existing controls from other frameworks you may already comply with. Create a free account to access all 216 controls and track your progress.
Start Your Compliance Journey
Create a free account to run self-assessments, get AI advisory, and track your compliance progress across 1,120 frameworks.
Get Started Free →Free forever, no credit card required