This guide is general information, not legal advice. Confirm how the rules apply to you with your compliance team or counsel.
The short answer: if you are an NBFC in the Middle Layer or above, RBI expects a board-approved IT outsourcing policy, a current inventory of outsourced IT services with each one assessed for materiality, risk-based due diligence before and during the relationship, written contracts that give you and RBI full access and audit rights, a tested exit plan and BCP for every material arrangement, incident reporting fast enough to tell RBI within six hours, and periodic review reported to senior management and the Board. You stay responsible for everything you outsource.
Which RBI directions on IT outsourcing apply now
Three documents matter, and policy manuals often cite the older ones.
- Master Direction on Outsourcing of Information Technology Services (10 April 2023, effective 1 October 2023). This is what most people mean by the RBI master direction on outsourcing of IT services. It set the board policy, materiality, due diligence, contract, cloud, offshore and exit requirements discussed below.
- Reserve Bank of India (Non-Banking Financial Companies – Managing Risks in Outsourcing) Directions, 2025 (28 November 2025). For NBFCs this consolidated the 2023 IT outsourcing Master Direction with the financial services outsourcing instructions. Chapter IV covers IT outsourcing and applies to the Middle Layer and above. It is largely a consolidation, but it makes due diligence explicitly ongoing, brings material sub-contractors inside the definition of service provider, and asks for structured audits of providers. Existing agreements had to comply at renewal or by 10 April 2026, whichever was earlier.
- Master Direction on Information Technology Governance, Risk, Controls and Assurance Practices (7 November 2023, effective 1 April 2024), and its successor for NBFCs, the RBI (Non-Banking Financial Companies) Cybersecurity, Technology Risk, Resilience and Assurance Framework Directions, 2026, issued on 31 July 2026. These set the governance around technology risk: the IT Strategy Committee, the CISO, IS audit, BCP and DR. We cover them in the IT governance section.
If your IT outsourcing policy, vendor contracts or board notes still refer only to the April 2023 Master Direction, update the references at the next policy review. The substance has carried forward, so the work below still holds.
Who the RBI IT outsourcing guidelines for NBFCs cover
The IT outsourcing chapter applies to NBFCs in the Middle, Upper and Top Layers under RBI's scale-based regulation. It covers IT services provided on a continuing basis by a third party, including group companies and including arrangements a provider sub-contracts. Typical examples are cloud hosting, a loan management system run as SaaS, managed security services, data centre operations, application development and support, and data analytics.
Some things sit outside the definition, such as one-off consulting, purchase of off-the-shelf hardware, and services like telecom or payment network access that are not specific to you. Record the reasoning when you exclude a contract; an inspector will ask why the ticketing tool that holds customer complaints is not on your list.
1. Board-approved IT outsourcing policy
The Board approves the policy and stays accountable. Responsibility for IT strategy, governance and risk decisions cannot be outsourced. The policy should set out the roles of the Board and senior management, the criteria for selecting activities and providers, how materiality is decided, the delegation of authority, how arrangements are monitored and reviewed, the approach to cloud and offshore outsourcing, and how you exit.
Owner: Chief Compliance Officer or CRO drafts; the Board approves.
Evidence to keep: the approved policy with version and date, the board resolution or minutes, and the record of the last annual review.
2. Material outsourcing and the inventory of services
An arrangement is material when a disruption would significantly affect your operations, or when unauthorised access, loss or theft of customer data at the provider would significantly affect your customers. Look at the impact on operations, finances, reputation and customers, and at how dependent you are on that provider.
- Maintain an inventory of every outsourced IT service, including the key entities in each provider's supply chain.
- Record the materiality assessment and its date against each entry.
- Flag intra-group arrangements and confirm they are on arm's length terms.
- Under the 2025 Directions, identify material sub-contractors. For a SaaS lending platform, the cloud provider underneath it is usually one.
Owner: vendor management or IT risk.
Evidence to keep: the inventory, materiality assessments with reviewer and date, and sub-contractor lists from providers.
Track each direction with its clause, owner and evidence
BeAuditReady's obligation register records the official source, clause reference, applicability by entity type, effective date, frequency, owner and linked controls for each RBI requirement. Vendors and outsourcing arrangements sit in their own register with contracts, notice dates and scheduled reviews.
3. Due diligence before and during the relationship
Due diligence should be risk-based and, under the 2025 Directions, ongoing. Before signing, assess the provider's financial soundness, track record and reputation, technical and security capability, business continuity arrangements, ability to meet your SLAs, conflicts of interest, and the legal environment it operates in. After signing, keep watching uptime, SLA performance, incident handling and any decline in the provider's financial or operational strength.
Owner: procurement with IT risk and the CISO.
Evidence to keep: the due diligence file per provider, security questionnaires and their certifications (ISO 27001 certificate, SOC 2 report), and periodic performance reviews.
4. Contract clauses RBI expects
Every outsourcing arrangement needs a written, legally vetted agreement. For material arrangements, check that it covers:
- scope of services and measurable service levels;
- confidentiality, security of customer data and segregation of your data from other clients';
- your right to audit the provider, through your own team, an external auditor or a pooled audit with other regulated entities;
- RBI's right to access and inspect the provider's and sub-contractors' books, records, systems and premises, without conditions that depend on the provider's consent;
- prior approval for sub-contracting, with your obligations flowing down to sub-contractors;
- incident reporting timelines that let you meet RBI's six-hour window;
- business continuity and disaster recovery obligations, with your right to test them;
- termination rights, exit and transition assistance, and return or destruction of data;
- governing law and dispute resolution that do not obstruct supervision.
A practical test: give your top ten contracts to someone in compliance with this list and a highlighter. Missing RBI access clauses and vague incident timelines are the gaps that come up most often.
Owner: legal, with compliance sign-off.
Evidence to keep: executed contracts, a clause-by-clause review sheet per material contract, and addenda signed to close gaps.
5. Monitoring, audit and periodic review
Review material arrangements at least once a year and whenever something significant changes. Audit material providers against the contract and your framework. You may rely on pooled audits or recognised third-party certifications, but you remain responsible for the result. Report findings to senior management, set remediation timelines, and escalate material or adverse developments to the Board.
Owner: vendor management, internal audit.
Evidence to keep: annual review reports, provider audit reports, findings with remediation status, and board or committee papers.
6. Concentration risk and exit strategy
If your loan system, your data warehouse and your collections platform all run on one cloud region from one provider, that is concentration risk, and RBI expects you to assess it. Record dependencies in the inventory so you can see them.
For each material arrangement, write an exit plan: the trigger events, alternative providers or how you would bring the service in-house, how data is returned and verified, how long the migration would take, and who leads it. Test the parts you can, such as a full data export, rather than leaving the plan as a document.
Owner: CTO or Head of IT with the CRO.
Evidence to keep: concentration analysis, exit plans with approval dates, and records of exit tests or data export trials.
7. BCP, DR and incident reporting
Your BCP must cover outsourced services, and the provider's own BCP must be adequate and tested. Ask for test results, not policy documents. Under the 2026 cyber security Directions, Middle Layer and above NBFCs run DR drills for critical systems at least every six months. Agree an incident path with each provider so that you can report cyber incidents to RBI within six hours of detection, and remember that CERT-In expects its own report within six hours too.
Owner: Head of IT, CISO.
Evidence to keep: provider BCP and DR test reports, your own drill records, incident logs with detection and reporting timestamps.
8. Cloud and offshore outsourcing
Cloud
Cloud is outsourcing. Have a documented approach to cloud adoption covering which workloads may move, the shared responsibility split, where data is stored and processed, encryption and key management, identity and access, logging, segregation in a multi-tenant setup, audit rights and exit. If you also outsource your security operations centre, the Directions add requirements for that arrangement.
Offshore
Where a provider processes your data outside India, choose jurisdictions whose laws do not stop RBI from supervising. Keep records accessible in India, make sure foreign authorities cannot reach your customer data merely because it is processed there, and set governing law accordingly. Check this against the data localisation rules that apply to payment data if you handle it.
Owner: CISO, legal.
Evidence to keep: cloud adoption approval, data location records, shared responsibility matrices, and offshore legal assessments.
9. Customer grievances on outsourced services
Outsourcing does not move your obligations to customers. Complaints about an outsourced service, such as a failed e-mandate or a mobile app outage at your provider, go through your grievance redressal mechanism and count toward your timelines. Make sure the provider's support team routes complaints to you and that your complaint data identifies which provider was involved.
Owner: Principal Nodal Officer or grievance team.
Evidence to keep: grievance logs tagged by provider, root-cause notes, and escalation records.
NBFC IT governance compliance: the structure around outsourcing
Outsourcing reviews only work if the governance above them works. The 2023 IT governance Master Direction set this structure, and the 2026 cyber security Directions carry it forward with requirements tiered by layer and asset size. For Middle Layer and above NBFCs, expect:
- an IT Strategy Committee of the Board, chaired by an independent director with substantial IT experience, meeting at least quarterly;
- an IT Steering Committee of senior management from IT and business, also meeting quarterly;
- a Head of IT and a CISO who does not report to the Head of IT and has no business targets;
- a board-approved IT and cyber security strategy and policies, reviewed at least once a year;
- IS audit overseen by the Audit Committee of the Board, with a risk-based plan and findings tracked to closure;
- BCP and DR with tested recovery objectives approved by the IT Strategy Committee.
Base Layer NBFCs have lighter, size-based requirements. Read the chapter that applies to your layer and asset size rather than assuming the Middle Layer rules.
RBI IT outsourcing evidence checklist
| Requirement | Owner | Evidence to keep |
|---|---|---|
| IT outsourcing policy | CCO, Board | Approved policy, minutes, annual review |
| Inventory and materiality | Vendor management | Inventory, assessments, sub-contractor lists |
| Due diligence | Procurement, CISO | Due diligence files, certifications, reviews |
| Contracts | Legal, compliance | Executed contracts, clause review sheets |
| Audit and periodic review | Internal audit | Review reports, audit reports, findings |
| Concentration and exit | CTO, CRO | Concentration analysis, exit plans, tests |
| BCP, DR and incidents | Head of IT, CISO | Drill records, incident timestamps |
| Cloud and offshore | CISO, legal | Cloud approval, data location, legal opinions |
| Grievances | Nodal officer | Complaint logs tagged by provider |
| IT governance | ITSC, ACB | Committee minutes, IS audit reports |
Keep each piece of evidence with a date, an owner and the period it covers. When the inspection letter arrives with a list of thirty data requests and a two-week deadline, the difference between a calm fortnight and a frantic one is whether those three fields exist. For more on how RBI obligations are tracked, see our RBI and NBFC framework page. If you also handle personal data at scale, the DPDP Act compliance checklist covers the overlapping breach and vendor obligations.
Sources: RBI Master Direction on Outsourcing of Information Technology Services, 10 April 2023; RBI Master Direction on Information Technology Governance, Risk, Controls and Assurance Practices, 7 November 2023; Reserve Bank of India (Non-Banking Financial Companies – Managing Risks in Outsourcing) Directions, 2025, 28 November 2025; RBI (Non-Banking Financial Companies) Cybersecurity, Technology Risk, Resilience and Assurance Framework Directions, 2026, 31 July 2026.