A SOC 2 examination is an independent audit, performed by a licensed CPA firm under standards set by the American Institute of Certified Public Accountants (AICPA), that evaluates whether a service organization’s internal controls actually protect the client data it handles.1AICPA & CIMA. System and Organization Controls: SOC Suite of Services The examination produces a detailed, restricted-use report that clients, prospects under NDA, and regulators use to judge whether the organization’s security promises hold up in practice. Cloud providers, payroll processors, managed IT firms, and other companies that touch customer data pursue these reports because enterprise buyers increasingly refuse to sign contracts without one.
Type 1 or Type 2
The first real decision is which flavor of report to pursue. A Type 1 examination looks at the organization’s controls as of a single date and confirms they are designed to meet the selected criteria. It proves you had the right controls in place on a specific Tuesday.
A Type 2 examination tests whether those same controls operated effectively over a stretch of time. The observation window runs from three months to a full year, and twelve months is the standard enterprise clients and government agencies expect. First-time Type 2 reports sometimes cover a shorter three-to-six-month window and then extend to twelve months in later cycles.
Most organizations start with a Type 1 to establish a baseline and transition to a Type 2 within a few months. A single-day snapshot rarely satisfies buyers making significant commitments, because it says nothing about how the controls hold up day after day under real conditions.
What Gets Tested: The Five Trust Services Criteria
Every SOC 2 examination is scoped around the AICPA’s Trust Services Criteria.2AICPA & CIMA. 2017 Trust Services Criteria With Revised Points of Focus 2022 Security is mandatory in every report and is sometimes called the “common criteria.” The other four are optional and included only when they match the services the organization provides.
- Security covers protection against unauthorized access, including firewalls, multi-factor authentication, and intrusion detection.
- Availability looks at uptime monitoring, disaster recovery, and the ability to recover from outages against service-level commitments.
- Processing integrity examines whether the system processes data completely, accurately, and on time. It applies to organizations running calculations, transactions, or automated workflows for clients.
- Confidentiality addresses protections for information the organization has agreed to keep restricted, such as intellectual property or data shared under NDA.
- Privacy focuses on personal information and whether it is collected, used, stored, and disposed of consistent with the organization’s published privacy notice.
Choosing the optional criteria is a real strategic call. Too few and the report loses value with prospective clients; too many and audit scope and cost expand for no return. Most SaaS companies begin with security and availability, then add confidentiality or privacy as the client base demands it.
Readiness Assessment
Going straight into a formal audit without a readiness assessment is where companies waste the most money. The readiness assessment is a practice run: the organization examines the same controls the auditor will test, but with time to remediate before anything ends up in a published report.
During readiness, the organization confirms which criteria apply, inventories existing controls, and maps them against what the criteria require. Gaps surface early. Discovering a missing quarterly access review during readiness is a small project. Discovering it during fieldwork produces an exception that prospective clients will scrutinize.
For a Type 2, starting the readiness assessment twelve to eighteen months ahead of the target report delivery date is realistic. That runway allows time to implement any new controls, let them operate through the observation window, and finish audit fieldwork on schedule. Skipping this step is how organizations end up with qualified opinions or have to restart the process.
How the Audit Actually Works
Once documentation is finalized, the auditor begins fieldwork. Before fieldwork starts, the organization must produce final versions of its information security policies, incident response plan, access control procedures, and change management processes. Drafts don’t count. Alongside those policies sits the system description, a narrative that explains the environment to the auditor and to anyone who later reads the report, and defines the boundary around exactly which components are in scope.
Fieldwork itself is evidence-based, not policy-based. If the organization claims it reviews user access quarterly, the auditor will ask for the last four reviews and confirm they happened. If policy says terminated employees lose access within 24 hours, the auditor samples termination records against access logs. Evidence is uploaded through a secure portal: log files, configuration screenshots, access review records, training documentation. This is what separates a SOC 2 from a self-assessment.
Communication runs throughout. Auditors ask for context on unusual findings and request supplementary evidence when needed. If a gap surfaces and gets remediated before the period ends, the auditor will test the remediated control, though the original gap may still appear in the report depending on how long it lasted.
At the end of fieldwork, the organization’s leadership signs a management representation letter required under AT-C Section 205, affirming that the system description is accurate and that all relevant information has been disclosed.3AICPA & CIMA. Illustrative Management Representation Letter: SOC 2 Type 2 The auditor drafts the report, and it goes through the firm’s internal quality review before issuance.
The Auditor’s Opinion
The opinion page is the report’s headline. Three outcomes are possible.
- An unqualified opinion is the clean result: controls were designed properly and operated effectively throughout the period.
- A qualified opinion means some objectives or commitments were not met. It may be limited to specific controls, but prospective clients will ask pointed questions about what went wrong.
- An adverse opinion indicates widespread, material failures. This is rare because most organizations pause and remediate rather than allow one to publish.
Testing exceptions are not the same thing as a qualified opinion, and this distinction confuses first-time auditees. An exception is a single instance where a control didn’t work as intended, such as one missed access review or one late patch. Exceptions are common. The auditor evaluates whether they are isolated incidents or part of a pattern. A handful of exceptions in an otherwise strong report typically ends in an unqualified opinion with the exceptions noted in the detailed testing section.
Subservice Organizations and User Controls
Nearly every service organization relies on third parties for part of its stack: cloud hosting, data centers, payment processors. When those third parties directly affect the organization’s ability to meet its criteria, they are subservice organizations, and the report has to address them one of two ways.
The carve-out method excludes the subservice organization’s controls from audit scope. The system description identifies the third party and its role, and the organization is expected to review that vendor’s own SOC 2 annually. Most SOC 2 reports use this method because it keeps scope manageable and does not require a vendor to cooperate with someone else’s audit.
The inclusive method pulls the subservice organization’s controls into scope and tests them directly, with results appearing in the report. This requires the vendor to provide a written assertion and representation letter. It makes sense when the third party’s controls are deeply intertwined with the service or when the vendor has no SOC 2 of its own, but scope, cost, and vendor cooperation risk all rise.
Complementary user entity controls (CUECs) are the opposite side of the picture. These are controls the service organization expects its clients to implement, such as strong password policies for user accounts. The report identifies these expectations, and clients reading the report should confirm their own controls satisfy them. CUECs are easy to overlook, and ignoring them leaves a gap that neither side has covered.
Cost
Costs vary widely based on company size, number of criteria in scope, and the tier of the audit firm.
For a small company with fewer than 50 employees, a Type 1 typically runs $12,000 to $30,000, and a Type 2 runs $15,000 to $45,000. Mid-size organizations with 50 to 200 employees generally pay $20,000 to $60,000 for a Type 1 and $30,000 to $90,000 for a Type 2. Large enterprises can spend well into six figures, with Big Four Type 2 fees reaching $450,000.
Those figures cover the audit itself. Internal labor for documentation, remediation work identified during readiness, and any compliance automation platform the organization subscribes to typically push total first-year investment 50 to 100 percent above the audit fee alone.
Timeline
How long the process takes depends heavily on prior experience. A Type 1 for a well-prepared company can finish in two to three months. A first-time Type 2 with a twelve-month observation window takes roughly a year from the start of the observation period, plus six to twelve weeks of pre-audit preparation and three to six weeks for report drafting and quality review.
The preparation phase is where organizations miss their target dates. Writing policies, implementing new controls, and collecting evidence take longer than most teams estimate, and the observation window cannot begin until the controls are actually in place.
Keeping the Report Current
A SOC 2 report is not a permanent credential. Type 2 reports are expected to renew annually, and clients increasingly treat any report older than twelve months as stale. A missed renewal creates a coverage gap that can stall sales cycles and prompt uncomfortable conversations with clients who require continuous compliance evidence.
When a gap between reports is unavoidable, a bridge letter provides temporary cover. Also called a gap letter, it is written by the organization, not the CPA firm, and states that controls have not materially changed since the last report. Industry practice caps bridge letters at three months of coverage. A useful bridge letter lists the validity dates of the previous audit, the specific dates it covers, the CPA firm that performed the last examination, any changes to controls since the report, and a confirmation that the prior report still reflects the current environment. Using bridge letters as a routine substitute rather than a stopgap is a signal experienced clients notice.
Beyond the annual renewal cycle, staying compliant means treating controls as living systems. Policies need updates when the technology stack changes. Access reviews need to happen on schedule regardless of whether an auditor is watching. Evidence collection works best as an ongoing practice rather than a scramble in the weeks before fieldwork begins. Organizations that automate evidence collection and continuously monitor their controls spend far less on each renewal than those treating SOC 2 as an annual fire drill.