Illustrative example · composite scenario, not a named customer
Fintech: SOC 2, ISO 27001 and DPDP on one control set
This example follows a typical lending fintech, about 150 people, that provides a digital lending platform to NBFC partners and has a US investor asking for SOC 2. Its NBFC partners must meet RBI expectations on outsourcing and digital lending, which they pass down in vendor audits. Here is how three frameworks would run on one control set in AuditIQ GRC.
The situation
The company processes borrower KYC documents, bank statements, credit bureau data and repayment histories on behalf of its NBFC partners. Each partner runs an annual vendor audit shaped by RBI's outsourcing and digital lending expectations. The US investor wants a SOC 2 Type 2 report. And with the DPDP Act's main duties arriving in May 2027, partners are adding processing clauses to contracts.
The challenge
- Three partner audits a year, each asking for the same evidence in a different format
- An ISO 27001 certificate whose scope no longer matches the product
- A SOC 2 observation period starting in two months
- Borrower data in several systems, some managed by sub-processors
How the programme would run
| Phase | Work in AuditIQ GRC |
|---|---|
| Month 1 | Turn on ISO 27001, SOC 2 and DPDP. Rescope the ISMS to the lending platform. Import the existing risk register and controls. |
| Month 2 | Map controls across all three frameworks; gaps show per framework. Start the SOC 2 observation period with evidence collected automatically where possible. |
| Month 3 | Vendor risk: tier sub-processors handling borrower data, collect certificates and contracts, add DPDP clauses. |
| Month 4 | DPDP: breach plan with both the CERT-In six-hour and DPDP 72-hour clocks, processor commitments to partners, retention schedule for loan records. |
| Months 5 to 9 | Run controls; partner auditors get read-only workspaces instead of evidence zip files. |
| Month 10 | ISO 27001 surveillance audit and SOC 2 Type 2 report from the CPA firm, using the same evidence. |
What makes the difference
- One answer, many audits. Each partner audit pulls from the same mapped evidence.
- Deployment choice. A partner that insists on data staying within its own infrastructure can be served by deploying in the company's own cloud account.
- Vendor register. Sub-processors are visible to partners, with contracts and expiry dates tracked.
Lessons for other fintechs
Fix your ISMS scope before you start SOC 2; an outdated scope causes more pain than any missing control. Treat partner audits as a product: one evidence library, one trust center, one set of answers. And plan for DPDP as a processor now. Your partners will hold you to their own deadlines.
Running a similar programme?
See it on your scope in a 30-minute demo. Book a demo.