We use essential cookies to run this site. Analytics & marketing cookies load only with your consent — see our Cookie Policy and Privacy Policy.

Knowledge Center / RBI Cyber Security Framework
Reserve Bank of India · India

RBI Cyber Security Framework for Banks

Baseline cybersecurity and resilience controls mandated by RBI for banks.

Jurisdiction: IndiaIssued by: Reserve Bank of IndiaLast reviewed: November 2026Reviewed by CyberSigma — CERT-In empanelled, PCI QSAPrimary source: RBI Notifications & Master Directions ↗
Where do you stand on RBI Cyber Security Framework?
Free self-assessment \u2014 your readiness score, top gaps and what to fix first, in minutes.
Score yourself \u2192
This guide reflects the current 2026 RBI cyber framework
RBI cyber security requirements for banks and NBFCs are now set by the RBI (Cybersecurity, Technology: Risk, Resilience and Assurance Framework) Directions, 2026, issued on 31 July 2026. These repealed and replaced the 2 June 2016 Cyber Security Framework in Banks (DBS.CO/CSITE/BC.11/33.01.001/2015-16) and the November 2023 IT Governance Master Direction, consolidating them with around 626 circulars into a single, entity-specific framework in force immediately with no transition window. This guide is written to the 2026 Directions; the 2016 Cyber Security Framework is referenced only as their lineage.

Introduction

The RBI Cyber Security Framework began with the 2 June 2016 circular that first made cyber resilience a board-level obligation for Indian banks. That circular, and the November 2023 Master Direction on IT Governance, Risk, Controls and Assurance Practices, have now been consolidated and replaced by the RBI (Cybersecurity, Technology: Risk, Resilience and Assurance Framework) Directions, 2026. The 2026 Directions keep the DNA of the 2016 framework — a board-approved cyber posture, a baseline of mandatory controls, continuous surveillance and prompt incident reporting — and go considerably further on governance, a round-the-clock Cyber Security Operations Centre, resilience and independent assurance.

Crucially, the 2026 Directions are entity-specific: the Reserve Bank issued separate Directions under one common title for commercial banks (RBI/DoS/2026-27/410), small finance banks, payments banks, urban co-operative banks, all-India financial institutions, NBFCs and credit information companies. Each is calibrated to the entity's size, risk and digital footprint, with proportionality for smaller entities and a comply-or-explain path for foreign banks on certain chapters.

This deep-dive is written for Chief Information Security Officers (CISOs), Heads of IT, the Board-level IT Strategy Committee, internal auditors and independent assessors who must plan, run or defend a self-assessment or supervisory examination against the framework. It provides an auditor-grade decomposition of the baseline control themes, a master assessment checklist, an evidence taxonomy, maturity and scoping guidance, and a mapping to NIST CSF 2.0, ISO/IEC 27001:2022 and PCI DSS v4.0.1.

Source note
The RBI Directions and their chapters are issued by the Reserve Bank of India and are Crown-equivalent regulatory material. This guide is an original interpretive summary prepared by CyberSigma for educational and readiness purposes. It paraphrases and does not reproduce the verbatim text of any RBI Direction. Entities must always refer to the authoritative text of the applicable 2026 Direction on rbi.org.in.

What changed on 31 July 2026

The change is a repeal-and-consolidate, not an amendment. On 31 July 2026 the 2016 Cyber Security Framework in Banks and the 2023 IT Governance Master Direction — along with roughly 626 other circulars — ceased to have effect and were replaced by the 2026 Directions, which took effect immediately with no glide path. Action already taken under the repealed instruments remains governed by them, and approvals already granted are treated as granted under the 2026 Directions.

  • A 24x7 Cyber Security Operations Centre (C-SOC) is now a first-class, explicitly structured requirement — with SIEM-based log collection and correlation and tiered L1/L2/L3 staffing — not merely "continuous surveillance".
  • An independent Chief Information Security Officer of General Manager rank is required, with no reporting line to the Head of IT, no business targets, and quarterly reporting to the Board.
  • Cyber incidents must be reported to the RBI on the DAKSH platform within six hours of detection, alongside CERT-In notification.
  • Defined testing cadence: vulnerability assessment at least every six months and penetration testing at least annually for critical and internet-facing systems, by independent, competent assessors.
  • Board ownership is formalised through an IT Strategy Committee that meets at least quarterly and approves the cyber strategy at least annually.
  • The framework is entity-specific and consolidated, so a single Direction now carries IT governance, cyber security, resilience and assurance that previously sat across multiple instruments.

The practical implication: a cyber posture last built to the 2016 framework or the 2023 Master Direction is not automatically compliant. The gaps most entities must close are the mandatory C-SOC, CISO independence, the six-hour DAKSH reporting runbook, and evidencing the VA/PT cadence.

What the 2026 RBI cyber framework is

The framework is a mandatory, board-driven set of outcomes and baseline controls that every covered entity must implement to govern technology, manage cyber and IT risk, operate detection and response, and prove resilience. It is both outcome-oriented — the Reserve Bank cares that the control works and can be evidenced — and prescriptive at the baseline, specifying controls such as asset inventory, data classification, network segmentation, non-deprecated cryptography and multi-factor authentication for privileged access.

The Commercial Banks Direction runs to 233 paragraphs across eight chapters; the other entity versions follow the same architecture, proportioned to the entity. At a theme level the chapters cover: preliminary matters and applicability; the role of the Board; IT governance and oversight; risk management; baseline cybersecurity controls; the Cyber Security Operations Centre; business continuity and resilience; and Information Systems audit.

Chapter themeWhat it covers
PreliminaryShort title, commencement, applicability and definitions; the repeal of the 2016 framework and 2023 Master Direction.
Role of the BoardBoard accountability for technology and cyber risk; the IT Strategy Committee (composition, quarterly cadence); annual approval of the cyber strategy and board-level training.
IT governance & oversightGovernance structure, senior-management responsibilities, the independent CISO, policies and the information-security function.
Risk managementIT and information-security risk framework, third-party and outsourcing risk, and cyber-risk assessment.
Baseline cybersecurity controlsAsset inventory and classification, secure configuration, network and endpoint security, cryptography, access control and MFA, application security, data protection and the enduring control themes checklisted below.
Cyber Security Operations CentreA 24x7 C-SOC with SIEM, log collection and correlation, tiered staffing and continuous monitoring and threat detection.
Business continuity & resilienceBCP, disaster recovery with defined RTO/RPO, half-yearly DR drills for critical systems, and incident and cyber-crisis management including six-hour DAKSH reporting.
Information Systems auditAn independent, risk-based IS audit overseen by the Audit Committee of the Board, with tracked closure of findings.

Who must comply

The 2026 framework binds a defined universe of RBI-regulated entities, each under its own entity-specific Direction issued on 31 July 2026. Requirements are proportionate to the entity's category, scale and digital footprint.

Entity typeApplicability and notes
Commercial banksBanking companies, State Bank of India and corresponding new banks. Governed by RBI/DoS/2026-27/410; foreign banks may follow a comply-or-explain approach for certain chapters.
Small finance banks / payments banksCovered by their own entity-specific 2026 Directions, proportioned to their model.
Urban co-operative banks (UCBs)Covered by a UCB-specific 2026 Direction; expectations scale with the bank’s digital footprint and tier.
NBFCsCovered by an NBFC-specific 2026 Direction, calibrated to the layer under scale-based regulation (Base, Middle, Upper, Top).
All-India financial institutionsEXIM Bank, NABARD, NaBFID, NHB and SIDBI, under the AIFI-specific Direction.
Credit information companies (CICs)Covered by a CIC-specific 2026 Direction.
Payment system participants & auditorsReference the framework for assurance, SAR and third-party certification obligations.

Master assessment checklist

This is the operative section of the guide. The baseline control themes below are the enduring core that the 2026 Directions carry forward from the earlier framework and that an assessment, a C-SOC and the Information Systems audit all verify in practice. Each domain is decomposed into what to verify and the typical evidence an assessor or examiner expects. Read them against the applicable 2026 Direction for your entity type; the 2026 additions — mandatory 24x7 C-SOC, independent GM-rank CISO, six-hour DAKSH reporting and the VA/PT cadence — are called out in the relevant domains and in the sections that follow.

D1 - Inventory Management of Business IT Assets

What to verifyTypical evidence
A centralised, current inventory of all IT assets (hardware, software, network devices, virtual assets) exists.Asset management system export; CMDB records; reconciliation reports.
Assets are classified by business criticality and information sensitivity.Asset classification policy; criticality-tagged inventory; data classification matrix.
Ownership is assigned for each asset / information asset.Asset owner register; RACI for asset stewardship.
Unauthorised or unknown devices on the network are detected.Network access control (NAC) logs; rogue-device detection reports.
Inventory is reconciled periodically and on change.Periodic reconciliation sign-offs; discovery scan results.
End-of-life and unsupported assets are identified and risk-managed.EOL register; exception approvals; compensating-control notes.

D2 - Preventing Execution of Unauthorised Software

What to verifyTypical evidence
Application whitelisting is enforced on critical endpoints and servers.Whitelisting policy configuration; agent deployment coverage report.
Users cannot install software without authorisation.Endpoint privilege configuration; software request/approval workflow.
A defined list of authorised software is maintained and enforced.Approved software catalogue; deviation exception log.
Unauthorised software execution attempts are logged and alerted.Blocked-execution logs; SIEM alerts.
Regular scans detect unauthorised or unlicensed software.Software discovery scan reports; licence compliance records.

D3 - Environmental Controls

What to verifyTypical evidence
Physical access to data centres and critical rooms is restricted and logged.Access control (badge/biometric) logs; visitor register.
Environmental protections (fire, power, cooling, water) are in place and tested.Maintenance records; fire suppression test certificates; UPS/genset logs.
CCTV surveillance covers critical areas with adequate retention.CCTV coverage map; footage retention configuration.
Environmental monitoring and alerting is operational.BMS alerts; temperature/humidity monitoring logs.

D4 - Network Management and Security

What to verifyTypical evidence
Network is segmented, with critical systems isolated from general/corporate networks.Network architecture diagram; VLAN/segmentation configuration; firewall zones.
Firewall and perimeter rulesets follow least-privilege and are reviewed periodically.Firewall rule base; periodic rule review reports; rule change tickets.
Ingress/egress traffic is controlled and monitored; unnecessary ports/services closed.Egress filtering config; port scan baselines.
Wireless networks are secured, segregated and monitored.Wireless security policy; WPA2/enterprise config; rogue AP detection.
Remote access (VPN) uses strong authentication and is restricted.VPN configuration; MFA enforcement; access approval records.
Intrusion Prevention/Detection is deployed at network boundaries.IPS/IDS deployment; signature update logs; alert samples.

D5 - Secure Configuration

What to verifyTypical evidence
Hardening baselines (e.g., CIS Benchmarks) are defined for OS, DB, network devices.Configuration standards documents; baseline templates.
Default credentials and unnecessary services/accounts are removed.Configuration audit results; account review reports.
Configuration compliance is scanned periodically and deviations remediated.Configuration compliance scan reports; remediation tracker.
Golden images are used for standardised deployment.Image build documentation; deployment records.

D6 - Application Security Life Cycle (ASLC)

What to verifyTypical evidence
Secure coding standards are adopted and developers trained.Secure coding policy; training records.
Security requirements are captured at design; threat modelling performed for critical apps.Requirement docs; threat model artefacts.
Static and dynamic application security testing (SAST/DAST) is performed before release.SAST/DAST reports; defect remediation evidence.
Independent application security testing / VAPT precedes go-live for critical applications.VAPT reports; sign-off before deployment.
Change and version control governs code promotion to production.Change tickets; approval workflow; segregation of dev/test/prod.
Third-party and open-source components are inventoried and vulnerability-checked.SBOM/component inventory; SCA scan results.

D7 - Patch / Vulnerability and Change Management

What to verifyTypical evidence
A documented patch management policy defines timelines by severity.Patch management policy; SLA matrix.
Vulnerability assessment and penetration testing (VAPT) is performed at defined frequency.VAPT scope and reports; retest evidence.
Vulnerabilities are prioritised by risk and remediated within SLA.Vulnerability register; ageing/SLA reports.
Critical/security patches are applied promptly across the estate.Patch deployment reports; coverage dashboards.
Changes follow a formal change management process with rollback plans.Change advisory board minutes; change records.

D8 - User Access Control / Management

What to verifyTypical evidence
Access is granted on least-privilege and need-to-know, via role-based access control.Access control policy; role definitions; provisioning records.
Privileged accounts are managed through a PAM solution with session recording.PAM configuration; privileged session logs; vaulting evidence.
Multi-factor authentication protects privileged and remote access.MFA policy and enforcement configuration.
User access is recertified periodically and on role change / exit.Access recertification reports; joiner-mover-leaver records.
Segregation of duties prevents toxic access combinations.SoD rule set; conflict analysis reports.
Dormant, orphan and shared accounts are eliminated or controlled.Dormant account reports; shared-account justification.

D9 - Authentication Framework for Customers

What to verifyTypical evidence
Customer-facing channels use multi-factor / additional-factor authentication.Authentication design docs; 2FA/OTP configuration.
Risk-based / adaptive authentication is applied to higher-risk transactions.Adaptive auth rules; risk-scoring configuration.
Session management, timeout and re-authentication controls are enforced.Session policy; application configuration.
Credentials are stored and transmitted securely (hashing, TLS).Cryptographic standards; TLS configuration; secure storage evidence.
Customer authentication anomalies trigger alerts and controls.Fraud/anomaly detection rules; alert samples.

D10 - Secure Mail and Messaging Systems

What to verifyTypical evidence
Anti-spoofing controls (SPF, DKIM, DMARC) are implemented for the bank's domains.DNS records; DMARC policy and reports.
Inbound e-mail is filtered for spam, malware and phishing.Mail gateway configuration; quarantine/detection reports.
Outbound e-mail is monitored for data leakage.Outbound DLP rules; blocked-message logs.
Messaging systems enforce encryption and access control.Encryption configuration; access logs.

D11 - Vendor / Outsourcing Risk Management

What to verifyTypical evidence
Third parties are risk-assessed before onboarding.Vendor due-diligence reports; risk-tiering.
Contracts include security, audit, incident-notification and right-to-audit clauses.Executed contracts / SLAs with security schedules.
Vendor access to bank systems and data is controlled and monitored.Access provisioning records; monitoring logs.
Vendor security posture is periodically reviewed / audited.Vendor audit reports; SOC 2 / ISO 27001 certificates.
Concentration and fourth-party risks are considered.Outsourcing register; sub-contractor disclosures.

D12 - Removable Media Controls

What to verifyTypical evidence
Use of USB and removable media is disabled by default and allowed only by exception.Endpoint device-control policy; exception approvals.
Data written to removable media is encrypted and logged.Encryption enforcement config; media usage logs.
Media disposal follows secure sanitisation.Media disposal / destruction certificates.

D13 - Advanced Real-time Threat Defence and Management

What to verifyTypical evidence
Anti-malware / EDR is deployed across endpoints and servers with current signatures.EDR coverage report; signature/definition update logs.
Advanced threat (APT/sandboxing) defences protect key ingress points.Sandbox/ATP configuration; detection reports.
DDoS mitigation protects internet-facing services.DDoS protection service configuration; drill/test evidence.
Behaviour-based and threat-intelligence-driven detection is operational.Threat-intel feed integration; behavioural alert samples.

D14 - Anti-Phishing

What to verifyTypical evidence
The bank subscribes to an anti-phishing / brand-monitoring service.Anti-phishing service contract; monitoring dashboard.
Phishing sites impersonating the bank are detected and taken down.Takedown request logs; resolution timelines.
Customers are educated to identify phishing and report it.Awareness communications; reporting channel evidence.

D15 - Data Leak Prevention Strategy

What to verifyTypical evidence
Data is classified and a DLP strategy covers endpoint, network and storage.Data classification policy; DLP deployment architecture.
DLP policies detect and block unauthorised exfiltration of sensitive data.DLP rule set; incident/blocked-transfer reports.
Encryption protects data at rest and in transit.Encryption standards; key management records.
Data retention and secure disposal are governed.Retention schedule; disposal records.

D16 - Audit Logs and Continuous Surveillance (C-SOC)

What to verifyTypical evidence
A Cyber Security Operations Centre provides 24x7 monitoring (in-house or managed).C-SOC charter; staffing roster; shift coverage.
Logs from critical systems are centrally collected in a SIEM.Log source inventory; SIEM onboarding coverage.
Correlation rules and use cases generate actionable alerts.Use-case library; alert triage records.
Log integrity, retention and time synchronisation are assured.Log retention config; NTP configuration; tamper-protection controls.
Alerts are triaged and escalated per defined runbooks.SOC runbooks; escalation matrix; ticket samples.
SOC effectiveness is measured and reviewed.SOC metrics/MIS; management review minutes.

D17 - Incident Response and Management

What to verifyTypical evidence
A Cyber Crisis Management Plan (CCMP) is documented and board-aware.CCMP document; board/committee approval.
Incident response roles, severity classification and workflows are defined.IR plan; severity matrix; RACI.
Cyber incidents are reported to the RBI within the mandated window.Incident reports to RBI (Annex 2 format); dispatch timestamps.
Incidents are contained, eradicated and recovered with post-incident review.Incident tickets; RCA / lessons-learned reports.
Forensic readiness and evidence preservation capability exist.Forensics procedures; chain-of-custody templates; retainer with forensic provider.
IR plan is tested through drills / tabletop exercises.Drill reports; tabletop exercise records.

D18 - Risk-based Transaction Monitoring, Metrics and Awareness

What to verifyTypical evidence
Transactions are monitored on a risk basis for fraud and anomalies.Transaction monitoring rules; fraud alert reports.
Security metrics / KRIs are reported to management and the board.Security MIS; board dashboards; committee minutes.
Staff undergo periodic cybersecurity awareness training.Training completion records; phishing simulation results.
Customer awareness programmes on cyber hygiene are run.Customer advisories; campaign records.
Periodic self-assessment against the framework is performed.Self-assessment reports submitted to RBI; gap trackers.

Scoping

Scoping determines the boundary of systems, data, people, facilities and third parties subject to assessment. For the RBI framework, scope is inherently broad: the framework applies to the bank as a whole, so scope-reduction techniques familiar from card-data assessments do not apply in the same way. The objective of scoping here is to prioritise assessment depth by criticality, not to exclude systems from applicability.

  • In-scope systems: core banking system (CBS), internet and mobile banking, payment switches (ATM/POS), SWIFT/RTGS/NEFT/UPI/IMPS interfaces, treasury, and all supporting infrastructure.
  • In-scope data: customer PII, account and transaction data, authentication credentials, and any data whose compromise affects confidentiality, integrity or availability of banking services.
  • In-scope facilities: primary and disaster-recovery data centres, network operations centres, the C-SOC, and branch infrastructure with system access.
  • In-scope people: employees, contractors, privileged administrators, and vendor personnel with system or data access.
  • In-scope third parties: managed service providers, cloud providers, ATM switch operators, and any outsourced technology function.
  • Connected environments: ATM Switch and SWIFT-related systems attract additional, specifically enumerated controls under the graded coverage guidance and must be scoped explicitly.
  • Interconnections and trust relationships between the bank and payment networks, aggregators and fintech partners must be mapped and assessed.
Scoping caution
Because accountability cannot be outsourced, cloud-hosted and vendor-operated systems remain fully in scope. A common examination finding is that a bank treats a managed C-SOC or cloud CBS as 'the vendor's responsibility'. The assessor must trace controls into the vendor environment through contracts, audit rights and independent assurance reports.

Implementation approach

A pragmatic implementation programme progresses through five phases. Each phase produces defined deliverables that also serve as assessment evidence. Larger banks may run phases in parallel across business units; smaller banks should sequence them to manage capacity.

Phase 1 - Governance and Baseline Establishment

  • Activities: constitute cybersecurity governance (Board oversight, IT Strategy Committee, CISO office); draft the board-approved Cyber Security Policy distinct from the IT policy; define risk appetite and control ownership.
  • Deliverables: approved Cyber Security Policy; CISO charter and reporting line; governance RACI; policy suite (access, network, incident, vendor, DLP).

Phase 2 - Gap Assessment and Remediation Planning

  • Activities: perform a self-assessment against Annex 1; conduct discovery of assets and data flows; identify control gaps and quantify risk; prioritise remediation.
  • Deliverables: current-state gap assessment; risk register; prioritised remediation roadmap with owners and timelines; board-reported gap summary.

Phase 3 - Control Implementation

  • Activities: deploy technical controls (network segmentation, EDR, PAM, DLP, MFA, whitelisting, DMARC); harden configurations; establish patch/vulnerability cadence; embed ASLC into the SDLC.
  • Deliverables: implemented control configurations; hardening baselines; VAPT remediation evidence; secure-SDLC gates operational.

Phase 4 - Detection, Response and C-SOC Operationalisation

  • Activities: stand up or contract the C-SOC; onboard log sources to SIEM; author use cases and runbooks; finalise the CCMP and RBI incident-reporting procedure; conduct drills.
  • Deliverables: operational C-SOC with 24x7 coverage; SIEM use-case library; approved CCMP; incident-reporting workflow tested; tabletop/drill reports.

Phase 5 - Continuous Assurance and Improvement

  • Activities: institutionalise periodic self-assessment, VAPT, red-teaming, metrics reporting and management review; track threat intelligence; mature controls beyond baseline for higher-exposure areas.
  • Deliverables: periodic self-assessment submissions to RBI; KPI/KRI dashboards; continuous improvement backlog; independent assurance reports.

Maturity / capability model

The core 2016 framework does not itself define numeric maturity levels, but the RBI's proportionality philosophy - later formalised for UCBs as a four-level graded framework - maps naturally onto a capability maturity model. Assessors should rate each domain against the levels below to produce a defensible maturity heat-map and to justify where a bank must exceed the baseline.

LevelDescriptorCharacteristics
Level 1Initial / BaselineAd hoc or documentation-only controls; baseline partially met; reliance on reactive measures; minimal evidence of operation.
Level 2ManagedBaseline Annex 1 controls implemented and documented; controls operate but monitoring is inconsistent; self-assessment performed.
Level 3DefinedControls standardised across the estate; C-SOC operational; incident reporting timely; metrics reported to management regularly.
Level 4Quantitatively ControlledControls measured and continuously monitored; risk-based and adaptive controls; threat intelligence integrated; drills and red-teaming routine.
Level 5Optimising / AdaptivePre-emptive and predictive defence; automation and orchestration; continuous improvement; posture materially exceeds baseline commensurate with exposure.

Assessment and audit approach

  1. Confirm scope and applicability: identify the bank's tier, digital exposure, connected environments (ATM switch, SWIFT) and third-party landscape.
  2. Review governance: examine the board-approved Cyber Security Policy, CISO reporting line, committee minutes and risk appetite.
  3. Perform document review: obtain and assess the policy suite, CCMP, incident-reporting procedure and prior self-assessments against Annex 1.
  4. Conduct control walkthroughs: interview owners and observe control operation across each of the 18 domains.
  5. Perform technical validation: review configurations, run or review VAPT results, sample logs and alerts, and test detection use cases.
  6. Sample evidence for operating effectiveness: test a representative period for access recertification, patch SLAs, incident handling and log monitoring.
  7. Assess incident and crisis readiness: verify RBI reporting timeliness, review incident records and drill outcomes.
  8. Evaluate third-party assurance: examine contracts, audit reports and monitoring for outsourced and cloud services.
  9. Rate maturity per domain and identify gaps against the baseline and against the bank's required (exposure-adjusted) posture.
  10. Report findings with risk ratings, root causes and prioritised remediation; agree management action plans and retest dates.

Evidence request list

The following categorised evidence list expedites both self-assessment and supervisory examination. Assessors should request current versions and a sample of operating records for the review period.

  • Governance: board-approved Cyber Security Policy; CISO charter and org chart; IT Strategy Committee minutes; risk appetite statement.
  • Policies and standards: access control, network security, hardening baselines, patch/vulnerability, DLP, vendor risk, incident response, e-mail security policies.
  • Asset and data: IT asset inventory/CMDB; data classification matrix; data-flow diagrams; network architecture diagrams.
  • Access management: RBAC role definitions; PAM configuration and session logs; MFA enforcement; access recertification reports; JML records.
  • Vulnerability and change: VAPT reports and retests; patch deployment reports; vulnerability register with ageing; change management records.
  • Detection and monitoring: C-SOC charter and roster; SIEM log-source inventory; use-case library; alert/ticket samples; log retention and NTP configuration.
  • Incident and crisis: CCMP; RBI incident reports (Annex 2) with timestamps; RCA reports; drill/tabletop records.
  • Application security: secure coding standard; SAST/DAST/VAPT reports; SDLC change and environment segregation evidence; component/SBOM inventory.
  • Third-party: vendor due-diligence and risk-tiering; executed contracts with security schedules; vendor audit/SOC 2/ISO 27001 reports.
  • Awareness and testing: training completion records; phishing simulation results; customer awareness campaign evidence.
  • Prior assurance: previous self-assessments submitted to RBI; internal/external audit reports; prior examination observations and closure evidence.

Roles and responsibilities

RoleKey responsibilities
Board of DirectorsApprove the Cyber Security Policy; ensure adequate resourcing; hold management accountable for cyber resilience.
IT Strategy / IT Sub-Committee of the BoardOversee the cyber programme; review risk posture, incidents and self-assessments; challenge management.
Chief Information Security Officer (CISO)Own and drive implementation; report independently of the CIO; manage incident reporting to RBI and periodic self-assessment.
Chief Information Officer / Head of ITDeliver secure IT operations, patching, configuration and infrastructure controls.
C-SOC / Security Operations TeamOperate 24x7 monitoring, detection, triage and escalation; maintain SIEM use cases.
Incident Response TeamExecute the CCMP; contain, eradicate and recover; preserve forensic evidence; conduct post-incident reviews.
Risk Management / ComplianceIntegrate cyber risk into enterprise risk; track regulatory obligations and reporting timelines.
Internal AuditProvide independent assurance over control design and operating effectiveness; verify remediation.
Business / Application OwnersOwn application security requirements, access recertification and data classification for their systems.
Third-Party / Vendor ManagersConduct due diligence, embed security clauses, and monitor vendor control performance.
All StaffComply with policies, complete awareness training, and report suspected incidents promptly.

KPIs to track

  • Percentage of critical/security patches applied within SLA.
  • Mean time to detect (MTTD) and mean time to respond (MTTR) for security incidents.
  • Number and timeliness of cyber incidents reported to the RBI within the mandated window.
  • Percentage of log sources onboarded to the SIEM versus in-scope critical systems.
  • Open high/critical vulnerabilities and their ageing beyond SLA.
  • Percentage of privileged accounts under PAM with session recording.
  • Access recertification completion rate and orphan/dormant account count.
  • Phishing simulation click and report rates; staff awareness training completion.
  • VAPT findings closure rate and average time to remediate.
  • C-SOC alert triage backlog and false-positive ratio.
  • Third-party assessments completed versus due; high-risk vendors with expired assurance.
  • Percentage of Annex 1 domains at or above target maturity level.

Readiness checklist

  • Board-approved Cyber Security Policy exists and is distinct from the IT/IS policy.
  • CISO is appointed with an independent reporting line and defined charter.
  • A complete, classified IT asset inventory is maintained.
  • Network segmentation isolates critical systems; firewall rules are reviewed periodically.
  • Application whitelisting and endpoint privilege control are enforced.
  • Hardening baselines are applied and configuration compliance is scanned.
  • VAPT is performed at defined frequency and findings are remediated within SLA.
  • Patch management operates to severity-based SLAs across the estate.
  • RBAC, PAM and MFA govern access; recertification runs periodically.
  • Customer channels use multi-factor / adaptive authentication.
  • SPF, DKIM and DMARC protect the bank's e-mail domains.
  • EDR, anti-APT and DDoS mitigation are deployed and current.
  • An anti-phishing / brand-monitoring and takedown capability is in place.
  • DLP covers endpoint, network and storage with data classification.
  • A 24x7 C-SOC monitors a SIEM covering all critical log sources.
  • A board-aware CCMP and tested incident-response workflow exist.
  • Cyber incidents are reported to the RBI within the mandated window.
  • Vendor risk is assessed, contracted and monitored with right-to-audit.
  • Staff and customer awareness programmes run periodically.
  • Periodic self-assessment against Annex 1 is completed and submitted.

Common gaps against the 2026 Directions

  • No genuine 24x7 C-SOC: monitoring is business-hours only, or outsourced without the tiered L1/L2/L3 structure and SIEM correlation the Directions expect.
  • CISO not independent: the CISO reports into the Head of IT, carries business targets, or does not report to the Board quarterly.
  • No six-hour runbook: the entity cannot actually detect, triage and report a cyber incident to RBI on the DAKSH platform within six hours of detection.
  • VA/PT cadence not evidenced: vulnerability assessment is not run at least six-monthly and penetration testing at least annually on critical and internet-facing systems, or assessor independence cannot be shown.
  • Board ownership on paper only: the IT Strategy Committee does not meet at least quarterly, and the cyber strategy is not approved annually.
  • Posture still built to 2016/2023: policies and evidence reference the repealed framework and have not been re-mapped to the applicable 2026 Direction.
  • Logs collected but not monitored; privileged access without review; DR untested; third-party/outsourcing security unassessed.

The 2026 framework mapped to other standards

The 2026 Directions are deliberately consistent with international practice, so controls built for one standard largely satisfy the others. The mapping below is indicative and helps an entity reuse existing evidence.

2026 RBI control areaNIST CSF 2.0ISO/IEC 27001:2022 (Annex A)PCI DSS v4.0.1
Board role & IT governanceGOVERNA.5 Organisational controlsReq 12 (governance, policy)
Risk managementID.RA, GOVERNA.5.9, Clause 6 (risk)Req 12.3 (targeted risk analysis)
Baseline controls (config, network, endpoint)PROTECTA.8 Technological controlsReq 1, 2, 5, 6
Access control & MFAPR.AAA.5.15-A.5.18, A.8.2-A.8.5Req 7, 8
Cryptography & data protectionPR.DSA.8.24, A.5.33Req 3, 4
Cyber Security Operations Centre (C-SOC)DETECTA.8.15, A.8.16Req 10, 11.5
Incident response & DAKSH reportingRESPONDA.5.24-A.5.28Req 12.10
Business continuity & DRRECOVERA.5.29, A.5.30Req 12.10.1
Information Systems auditGOVERN (oversight)Clause 9 (performance evaluation)Req 11, 12 (assessment)

Frequently asked questions

How CyberSigma helps

Partner with CyberSigma for RBI 2026 cyber resilience
CyberSigma is CERT-In empanelled. We run the gap assessment against the applicable 2026 Direction for your entity type, stand up or review the 24x7 C-SOC and SIEM, help structure the independent CISO function and the Board’s IT Strategy Committee, perform the mandated VA/PT, build the six-hour DAKSH incident-reporting runbook, and deliver the independent Information Systems audit — with audit-ready evidence and retest to closure.
Free 1-minute check
Free Security Assessment
Get a complimentary, no-obligation assessment from CERT-In empanelled senior auditors.
Try it free →

Frequently asked questions

Is the 2016 RBI Cyber Security Framework still in force?
No. It was repealed on 31 July 2026 and replaced, together with the 2023 IT Governance Master Direction, by the entity-specific RBI (Cybersecurity, Technology: Risk, Resilience and Assurance Framework) Directions, 2026, which took effect immediately with no transition window.
Who must comply with the 2026 RBI cyber framework?
Commercial banks, small finance banks, payments banks, urban co-operative banks, all-India financial institutions, NBFCs and credit information companies — each under its own entity-specific Direction issued on 31 July 2026.
Does it require VAPT?
Yes — the 2026 Directions require vulnerability assessment at least every six months and penetration testing at least annually for critical and internet-facing systems, by independent, competent assessors (ideally CERT-In empanelled).
Free download

Download the RBI cyber-security audit checklist

The controls RBI inspections actually test, as a checklist you can work through before they arrive.

Open the asset page →
Download the RBI cyber-security audit checklist

Enter your work email and we’ll unlock the Excel + PDF instantly.

Need help with RBI Cyber Security Framework?

CERT-In empanelled, PCI QSA senior auditors can take you from reading about it to compliant — with a scoped, guided programme.

Verified facts

Drawn from the CyberSigma Compliance Registry (updated 5 October 2026). Every statement below is checked against the issuing body’s own publication, with the date it was last verified.

  • IT Governance, Risk, Controls and Assurance Practices Directions (2023) - repealed 2026Effective 1 April 2024

    The Reserve Bank of India (Information Technology Governance, Risk, Controls and Assurance Practices) Directions, 2023 (RBI/2023-24/107), effective 1 April 2024, was a Master Direction that consolidated earlier RBI IT-governance and cyber-risk instructions and required a board-level IT governance framework, an IT and information-security risk management framework and periodic information systems audits. IMPORTANT - NO LONGER IN FORCE: this Master Direction was repealed on 31 July 2026 and replaced, together with the 2016 Cyber Security Framework and other circulars, by the entity-specific RBI (Cybersecurity, Technology: Risk, Resilience and Assurance Framework) Directions, 2026. Regulated entities must now comply with the applicable 2026 Directions (see 'rbi-cyber-tech-risk-framework-2026').

  • Cybersecurity, Technology: Risk, Resilience and Assurance Framework Directions (2026)Effective 31 July 2026

    The RBI (Cybersecurity, Technology: Risk, Resilience and Assurance Framework) Directions, 2026 are the current, in-force cyber and technology-risk directions for RBI-regulated entities. Issued on 31 July 2026 (Commercial Banks version: RBI/DoS/2026-27/410, DoS.CO.CSITEG.4/31.01.015/2026-27) and effective immediately with no transition window, they repealed and consolidated the 2016 Cyber Security Framework in Banks, the November 2023 IT Governance, Risk, Controls and Assurance Practices Master Direction and around 626 other circulars into a single framework. RBI issued separate, entity-specific Directions under this common title for commercial banks, small finance banks, payments banks, urban co-operative banks, all-India financial institutions, NBFCs and credit information companies. Core requirements include board oversight and an IT Strategy Committee, an independent CISO (GM rank), baseline cybersecurity controls, a 24x7 Cyber Security Operations Centre (C-SOC) with SIEM, risk-based information systems audit, VA at least every six months and penetration testing at least annually for critical and internet-facing systems, and reporting of cyber incidents to the RBI on the DAKSH platform within six hours of detection.

  • Cyber Security Framework in Banks (2016) - repealed 2026Effective 2 June 2016

    The RBI circular Cyber Security Framework in Banks (RBI/2015-16/418, DBS.CO/CSITE/BC.11/33.01.001/2015-16), dated 2 June 2016, required scheduled commercial banks to put in place a board-approved cyber-security policy distinct from their IT or IS-security policy, a baseline cyber-security and resilience framework, continuous surveillance (for example through a Security Operations Centre), a Cyber Crisis Management Plan and incident reporting to the RBI. IMPORTANT - NO LONGER IN FORCE: this circular was repealed on 31 July 2026 and replaced, together with the November 2023 IT Governance Master Direction and other circulars, by the entity-specific RBI (Cybersecurity, Technology: Risk, Resilience and Assurance Framework) Directions, 2026 (see 'rbi-cyber-tech-risk-framework-2026').

  • Master Direction on Digital Payment Security Controls (2021)Effective 18 February 2021

    The RBI Master Direction on Digital Payment Security Controls (RBI/2020-21/74, DoS.CO.CSITE.SEC.No.1852/31.01.015/2020-21), dated 18 February 2021, sets out a robust governance structure and common minimum standards of security controls for digital payment products and services. It covers areas such as internet banking, mobile banking and card payments, along with customer protection and grievance redressal. It applies to Scheduled Commercial Banks (excluding Regional Rural Banks), Small Finance Banks, Payments Banks and credit-card-issuing NBFCs, and took effect within six months of being placed on the RBI website.

  • Storage of Payment System Data (data localisation)Effective 6 April 2018

    The RBI circular on Storage of Payment System Data (RBI/2017-18/153, DPSS.CO.OD No.2785/06.08.005/2017-2018), dated 6 April 2018, requires all system providers to ensure that the entire data relating to the payment systems they operate is stored in a system only in India. This includes the full end-to-end transaction details and any information collected, carried or processed as part of the payment message or instruction. Providers were given six months to comply and to submit a System Audit Report conducted by a CERT-In empanelled auditor. It applies to all Payment System Providers authorised under the Payment and Settlement Systems Act, 2007.

  • Regulation of Payment Aggregators Directions, 2025Effective 31 December 2025

    The Reserve Bank of India (Regulation of Payment Aggregators) Directions, 2025 (RBI/DPSS/2025-26/141), issued 15 September 2025 and in force from 31 December 2025, consolidate the earlier 2020, 2021 and 2023 payment-aggregator guidelines into a single framework covering online and face-to-face (proximity) payment aggregators. A non-bank entity carrying on payment-aggregator business must obtain RBI authorisation, and must have a minimum net worth of INR 15 crore at the time of application, rising to a minimum net worth of INR 25 crore by the end of the third financial year after authorisation, maintained thereafter. The directions also cover governance, KYC of merchants, escrow-account operation, security and reporting.

  • Payment system data storage in IndiaEffective 6 October 2018

    RBI circular DPSS.CO.OD No.2785/06.08.005/2017-2018 (6 April 2018) requires payment system providers to store the entire data relating to their payment systems only in India, with compliance within six months (by October 2018). End-to-end transaction data is covered.

    Circular number cited for retrieval via RBI's notification search; we deliberately avoid deep-linking RBI's session-bound URLs.

  • IT Governance Master Direction (repealed 2026)Effective 1 April 2024

    Master Direction on Information Technology Governance, Risk, Controls and Assurance Practices (RBI/DoS/2023-24/107) issued 7 November 2023; effective 1 April 2024. NO LONGER IN FORCE: repealed on 31 July 2026 and replaced, with the 2016 Cyber Security Framework and other circulars, by the entity-specific RBI (Cybersecurity, Technology: Risk, Resilience and Assurance Framework) Directions, 2026.

    Direction number cited for retrieval via RBI notification search; RBI deep links are session-bound.

  • IT Outsourcing Master DirectionEffective 1 October 2023

    Master Direction on Outsourcing of Information Technology Services (RBI/2023-24/102) issued 10 April 2023; effective 1 October 2023. Governs material IT outsourcing by regulated entities, including vendor risk, audit rights and concentration risk.

    Direction number cited for retrieval via RBI notification search.

  • Digital Payment Security Controls Master DirectionEffective 18 February 2021

    Issued 18 February 2021: minimum security standards for digital payment channels — internet banking, mobile payments and card payments — binding scheduled commercial banks, small finance banks, payments banks and card-issuing NBFCs.

    Direction cited by title and date for retrieval via RBI notification search.

  • Cyber Security Framework in BanksEffective 2 June 2016

    RBI’s Cyber Security Framework in Banks (2 June 2016) requires scheduled commercial banks to report cyber incidents to RBI within 2 to 6 hours of detection, alongside board-approved cyber security policy, SOC capability and cyber crisis management plans.

Ask about RBI

Answered from CyberSigma’s verified compliance registry — with sources. Not legal advice.