Banks and larger NBFCs in India answer to a layered set of Reserve Bank of India directions on IT governance, cyber security and outsourcing, and the pieces were reorganised in November 2025. The core instrument is the Reserve Bank of India (Information Technology Governance, Risk, Controls and Assurance Practices) Directions, 2023, in force since 1 April 2024, which sits on top of the 2016 Cyber Security Framework in Banks and alongside the November 2025 entity-specific directions on managing risks in outsourcing. This guide summarises who is covered, the main obligations, the current status of each instrument and what the directions mean for service accounts, privileged access and AI agents. It is written for CISOs, IT risk teams, internal auditors and technology providers serving Indian regulated entities. Status line: checked against rbi.org.in on 27 October 2026. This page is not legal advice.
Key takeaways
- One master direction anchors IT and cyber governance. The 2023 IT Governance Directions (RBI/2023-24/107) apply from 1 April 2024 to commercial banks, small finance and payments banks, NBFCs in the Top, Upper and Middle Layers, credit information companies and the All India Financial Institutions.
- Governance roles are prescribed. A Board-level IT Strategy Committee, an IT Steering Committee, a Head of IT and a CISO who does not report to the Head of IT and carries no business targets.
- Technical floors are explicit. Vulnerability assessment every six months and penetration testing every 12 months for critical and DMZ systems, half-yearly DR drills, MFA for privileged users of critical systems, and audit trails good enough for forensics.
- Outsourcing was rebuilt in November 2025. Entity-specific "Managing Risks in Outsourcing" directions dated 28 November 2025 cover IT and cloud outsourcing, with existing IT contracts to comply at renewal or by 10 April 2026, and service-provider cyber incidents reported so the bank can tell RBI within six hours.
- Non-human identities are in scope by implication. Access by business need, logging of elevated access and IAM with MFA for cloud cover service accounts, API credentials and AI agents just as much as staff, even where the text does not name them.
Scope: who and what is covered
| Instrument | Applies to | Status as checked |
|---|---|---|
| Master Direction on IT Governance, Risk, Controls and Assurance Practices, 7 November 2023 (RBI/2023-24/107, DoS.CO.CSITEG/SEC.7/31.01.015/2023-24) | Scheduled commercial banks (excluding regional rural banks), small finance banks, payments banks, NBFCs in Top, Upper and Middle Layers, credit information companies, EXIM Bank, NABARD, NaBFID, NHB and SIDBI. Foreign bank branches: comply or explain. Not local area banks or NBFC Core Investment Companies | In force from 1 April 2024; listed on RBI's Master Directions page with no withdrawal shown |
| Cyber Security Framework in Banks, 2 June 2016 (RBI/2015-16/418, DBS.CO/CSITE/BC.11/33.01.001/2015-16) | Banks | Not in the 2023 repeal list (the 2017 CISO circular and others were repealed); treat as background expectation and confirm on RBI's site |
| Managing Risks in Outsourcing Directions, 2025, 28 November 2025 (separate directions for commercial banks, small finance banks, payments banks, local area banks, urban co-operative banks) | The named bank type, Chapter IV covering material IT outsourcing including cloud | Immediate effect; existing IT outsourcing agreements comply at renewal or by 10 April 2026, whichever is earlier |
| CERT-In Directions | All service providers and body corporates in India, including regulated entities | Separate regime; the RBI direction requires proactive notification to CERT-In and RBI. See the CERT-In Directions 2022 Guide |
The 2023 direction is issued under section 35A of the Banking Regulation Act 1949, section 45L of the Reserve Bank of India Act 1934 and section 11 of the Credit Information Companies (Regulation) Act 2005. It repealed twelve older circulars, including the 1998 computer and telecommunication risk circular, the 2004 information system audit circular, BCP, DR and VAPT circulars from 2006 to 2013, the 2014 security incident tracking platform circular, the 2017 CISO circular and, for Top, Upper and Middle Layer NBFCs only, the 2017 IT Framework for the NBFC Sector. Base Layer NBFCs remain under that 2017 framework.
Key obligations
Governance
- Board: approves strategies and policies on IT, information assets, business continuity, information security and cyber security, including incident response and cyber crisis management, and reviews them at least annually (section 5).
- IT Strategy Committee: Board-level, at least three directors, chaired by an independent director with substantial IT expertise, meeting at least quarterly.
- IT Steering Committee: senior management from IT and business, assisting the ITSC on strategic IT planning and BCP and DR oversight, meeting at least quarterly (section 7).
- Head of IT: a sufficiently senior, technically competent official who, as first line of defence, manages IT controls and IT risk (section 8).
- CISO: preferably General Manager or equivalent, no direct reporting line to the Head of IT, no business targets, runs the SOC through the CISO's office and presents a quarterly review of cyber risk and preparedness to the Board or its committee (section 24). An Information Security Committee under ITSC oversight is headed from risk management.
Controls the direction names
| Area | What the 2023 direction requires | Section |
|---|---|---|
| IT service management | Service management framework covering DR sites; CIA classification of information assets by criticality; avoid unsupported hardware and software with a technology refresh plan | 9 |
| Patch and change | Impact assessment, timely and approved patching, approved changes, recovery from failed changes | 13 |
| Data migration | Documented policy preserving integrity and completeness, sign-offs and audit trails | 14 |
| Audit logs | Logging for applications that touch critical or sensitive data; trails usable as forensic evidence and for non-repudiation; regular monitoring | 15 |
| Cryptography | Strong key lengths, algorithms, cipher suites and protocols to internationally accepted, non-deprecated standards | 16 |
| Straight through processing | No manual intervention in critical application data transfers | 17 |
| Access control | Access only on valid business need under ITSC-approved standards; elevated access closely supervised, logged and reviewed; MFA for privileged users of critical systems and critical activities | 19 |
| Teleworking | MFA for enterprise access to critical systems | 20(b) |
| BCP and DR | Half-yearly DR drills for critical systems, switchover covering at least a full working day, minimal RTO and near-zero RPO for critical systems, identical DC and DR configuration | Chapter V, 21 |
| Vulnerability testing | VA at least every six months and PT at least every 12 months for critical and customer-facing DMZ systems, by trained independent testers; fix vulnerabilities within set time frames | 26 |
| Incident management | Classification, containment, recovery, root cause; roles including outsourced staff; escalation to Board, management and customers; proactive notification to CERT-In and RBI; drills | 27 |
| IS audit | Audit Committee of the Board oversight, a separate IS audit function, risk-based planning, periodicity set in a policy reviewed annually; continuous auditing encouraged | Chapter VI, 30 |
Outsourcing and cloud (November 2025 directions)
Using the commercial banks direction as the example, Chapter IV (paragraphs 53 to 92) covers material IT outsourcing, including cloud computing. It requires a Board-approved IT outsourcing policy, defines materiality by operational disruption and customer impact from unauthorised access to customer data, requires concentration risk assessment, audit rights for the bank, its auditors and RBI over providers and subcontractors, data storage only in India where existing rules require it, exit strategies, and cloud-specific controls including identity and access management with MFA. Service providers must report cyber incidents to the bank without undue delay so the bank can report to RBI within six hours of the provider's detection (paragraph 56). External VA and PT and security consultancy are carved out of some requirements. See the Cloud Concentration Risk and Exit Strategy Guide.
Timeline and current status
| Date | Event |
|---|---|
| 2 June 2016 | Cyber Security Framework in Banks issued: Board-approved cyber security policy separate from IT policy, cyber crisis management plan, SOC, Annex 1 baseline controls, reporting of unusual incidents including unsuccessful attempts in the Annex 3 format, gap assessment by 31 July 2016 |
| 8 June 2017 | IT Framework for the NBFC Sector issued |
| 7 November 2023 | IT Governance, Risk, Controls and Assurance Practices Directions issued |
| 31 March 2024 | Repealed circulars cease to apply |
| 1 April 2024 | 2023 directions come into effect |
| 28 November 2025 | Entity-specific Managing Risks in Outsourcing Directions issued, repealing earlier outsourcing instructions for each bank type |
| 10 April 2026 | Latest date for existing IT outsourcing agreements to comply (or at renewal if earlier) |
The November 2025 exercise issued many consolidated directions by entity type. On 27 October 2026 the 2023 IT Governance Directions were still listed on RBI's Master Directions page with no withdrawal note, and the commercial banks governance direction of the same date does not mention them. Because RBI consolidates frequently, check the Master Directions list for your entity type before relying on paragraph numbers.
Enforcement and penalties
RBI enforces the directions through its supervisory process: on-site inspection, off-site monitoring by its cyber security and IT examination function, and supervisory action. The directions themselves do not set penalty amounts; they draw force from the statutes they are issued under, and penalties for contravening directions are set in those Acts (for banks, the Banking Regulation Act 1949; for NBFCs, the RBI Act 1934). RBI may also impose monetary penalties and other supervisory measures, so check its press releases for current enforcement practice. We could not read the statute penalty sections on an official site for this edition, so check amounts in the current Acts.
- Audit trail: the outsourcing directions give RBI direct access to service provider data and premises, so third parties are examined too.
- Incident reporting failures: late or missing reports to RBI and CERT-In are easy for supervisors to evidence and frequently cited.
- Internal penal measures: section 24(a) requires the Information Security Policy to set penal measures for staff non-compliance with policies.
What it means for AI agents and non-human identities
None of the RBI instruments uses the term non-human identity, but their access control and logging rules apply to any identity that touches critical systems. In Indian banks that includes core banking batch accounts, UPI and payment switch integrations, API gateway credentials for fintech partners, RPA bots and, increasingly, AI agents in customer service and operations.
- Business need applies to machines: section 19(a) access standards should cover service accounts and API clients with a named owner and purpose for each. See the Service Account Security Guide.
- Privileged machine access: many service accounts hold privileged access to critical systems; supervision and logging under 19(b) need vaulting and session or command logging, since MFA under 19(c) does not fit non-interactive accounts. Document the compensating control. See the Privileged Access Management Guide.
- Straight through processing: section 17's ban on manual intervention increases reliance on machine-to-machine credentials, which must be protected with strong cryptography under section 16.
- Cloud IAM: the outsourcing directions' cloud controls require identity and access management with MFA; workload identities and keys in cloud tenants need the same inventory and rotation.
- AI agents: an AI agent acting on customer or internal systems is a new privileged identity. Classify it under section 9, give it its own credentials, scope it to the business need and log its actions to the forensic standard of section 15. See the Agent Identity and Access Guide.
- Vendor-held credentials: credentials issued to IT service providers and fintech partners fall under the outsourcing directions' confidentiality and audit clauses; include them in exit plans.
Compliance steps
- Confirm applicability: identify your entity type and NBFC layer, then list the current RBI directions that apply from the Master Directions page, including the November 2025 outsourcing and digital banking directions.
- Build a requirements register: one row per paragraph of the 2023 direction and the outsourcing direction, with owner, evidence and test frequency.
- Fix the governance structure: verify ITSC composition and chair, quarterly meetings, CISO reporting lines and absence of business targets, and the quarterly CISO report.
- Classify assets and identities: complete CIA classification of information assets and an inventory of human and non-human identities with access to critical systems.
- Close access control gaps: MFA for privileged users of critical systems, vaulting and logging for privileged service accounts, periodic access review as good practice even though the direction does not fix a cycle.
- Set testing calendars: six-monthly VA and 12-monthly PT for critical and DMZ systems, half-yearly DR drills with a full working day on DR, and remediation time frames.
- Rework incident reporting: run a timed drill from detection to RBI and CERT-In notification, including a provider-detected incident to test the six-hour path.
- Remediate outsourcing contracts: map every material IT and cloud contract to Chapter IV and amend at renewal, with a 10 April 2026 backstop for existing agreements.
- Prepare for inspection: keep evidence packs for each requirement, and run an internal IS audit before supervisory visits.
Decision guidance
- Large banks: integrate the register into GRC tooling and test continuously; the challenge is consistency across many subsidiaries and vendors.
- Middle Layer NBFCs and small finance banks: prioritise the CISO role, MFA for privileged users, the testing calendar and outsourcing contracts, which supervisors check first.
- Technology providers: expect banks to push the six-hour incident path, audit rights and data localisation into your contracts.
Detection, measurement and framework mapping
- Critical systems with current VA and PT: percentage within six and 12 months.
- Privileged accounts covered by MFA or vaulting: human and non-human, target 100 percent for critical systems.
- Incident notification time: median detection to RBI report, against six hours for provider incidents.
- DR drill results: achieved RTO and RPO against targets for each critical system.
- Unsupported assets: count past end of support, from the section 9 refresh plan.
- Outsourcing contracts remediated: share of material IT contracts meeting Chapter IV.
| RBI requirement | NIST CSF 2.0 | NIST SP 800-53 Rev 5 |
|---|---|---|
| Board, ITSC and CISO roles (5, 7, 24) | GV.OC-03, GV.RR-02 | PM-9 Risk Management Strategy |
| Access control and privileged MFA (19) | PR.AA-05 | AC-2 Account Management, AC-6 Least Privilege, IA-2 Identification and Authentication |
| Audit logs (15) | DE.CM-09 | AU-2 Event Logging, AU-12 Audit Record Generation |
| Patch and change (13) | PR.PS-02 | SI-2 Flaw Remediation, CM-3 Configuration Change Control |
| Cryptography (16) | PR.DS-02 | SC-13 Cryptographic Protection |
| VA and PT (26) | ID.RA-01 | RA-5 Vulnerability Monitoring and Scanning, CA-8 Penetration Testing |
| BCP and DR (Chapter V) | RC.RP-01 | CP-2 Contingency Plan, CP-4 Contingency Plan Testing |
| Incident management (27) | RS.MA-01 | IR-4 Incident Handling, IR-6 Incident Reporting, IR-8 Incident Response Plan |
| IT outsourcing (2025 directions) | GV.SC-05, GV.SC-07 | SA-9 External System Services |
Common failure patterns
- CISO under the CIO: a reporting line to the Head of IT, or business targets in the CISO's scorecard, both contrary to section 24.
- Testing the wrong scope: annual PT on internet banking only, missing other critical and DMZ systems and the six-monthly VA cycle.
- Service accounts outside PAM: privileged batch and integration accounts with static passwords, no owner and no logging, while human admins are fully controlled.
- DR on paper: drills that switch only a subset of services, or DR configurations that have drifted from production.
- Six-hour reporting not contracted: provider contracts without incident timelines, so the bank learns too late to report.
Practitioner checklist
- Current list of RBI directions applicable to your entity type, checked on rbi.org.in.
- Requirements register covering the 2023 IT Governance Directions and the 2025 outsourcing direction.
- ITSC, IT Steering Committee and CISO structure meets composition, frequency and reporting rules.
- CIA classification of assets and inventory of human and non-human identities on critical systems.
- MFA for privileged users of critical systems and vaulting with logging for privileged service accounts.
- VA every six months and PT every 12 months for critical and DMZ systems, tracked to closure.
- Half-yearly DR drills with a full working day on DR and recorded RTO and RPO.
- Timed incident notification path to RBI and CERT-In, including provider incidents.
- Material IT and cloud outsourcing contracts updated for audit rights, localisation, exit and incident timelines.
Standards and references
- Reserve Bank of India: Master Direction on Information Technology Governance, Risk, Controls and Assurance Practices
- Reserve Bank of India: Master Directions listing for IT Governance Directions, 2023
- Reserve Bank of India: Cyber Security Framework in Banks
- Reserve Bank of India: Commercial Banks, Managing Risks in Outsourcing Directions, 2025
- Reserve Bank of India: Master Directions
- Reserve Bank of India: Commercial Banks, Governance Directions, 2025
Related NHI Mgmt Group resources: Financial Services Cyber Regulation Map · CERT-In Directions 2022 Guide · India DPDP Act Guide · Service Account Security Guide. This guide summarises the Reserve Bank of India's IT governance, cyber security and outsourcing directions as at 27 October 2026 and is not legal advice.