SOC 2 Readiness for Indian SaaS Companies: Type I vs Type II

The $40,000 deal that stalled on a security questionnaire
In late 2025, a 60-person SaaS company in Bengaluru lost a $40,000 annual contract with a US healthcare client. The product passed every technical evaluation. The deal died on a single line in the vendor security questionnaire: "Do you have a SOC 2 Type II report?" The company had a Type I report, a year old, covering a period when they had 28 employees and no dedicated security lead. The client's procurement team would not accept it. The sales cycle restarted, and the company spent the next nine months and roughly ₹18 lakh getting audit-ready for a Type II.
That pattern is now common. If you sell B2B SaaS to US or European buyers, SOC 2 has moved from a differentiator to a checkbox. Indian companies with 20–200 staff are the ones hit hardest: large enterprises already have it, and startups under 20 people can sometimes skate by on a security questionnaire and a penetration test report. The 50-person company with $2 million ARR and a US enterprise pipeline is where the pain concentrates.
This article is about what SOC 2 readiness actually involves for an Indian SaaS company, what it costs in rupees, how long it takes, and where the common traps are. It assumes you are evaluating this seriously, not just curious.
What SOC 2 is, and what it is not
SOC 2 is an attestation report issued by a licensed CPA firm under the AICPA's Trust Services Criteria. It is not a certification. Nobody "becomes SOC 2 certified." You undergo an audit, and the auditor issues a report that says whether your controls, as described by management, were suitably designed and operating effectively over a period.
The report covers five trust services categories: Security, Availability, Processing Integrity, Confidentiality, and Privacy. Almost every SaaS company starts with Security only. Adding Availability is common if you have uptime SLAs. Privacy is rarely needed unless you handle consumer PII at scale.
The two report types are not interchangeable.
| Feature | SOC 2 Type I | SOC 2 Type II |
|---|---|---|
| What it covers | Design of controls at a single point in time | Design and operating effectiveness over a period (typically 3–12 months) |
| Typical audit duration | 2–6 weeks | 3–12 months of evidence, plus 4–8 weeks of audit fieldwork |
| Cost range (India, 2026) | ₹3.5–8 lakh | ₹12–35 lakh |
| Sales acceptance | Often rejected by US enterprise buyers | Widely accepted |
| Best for | Early-stage companies needing a quick artefact | Companies with real enterprise pipeline |
A Type I tells a buyer "we have designed the right controls." A Type II tells them "those controls actually ran for six months and we have evidence." Buyers have learned the difference. If your sales team is telling you a Type I will close the deal, ask them which buyer accepted one in the last 12 months.
The realistic timeline for an Indian SaaS company
Most founders underestimate this by a factor of two. Here is a calendar that reflects what actually happens.
Months 1–2: Scoping and gap assessment
You decide which trust services categories to include, which systems are in scope, and which are out. You engage a compliance platform (Vanta, Drata, Sprinto, Secureframe) or a consultant. You run a gap assessment against the criteria. You will find 40–80 gaps, depending on your maturity.
Common findings at this stage: no formal access review process, no documented change management, no vendor risk register, no incident response plan, no background checks for new hires, no security awareness training records.
Months 3–5: Remediation
This is the expensive part. You are writing policies, configuring tools, and changing habits. Engineering teams resist change management because it slows deploys. HR resists background checks because it adds a week to onboarding. Finance resists the tool spend. Expect friction.
Months 6–11: Observation window
A Type II requires evidence over time. Six months is the shortest window most auditors will accept for a first report. Twelve months is better if your buyer is a bank or healthcare company. During this window, your controls must actually run. Miss a monthly access review in month three, and you have a gap your auditor will flag.
Months 12–14: Audit fieldwork and report
Your auditor samples controls, requests evidence, interviews staff, and issues a draft. Expect two rounds of corrections. The final report lands about 14 months after you started, if you moved fast.
A realistic end-to-end timeline is 12–16 months for a company starting from zero. If you already have ISO 27001, you can cut 3–4 months because many controls overlap. If you have neither, 14 months is honest.
What it costs in rupees (2026 pricing)
Costs vary widely. Here are ranges we see for Indian SaaS companies with 30–150 employees.
| Cost item | Type I (₹) | Type II (₹) |
|---|---|---|
| Compliance platform (Vanta, Drata, Sprinto) — annual | 4,00,000–9,00,000 | 4,00,000–9,00,000 |
| Auditor fees | 3,00,000–6,00,000 | 7,00,000–18,00,000 |
| Consultant / readiness partner (optional) | 1,50,000–4,00,000 | 4,00,000–12,00,000 |
| Tooling (MDM, SIEM, vulnerability scanner, password manager) | 1,00,000–3,00,000 | 2,00,000–5,00,000 |
| Internal staff time (engineering, HR, ops) | 3,00,000–6,00,000 | 10,00,000–25,00,000 |
| Total | 12,50,000–28,00,000 | 27,00,000–69,00,000 |
The internal staff time is the line most founders miss. A SOC 2 programme consumes 0.5–1.5 FTE for a year. If your CTO is spending 20% of her time on compliance, that is real money.
A few notes. Auditor fees in India are lower than US fees, but the best-known US firms charge US rates even for Indian audits. Mid-tier Indian CPA firms and boutique audit practices charge ₹7–12 lakh for a Type II and do solid work. Compliance platforms are priced per employee or per integration; Sprinto is often cheaper for Indian companies than Vanta at the same headcount.
The five controls that sink most first-time audits
Most of the audit findings we see in Indian SaaS companies cluster in five areas. Each has a straightforward fix, and each is routinely neglected.
1. Access reviews
SOC 2 requires you to review who has access to what, on a defined cadence, and remove access that is no longer justified. Quarterly is common. Monthly is better for production systems.
The failure mode: you run a review, everyone replies "looks good," and nobody actually checks. Your auditor will sample five users. Two will have left the company three months ago but still have active accounts. That is a finding.
The fix: automate deprovisioning from your HRIS. When an employee is marked terminated in Keka or Zoho People, a workflow should disable their Google Workspace account, revoke AWS IAM credentials, and close their GitHub access within 24 hours. Manual checklists fail at scale.
2. Change management
Every production change needs a ticket, an approval, a test, and a rollback plan. Most engineering teams already do this informally. The audit requires evidence.
The failure mode: your team deploys through GitHub Actions without a linked Jira ticket. The auditor samples 25 changes and finds 8 with no approval record. That is a finding.
The fix: enforce branch protection rules, require pull request approvals, and link PRs to tickets. If you use Jira, ServiceNow, or Linear, configure webhooks so every deploy has a trail. Most auditors will accept a GitHub PR with two approvals and a passing CI run as evidence of change management. What they will not accept is "we discussed it on Slack."
3. Vendor risk management
Every third-party vendor that touches customer data needs a risk assessment. That includes your cloud provider, your support desk, your email provider, your payroll system, and your analytics tools. It also includes the IT support provider who has admin access to your laptops.
A common gap: the company has a vendor list but no evidence of reviews. The fix is a simple register with a risk tier, a review cadence, and a signed DPA or security questionnaire on file. Thirty vendors is typical. Reviewing all thirty annually is fine.
This is also where the choice of IT partner matters. If your managed services provider cannot produce a SOC 2 report, an ISO 27001 certificate, or a completed security questionnaire for your audit, you have a gap in your own evidence. When evaluating partners, ask for their own attestations. Our managed services practice maintains documentation specifically because our clients' auditors ask for it.
4. Logging and monitoring
SOC 2 expects you to log security-relevant events and review them. For most SaaS companies, this means centralised logging of authentication, authorisation, and administrative actions, with alerting on anomalies.
The failure mode: logs exist but nobody reviews them. Or logs are retained for 7 days, and the auditor wants 90. The fix is straightforward: ship logs to a central store, retain for 12 months, and set up alerts for failed logins, privilege escalation, and unusual data access. Products like Datadog Cloud SIEM, Panther, or AWS Security Hub cover this. For smaller companies, CloudWatch Logs with a few metric filters is enough to pass.
5. Incident response
You need a written incident response plan, a defined team, and evidence of a test. The failure mode: the plan exists but has never been exercised. The auditor will ask for a tabletop exercise record.
The fix: run one tabletop exercise per year, document it, and update the plan. A two-hour session with your engineering lead, CTO, and head of customer success is sufficient. Record the scenario, the decisions, and the follow-up actions.
Building a SOC 2 evidence pipeline that does not collapse
The single biggest predictor of a smooth audit is whether evidence collection is automated. Companies that collect evidence manually in spreadsheets spend 200–400 hours in the audit window. Companies that automate spend 40–80.
A practical stack:
- Compliance platform: Vanta, Drata, Sprinto, or Secureframe. Pick one and commit. Sprinto is popular in India because of pricing and local support.
- Identity provider: Google Workspace or Microsoft Entra ID. Both integrate natively with compliance platforms.
- MDM: Jamf for Mac-heavy teams, Intune for Windows, or Kandji if you want a lighter Mac option. Every laptop must be enrolled.
- Vulnerability scanning: Tenable, Qualys, or the built-in scanners in AWS Security Hub and GCP Security Command Center.
- Password manager: 1Password or Bitwarden. Shared credentials in spreadsheets will fail the audit.
- Ticketing: Jira, Linear, or GitHub Issues. The system matters less than the discipline of linking every change to a ticket.
If your team is 30 people or fewer, a compliance platform plus these tools will cover 80% of evidence. Above 50 people, you will need a dedicated compliance owner, even if part-time.
Type I vs Type II: which one first?
A common pattern is to do a Type I first, then a Type II six months later. This is defensible but not always the right move.
A Type I is useful if you need a quick artefact to unblock a sales cycle and your buyer accepts it. It costs less and takes two months. But if your buyer is a US enterprise or a regulated industry, a Type I will not close the deal. You will end up doing the Type II anyway, and the Type I spend is sunk.
A more efficient path for most Indian SaaS companies is to skip the Type I and go straight to a Type II. The remediation work overlaps almost completely. You start the observation window as soon as your controls are in place, and you have a report in 12–14 months instead of 18–20.
The exception is a company with no security programme at all and a buyer who will accept a Type I. In that case, do the Type I, but only if the buyer has confirmed in writing they will accept it.
A failure story: how a missed access review cost ₹9 lakh
A 90-person SaaS company in Whitefield, Bengaluru, started its SOC 2 Type II observation window in January 2025. They had done the remediation, implemented Vanta, and were confident. In August 2025, three weeks before audit fieldwork began, the auditor sampled the quarterly access review for Q1. The review had been run, signed off, and filed. But the auditor asked a simple question: show us the evidence that someone actually checked the list.
The company had a PDF with 142 names and a manager signature. There was no evidence that anyone had verified each person's role, no comparison against the HRIS, and no record of removals. The auditor escalated. A deeper sample found 11 terminated employees still had active AWS and GitHub accounts, one of whom had left eight months earlier.
The auditor issued a qualification. For a company that needed a clean Type II for a US healthcare deal worth ₹9 lakh annually, a qualification was worse than useless. They had to restart the observation window, push the audit to mid-2026, and spend roughly ₹9 lakh on an extra six months of compliance platform fees, auditor rescheduling, and internal time. The root cause was a manual process with no evidence of actual review.
The fix was not glamorous. They integrated Keka with Google Workspace and AWS IAM, automated deprovisioning within 4 hours of termination, and moved access reviews into Vanta with per-user attestation. The Q3 review had 142 individual confirmations and a full audit trail. That is what the auditor wanted in the first place.
The India-specific complications
The AICPA criteria are jurisdiction-agnostic, but the operating environment is not. A few things to plan for.
Data residency and the DPDP Act
India's Digital Personal Data Protection Act (DPDP Act) 2023 imposes obligations on how you handle personal data of Indian residents. SOC 2 and DPDP are not substitutes for each other, but the controls overlap. If your SOC 2 scope includes systems storing Indian customer PII, your auditor will ask about data residency and cross-border transfer. Document where data lives. If you use AWS ap-south-1 (Mumbai) or GCP asia-south1, you are in a stronger position than if you are on us-east-1 by default.
CERT-In directions
The CERT-In directions of April 2022 require covered entities to report cyber incidents within six hours, maintain logs for 180 days within India, and synchronise clocks to NIC or NPL time sources. These obligations apply to a broad set of service providers. Your SOC 2 incident response plan should reference CERT-In reporting timelines and your log retention should meet the 180-day requirement. Auditors increasingly check this.
ISP and power realities
If your SOC 2 scope includes availability, your auditor will ask about business continuity. In Bangalore, this means documenting how you handle ISP outages (Airtel and Jio enterprise circuits typically take 7–14 working days to provision, longer for new fibre paths), power interruptions (DG backup, UPS health checks), and monsoon-related cabling faults. A written BC plan that references these realities is stronger than a generic template.
GST treatment
The good news: audit fees from Indian CPA firms attract 18% GST and are creditable if you are GST-registered. Foreign auditors are subject to reverse charge mechanisms and often more complexity than the fee difference justifies. Price Indian auditors against foreign ones with GST included.
Choosing an auditor and a readiness partner
You need a CPA firm licensed to issue SOC 2 reports. In India, that means firms with AICPA peer review or equivalent. Mid-tier firms such as BDO India, Grant Thornton Bharat, Walker Chandiok, and a long tail of boutique practices do this work. Pricing varies by a factor of three.
Questions to ask before you engage:
- Have you issued SOC 2 Type II reports for SaaS companies under 150 employees? Ask for two references.
- What is your typical timeline from fieldwork start to draft report? Anything over 8 weeks is slow.
- Will you review our evidence in advance, or only at fieldwork? A good auditor offers a pre-assessment.
- What is your policy on qualifications? If they cannot tell you what causes one, they have not done enough of these.
A readiness partner or consultant can be useful if you have no internal compliance experience. A good one will not just hand you policies; they will sit with your engineering lead and fix the change management workflow. Budget ₹4–12 lakh for a Type II readiness engagement.
If you are already working with a managed services provider for your IT infrastructure, ask whether they can support the technical controls: MDM rollout, endpoint hardening, log centralisation, and access review automation. This is not core SOC 2 work, but it is the underlying plumbing. Our managed services team does this for several SaaS clients, and it is often faster than having your engineering team build it from scratch.
Where the standard approach breaks down
SOC 2 readiness is not right for every company at every stage. If you are pre-product-market fit, or if 90% of your revenue comes from Indian SMBs, the sales pressure that drives SOC 2 may not exist. The cost of a Type II is ₹27–69 lakh in Year 1, and you will spend ₹15–25 lakh every year after that on audit, tooling, and internal time. For a company with ₹3 crore ARR and no US pipeline, that math does not work.
Similarly, if your product runs entirely within India and your buyers are Indian banks, ISO 27001 is often the more useful certificate. Some Indian procurement teams will ask for both.
And if you are already deep into a Type II observation window with a weak control environment, the honest advice is to pause and fix the controls rather than push through. A qualified report is worse than no report. Better to delay the audit by six months and pass cleanly.
The 90-day starter plan
If you are starting from zero, here is what the first 90 days should look like.
Days 1–15: Pick a compliance platform. Sprinto, Vanta, Drata, or Secureframe. Sign up for a trial and connect your IdP, cloud accounts, and ticketing system. Run the gap assessment.
Days 16–45: Fix the five high-risk gaps. Deprovisioning automation. Change management workflow in GitHub plus Jira. Vendor register with 30 vendors. Log retention set to 12 months. Incident response plan drafted.
Days 46–75: Enrol every laptop in MDM. Roll out password manager. Run security awareness training and record completion. Start quarterly access reviews with per-user attestation.
Days 76–90: Engage your auditor. Share evidence. Ask for a pre-assessment. If they are confident, start the observation window. If not, fix what they flag and start the window 30 days later.
If you want a sanity check on the infrastructure side before you commit to a window, talk to us. We can review your endpoint and network posture against the criteria in a week, and tell you honestly whether your observation window will survive contact with an auditor.
FAQ
How long does a SOC 2 Type II take in India?
Most Indian SaaS companies need 12–16 months from a standing start. The remediation phase runs 3–5 months, the observation window is 6–12 months, and audit fieldwork takes 4–8 weeks. Companies with ISO 27001 already in place can finish in 9–11 months.
What is the difference between SOC 2 Type I and Type II?
Type I covers the design of controls at a single point in time; Type II covers operating effectiveness over a period, usually 6–12 months. Type II is what US enterprise buyers expect. Type I is cheaper (₹3.5–8 lakh versus ₹12–35 lakh) but is often rejected by serious procurement teams.
How much does SOC 2 cost for an Indian company in 2026?
Expect ₹12–28 lakh for a Type I and ₹27–69 lakh for a Type II, including auditor fees, compliance platform, tooling, optional consultant, and internal staff time. Annual ongoing cost after the first report is ₹15–25 lakh.
Do we need a compliance platform like Vanta or Sprinto?
Not strictly, but achieving SOC 2 without one is painful. Platforms automate evidence collection, integrate with your IdP, cloud, and ticketing tools, and cut audit prep time by 60–70%. Sprinto is typically cheaper in India; Vanta and Drata are popular with US-based auditors.
What is the most common SOC 2 audit finding for Indian SaaS companies?
Access reviews are the single most common finding. Companies run reviews but cannot show evidence that anyone verified each user's access. Terminated employees retaining active accounts in AWS, GitHub, or production databases is the recurring failure mode.
Does SOC 2 satisfy Indian data protection law?
No. SOC 2 is an AICPA attestation; DPDP Act obligations under Indian law are separate. Many controls overlap, but you still need DPDP-specific documentation, consent records, and breach notification processes. CERT-In reporting requirements are also distinct and should be referenced in your incident response plan.
