RBI’s IT outsourcing norms made your MSP contract a compliance document. Read it again

Arun Valecha, founder of AV Services
By Arun Valecha
28 Oct 2026
Brass key lying across a signed IT services agreement with numbered tabs along the edge

Disclosure first: I run a managed services firm. I earn money when companies outsource their infrastructure. Read everything below knowing that, and discount accordingly.

In April 2023, RBI issued its Master Direction on Outsourcing of Information Technology Services. In November 2025 it repealed that direction and replaced it with entity-specific Managing Risks in Outsourcing Directions. I checked the clauses below against the commercial banks version, and I use “the direction” for the current text. If you’re a bank, an NBFC or another regulated entity, your agreement with an IT vendor for material services is audit material. The deadline to bring existing agreements into line was 10 April 2026.

And if you’re none of those things, keep reading anyway. RBI’s template is what auditors and large customers across India now borrow when they assess anyone’s vendor arrangements. I’ve watched it happen in due diligence questionnaires from companies nowhere near RBI’s jurisdiction.

The principle that changes everything downstream

The direction’s central idea fits in one sentence: outsourcing an activity doesn’t outsource the responsibility for it. The regulated entity stays fully answerable to RBI for whatever its vendor does or fails to do.

That sounds obvious. Its consequence is what bites. If the regulator holds you responsible for your vendor’s conduct, your only instrument of control is the contract. So the direction reaches into the contract itself and lists what it must contain.

Most MSP agreements I’ve read, including ones I inherited from previous vendors, would fail that list.

7 clauses to check in your current agreement

Pull your contract and check for these. I’m compressing regulatory language into plain terms.

1. Audit and inspection rights. You, your auditors, and RBI must be able to audit the vendor’s relevant operations. If your contract is silent on this, it’s non-compliant on its face.

2. Data location and access. Where is your data stored and processed, and can you reach your own data and logs without the vendor’s permission? Some contracts don’t even name a country.

3. Exit and transition. Notice periods, the format in which your data comes back, and the vendor’s obligation to assist migration. Ask the blunt version: if we fired this vendor today, in what format do we receive our own database, and who pays for the handover?

4. Subcontracting control. The vendor can’t quietly pass your workload to a fourth party you’ve never heard of. You get visibility and a say: under the bank directions, the vendor needs your prior consent before it engages any subcontractor.

5. Incident reporting timelines. Your vendor must tell you about incidents fast enough for you to meet your own obligations, including CERT-In’s 6-hour reporting clock. A vendor who reports breaches “in due course” makes you non-compliant by proxy.

6. Business continuity, tested. A DR plan on paper counts for nothing. The direction expects the vendor to test its continuity and recovery plan periodically, and you’re accountable for making sure it does.

7. Compliance with RBI directions, and an orderly exit. The vendor must be bound to follow RBI’s directions on the outsourced activity, and your contract needs a termination clause that lets you unwind the arrangement in an orderly way, without a penalty clause bankrupting you on the way out.

If 3 or more of these are missing from your agreement, put redrafting on the agenda before your next renewal.

The clause vendors hate, and why I’ve switched sides on it

Root access ownership.

I’ve taken over servers where the previous vendor held every password and the client held none. No documentation, no admin credentials, no idea which of their own domains pointed where. The client wasn’t a customer at that point. They were a hostage with an invoice.

Under these norms, that arrangement is indefensible for a regulated entity, and I’d argue it’s indefensible for everyone else too. The client should own the root credentials and the documentation. The vendor works through delegated, logged access.

Plenty of small MSP relationships in India run the other way around, and some vendors defend it as operational convenience. It’s a retention strategy wearing an operations costume. A vendor confident in their service doesn’t need to hold your keys to keep your business.

Yes, I’m aware I’m arguing against my own industry’s leverage. That’s rather the point of the direction.

Where the direction is weakest

Fair criticism deserves airtime. Enforcement depth is the open question: RBI examines large banks closely, and whether the MSP contract of a smaller regulated entity ever gets read by a supervisor is doubtful. Concentration risk is a real gap: when most of the industry sits on a handful of large cloud providers, a contract clause won’t fix it.

And paper compliance is cheap. A contract can contain all 7 clauses while the vendor still holds every password. The direction tests documents; behaviour only gets tested at audit time or during a failure, whichever comes first.

What to actually do

If you’re a regulated entity: contract review this quarter, gap list against the direction, redraft at renewal or sooner if the gaps are material.

If you’re any other business: borrow the 7 clauses anyway. They cost nothing to include and they’re the difference between changing vendors and escaping one.

If you’re a vendor: hand your clients their root credentials and documentation before they ask. The ones worth keeping will stay.


Arun Valecha is the founder of AV Services, a Linux infrastructure services firm in Mumbai.

←I love using AI to do the work I hate doingSSH terminal color per server: a bash wrapper for when the hostname isn't enough→