Key takeaways
- The Reserve Bank of India (RBI) Directions RBI/DoS/2026-27/437 were issued on 31 July 2026 and came into force immediately.
- The Directions define four levels using full criteria that include payment-system membership, digital services and specified infrastructure.
- Each level applies cumulative chapters. Each bank should document its paragraph 4 assessment and applicable controls.
- Re-apply the criteria when services or infrastructure change; RBI does not set a fixed reassessment cycle in paragraph 10.
Information correct as at 31 October 2026.
What are the four UCB levels?
The Directions apply to urban co-operative banks (UCBs), defined as Primary Co-operative Banks under the Banking Regulation Act. Paragraph 4 classifies each UCB into one of four levels based on the specified criteria and states which chapters apply. Paragraph 10 requires each bank to self-assess its level and meet the applicable controls. A bank may adopt higher-level measures based on its Board’s risk and capability assessment. Reserve Bank of India UCB Cybersecurity, Technology: Risk, Resilience and Assurance Framework Directions, 2026, notification RBI/DoS/2026-27/437
Centralised payment system (CPS), Cheque Truncation System (CTS), Immediate Payment Service (IMPS), Unified Payments Interface (UPI), and Society for Worldwide Interbank Financial Telecommunication (SWIFT) are used below. Paragraph 4 also defines which payment systems count as CPS. Reserve Bank of India UCB Cybersecurity, Technology: Risk, Resilience and Assurance Framework Directions, 2026, notification RBI/DoS/2026-27/437
| Level | Criteria summary | Chapters |
|---|---|---|
| I | Every UCB, regardless of digital services | II–III |
| II | CPS sub-member plus at least one: internet banking, mobile banking, or direct CTS, IMPS or UPI membership | II–IV |
| III | At least one: direct CPS membership, own ATM switch, or SWIFT interface | II–V |
| IV | CPS direct/sub-member plus at least one: own ATM switch and SWIFT interface; or hosting a data centre / software support to other banks, directly or through a wholly owned subsidiary | II–VI |
This summary is a starting point; confirm the bank’s actual status and all paragraph 4 conditions against the notification. Reserve Bank of India UCB Cybersecurity, Technology: Risk, Resilience and Assurance Framework Directions, 2026, notification RBI/DoS/2026-27/437
What changes should prompt a reassessment?
A change to payment-system membership, digital channels or specified infrastructure can affect how the paragraph 4 criteria apply. Use these changes as prompts to repeat the full self-assessment, not as standalone classification rules.
- A CPS sub-member adds internet banking, mobile banking or a direct CTS, IMPS or UPI membership.
- The bank becomes a direct member of a centralised payment system.
- The bank adds an own ATM switch or SWIFT interface.
- The bank starts qualifying data-centre hosting or software support for other banks.
The Directions require self-assessment but do not set a fixed reassessment cycle. A periodic review and a review when relevant services change are practical governance recommendations.
What does each level add?
Level I: baseline requirements for every UCB
Chapters II and III cover Board roles and baseline cybersecurity and resilience requirements, including policies, asset inventory, information protection, access, patching, backup, vendor risk, incident response and information systems audit. The exact control obligations should be read in the applicable paragraphs of the Directions. Reserve Bank of India UCB Cybersecurity, Technology: Risk, Resilience and Assurance Framework Directions, 2026, notification RBI/DoS/2026-27/437
Paragraph 88 requires UCBs to report cyber incidents within six hours of detection on DAKSH, the Reserve Bank’s Advanced Supervisory Monitoring System. This is separate from reporting to the Indian Computer Emergency Response Team (CERT-In), which has its own covered incident categories and clock: six hours from noticing or being brought to notice. Reserve Bank of India UCB Cybersecurity, Technology: Risk, Resilience and Assurance Framework Directions, 2026, notification RBI/DoS/2026-27/437
Level II: testing and a security official
Chapter IV applies to Level II and higher UCBs. Paragraph 104 requires an official responsible for information security policy and compliance. Paragraph 116 covers internet-facing web and mobile applications, servers and network components through their lifecycle: vulnerability assessments of critical applications and those in the demilitarised zone (DMZ) at least every six months, and penetration testing at least annually. Paragraph 117 addresses a Core Banking Solution (CBS) on shared Application Service Provider (ASP) infrastructure: the provider must subject the CBS application and hosting infrastructure to vulnerability assessment and penetration testing (VA/PT). Paragraph 119 requires professionally qualified testing teams. Reserve Bank of India UCB Cybersecurity, Technology: Risk, Resilience and Assurance Framework Directions, 2026, notification RBI/DoS/2026-27/437
Level III: monitoring and response
Chapter V adds advanced real-time threat defence, audit-log monitoring and analysis, incident response, awareness, and a risk-based transaction monitoring system. Map the applicable controls to system owners and retain evidence of operation, review and follow-up. Reserve Bank of India UCB Cybersecurity, Technology: Risk, Resilience and Assurance Framework Directions, 2026, notification RBI/DoS/2026-27/437
Level IV: operations and governance
Chapter VI adds a cybersecurity operations centre (CSOC), cyber drills, incident response, metrics and forensics. For Level IV governance, paragraph 173 says a Board-level IT Strategy Committee (ITSC) may be considered; paragraph 174 requires an IT Steering Committee. Paragraphs 175–176 require a sufficiently senior Chief Information Security Officer (CISO) and a quarterly review of cybersecurity arrangements before the IT Steering Committee or Board. Paragraphs 177–178 require an Information Security Committee (ISC) to meet quarterly, keep minutes and escalate decisions and reviews to the Board / IT Strategy Committee quarterly. Reserve Bank of India UCB Cybersecurity, Technology: Risk, Resilience and Assurance Framework Directions, 2026, notification RBI/DoS/2026-27/437
What evidence should the bank prepare?
- A dated paragraph 4 self-assessment, the criteria applied and the governance approval record.
- Board-approved cybersecurity policy and cyber crisis management plan.
- An asset inventory reconciled with payment-system connections and production channels.
- Access reviews, patch records and other control evidence required at the bank’s level.
- Incident records showing detection, DAKSH and any CERT-In reporting times.
- Level II and above: applicable VA/PT reports, remediation and retest evidence.
- Level IV: cybersecurity operations centre, drill, committee-minute and quarterly escalation evidence.
How can the bank check whether its level needs review?
Compare the bank’s current services and infrastructure with the exact paragraph 4 criteria and its last documented assessment. Any relevant change is a sensible prompt to repeat the assessment. This is a practical recommendation; RBI has not prescribed a fixed reassessment cycle in paragraph 10.
- Is the bank a CPS sub-member or direct member, and which system is involved?
- Does it offer internet banking or mobile banking?
- Does it operate an own ATM switch or SWIFT interface?
- Does it host a data centre or provide software support to other banks under the stated conditions?
What should the Board and management do now?
- Board: request the latest dated self-assessment and the evidence behind each criterion.
- CEO/security official: apply the complete paragraph 4 wording and take the documented result through governance.
- IT head: reconcile the asset inventory with payment connections, apps and hosting arrangements.
- Security official: walk through a recent incident timeline to DAKSH and, where applicable, CERT-In.
- Level II and above: check VA/PT scope, dates, remediation and retest records.
- Level IV: check CSOC, drill and required committee records and quarterly escalation.
This article is general information for awareness and education. It is not legal, regulatory or professional advice and does not take into account the circumstances of your organisation. Laws, standards and threats change; check the primary sources cited and take qualified advice before acting.
How Bravewall helps
Bravewall coordinates cybersecurity programmes around agreed requirements, responsibilities and evidence. The bank’s compliance function and advisers should determine the application of the Directions to its particular circumstances.

