Skip to content

Trusted across the UK, USA, EU & India - 24/7 incident response.

VAPT for NBFCs

Non-banking finance companies processing digital lending, KYC and payment data are subject to RBI's IT Governance Master Direction 2023, which requires annual VAPT on all internet-facing systems. IntelligenceX delivers engagements scoped to NBFC technology stacks — lending portals, KYC integrations, payment APIs and cloud infrastructure — with reports structured for RBI IS audit evidence.

RBI-aligned scope
Mobile app + API testing
Cloud infrastructure review
Signed attestation
Security testing and assessment

What RBI requires from NBFCs

The RBI IT Governance Master Direction 2023 applies to all NBFC-Investment and Credit Companies (NBFC-ICCs), NBFC-MFIs, housing finance companies, and payment aggregators regulated by the RBI. The direction requires annual VAPT on all internet-facing applications and infrastructure, with testing after significant system changes.

NBFC IS audits increasingly scrutinise the VAPT evidence package. An examiner expects the report to cover the borrower portal, mobile app, API layer and cloud infrastructure, not just the front-end website. Internal teams do not qualify as independent testers.

  • Annual VAPT mandatory for all RBI-regulated NBFCs
  • Scope must cover all internet-facing systems, APIs, mobile apps and cloud
  • Testing after significant system changes
  • Free retest confirming remediation required
  • Signed attestation letter for IS audit submission

NBFC technology stack: what to test

NBFC technology stacks have specific attack surfaces that differ from other financial institutions. These are the asset classes most relevant to an NBFC VAPT scope.

  • Digital lending portal — borrower registration, KYC submission, loan application and account dashboard
  • Loan management system (LMS) API — disbursement, repayment, statement and NOC endpoints
  • KYC integration APIs — Aadhaar eKYC, CKYC, video KYC and document verification flows
  • Payment integration — UPI, NACH mandate and loan repayment payment gateway APIs
  • Mobile app — iOS and Android, OWASP MASVS L1+L2
  • AWS or Azure infrastructure — IAM policies, S3/Blob storage, security groups, CloudTrail coverage
  • Credit bureau integration APIs — CIBIL, Experian, Equifax access credentials and data handling

Common findings in NBFC VAPTs

Based on the typical attack surfaces of digital NBFCs, these are the finding categories that appear most frequently in assessments of this sector.

  • BOLA (Broken Object-Level Authorisation) in loan APIs — one borrower accessing another's loan details, Aadhaar-linked data or account balance
  • Hardcoded API keys or credentials in mobile app binaries — common in React Native and Flutter apps
  • Overprivileged IAM roles — Lambda functions or EC2 instances with S3:* permissions on all buckets
  • Insecure NACH mandate handling — unsigned mandate parameters that can be tampered with
  • KYC data exposed in unauthenticated endpoints — a DPDP Act material risk
  • Password reset flows that do not invalidate existing sessions on completion

Frequently asked questions

The RBI IT Governance Master Direction 2023 requires testing by trained, independent personnel, not specifically a CERT-In empanelled firm. The key requirement is independence from the internal IT team. Where a specific RBI circular applicable to a particular NBFC category requires empanelment, that work is delivered through an empanelled partner.

At minimum: the borrower portal, loan management API, mobile app, KYC integration APIs, payment gateway integration, and the cloud infrastructure hosting these systems. RBI examiners expect the scope to reflect the full technology stack used for customer-facing and core lending operations, not just the front-end website.

A typical NBFC scope (borrower portal, API, Android and iOS apps, AWS infrastructure) takes 5 to 8 business days of active testing. We agree the testing window in advance so it does not conflict with month-end settlement cycles or regulatory submission deadlines.

Broken object-level authorisation (BOLA) in loan and account APIs is the most frequently observed critical finding. An authenticated borrower can access another borrower's loan details, Aadhaar-linked identity data or account statements by manipulating the resource identifier in an API request. This is both a severe security risk and a material DPDP Act exposure.

Talk to a security expert today

A penetration test, an audit, or 24/7 monitoring, our team is ready across the UK, USA, EU and India.