RBI Cybersecurity Framework for NBFCs: IT Evidence Auditors Want

The ₹18 lakh lesson from a 4-hour outage
In March 2025, a Bangalore-based NBFC with 140 staff and ₹600 crore in assets under management lost four hours of loan-disbursement processing. The trigger: a ransomware binary that got in through an unpatched VPN appliance — a FortiGate 60F running firmware from 2022, two major releases behind. The attacker encrypted the file server and the local backup NAS. The NBFC had backups. They were on the same Synology DS920+ that got encrypted.
Recovery took 11 days and cost ₹18.4 lakh: ₹6.2 lakh for an emergency incident-response retainer, ₹4.5 lakh in lost disbursement interest, ₹3.1 lakh to rebuild two servers and a domain controller, and ₹4.6 lakh in overtime and temporary staff. The RBI supervisory visit three months later asked for one document: the incident report filed under the 2-hour and 6-hour reporting timelines. It did not exist. The NBFC got a supervisory observation that took another ₹9 lakh and six months to close.
This is the operating reality behind the RBI Cybersecurity Framework for NBFCs. The framework is not a document you download and file. It is a set of controls that generate evidence, and auditors — RBI inspectors, statutory auditors, and increasingly CERT-In empanelled auditors — read that evidence line by line. Where the evidence is missing, the assumption is the control is missing. Sometimes that assumption is wrong, but you carry the cost of proving it either way.
This article is for the IT manager, ops head, or promoter at an NBFC with 20 to 500 staff who is being asked to “get RBI-compliant” and needs to know what that means on the ground. The SynergyScape client engagements we run in this space are mostly mid-sized NBFCs in Bangalore, Chennai, and Hyderabad, and the pattern of gaps is remarkably consistent.
What the RBI framework actually requires from IT
The RBI's cyber security framework for NBFCs sits on three layers.
First, the Master Direction on Information Technology Governance, Risk, Controls and Assurance Practices (issued November 2023, effective April 2024 for larger NBFCs and phased for smaller ones). This is the parent document. It mandates an IT Strategy Committee, a Board-level IT oversight structure, a documented IT governance framework, and annual assurance.
Second, the Cyber Security Framework circular (the one originally issued in 2016 and revised since), which lays out the control expectations: baseline security, identity management, patch management, incident response, vendor risk, and board reporting.
Third, sectoral and cross-sectoral circulars that touch IT: the Digital Lending Guidelines (2022), the Storage of Payment System Data circular (2018), CERT-In directions (2022), and the DPDP Act 2023 obligations that overlap heavily with the RBI framework but carry their own penalties.
The practical translation for a 100-person NBFC is roughly 40 to 60 controls across 11 domains. You will not implement all of them in a quarter. You will be asked about all of them in an inspection. The gap between those two facts is where most NBFC IT teams live.
The 11 domains, in plain terms
| Domain | What it actually means for a 100-person NBFC | Typical first-year effort |
|---|---|---|
| IT governance | Board IT Strategy Committee, documented policies, annual review | 6-8 weeks, mostly documentation |
| Asset inventory | Every laptop, server, firewall, and SaaS app in one register | 2-3 weeks if you have no CMDB |
| Identity & access | AD hygiene, MFA on email and VPN, privileged access review | 4-6 weeks |
| Patch & vulnerability management | Monthly patch cycle, quarterly vulnerability scan, remediation SLAs | Ongoing, 1 day/week |
| Network security | Segmented LAN, NGFW with IPS, secure Wi-Fi, egress filtering | 6-10 weeks |
| Endpoint security | EDR on all endpoints, disk encryption, USB control | 3-4 weeks |
| Data protection | Encryption at rest, DLP basics, backup with offsite copy | 6-8 weeks |
| Incident response | Documented IR plan, tested annually, CERT-In reporting | 4-6 weeks then annual drill |
| Vendor / third-party risk | Due diligence, contract clauses, ongoing monitoring | 4-6 weeks per critical vendor |
| Business continuity | BCP tested, DR drill annually, RTO/RPO defined | 8-12 weeks including a drill |
| Board reporting | Quarterly cyber dashboard to Board IT Committee | 2 weeks to template, then quarterly |
That table is the skeleton. The rest of this article is about the muscle auditors actually poke.
Baseline controls: the 12 that matter most
RBI does not publish a numbered control list you can tick off. It publishes principles, and inspectors translate. But in practice, the same 12 technical controls come up in almost every NBFC inspection we support. If you get these right, you cover 70% of the technical findings. The remaining 30% is process evidence.
1. Firewall with IPS and logging
A FortiGate 90G or 100F (₹2.8-₹4.2 lakh with 3-year UTM bundle, 2026 pricing) is the floor. A consumer router or a basic Cisco RV series is not acceptable for a regulated entity. What the auditor will ask is not “what firewall do you have” but “show me 30 days of blocked-traffic logs, and show me who reviewed them.” The log review evidence is where 60% of NBFCs fail first time.
2. Email security beyond the spam filter
Microsoft 365 Defender for Business at ₹145-₹220 per user per month (2026) is the practical baseline for a 50-200 user environment. Google Workspace with the enhanced security add-on is fine too. What auditors look for: DMARC enforcement, MFA enforced for all users including service accounts, and evidence of phishing simulation results. A common failure: MFA is on for staff but the CFO's account is on an exclusion list because “the app on the old phone broke.” That is a finding.
3. EDR on every endpoint
CrowdStrike Falcon Go for 100 endpoints runs around ₹2.1-₹2.8 lakh annually (2026). Sophos Intercept X is in the same band. Microsoft Defender for Business at ₹145 per user per month is cheaper and adequate if your environment is mostly Windows and you actually tune it. Do not buy EDR and then run it in detect-only mode without alerts routed to someone. An unmonitored EDR is evidence of nothing.
4. Disk encryption and USB control
BitLocker on Windows Pro, with recovery keys escrowed in Azure AD or on-prem AD. If a laptop gets stolen and the auditor finds unencrypted disks, that is a reportable incident under the framework. USB port control via Group Policy or your EDR console.
5. Patch management with evidence
A monthly patch cycle is the requirement. The evidence is a report showing patch compliance by endpoint, with SLA (critical patches within 14 days, high within 30). WSUS is free but painful at scale; ManageEngine Patch Manager Plus (₹350-₹500 per endpoint per year, 2026) or Microsoft Intune are practical. The point is not the tool. The point is the monthly signed-off report.
6. Backup with offsite and immutable copy
This is the domain where the ₹18 lakh failure story at the top of this article happened. The RBI framework does not name a product, but auditors want to see: daily backup, offsite copy, immutable or air-gapped copy, and a tested restore in the last 12 months. Veeam Backup & Replication v12 (from ₹1.2 lakh for a 2-host environment, 2026) plus an offsite target (Synology DS1823xs+ with Active Backup for Business, or Wasabi/Backblaze B2 cloud) is the common pattern. Test the restore. Write it down.
7. Log retention for 180 days minimum
CERT-In directions require 180 days of log retention within India. RBI does not specify a number but expects sufficiency for forensics. A 50-user NBFC should budget ₹45,000-₹70,000 for a 2026 log management setup — a Graylog or Wazuh instance on-prem, plus syslog from the firewall, AD, and servers. Cloud SIEM (Microsoft Sentinel, Sumo Logic) starts at ₹90,000-₹1.8 lakh annually for the same scale and is genuinely better if your team can operate it. Most can't, and that is fine to admit.
8. MFA on remote access and privileged accounts
VPN with MFA is the floor. RADIUS or SAML against Azure AD. A FortiGate with FortiToken or Duo, or a Cisco AnyConnect with Duo, all work. What auditors reject: shared VPN credentials, an admin password in a text file, and “we use TeamViewer for remote support.”
9. Segmented network for the loan management system
The core lending application (whether it is Finflux, Nucleus FinnOne, or a custom build) sits on a VLAN with ACLs that restrict access to specific staff subnets. The auditor will ask for the network diagram and the ACL rules. If the diagram was drawn in PowerPoint in 2019 and the ACLs do not match, that is a finding.
10. Physical security of server room and branch IT
Access logs, CCTV retention (90 days), UPS with runtime enough for graceful shutdown. Branch-level NBFCs often fail here because the branch server room is also the stationery cupboard.
11. Secure configuration baseline
CIS benchmarks for Windows Server 2019/2022 and the firewall. This is the most-skipped control in mid-market NBFCs and the one auditors increasingly flag because it is easy to check.
12. Asset inventory that matches reality
The auditor picks five laptops at random and checks them against your asset register. If any are missing, or the register shows 80 and the network sees 94, that is a finding. A lightweight approach: sync from Intune or your EDR console monthly and reconcile.
What the auditors actually ask for: the evidence checklist
The framework lives or dies on documentation. Here is the evidence pack that a typical RBI inspection, or a statutory audit with an IT component, will ask to see. Build it once and refresh quarterly.
| Evidence item | Format | Refresh cadence | Audit weight |
|---|---|---|---|
| Board IT Strategy Committee minutes | Signed PDF | Quarterly | High |
| Cyber security policy (approved by Board) | Signed PDF + version log | Annual | High |
| Asset register (all endpoints, servers, network) | Excel / CMDB export | Monthly | High |
| Patch compliance report | PDF from tool | Monthly | Medium |
| Vulnerability scan report + remediation tracker | PDF + Excel | Quarterly | High |
| Firewall log review sign-off | Signed PDF | Monthly | High |
| Incident register (all incidents, closed and open) | Excel | Continuous | High |
| Incident reports filed with CERT-In / RBI | PDF + acknowledgement | As needed | Critical |
| Vendor due diligence files (top 5-10 vendors) | Folder per vendor | Annual | High |
| Backup restore test report | Signed PDF | Annual (twice for critical) | Critical |
| DR drill report | Signed PDF | Annual | High |
| Access review for privileged accounts | Signed Excel | Quarterly | High |
| Awareness training completion records | LMS export | Annual | Medium |
| Phishing simulation results | Tool export | Quarterly | Medium |
| Penetration test report (external) | Annual | Medium-High | |
| Cyber insurance policy | Annual | Low-Medium |
Two things about this table. First, the weight column reflects what we see in actual supervisory findings, not a formal RBI scorecard — the RBI does not publish weights. Second, the “critical” items are the ones that have produced monetary consequences in cases we have seen: incident reporting failures and untested backups.
The incident reporting timeline
This is the single most-failed evidence item. Under the RBI framework and CERT-In directions, incidents must be reported within 6 hours of detection to CERT-In, and material cyber incidents to RBI within 2-6 hours depending on classification. The failure mode is not that NBFCs hide incidents. It is that nobody on duty at 11pm knows the reporting obligation exists, so the incident gets reported 18 hours later after being escalated through three WhatsApp groups.
Write a one-page incident reporting card. Tape it to the wall of the IT room. Train the on-call engineer. Test it with a tabletop exercise twice a year. The card should name: who decides it is reportable, who files the CERT-In report (incidents@cert-in.org.in), who drafts the RBI communication, and who signs.
Board reporting: what the Board IT Committee actually needs
RBI expects the Board to oversee cyber risk, not delegate it entirely. In practice, this means a quarterly report that is readable by a director who is not technical. The report should fit on two pages. Here is the template structure we use with NBFC clients, and it survives inspection.
Page 1: Risk posture
- Open high-severity findings — count, aging, owner, target close date
- Incidents in the quarter — count by severity, with one-line summary each
- Patch compliance % — endpoints and servers separately, with SLA breaches named
- MFA coverage % — users, privileged accounts
- Backup success rate and last successful restore test date
- Third-party risk items — new vendors onboarded, vendors pending due diligence, contract renewals with security clauses
Page 2: Decisions requested
- Budget ask — the specific line items with amounts (e.g. “₹4.5 lakh for FortiGate replacement, ₹2.1 lakh EDR renewal”)
- Policy approvals — new or revised policies needing Board sign-off
- Risk acceptances — where the business is choosing to accept a risk, with the rationale and the compensating control
- Regulatory updates — new circulars, inspection observations, deadlines
The most common board reporting failure is turning this into a 30-slide technical deck that directors ignore. The second most common is not having it at all. If nothing else, get to page 1 by the next quarterly cycle. For a 100-200 person NBFC, a managed provider can produce this report from your tooling for ₹40,000-₹80,000 per quarter (2026), or you can template it in Excel and have the IT head fill it in monthly.
Vendor risk: the part everyone fumbles
Third-party risk is where NBFCs get caught because the ecosystem is complex. A typical 100-person NBFC has 15-30 technology vendors: core lending software (Finflux, Nucleus, Orange), payment gateway (Razorpay, Cashfree), KYC (Karza, IDfy), credit bureau (CIBIL, Experian), cloud (AWS, Azure), ISP (Airtel, Jio, Act), managed IT, AMC, and a spread of SaaS.
RBI expects due diligence on all of them, but in practice the depth should match the criticality. A pragmatic tiering:
| Tier | Definition | Examples | Due diligence depth | Contract clauses | Review frequency |
|---|---|---|---|---|---|
| Critical | Holds customer data or processes transactions | Core lending, payment gateway, KYC, cloud | Full security questionnaire, SOC 2 / ISO 27001 review, on-site or virtual audit | Right to audit, data residency India, breach notification 24h, exit / data return | Annual, plus event-driven |
| High | Accesses systems or data | Managed IT, AMC, log management, EDR | Security questionnaire, certifications review | Breach notification 48h, confidentiality, subcontractor controls | Annual |
| Medium | Peripheral access | ISP, facilities, CCTV vendor | Light questionnaire, contract clauses | Basic confidentiality, data handling | Every 2 years |
| Low | No data access | Stationery, courier | None | Standard | None |
The gaps auditors find most often:
- No due diligence file for the core lending vendor. The NBFC assumes the vendor is compliant because they are large. The vendor's SOC 2 has exclusions. Read it.
- Contracts missing breach notification clauses. If your KYC vendor has a breach, you need to know within 24 hours, not read about it in the news.
- Cloud data residency. RBI's 2018 payment data circular requires payment system data to be stored only in India. Audit logs, backups, and DR copies count. Azure Central India and AWS Mumbai are fine. Azure Southeast Asia is not, for payment data.
- Managed IT provider not covered by a security addendum. If your IT provider has domain admin and remote access, they are a critical vendor. Their contract should say so.
- Sub-processor visibility. Your payment gateway uses a sub-processor in another country. Do you know which? The auditor may ask.
Cloud residency is a real cost line, not a checkbox
Running core lending workloads in Azure Central India costs 15-25% more than Singapore in 2026, and the latency from Bangalore to Mumbai is fine (12-18ms). The cost premium is real and you should budget for it. Azure SQL in Central India for a 100-user NBFC typically runs ₹1.8-₹3.2 lakh per year versus ₹1.4-₹2.4 lakh in Southeast Asia. The difference is the price of compliance. Do not negotiate this one.
Incident response: the four-hour problem
Incident response is the domain where NBFCs most consistently under-invest, and where the consequences are most visible in a supervisory finding. Two issues:
Detection is usually the failure, not response
Most NBFC incidents we are called into are discovered by someone noticing something (a user's files renamed, a branch manager unable to log in), not by a monitoring alert. Detection typically lags by hours to days. The typical remediation: a basic SIEM or an EDR with alerting routed to an on-call rotation, plus a log correlation for failed logins.
The 2-hour and 6-hour clocks
Once an incident is detected and classified as material, the clock starts. In practice, classification itself is the hard part. Is a single phishing click material? Is a stolen unencrypted laptop material? Is a defaced marketing website material? The RBI does not give a bright-line test. Our guidance to clients: define materiality in the IR plan in writing, get the Board IT Committee to approve it, and when in doubt, report. Over-reporting is a far smaller problem than under-reporting.
A workable classification matrix for a mid-sized NBFC:
- Reportable to RBI and CERT-In within 2-6 hours: any confirmed unauthorised access to production systems, any data breach involving customer PII, any ransomware event, any DDoS that degrades customer-facing services for >15 minutes.
- Reportable to CERT-In within 6 hours, internal escalation to Board within 24 hours: phishing that resulted in credential compromise, lost or stolen device with unencrypted data, insider data exfiltration confirmed.
- Internal only, log in register: single phishing attempt blocked, failed brute-force, isolated malware quarantined by EDR.
The IR plan should also name your CERT-In empanelled auditor for forensics. Not all auditors handle all incident types. Have the retainer conversation before you need it — the difference between a ₹3 lakh retainer and a ₹9 lakh emergency call is the retainer.
The tabletop exercise nobody runs
RBI expects an annual IR drill. Most NBFCs do a tabletop once, log it, and never again. Run it every six months with a scenario that is actually plausible for you. A ransomware scenario that locks the loan management system at 4pm on a month-end. A branch manager's laptop stolen from a car in Koramangala with the customer onboarding file on the desktop. Your cloud provider region going down for 6 hours. Write the timeline down. Update the IR plan from what you learn. The auditor wants to see the plan was exercised, not that it was printed.
The infrastructure evidence auditors request, line by line
The RBI framework is principle-based; the auditor's checklist is not. Here is what an audit team will photograph, screenshot, or sample from your infrastructure. Build the evidence file proactively and the inspection is a two-day exercise instead of a two-month one.
Network
- Network diagram, dated, showing VLANs, firewall zones, remote-access paths, and cloud interconnection. One page, current month.
- Firewall rule export and the change log for the last 12 months.
- Firewall log sample for 30 days, plus the monthly review sign-off.
- Wi-Fi configuration: WPA2-Enterprise or WPA3, separate guest SSID, no PSK for staff. A branch with a single shared Wi-Fi password is a finding.
- VPN configuration showing MFA enforcement.
Endpoints
- EDR console screenshot showing all endpoints, agent health, and last-scan dates. Endpoints with agent offline >7 days need an explanation.
- BitLocker recovery key escrow report — coverage % and where keys are stored.
- Patch compliance report with the SLA definition.
- USB control policy and enforcement evidence.
- Sample of 10 endpoints with the auditor checking local admin rights (staff should not have local admin by default).
Servers and applications
- Server inventory with OS version, patch level, and role.
- AD hygiene report — stale accounts, accounts with password never expires, privileged group memberships.
- Privileged access review signed quarterly.
- Vulnerability scan report (internal, quarterly, at minimum) with remediation tracker. An external pen test annually.
- Change management log for production changes.
- Backup configuration and the last restore test report. The restore test is non-negotiable. We have seen three NBFCs in two years whose backups had never been restored. All three failed the audit. One failed in production.
Cloud and SaaS
- Residency attestation for each workload holding customer data.
- MFA and SSO evidence — who has access to the Azure / AWS console, and how.
- SaaS inventory with data classification and owner per app.
- Offboarding process evidence — last 10 leavers and their access revoked within a stated SLA (24h is the norm).
Physical and environmental
- Server room access logs for 90 days.
- CCTV clip or retention evidence.
- UPS maintenance records and battery replacement dates. Bangalore power is generally reliable, but a 10-minute outage on an unprotected server room can corrupt a file system. Surge protection, UPS, and generator or long-runtime UPS for the server room.
- Cable labelling and patching — auditors do not need pretty cabling, but they do need to trace a cable. Monsoon season in Bangalore puts water into older building risers; outdoor cabling runs need conduit and drip loops. We have seen a Cat6 run in a Rajajinagar basement take on water three monsoons in a row and fail intermittently before anyone traced it.
Governance and people
- Policy library with version control and Board approval dates.
- Training completion records for the last 12 months.
- Background verification records for IT staff.
- Segregation of duties evidence for IT operations (who can deploy, who can approve).
One worked recovery story
In August 2024, a 90-person NBFC in Bangalore had a recovery test that failed cleanly. Their Veeam backups were running to a Synology DS923+ in the same room, and the restore of the loan management server took six hours, double the stated 3-hour RTO. The reason was not Veeam; it was that the NAS was on the same switch as the server, the 1Gbps link saturated, and the restore job was queued behind a backup job. They spent ₹2.4 lakh (2025 pricing) on a second switch, a 10GbE link between the NAS and the restore host, and moving the backup window. The next test restored in 1 hour 50 minutes. The auditor's question — “show me the last restore test” — got a one-page report with timings, and the finding did not appear. The ₹2.4 lakh was cheaper than the ₹7-12 lakh penalty and remediation cost we typically see when an untested backup is flagged.
Where SynergyScape's approach is not the right fit
We run managed IT and security for NBFCs, and we are honest about the boundary. Three situations where we are not the right partner:
-
You need a full-time CISO on payroll. The RBI framework expects Board-level cyber expertise on the governance structure. A virtual CISO retainer (₹1.2-₹2.4 lakh per year for a mid-sized NBFC, 2026 pricing) covers the reporting and policy side. It does not replace a senior internal owner for a ₹2,000 crore+ NBFC with a complex product mix. At that scale, hire.
-
You are running a heavily custom-built core lending stack with a 30-person internal engineering team. Our value is breadth of infrastructure and security operations, not depth in your custom application. Bring us in for the network, endpoint, backup, and audit evidence; keep your engineering team on the app.
-
You are a very small NBFC (under 20 staff) with a single branch and no cloud footprint. You still have RBI obligations, but the £… sorry, the ₹ outlay for a full managed security stack may not be justified. A lighter touch — policy templates, a FortiGate 60F, Microsoft 365 Defender, and an annual audit prep engagement — is more proportionate. We will tell you that in the first meeting.
Where we do fit: mid-sized NBFCs with distributed branches, a need for managed detection and response, and a board that wants a quarterly report they can read. The SynergyScape clients page has the detail on how engagements are structured.
A practical 2026 budget for a 100-person NBFC
Here is a representative annual outlay (2026 pricing, Bangalore) for a 100-user NBFC building to the RBI framework baseline from a low starting point. This is a budget, not a quote; your mileage will vary with the existing estate.
| Item | Annual cost (₹) | One-time cost (₹) | Notes |
|---|---|---|---|
| Firewall (FortiGate 90G, 3-yr UTM) | — | 2,80,000-4,20,000 | Amortise over 3 years |
| EDR (CrowdStrike Falcon Go / Sophos, 100 endpoints) | 2,10,000-2,80,000 | — | Per endpoint per year |
| Microsoft 365 Business Premium (100 users) | 9,60,000-12,00,000 | — | Bundles Defender + Intune |
| Patch management (ManageEngine, 100 endpoints) | 35,000-50,000 | — | Or Intune if already licensed |
| Log management / basic SIEM | 45,000-1,80,000 | — | On-prem option cheaper, cloud better |
| Backup (Veeam + offsite target) | 1,20,000-2,40,000 | 80,000-1,60,000 | Offsite copy essential |
| External pen test (annual) | — | 1,80,000-3,50,000 | Scope matters |
| Vulnerability scanning (quarterly) | 60,000-1,20,000 | — | Or bundled with EDR |
| Awareness training (100 users) | 40,000-70,000 | — | Annual + phishing sims |
| Virtual CISO / audit prep | 1,20,000-2,40,000 | — | Policy, board reporting, audit support |
| Managed IT / support | 3,60,000-6,00,000 | — | If outsourced |
| Cyber insurance | 1,50,000-3,00,000 | — | Premium depends on controls |
| Indicative total year 1 | — | — | ₹ 16-25 lakh including one-time |
For a 20-50 person NBFC, halve most of it. For a 300-person NBFC with multiple branches, double it. The FY2026-27 budget cycle is when most of our NBFC clients are approving these spends; the ones that approved in FY2024-25 are now at steady-state spend of ₹8-15 lakh annually for maintenance and renewals.
GST: all of this attracts 18% GST as IT services, and the input credit is claimable if you are GST-registered. Budget for the gross number; some NBFCs forget the tax and get a surprise. An NBFC with a mix of taxable and exempt income may have partial ITC restrictions under the standard apportionment rules; check with your CA.
A 90-day starting plan
If you are starting from a low baseline and have an inspection in the next 6-9 months, here is the sequence that produces the most audit-credible evidence fastest.
Days 1-30: foundation. Asset inventory reconciled against EDR and Intune. MFA on email and VPN for all users. Firewall firmware current, IPS on, logs flowing somewhere retained. Draft the cyber security policy, incident reporting card, and IR plan. Get the Board IT Strategy Committee on the calendar for the next quarter.
Days 31-60: depth. BitLocker rollout to 100% with escrow. Patch cycle in place with monthly report. Backup configured with offsite and one successful restore test documented. Vendor tiering complete for the top 10 vendors. First vulnerability scan.
Days 61-90: evidence hardening. Pen test scoped and booked. DR drill scheduled. First board report drafted from the template above. Incident reporting card taped to the IT room wall and the on-call rota briefed. Audit evidence pack folder structure created with the table of contents from the checklist earlier in this article.
If you want to talk through the specific gaps in your environment, the contact page is the fastest route. Bring your last audit observation or your last inspection letter, if you have one. That is usually the only brief we need.
FAQ
What is the RBI cybersecurity framework for NBFCs?
It is a set of RBI circulars and directions — anchored by the Master Direction on IT Governance, Risk, Controls and Assurance Practices (2023) and the Cyber Security Framework — that require NBFCs to implement cyber controls, document them, report incidents, and have Board-level oversight. It is principles-based, so auditors translate it into a specific checklist. The evidence pack, not the policy document, is what determines your inspection outcome.
Which NBFCs does the framework apply to?
All NBFCs regulated by the RBI, with proportionality. Larger NBFCs (typically deposit-taking, or above asset-size thresholds) face the full set of requirements on the 2024 timeline. Smaller NBFCs get phased implementation but the same substantive controls. If you are unsure of your category, check with your compliance head or chartered accountant; the classification matters for the timeline, not the controls.
What is the incident reporting timeline for an NBFC cyber incident?
CERT-In directions require reporting within 6 hours of noticing the incident. RBI expects material cyber incidents to be reported to it within 2-6 hours depending on classification. The practical failure is not the reporting portal; it is that the on-call person does not know the obligation exists. Define materiality in writing, get Board approval, and keep a one-page reporting card with the email addresses and phone numbers.
How much does it cost to become RBI cyber-compliant for a 100-person NBFC?
Budget ₹16-25 lakh in year 1 (2026 pricing) including one-time firewall, pen test, and audit prep, then ₹8-15 lakh annually for renewals, managed services, and audit support. The variance depends heavily on whether you already have Microsoft 365 Business Premium and EDR, and whether you outsource managed IT. A 20-person NBFC can start at ₹5-8 lakh. A 300-person multi-branch NBFC should plan ₹30-50 lakh in year 1.
Do we need a CISO to comply?
RBI expects Board-level cyber expertise, but not necessarily a full-time CISO on payroll for mid-sized NBFCs. A virtual CISO retainer, combined with an active Board IT Strategy Committee, is accepted practice for NBFCs under roughly ₹2,000 crore AUM. Above that, or with complex product mixes, an internal senior owner is the safer structure.
Are cloud backups sufficient for the RBI framework?
Only if they meet three tests: data is stored in India (for payment and customer data), an immutable or air-gapped copy exists, and a restore test has been successfully completed in the last 12 months with a written report. A backup that has never been restored is evidence of nothing, and auditors have started asking for the restore test report by name.
Can we use our existing IT AMC provider for this?
Sometimes. The question to ask is whether the AMC covers security operations (EDR alerting, firewall log review, patch management) or just break-fix and device management. Most traditional desktop AMCs are break-fix contracts. The RBI framework requires continuous security operations and evidence. If your AMC cannot produce a monthly patch compliance report and a firewall log review sign-off, it is not the right contract for this scope.
Next step
Open your last audit observation letter, or if you do not have one, pull the IT section of your last statutory audit management letter. Count the open items. If the number is more than five, or if any item is older than two quarters, you have a supervisory risk that is cheaper to close now than after an inspection. The 90-day plan in this article is the sequence we use; the evidence checklist is the file structure. Start with the asset inventory and the backup restore test this month. Those two items alone move the needle more than any policy rewrite.
