Arihant Global Ventures Inc. Machine-readable Markdown for this page: send Accept text/markdown, or open /guides/soc2-readiness-guide/index.md. Site overview for language models: /llms.txt. Full guide text: /llms-full.txt.

Canadian enterprise & public-sector advisoryPrincipal-led deliveryToronto, ON, Canada

Arihant Global Ventures Inc.
Discuss an Assessment
← All guides

Guide · October 1, 2026 · 12 min read

SOC 2 Readiness: A Practical Guide for Growing Technology Companies

What SOC 2 actually requires: trust services criteria, Type I vs Type II, scoping, evidence collection, common gaps, and a realistic timeline.

ComplianceSecuritySOC 2

Most growing technology companies first hear about SOC 2 when a deal stalls on it. A prospect’s security team asks for your SOC 2 Type II report, you do not have one, and the sales cycle adds six to twelve months while you start from zero. The companies that get through it fastest understand what SOC 2 actually is before they begin — the process rewards the already-disciplined and punishes the theatrical. This guide is written from the achiever’s side: the technology company preparing for its own SOC 2 engagement. (If you are on the buying side, assessing a supplier’s security posture, see our vendor security review guide; the two perspectives are different disciplines.)

Note that this is general information, not legal or audit advice; your auditor will set the requirements for your specific engagement.

What SOC 2 is — and is not

SOC 2 (System and Organization Controls 2) is an attestation engagement performed by an independent licensed auditor (a CPA firm) against the AICPA’s Trust Services Criteria. The auditor examines the controls your organization operates to protect customer data and the systems that handle it, then issues a report expressing an opinion on whether those controls were suitably designed and, for Type II, operated effectively.

Three things SOC 2 is not. First, it is not a certification. Nobody “gets SOC 2 certified.” You receive a report with an auditor’s opinion; there is no certificate and no logo-licensing program run by the AICPA. Second, it is not a security rating. SOC 2 reports on whether your controls operate as you described them; it does not say your controls are the right ones for every threat. Third, it is not a one-time project. The report covers a period, and the controls have to keep operating after the period ends, or the next report fails.

Who asks for it and why: enterprise and mid-market buyers increasingly require a SOC 2 Type II report before signing contracts that involve their data. It is a procurement shortcut — a standardized, auditor-backed way for a buyer to conclude your control environment exists without running a full security assessment themselves. Without it, every enterprise deal carries a bespoke security review; with it, many of those reviews shrink or disappear.

The five trust services criteria

The AICPA defines five Trust Services Criteria (TSC). Every SOC 2 engagement covers Security — the common criteria — and may additionally cover one or more of the others depending on what the business commits to its customers.

Security (CC series). The baseline. Controls that protect systems against unauthorized access, use, or modification. Logical access controls, authentication, encryption in transit and at rest, network protections, vulnerability management, incident response, change management. Every SOC 2 includes the common criteria; you cannot opt out of security.

Availability (A series). Controls around system availability as committed to customers — uptime, capacity planning, backup and recovery, failover, performance monitoring. Include this criterion only if you actually make availability commitments in contracts or service-level agreements. Adding availability because it “sounds good” invites the auditor to test disaster recovery and capacity planning in depth, which is expensive if you were not operating those controls already.

Processing integrity (PI series). Controls that processing is complete, valid, accurate, timely, and authorized. Relevant for platforms where customers rely on your processing being correct — billing engines, payroll systems, transaction processors. If a calculation error in your product is a customer-facing incident, processing integrity belongs in scope.

Confidentiality (C series). Controls protecting information designated as confidential — classification schemes, handling of customer data, encryption, non-disclosure enforcement. Often relevant alongside security when customer data includes trade secrets or proprietary information beyond personal data.

Privacy (P series). Controls around the collection, use, retention, disclosure, and disposal of personal information — consent, notice, data-subject rights, retention schedules. Privacy is the most demanding criterion to add because it reaches into product design and data governance, not just IT controls. Add it when you process personal data in ways customers scrutinize, and read our AI governance guide for the data-lineage and audit-trail discipline that underpins it.

The practical guidance: start with security plus only the criteria that match real customer commitments. You can expand the criteria in a later period. An engagement that covers everything on the first pass is an engagement that takes longer, costs more, and fails more often.

Type I vs Type II: design vs operating effectiveness

Type I reports on a point in time: the auditor examines whether your controls are suitably designed to meet the criteria as of a specific date. It answers “did you design good controls?” It says nothing about whether anyone followed them.

Type II reports on operating effectiveness over a period of time — typically 6 to 12 months. The auditor tests whether the controls actually operated as designed throughout that period, sampling evidence across the whole window. It answers “did the controls actually work, consistently, for months?”

The market reality: Type I has limited commercial value. Most enterprise buyers require Type II specifically; a Type I report reads as “we wrote policies last month.” A common strategy is a short Type I to find design gaps quickly, followed by a Type II observation period — but budget and plan for the Type II, because that is the report that unblocks deals.

The observation period is the crux of the timeline. You cannot compress it: the auditor must sample evidence across the full period. A six-month minimum is typical for a first Type II, with twelve months becoming standard for established programs. The clock starts when your controls are actually operating — policies written, evidence being collected — not when you sign the auditor’s engagement letter. Every gap you discover mid-period that requires a control change can reset parts of the clock.

Scoping the audit

The system description — the narrative section of the report that describes your organization, its services, and its boundaries — is the most important scoping document in the engagement. It defines what the auditor examined and, implicitly, what the report says nothing about.

Scope deliberately and keep it tight. Include the production systems, infrastructure, and processes that directly support the service your customers buy. Exclude early experiments, internal tooling that touches no customer data, and product lines that no buyer is asking about. Every system in scope adds controls to test and evidence to collect. A growing SaaS company with one flagship product should scope the production environment for that product and the corporate systems that administer it — not the marketing website, not the internal wiki, not the data-science sandbox.

Two scoping decisions trip people up. First, infrastructure scope: if you run on a major cloud provider, their SOC 2 covers the physical infrastructure and hypervisor layer, and you inherit that through their report — you do not re-audit the cloud provider’s data centers. Your responsibility is everything above that line: your configurations, your identities, your data. Second, subservice organizations and the carve-out method: if you depend on a vendor (a payment processor, an identity provider, a managed database), you can “carve out” their controls and reference their own SOC 2 report — but your auditor will verify those vendor reports exist and that you monitor them. Unmonitored carve-outs are a common audit finding.

The control inventory and evidence discipline

A SOC 2 engagement typically involves 60 to 120 individual controls, each mapped to the trust services criteria. The discipline is not writing the controls — it is the evidence: for each control, for the entire observation period, you must produce proof that it operated.

Common evidence types, with the controls they support:

  • Access reviews. Quarterly reviews of who has access to what, signed by the system owner, with deprovisioning tickets for the leavers found. This is the single most failed control in first engagements — not because companies lack access controls, but because the review was informal, undocumented, or skipped a quarter.
  • Change tickets. Every production change linked to a ticket with approval, testing evidence, and rollback consideration — including emergency changes, documented after the fact with a post-implementation review. The control is not “we are careful”; it is “here is the record for each of the 340 changes in the period.”
  • Vulnerability scans and remediation. Periodic scan reports with remediation timelines per severity. Auditors check that critical findings were remediated within the policy window — a scan that found criticals and a ticket closed six months later is a failed control.
  • Incident records. Every incident in the period with classification, response actions, and lessons learned — including the ones that turned out to be nothing. A period with zero recorded incidents makes an auditor suspect you do not detect incidents, not that you had none.
  • Background checks and onboarding records. Evidence that hiring controls operated for employees who joined during the period: background check results, signed acceptable-use policies, day-one access provisioning following the standard process.
  • Vendor reviews. Annual reviews of critical vendors: their SOC 2 or security posture, contract terms, and approval to continue.

The evidence discipline has one rule that matters: controls operate on a cadence, and the evidence is collected on the cadence, not at the end. Quarterly access reviews cannot be reconstructed in December for the whole year — the auditor samples across the period, and a backfilled review is detectable and disqualifying. Build the collection into operations: calendar the reviews, automate the exports, assign owners. Companies that treat evidence collection as a quarterly 15-minute habit pass; companies that treat it as an end-of-period project fail.

Common gaps

First-time engagements fail or stall on the same handful of gaps. Audit yourself against these before the observation period starts.

Access reviews. Covered above; the usual gap is reviews that happened but were never documented with a sign-off, or leaver accounts discovered months after departure. Fix: quarterly calendar, owner sign-off, automated HR-to-identity-feed if you can.

Change management. The usual gap is changes deployed outside the ticket process — hotfixes, infrastructure tweaks, vendor console changes. Fix: make the ticket the path of least resistance, and define the emergency-change path explicitly so it is used instead of bypassed.

Vendor management. The usual gap is no inventory of vendors with access to customer data, no review of their security posture, and no contract language on incident notification. Fix: list every vendor that touches production data or production systems, classify by criticality, and review annually.

Incident response. The usual gap is a policy that says “we will respond” with no defined severity levels, no tabletop exercise ever run, and no incident records. Fix: write the playbook, define severities, run a tabletop, and start recording everything.

Risk assessment. The usual gap is never having performed a formal risk assessment — the auditor expects the organization to have identified its risks and designed controls against them. Fix: run one before the period starts, even a lightweight one, and keep the document.

Encryption and key management. The usual gap is encryption enabled but unmanaged — unknown who holds the keys, no rotation, TLS certificates expiring in production. Fix: document the key lifecycle.

Selecting an auditor

The auditor must be a licensed CPA firm — this is an AICPA attestation, not a consultancy deliverable. Beyond that:

  • Independence. The firm that helped you implement controls cannot audit them. If you hire a readiness consultant, they must be a different firm from the auditor. This is a hard rule, not a preference.
  • Experience with your profile. A firm that audits hundreds of SaaS companies will have template control sets, calibrated expectations, and efficient fieldwork. A generalist local firm doing its first SaaS SOC 2 will learn on your engagement and your timeline.
  • Fit on scoping judgment. In the selection conversation, ask how they would scope your environment. A good auditor asks about your systems before opining; a bad one quotes a price without understanding the business.
  • Timeline realism. Ask for the fieldwork schedule and report delivery date in writing. Reports take 4–8 weeks after the observation period ends to draft, review, and issue. Factor that into deal timelines — the report is not available the day the period closes.

Realistic timeline and cost drivers

A realistic first Type II timeline for a company starting from reasonable-but-undocumented operations:

  • Months 1–2: Readiness assessment and scoping. Gap analysis, control design, auditor selection, system description drafted.
  • Months 3–4: Remediation. Close the gaps — stand up the cadences (access reviews, change process, vendor reviews, incident playbook), deploy tooling, write the policies that were missing. The observation period clock starts when controls are operating.
  • Months 5–10: Observation period (6 months minimum). Evidence collected continuously. Expect interim check-ins with the auditor.
  • Months 11–12: Fieldwork and report issuance. Evidence testing, management responses to any exceptions, report drafting and partner review.

Twelve months end to end is normal; nine is fast; eighteen means something went wrong mid-period. The variables that compress it are pre-existing discipline (you already did access reviews) and a tight scope. The variables that stretch it are scope creep, mid-period control changes, and evidence gaps discovered in month five.

Cost drivers: auditor fees scale with scope (criteria included, systems in scope, number of controls) and organizational complexity. Readiness consulting — a different firm doing the gap assessment before the observation period, worth it for first-timers — is a separate cost. Tooling (identity management, ticketing, vulnerability scanning, logging) is often the hidden line item. The largest cost, rarely budgeted, is internal time: expect a meaningful fraction of one person’s year plus recurring hours from engineering, IT, HR, and leadership across the period.

Sustaining compliance after the report

The report is issued, the deals unblock, and then the dangerous part begins: the organization relaxes, the cadences slip, and the next observation period — which starts the day after the last one ended — accumulates gaps. Sustaining compliance is cheaper than re-achieving it.

  • Keep the cadence calendar. Access reviews, vendor reviews, risk assessment refresh, policy reviews, tabletop exercises — all scheduled, owned, and evidenced as they happen.
  • Onboard new systems into the control set. Every new production system, vendor, or data flow gets assessed against the control inventory before it handles customer data.
  • Track auditor feedback. Management-letter comments and prior-period exceptions are the remediation backlog for the next period. Close them early.
  • Treat the report as a product. Buyers will ask for it under NDA; have a process for sharing it and tracking versions. Know your renewal date and work backward from it.

SOC 2 readiness is, at bottom, an operations project wearing an audit costume. The companies that pass on schedule are not the ones with the best policies — they are the ones whose controls were already operating, on a cadence, with evidence, before the auditor arrived. Start the cadences now; the report follows.

Start with a conversation.

A free 30-minute introduction to discuss your AI governance challenge, constraints, and whether we can help. No project brief required.

Contact us for current availability. Scope, timing, and fees are agreed before paid work begins.