🇺🇸 United States · Framework guide

SOC 2: what it is, what auditors test and how to get a clean report

SOC 2 is the attestation that North American customers ask every SaaS and service provider for. It is not a certification and there is no pass mark; it is an independent auditor’s opinion on whether your controls meet the Trust Services Criteria you chose. This guide explains the criteria, the report types, the realistic timeline and what to automate.

OwnerAmerican Institute of Certified Public Accountants (AICPA)
FrameworkTrust Services Criteria (TSC) 2017, with 2022 revised points of focus
CategoriesSecurity (required, common criteria CC1–CC9), Availability, Processing Integrity, Confidentiality, Privacy
Report typesType 1: design at a point in time. Type 2: design and operating effectiveness over a period, typically 3–12 months
Who issues itA licensed CPA firm; the report is restricted-use for customers and prospects under NDA
RenewalAnnually, with a bridge letter covering the gap between reports

A SOC 2 report describes your system, lists the controls you say you operate, and records the auditor’s tests of each one. Customers read the exceptions section first. The work, therefore, is to define controls you can actually operate every day for the whole observation period, and to generate the evidence automatically so nothing is missed in month nine.

Security is mandatory and is where most of the criteria live. The other four categories are added when customers ask: Availability for uptime commitments, Confidentiality for sensitive customer data, Processing Integrity for transaction systems, Privacy for personal information handled under your own notice.

The common criteria, in plain terms

CC1 Control environment

Integrity and ethics, board oversight, organisational structure, competence and accountability. Policies, org charts, background checks, training records.

CC2 Communication and information

Security policies communicated internally; commitments and system changes communicated to customers.

CC3 Risk assessment

A documented risk assessment, including fraud risk and changes to the business, updated at least annually.

CC4 Monitoring

Ongoing evaluation of controls, with deficiencies reported and remediated.

CC5 Control activities

Controls selected and deployed to address the risks, including over technology and through policies and procedures.

CC6 Logical and physical access

The largest section: identity and access management, MFA, provisioning and deprovisioning, encryption, physical access, removal of data and endpoints.

CC7 System operations

Vulnerability management, monitoring, incident detection and response, recovery.

CC8 Change management

Changes to infrastructure and software are authorised, tested, approved and documented.

CC9 Risk mitigation

Business disruption risk and vendor and business partner risk, including vendor assessments and contracts.

The timeline

  1. Readiness (4–8 weeks). Scope the system and categories, map existing controls to the criteria, write missing policies, fix gaps.
  2. Type 1 (optional). A point-in-time report that proves control design. Useful to unblock a deal while the Type 2 window runs.
  3. Observation period (3–12 months). Controls operate and evidence accumulates. A first Type 2 is often run over 3 or 6 months; customers prefer 12.
  4. Audit and report (4–8 weeks). Auditor samples evidence, tests controls, drafts the report; management responds to exceptions.

Who it applies to

Any service organisation whose customers rely on its controls: SaaS vendors, hosting and managed service providers, payroll and HR platforms, data processors and fintechs. In practice, enterprise procurement in the US and Canada will not progress without a SOC 2 Type 2 or an ISO 27001 certificate, and often asks for both.

How GRCorb covers SOC 2

From scope to evidence, in one system

Scope by category, controls generated

Select Security plus any additional categories and GRCorb produces the control set, mapped to the criteria and points of focus, with owners and test frequencies.

Evidence that collects itself

Read-only adapters for AWS, Azure, Google Cloud, GitHub, GitLab, Okta, Microsoft Entra ID, Intune, Jamf, CrowdStrike and more pull the configuration and activity evidence the auditor samples, timestamped and hash-sealed, with fresh, stale and missing status throughout the observation period.

An Auditor Workspace

Your CPA firm gets a scoped workspace to request, review and accept evidence against each criterion, which shortens fieldwork and keeps requests out of your inbox.

Policies written for the TSC

The AI Policy Builder generates the policy set SOC 2 auditors expect, branded and versioned, with employee acknowledgement tracked.

Vendor risk for CC9

The third-party module tiers vendors, collects their SOC reports and tracks review dates, which is the evidence for the vendor criteria.

Frequently asked questions

Type 1 or Type 2?

Customers want Type 2. Do a Type 1 only if a deal depends on showing something before the observation window has run. Many organisations skip it and go straight to a 3-month Type 2.

How long does a first SOC 2 take?

Six to twelve months from start to a Type 2 report: a few weeks of readiness, a 3–6 month observation period, then the audit. Automated evidence collection removes most of the readiness and fieldwork time.

SOC 2 or ISO 27001?

SOC 2 for North American customers; ISO 27001 for international, government and regulated ones. The controls overlap heavily, so GRCorb maps them and reuses evidence; most companies selling globally end up with both.

Do we need all five categories?

No. Security is mandatory; add Availability if you give uptime commitments and Confidentiality if you hold sensitive customer data. Processing Integrity and Privacy are added when customers specifically ask.

Related frameworks

Reviewed November 2026. This guide is general information about the published framework and is not legal advice; always check the current official text from the publisher before relying on it.