October 29, 2026
On 31 July 2026, the RBI repealed 627 older circulars and replaced them with 64 consolidated Directions, issuing seven parallel Cybersecurity, Technology: Risk, Resilience and Assurance Framework Directions one each for commercial banks, small finance banks, payments banks, urban co-operative banks, all India financial institutions, NBFCs, and credit information companies. If you run technology, compliance, or risk for an NBFC or a fintech partner, this is the framework replacing the rules you've been building against for years.
This isn't a distant compliance deadline. It's already in force. This article breaks down who it applies to, what it actually requires, and what NBFCs and their technology partners need to do in the next few months to be ready for a supervisory review.
The Reserve Bank of India (Non-Banking Financial Companies Cybersecurity, Technology: Risk, Resilience and Assurance Framework) Directions, 2026 replace the earlier IT Governance, Risk, Controls and Assurance Practices (ITGRCA) Master Directions that NBFCs had been operating under since April 2024, along with the older 2017 IT Framework for NBFCs. Rather than scattered circulars issued over the years, NBFCs now work from one consolidated instrument covering IT governance, cybersecurity, technology risk management, and assurance in force immediately on issuance.
The Directions apply through RBI's Scale Based Regulation (SBR) layers, so the obligations that bind your NBFC depend on which layer you sit in.
| NBFC Layer | Chapter Applied | What That Means in Practice |
| Base Layer, under ₹500 crore (and Core Investment Companies) | Chapter III only | Lighter-touch governance and technology risk requirements |
| Base Layer, ₹500 crore and above | Chapter IV | Fuller governance, risk management, and assurance obligations |
| Middle Layer, Upper Layer, and Top Layer (excluding Core Investment Companies) | Chapter V full baseline | Complete framework, including the strictest VAPT cadence and incident reporting obligations |
Housing finance companies report cyber incidents to the National Housing Bank rather than directly to RBI under this instrument, and local area banks were not covered in this batch of Directions.
• Board-approved IT, information security, and cybersecurity policies not departmental documents, but instruments the Board itself has reviewed and signed off on
• IT Governance structure, including an IT Strategy Committee and an Information Security Committee with defined meeting cadences
• A Chief Information Security Officer role that is structurally independent from the head of IT, so security oversight isn't reporting to the function it's meant to check
• IT risk management covering application security, network security, and access controls
• Regular vulnerability assessment and penetration testing (VAPT), with the exact cadence set by your SBR layer
• Business continuity planning and disaster recovery that's tested, not just documented
• Formal oversight of IT services outsourcing, including contractual security obligations flowed down to vendors
• Independent Information Systems audit, conducted at a frequency proportionate to your risk profile
• A defined cyber incident response and recovery process, not an ad-hoc one built after the fact
One of the most operationally demanding requirements is incident reporting. NBFCs must report cyber incidents on RBI's DAKSH platform within six hours of detection. This isn't six hours to fully investigate and explain what happened, it's six hours to file an initial report, even if full details aren't yet known, with a follow-up update required once the picture becomes clearer.
Meeting this timeline in a real incident is nearly impossible without a pre-drafted incident response protocol and pre-identified reporting contacts already in place before anything goes wrong. Building that readiness is not optional preparation, it's what makes the six-hour clock achievable at all.
This framework doesn't sit in isolation. It reinforces two compliance threads NBFCs and fintechs are already navigating:
• Vendor and outsourcing accountability, since a large share of NBFC cyber exposure enters through third parties, LSPs, and cloud providers and RBI's position remains that outsourcing a function never outsources the accountability for it
• Data protection obligations under the DPDP Act, which run in parallel to these cybersecurity requirements rather than replacing them, particularly around consent, data localisation, and breach handling
LetsFin has covered both of these directly: how RBI's outsourcing rules make vendor risk the lender's responsibility, and how the DPDP Act is reshaping consent management. Read together, these three pieces cover most of the compliance surface NBFC tech and risk leaders need to be tracking right now.
• Governance that exists on an organisation chart but not in practice committees that were formed but rarely meet
• A CISO title held by someone who also owns IT delivery, undermining the independence the framework expects
• VAPT treated as an annual box to tick rather than mapped to the actual cadence required for your SBR layer
• Vendor contracts that never got a security annexure, leaving no contractual basis to enforce the six-hour reporting timeline down to a supplier
• BCP/DR plans that were written once and never tested against a realistic scenario
• Map your NBFC's exact SBR layer and confirm which chapter of the Directions applies to you don't assume the full baseline or the lighter tier without checking
• Run a gap analysis against the new Directions specifically, not just your existing ITGRCA compliance posture, since the instrument itself has changed
• Formalise CISO independence from IT operations if that separation doesn't already exist
• Pre-draft your DAKSH incident reporting protocol and identify who owns it, before you need it in a live incident
• Review outsourcing contracts for security clauses and incident reporting timelines that flow down to vendors
• Schedule and actually run a BCP/DR test rather than relying on a document that's never been exercised
The Directions describe obligations in regulatory language governance, resilience, assurance. In practice, meeting them means sourcing a specific set of technical and advisory services. Mapping the framework's requirements to concrete service categories makes it easier to know what you're actually shopping for.
| Requirement in the Framework | Services That Address It |
| VAPT cadence (Chapter IV/V) | Web, Mobile and Cloud VAPT; Network and OT VAPT |
| Network security, access controls | Deployment of DLP, EDR, MDM, Email Security, SIEM, SOAR, ZTNA, IAM, XDR; AD Setup and Hardening |
| Testing whether controls actually hold up | Blue, Red and Purple Teaming; Threat Hunting |
| Application security | Source Code Review |
| CISO independence from IT | Virtual CISO |
| Independent IS audit | Security Compliance & Assessment |
| Six-hour DAKSH incident reporting | Incident Response; Ransomware Detection and Response; Malware Analysis |
| Board and staff governance expectations | Awareness Training |
| Parallel DPDP Act obligations | DPDP Readiness Assessment |
| Customer-facing risk (phishing, impersonation) | Brand Protection |
Few NBFCs need every service on this list at once. Base Layer NBFCs under Chapter III can usually start with VAPT, a Virtual CISO, and basic awareness training, while Middle and Upper Layer NBFCs under the full Chapter V baseline typically need the fuller set, including red/purple teaming, dedicated incident response, and continuous security monitoring through SIEM/SOAR.
Meeting this framework typically isn't a single hire or a single tool it's a combination of governance, technical controls, and ongoing assurance work. LetsFin's Cyber Security listing lets you compare vetted partners for VAPT, security monitoring, and audit readiness against this exact framework, so you're not evaluating each vendor's compliance claims independently.
When did the new RBI cybersecurity Directions take effect?
They were issued on 31 July 2026 and are in force immediately on issuance, repealing the earlier circulars and Master Directions they replace.
Do these Directions apply to all NBFCs equally?
No. Applicability is tiered by RBI's Scale Based Regulation layer. Smaller Base Layer NBFCs carry a lighter chapter of obligations, while Middle, Upper, and Top Layer NBFCs carry the full baseline framework.
What replaced the old NBFC IT Framework?
The 2026 NBFC-specific Cybersecurity, Technology: Risk, Resilience and Assurance Framework Directions replace both the 2024 ITGRCA Master Directions and the earlier 2017 IT Framework for NBFCs.
How fast do NBFCs need to report a cyber incident?
Within six hours of detection, via RBI's DAKSH platform, with an initial report filed even before full details are known, followed by updates as the investigation progresses.
Do these rules apply to fintechs that aren't NBFCs themselves?
Fintechs partnering with regulated NBFCs or banks are typically drawn in indirectly, since regulated entities are required to flow down security and reporting obligations to their technology vendors and Lending Service Providers contractually.
This isn't a framework to schedule for next quarter; it's already the standard NBFCs are being assessed against. The NBFCs that treat this as a Board-level governance obligation, not just an IT department task, will be the ones with a clean answer when a supervisor asks to see the policy, the meeting minutes, and the last test date. Compare vetted cybersecurity partners on LetsFin to start closing the gaps before your next review.