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