Skip to main content
For Indian SaaS, cloud, fintech and IT services companies

SOC 2 Compliance and audit readiness, done in the right order

A SOC 2 is an auditor's opinion on controls you actually operate, not a certificate you buy. We get the controls running and the evidence flowing before the observation window opens, so the report says what you need it to say.

  • Criteria and system boundary scoped to your product
  • Gaps closed before the window opens, not during it
  • Evidence pipeline built once, reused every year
  • CPA firm selection and fieldwork support
Reviewed by Industry Experts & Startup Specialists.
Last Updated: 
FREE Consultation Get Started @ ₹299 ₹0

Get Expert Consultation

Share Your Business Requirement

Instant Response 100% Confidential Expert Advice

Encrypted in transit We do not sell your data

Trust Services Criteria
5
Month observation window
3 to 12
Common criteria covered
CC1 to CC9
Weeks of readiness work
8 to 12

Our partners & associations

Client RatingRazorpay TrustedZoho Partner
FAQs

Frequently asked questions about SOC 2 compliance

36 questions taken from real search queries, enterprise security questionnaires, AICPA guidance and the way examinations actually run.

The decision
A Type 1 reports on whether controls are suitably designed at a point in time. A Type 2 reports on whether those controls were suitably designed and operated effectively over a stated period, commonly 3 to 12 months. Enterprise buyers ask for Type 2, and most procurement teams treat a Type 1 as an interim signal rather than an answer. The practical sequence for a company starting from nothing is readiness, then a Type 1 if a deal needs something now, then a Type 2 covering the window that follows.
  • Type 1Design, at a point in time
  • Type 2Design and operation, across a period
  • Typical window3 months first, then 6 to 12
SOC 2 Type 1 compared with Type 2
DimensionType 1Type 2
What is examinedDesign of controls at a dateDesign and operating effectiveness across a period
Evidence requiredConfiguration and documentation as at the datePopulations and samples across the whole window
Time to reportWeeks after readinessWindow length plus 4 to 8 weeks of fieldwork
What buyers do with itAccepted as an interim step by someThe standard ask in enterprise procurement
Exceptions possibleDesign deficiencies onlyDesign and operating deviations, with management responses
Usual sequenceOptional first milestoneThe destination, repeated annually

The mistake that costs a quarter

Opening the observation window before the controls are genuinely running. Every deviation inside the window is inside the reported period, and no amount of later remediation removes it from the report. If access reviews, change approvals and offboarding are not yet operating consistently, spend the month fixing them first: a window that starts late still ends earlier than one that has to be re-run.

Why ProTax

Frequently asked questions about SOC 2 compliance

36 questions taken from real search queries, enterprise security questionnaires, AICPA guidance and the way examinations actually run.

Scope before spend

Criteria and system boundary fixed against what your buyer asked for, so you are not audited on promises you never made.

Controls that fit the team

Controls written to how your engineers actually work. A policy stricter than practice is the most reliable way to generate exceptions.

Evidence by design

Every control gets an owner, a cadence and a place where evidence lands, so the window produces proof instead of a reconstruction exercise.

Independent by construction

We prepare you; a licensed CPA firm examines you. We help you choose and brief that firm, and we never sign the report.

FAQs

Frequently asked questions about SOC 2 compliance vs the privacy laws

Key takeaway
SOC 2 is an attestation engagement, not a certification. An independent licensed CPA firm examines a service organisation's controls against the AICPA Trust Services Criteria and issues a report containing its opinion, management's system description, the controls, and in a Type 2 the tests performed and their results. The engagement runs under the AICPA attestation standards, AT-C sections 105 and 205, as amended by SSAE No. 21 for reports dated on or after 15 June 2022. The report is restricted-use: you share it with customers and their auditors under NDA, not on your website.
  • Framework ownerAICPA, Trust Services Criteria (TSP section 100)
  • Who signs itAn independent licensed CPA firm, never a consultant
  • Criteria in force2017 criteria with 2022 revised points of focus
  • DistributionRestricted use, shared under NDA; SOC 3 for public use

The distinction between attestation and certification matters more than it sounds. There is no accreditation body, no certificate number to verify, and no register to look you up in. What a buyer receives is a document with an auditor's opinion attached to your own description of your system. That is why two SOC 2 reports can look completely different: the scope, the criteria and the description are yours, and the opinion only speaks to what you put in them.

It also explains the way the market reads reports. A sophisticated buyer looks at the system boundary before the opinion, checks which criteria were included, notes the window length, and reads the exceptions and management responses. A report that covers a narrow slice of your platform for a one-month window answers less than it appears to.

ProTax security compliance team reviewing SOC 2 control evidence with an engineering lead Audit ready

What readiness produces

The deliverables below exist so that fieldwork is an audit of a working system rather than a scramble. They are also what a security questionnaire asks for months before any report exists.

  • Scope statement: criteria, system boundary, locations and subservice organisations
  • Gap assessment against the common criteria CC1 to CC9, with owners
  • Control matrix mapping each criterion to a control, an owner and its evidence
  • Policy set and the system description drafted to the description criteria
  • Evidence pipeline and a recurring control calendar
  • Internal test results, so nothing fails for the first time in fieldwork
FAQs

Frequently asked questions about SOC 2 compliance

36 questions taken from real search queries, enterprise security questionnaires, AICPA guidance and the way examinations actually run.

Trust Services Criteria categories and when to include them
CategoryWhat it coversInclude it when
Security (common criteria)Protection against unauthorised access, disclosure and damage: governance, risk assessment, access, operations, change management, risk mitigationAlways. Every SOC 2 includes it
AvailabilityThe system is available for operation and use as committed, including capacity, monitoring, backup and recoveryYou commit to uptime or a recovery objective in contracts or an SLA
Processing IntegrityProcessing is complete, valid, accurate, timely and authorisedThe accuracy of your output is the service, as in payments, payroll or analytics
ConfidentialityInformation designated as confidential is protected as committed, including retention and disposalYou hold customer confidential data under NDA or contractual confidentiality terms
PrivacyPersonal information is collected, used, retained, disclosed and disposed of in line with your privacy noticeA buyer specifically asks, and your privacy programme is already in place

Inside Security, the common criteria run from CC1 to CC9. CC1 to CC5 follow the COSO internal control framework: control environment, communication and information, risk assessment, monitoring activities and control activities. CC6 covers logical and physical access. CC7 covers system operations, including monitoring, incident response and vulnerability management. CC8 covers change management. CC9 covers risk mitigation, including vendor management. That structure is why a SOC 2 programme touches HR, engineering, IT and procurement rather than sitting in one team.

Adding Privacy is a bigger decision than it looks

The Privacy category examines your handling of personal information against your own privacy notice, which means the notice has to be accurate before it can be audited. Companies that add Privacy without a working privacy programme end up fixing notices, retention and rights handling under audit pressure. If the GDPR or the DPDP framework already applies to you, build that programme first and let the SOC 2 Privacy category follow it.

FAQs

Frequently asked questions about SOC 2 compliance vs the privacy laws

36 questions taken from real search queries, enterprise security questionnaires, AICPA guidance and the way examinations actually run.

Products and environments

Which product lines, which environments and which cloud accounts sit inside the boundary. Shared corporate infrastructure widens scope quickly.

People and locations

Every location where in-scope systems are operated or accessed, including Indian delivery centres, remote staff and contractors.

Subservice organisations

Cloud and platform providers are normally carved out, with the controls you expect them to operate named in your description.

User entity controls

Controls your customers must operate for yours to work, listed so the reader knows exactly where responsibility transfers.

Carve-out is the normal answer

Under the carve-out method, your cloud provider's controls sit outside your examination and its own SOC report is relied on, while your description names the controls you expect it to operate. The inclusive method pulls the provider into your engagement and needs its participation, which hyperscale providers do not give. Carve-out is not a weakness in your report; it is how the standard expects a modern stack to be described.

FAQs

Frequently asked questions about SOC 2 compliance

36 questions taken from real search queries, enterprise security questionnaires, AICPA guidance and the way examinations actually run.

Common SOC 2 controls, their evidence and the usual failure
Control areaEvidence the auditor samplesWhat usually goes wrong
Access provisioningJoiner tickets with approval, matched to identity provider recordsAccess granted in chat and approved later, or never
Access removalLeaver tickets with timestamps against last login and revocation recordsOffboarding that lags by days, especially for contractors
Periodic access reviewSigned review records per system, per periodA quarter skipped during a busy release cycle
Change managementChange tickets linked to merges, with approval and test evidenceHotfixes shipped outside the process with no retrospective ticket
Vulnerability managementScan output plus remediation records against your stated SLAFindings tracked in a spreadsheet with no closure dates
Incident responseIncident tickets showing detection, triage, resolution and reviewIncidents handled in a channel and never ticketed
Backup and recoveryBackup logs and a documented restore test in the periodBackups running, restores never tested
Vendor managementVendor list with risk ratings and review recordsNew sub-processors added without review
Security trainingCompletion records for all in-scope staffNew joiners missed between training cycles
Risk assessmentDocumented assessment with treatment decisions and datesOne assessment at the start, never revisited
Monitoring and alertingAlert-to-resolution trails for sampled alertsAlerts acknowledged with no record of what was done
Board or management oversightMinutes showing security matters reviewedOversight that happens verbally and is never minuted
FAQs

Frequently asked questions about SOC 2 compliance

36 questions taken from real search queries, enterprise security questionnaires, AICPA guidance and the way examinations actually run.

01

Find out what the buyer actually asked for

Some procurement teams accept a Type 1 as an interim step; others wait for a Type 2 with a stated window. The answer decides your timeline, your criteria and whether the window should open this quarter or after a month of control work.

02

Fix the criteria and the system boundary

Security is mandatory. Add Availability where you commit to uptime, Confidentiality where you hold data under NDA, Processing Integrity where accuracy is the service, Privacy only on request. Then draw the boundary: products, environments, teams, locations.

03

Run the gap assessment

Test the current state against CC1 to CC9 and any added categories, covering governance, risk assessment, logical and physical access, system operations, change management and risk mitigation. The output is a prioritised gap list with named owners.

04

Design controls that match how the team works

Write controls to the way your team operates, then tighten the operation, rather than writing an aspirational policy nobody follows. A control described more strictly than it runs is the most common source of exceptions in a Type 2.

05

Build the policy set and system description

Produce the policies the criteria expect: access control, change management, incident response, vendor management, business continuity, secure development and more. Draft the system description against the AICPA description criteria, since the opinion attaches to it.

06

Set up the evidence pipeline and control calendar

For every control, decide how evidence is produced, where it lives and who owns it: tickets with approvals, access review records, scan and remediation logs, restore tests, training records, vendor reviews. Put recurring controls on a calendar.

07

Select and brief the CPA firm

Only a licensed, independent CPA firm can perform the examination under AT-C 105 and 205. Compare proposals on scope, criteria, window length, fieldwork approach and reporting timeline, then brief the firm with your description and control matrix.

08

Test internally, then open the window

Run your own sample tests against every control before the window opens. Anything failing internally will fail in fieldwork, and a failure inside the window stays inside the reported period. Open the window only once controls have genuinely been running.

09

Operate through the observation period

Three months for a first Type 2, six to twelve once established. Operate the controls, collect evidence as it happens rather than reconstructing it later, and log every deviation with a management response so nothing surprises anyone in fieldwork.

10

Complete fieldwork and plan the next cycle

Support the auditor's sampling, answer requests quickly, and respond to exceptions with a remediation plan. Once the report is issued, open the next window immediately, keep controls running, and issue bridge letters to buyers who ask in the gap.

Find out how far you are from a clean Type 2

A readiness review maps your current controls against the common criteria, tells you which criteria belong in your report, and gives you the gap list with owners before any auditor is engaged.

FAQs

Frequently asked questions about SOC 2 compliance

36 questions taken from real search queries, enterprise security questionnaires, AICPA guidance and the way examinations actually run.

SOC 2 timing from readiness to the second annual report
StageTypical durationWhat is happening
Readiness8 to 12 weeksScoping, gap assessment, control design, policies, evidence pipeline, internal testing
Type 1 examination, if used2 to 4 weeksAuditor examines design at a point in time and issues the report
Observation window, first Type 23 monthsControls operate and evidence accumulates across the stated period
Observation window, mature cycle6 to 12 monthsContinuous coverage, with each window starting where the last ended
Fieldwork and reporting4 to 8 weeksSampling, testing, exceptions, management responses and report issuance
Practical report shelf lifeAbout 12 monthsBuyers expect a period ending within the last year
Bridge letter coverageUp to about 3 monthsManagement letter covering the gap between period end and today

Plan the window backwards from the deal

If a contract closes in June and the buyer wants a Type 2, a three month window has to open in roughly February, which means readiness starts in November. Teams that start when the buyer asks are always a quarter late. The cheapest fix is to open a window as soon as controls are running, even before a specific deal needs it, because an in-progress window is itself an answer procurement will accept.

FAQs

Frequently asked questions about SOC 2 compliance

36 questions taken from real search queries, enterprise security questionnaires, AICPA guidance and the way examinations actually run.

Section 1: the opinion

The auditor's conclusion, and whether it is unqualified or qualified. Read the scope paragraph with it: an opinion means nothing without the boundary it applies to.

Section 2: management assertion

Management's statement that the description is fair and the controls are suitably designed and, in a Type 2, operating effectively.

Section 3: system description

Services, infrastructure, people, procedures and data, plus subservice organisations and complementary user entity controls. This is what buyers scrutinise most.

Section 4: tests and results

Each control, the tests performed and their results, including exceptions and management responses. In a Type 1 this section does not exist.

Exceptions are not automatically a problem

A Type 2 with a small number of clearly explained exceptions and credible management responses reads better than a suspiciously spotless report over a one-month window. What damages trust is a pattern: the same control failing repeatedly, exceptions with no remediation date, or a scope so narrow that the interesting parts of the platform sit outside it.

FAQs

Frequently asked questions about SOC 2 compliance

36 questions taken from real search queries, enterprise security questionnaires, AICPA guidance and the way examinations actually run.

Produces a clean opinion

  • Controls written to match how the team actually works, then tightened deliberately
  • Access reviews on a calendar with a named owner, completed every period without exception
  • Change management that covers hotfixes, with a retrospective ticket where speed demanded it
  • Evidence produced as a by-product of work: tickets, approvals and logs with dates attached
  • A restore test actually performed inside the window, not merely scheduled
  • Vendor reviews that happen when a vendor is added, not once a year in a batch
  • Deviations logged with a management response as they occur

Produces exceptions

  • Aspirational policies copied from a template that describe a company you are not
  • A window opened before controls were genuinely operating
  • Access reviews skipped in the busiest quarter, discovered during sampling
  • Offboarding evidence that cannot be tied to a leaving date
  • Screenshots with no timestamps, offered where a ticket population was requested
  • New sub-processors added mid-window with no review record
  • Scope quietly widened by a new product without updating the description
FAQs

Frequently asked questions about SOC 2 compliance vs the privacy laws

36 questions taken from real search queries, enterprise security questionnaires, AICPA guidance and the way examinations actually run.

SOC 2, ISO 27001 and the privacy frameworks compared
DimensionSOC 2ISO 27001GDPR and DPDP
What it isAn auditor's report on controlsA certifiable management system standardStatutory obligations
Who signs offA licensed CPA firmAn accredited certification bodyNobody: you evidence compliance yourself
OutputRestricted-use report, shared under NDAA certificate valid three years with surveillance auditsAn evidence pack you produce on demand
Scope defined byYour system description and chosen criteriaYour ISMS scope statement and statement of applicabilityThe personal data you actually process
Time to first resultReadiness plus window plus fieldworkTypically 4 to 8 months to certification4 to 8 weeks for a first programme
Preferred byNorth American technology buyersEuropean and global enterprise buyersRegulators, and any buyer handling personal data
RecursAnnually, by windowSurveillance annually, recertification every three yearsContinuously, reviewed on change

The overlap is real but partial. One risk assessment, one access review process, one change workflow and one evidence pipeline can serve SOC 2 and ISO 27001 at once. Neither, however, gives you a lawful basis, a privacy notice, a data processing agreement or an EU transfer file, which is why companies selling into Europe run a GDPR programme alongside rather than instead.

FAQs

Frequently asked questions about SOC 2 compliance

36 questions taken from real search queries, enterprise security questionnaires, AICPA guidance and the way examinations actually run.

Service organisation
The entity being examined, providing services to user entities. In a SOC 2 that is your company, and the report describes the system through which those services are delivered.
User entity
Your customer: the organisation using your service, whose management and auditors are the intended readers of the report.
Subservice organisation
A vendor you rely on to deliver the service, typically a cloud or platform provider. Normally carved out of your examination, with its own SOC report relied on.
Common criteria
Criteria CC1 to CC9, the Security category present in every SOC 2. CC1 to CC5 follow the COSO framework; CC6 to CC9 cover access, operations, change and risk mitigation.
Points of focus
Illustrative considerations published with the criteria that describe characteristics of controls meeting them. The 2022 revision updated them for cloud infrastructure, remote working and current threats without changing the criteria.
Observation window
The stated period a Type 2 report covers, during which controls must operate and evidence must accumulate. Commonly three months for a first report, then six to twelve.
Exception
A test result showing a control did not operate as described. Reported with management's response, and material only when it forms a pattern or goes unremediated.
Restricted use
The distribution limit on a SOC 2 report: management, customers and their auditors, under NDA. Public distribution requires a SOC 3 derived from the same examination.
FAQs

Frequently asked questions about SOC 2 compliance

36 questions taken from real search queries, enterprise security questionnaires, AICPA guidance and the way examinations actually run.

FAQs

Frequently asked questions about SOC 2 compliance

36 questions taken from real search queries, enterprise security questionnaires, AICPA guidance and the way examinations actually run.

SOC 2 is an attestation report in which an independent licensed CPA firm examines and reports on a service organisation's controls against the AICPA Trust Services Criteria for security and, where included, availability, processing integrity, confidentiality and privacy.
No. SOC 2 is an attestation engagement, not a certification. Nobody issues a SOC 2 certificate, and no body accredits companies as SOC 2 certified. The output is a report containing the auditor's opinion, your system description, the controls and, in a Type 2, the tests performed and their results, which you share under NDA.
Only a licensed CPA firm, independent of the company being examined. The engagement is performed under the AICPA attestation standards, AT-C sections 105 and 205, as amended by SSAE No. 21 for reports dated on or after 15 June 2022. Consultants can prepare you for the audit but cannot sign the report.
No, and no consultant can. We do the readiness work: scoping, gap assessment, control design, policy and evidence build, tooling, and coordination with the CPA firm that performs the examination. Separating the two roles is a requirement of auditor independence, not a commercial preference.
Security, also called the common criteria and mandatory in every SOC 2; Availability; Processing Integrity; Confidentiality; and Privacy. You pick which of the other four to include based on what you promise customers. Most first reports cover Security alone, or Security with Availability and Confidentiality.
Start with what your contracts already promise. If you commit to uptime, Availability belongs in. If you handle customer confidential data under NDA, Confidentiality belongs in. Privacy is the heaviest category and is usually deferred unless a buyer specifically asks, because it overlaps with your GDPR or DPDP work rather than replacing it.
A Type 1 reports on whether controls are suitably designed at a point in time. A Type 2 reports on whether they were suitably designed and operated effectively over a period, typically 3 to 12 months. Buyers ask for Type 2. Type 1 is useful as an interim milestone while the Type 2 window runs.
Commonly 3 months for a first Type 2 and 12 months once the cycle is established. Six months is a frequent compromise. A shorter window gets a report faster but gives the auditor less evidence, and some enterprise buyers explicitly ask for a 12 month period in later years.

Get the controls right, and the report follows

Our security compliance experts scope your criteria and system boundary, close the gaps against the common criteria, build the evidence pipeline, and hand you to a licensed CPA firm ready for the window.

FROM THE PROTAX LIBRARY

Recent Articles & Guides

Practical reading on business records, tax filings and the decisions that come with running a company.

Newsletter

Stay ahead on compliance, tax & business updates

Get selected business and compliance updates by email. Once a month, no spam.

  • 100% privacy
  • 1 email / month
  • Unsubscribe anytime
Contact ProTax
Chosen by individuals and businesses

Get Help With Your Business

Tell us what you need help with. Our team will review your enquiry and explain the next steps.

Free Consultation No Obligations Expert Advice
FREE Consultation Get Started @ ₹299 ₹0

Talk To ProTax

Share Your Business Requirement

Instant Response 100% Confidential Expert Advice
FREE Consultation Get Started @ ₹299 ₹0

Request a Free Quote

Share Your Business Requirement

Instant Response 100% Confidential Expert Advice
Get audit ready before the auditor arrives 8 to 12 weeks Scope