What Is SOC 2 Compliance? A Plain Answer
What SOC 2 compliance means: an AICPA attestation report issued by a licensed CPA firm, Type 1 vs Type 2, the five criteria, who needs it, cost and time.
15 min readBy Sachin Shirish, Director
Reviewed by Pragya Dwivedi, Associate Director, CISM (ISACA), eWPTX (INE Security)
SOC 2 compliance means a licensed CPA firm has examined the controls around your system and issued a report on them, measured against the AICPA's Trust Services Criteria. It is an attestation report, not a certificate. There is no SOC 2 register, no badge issued by a regulator and no pass mark. What a US customer means when they ask "are you SOC 2 compliant?" is "can you send us your SOC 2 report?", and that report is what this guide explains.
The Short Answer
- What it is: an examination report on the controls at a service organisation, relevant to security and, if you choose, availability, processing integrity, confidentiality and privacy. It belongs to the AICPA's SOC suite of services.
- Who issues it: a licensed CPA firm. Not a consultant, not a software platform, and not SecureRoot.
- What it is measured against: the AICPA's Trust Services Criteria. Security is always in scope; the other four categories are optional.
- Two types: Type 1 looks at control design on a single date. Type 2 looks at whether controls operated over a period.
- Who asks for it: mostly US enterprise customers buying software or services that will hold their data.
- What it costs with SecureRoot: our readiness and audit support band is ₹1.5 lakh to ₹4.5 lakh, plus the CPA firm's own fee, which it quotes and invoices directly.
SOC 2 Is an Attestation, Not a Certification
The most common misunderstanding is the word "certified". ISO 27001 ends in a certificate issued by an accredited certification body. SOC 2 does not. It ends in a report written by an independent auditor, containing your management's description of the system, management's assertion about it, the auditor's opinion, and, in a Type 2, the tests the auditor performed and what they found.
That difference matters in practice. A certificate is a yes or no. A SOC 2 report is a document your customer reads. Their security reviewer will look at what is in scope, which categories were covered, which period was tested and whether the auditor noted exceptions. Two companies can both "have SOC 2" and present very different reports.
The AICPA describes the SOC family as a suite of services that CPAs may provide on system-level controls at a service organisation. Its SOC 2 topic page lists the guide for examinations relevant to security, availability, processing integrity, confidentiality or privacy. The word that recurs is "CPA". Only a licensed CPA firm can sign the opinion.
So when someone offers to make you "SOC 2 certified" in a few weeks, read it carefully. Software and consultants can get you ready. They cannot issue the report.
Who Issues a SOC 2 Report
A SOC 2 report is issued by a licensed CPA firm under the AICPA's attestation standards. The firm has to be independent of the company it examines, which is why the people who design your controls should not be the people who sign the opinion on them.
That splits a SOC 2 project into two jobs:
- Readiness. Scoping the system, choosing the categories, running a gap assessment, writing policies, putting controls in place and collecting evidence. A consultancy like SecureRoot, your own team, or both, can do this.
- The examination. The CPA firm reviews the description, tests the controls and issues the report. You contract with the firm directly.
SecureRoot does the first job and supports you through the second. We are not a CPA firm and we do not issue SOC 2 reports. During scoping we introduce partner CPA firms, and you choose and contract with one yourself. If you want to know what to look for when choosing, our guide on how to choose a SOC 2 auditor covers the questions to ask.
Type 1 vs Type 2 in One Paragraph
A Type 1 report gives an opinion on whether your system description is fairly presented and your controls were suitably designed as of a single date. A Type 2 report covers a period, the observation window, and adds an opinion on whether the controls operated effectively throughout it. Type 1 is quicker and is often used to unblock a first deal. Type 2 is what most enterprise security reviewers ultimately ask for, because it shows the controls working over time rather than existing on paper. Our comparison of SOC 2 Type 1 vs Type 2 covers how to sequence the two.
The Five Trust Services Criteria at a Glance
The Trust Services Criteria are grouped into five categories. Security, also called the common criteria, is in every SOC 2 report. The other four are added when they match what you promise customers.
| Category | What it asks | Typically added when |
|---|---|---|
| Security | Is the system protected against unauthorised access, use or change? | Always: it is required in every SOC 2 |
| Availability | Is the system available for operation and use as committed? | You sign uptime commitments or SLAs |
| Processing Integrity | Is processing complete, valid, accurate, timely and authorised? | Customers rely on your calculations or transactions |
| Confidentiality | Is information designated as confidential protected? | You hold customer business secrets, contracts or IP |
| Privacy | Is personal information collected, used, retained and disposed of as committed? | You process personal data on your own account |
More categories are not better. Each one adds criteria, evidence and audit time, and a customer who only asked for Security gains nothing from the rest. Most first-time SaaS reports start with Security alone, or Security plus Availability and Confidentiality. Our guide to the SOC 2 Trust Services Criteria explains each category and how to choose.
What Is Actually in a SOC 2 Report
Founders hearing about SOC 2 for the first time are often surprised by how much of the report they write themselves. A SOC 2 report has four main parts:
- The auditor's opinion. The CPA firm's conclusion, on the description and the controls. This is the part reviewers read first.
- Management's assertion. Your company's written statement that the description is fair and the controls meet the criteria.
- The system description. Your account of the services, infrastructure, software, people, procedures and data in scope, and the commitments you make to customers.
- Controls and tests. The controls mapped to the criteria, and in a Type 2, the auditor's tests and results, including any exceptions.
Because the report contains detail about your security, its distribution is restricted. Customers usually receive it under a non-disclosure agreement. If you want something you can publish, a SOC 3 report is a short general-use version based on the same examination. Our comparison of SOC 1 vs SOC 2 explains where SOC 3 fits.
Who Needs SOC 2
SOC 2 is a market requirement, not something an Indian law asks for. It arrives through a customer, usually in one of three ways: a security questionnaire that asks for your latest SOC 2 report, a procurement checklist that lists it as a condition of onboarding, or a contract clause that requires it within a set time.
The companies that hear it most are:
- B2B SaaS companies selling to US mid-market and enterprise customers, whose product stores or processes customer data.
- Cloud, hosting and managed IT providers who run infrastructure that customers depend on.
- IT services and outsourcing firms whose staff have access to customer systems or data.
- Data, analytics and AI vendors handling customer datasets.
If your product processes transactions that end up in a customer's financial statements, the customer's auditors may ask for SOC 1 instead of, or as well as, SOC 2. And if most of your customers are in Europe or Asia, ISO 27001 may be the more common request. Our comparison of ISO 27001 vs SOC 2 covers which to start with.
Before starting, read the clause or questionnaire item that triggered the request. It usually names the report, the type and sometimes the categories, and it can save months of work on things nobody asked for.
What SOC 2 Costs: The Summary
There are two separate bills, and it helps to keep them apart.
| Cost | Who charges it | Figure |
|---|---|---|
| Readiness and audit support | SecureRoot | ₹1.5 lakh to ₹4.5 lakh, the same band for Type 1 or Type 2 |
| SOC 2 Type 1 examination | The licensed CPA firm, invoiced directly | Indicative market range ₹2 lakh to ₹5 lakh |
| SOC 2 Type 2 examination | The licensed CPA firm, invoiced directly | Indicative market range ₹5 lakh to ₹12 lakh |
The SecureRoot band is published on our SOC 2 service page. The CPA fee ranges are indicative market figures from our SOC 2 cost guide, not SecureRoot fees: the firm quotes its own price during scoping and we do not mark it up or collect it. A compliance platform, if you use one, is quoted by its vendor. Your own team's time appears on no invoice and is usually the larger cost.
Our price is fixed in writing after a scoping call and a one-page written scope. The cost guide breaks down what moves the figure: the number of categories, the size of the system in scope, and how much already exists.
How Long SOC 2 Takes: The Summary
SecureRoot's published timelines are:
- Type 1: typically eight to twelve weeks.
- First Type 2: six to nine months, assuming a three-month observation window.
The Type 2 takes longer because the auditor needs controls to have operated over a period before testing them, and that period cannot be compressed. What stretches either timeline is remediation and how quickly your control owners produce evidence. We commit to dates after the gap assessment, not before. The step-by-step audit process, from scoping to fieldwork to the report, is in our guide to SOC 2 services in India.
SOC 2 Is Not a One-Time Project
A SOC 2 report has a shelf life. A Type 2 covers a past period, so customers will ask for a new one as it ages. In practice that means an annual cycle: controls keep running all year, evidence keeps being collected, and the CPA firm examines the next period.
That is the real meaning of "SOC 2 compliance" as a state rather than a report. It is a set of controls that operate every day, such as access reviews, change approvals, vulnerability management, incident handling, vendor reviews and security training, with evidence that they did. The report is the auditor's view of a window. The programme is what keeps the next window clean.
SOC 2 for Indian Companies That Also Handle Personal Data
Indian companies selling to US customers often also process personal data of Indians, which brings the Digital Personal Data Protection Act, 2023 into play. SOC 2 and the DPDP Act are different things: one is a voluntary examination report a customer asks for, the other is a law. A SOC 2 report does not make you DPDP compliant, and there is no DPDP certificate that anyone, including SecureRoot, can issue. The controls do overlap, particularly around security safeguards and access, and our guide to SOC 2 and DPDPA compliance maps where one control set can serve both.
What SecureRoot Does, and Does Not Do
SecureRoot prepares companies for SOC 2: scoping, category selection, gap assessment, policy and control design, evidence collection and support through the CPA firm's fieldwork. That work is described on our SOC 2 service page.
We are not a CPA firm. We do not issue SOC 1, SOC 2 or SOC 3 reports, and we cannot promise a clean opinion, because that judgement belongs to the independent auditor. What we can do is make sure that when the auditor arrives, the description is accurate, the controls exist and the evidence is ready.
Frequently Asked Questions
Is SOC 2 a certification?
No. SOC 2 is an attestation report, issued by a licensed CPA firm under the AICPA's attestation standards. It is not a certificate, and there is no public register of SOC 2 compliant companies. The report contains your system description, your management's assertion, the auditor's opinion and, in a Type 2, the tests performed and their results. People say "SOC 2 certified" as shorthand, and most customers will understand it, but the accurate phrase is that you have a SOC 2 report covering a stated scope and period. That precision matters when you answer a security questionnaire, because a reviewer will ask which type, which categories and which period your report covers, and whether the auditor noted exceptions. Compare this with ISO 27001, which does end in a certificate from an accredited certification body. If a vendor offers to make you "SOC 2 certified" without a CPA firm involved, what they are offering is readiness work, not the report itself.
Is SOC 2 mandatory for Indian companies?
No Indian law requires a SOC 2 report. It is a market requirement that arrives through customers, mostly US enterprises, who ask for it in a security questionnaire, a procurement checklist or a contract clause before they will share data with you. For a company that sells only to Indian customers, SOC 2 is rarely the first request; ISO 27001 or compliance with sector rules and the DPDP Act are more common concerns. For a SaaS or IT services company selling into the United States, though, a missing SOC 2 report is a frequent reason deals stall at security review. Treat it as a commercial decision. Look at the deals you are losing or slowing, the customers who have asked and what they asked for exactly. If the request is real and recurring, a report usually pays for itself. If nobody has asked yet, a gap assessment can tell you how far away you are without committing to the full programme.
Who can issue a SOC 2 report?
Only a licensed CPA firm can issue a SOC 2 report. The examination is an attestation engagement under the AICPA's standards, and the opinion must be signed by a firm entitled to perform it. The firm also has to be independent of the company it examines, which means whoever designed and built your controls should not be the one giving the opinion on them. Consultancies, including SecureRoot, and compliance automation platforms can prepare you. They can scope the system, close gaps, write policies, put controls in place and organise the evidence the auditor will ask for. They cannot sign the report. In practice an Indian company contracts with a CPA firm directly, often one introduced during scoping, and the firm quotes its own fee. When comparing firms, ask about their experience with companies of your size and stack, their sampling approach for Type 2, and how they handle the timing of fieldwork against your observation window.
Should we start with SOC 2 Type 1 or Type 2?
It depends on what your customer asked for and how soon. A Type 1 report examines control design as of a single date, so it can be reached sooner; SecureRoot's published timeline is typically eight to twelve weeks. It is often enough to unblock a first enterprise deal, especially when the customer agrees to accept a Type 2 later. A Type 2 report covers a period and shows the controls actually operating, which is what most mature security reviewers want in the end. A first Type 2 takes six to nine months with SecureRoot, assuming a three-month observation window. Many companies do both in sequence: Type 1 first to show progress, then the observation window starts and the Type 2 follows. Others skip Type 1 if no deal is waiting and go straight to the Type 2 window. Read the customer's request closely before choosing, because some contracts specify the type and accept no substitute.
How much does SOC 2 cost in India?
Budget for two separate costs. The first is readiness and audit support. SecureRoot's published band is ₹1.5 lakh to ₹4.5 lakh, the same band whether you are preparing for Type 1 or Type 2, fixed in writing after a scoping call and a one-page written scope. The second is the licensed CPA firm's examination fee, which the firm quotes and invoices directly. Our cost guide gives indicative market ranges of ₹2 lakh to ₹5 lakh for a Type 1 and ₹5 lakh to ₹12 lakh for a Type 2. Those are not SecureRoot fees, and we neither mark them up nor collect them. A compliance platform, if you use one, is priced by its vendor. Then there is your own team's time, which appears on no invoice and is usually the largest cost of all. What moves the totals is the number of categories in scope, the size of the system and how many controls already exist.
Where to Start
Find the clause, questionnaire item or email that asked for SOC 2, and note which type and categories it names. That tells you what you need. If you want to know how far you are from it, request an assessment and we will scope it against your system.
Have a Question About This?
If this raised something specific to your environment, a scoping call is the fastest way to get a direct answer.
We reply within one business day.
See Every Published Price Band