What Is a SOC Examination and How Does It Work?

A SOC examination is an independent audit of a service organization’s internal controls, performed by a licensed CPA firm under standards set by the American Institute of Certified Public Accountants (AICPA). It produces a formal report telling clients and their auditors whether the organization’s systems and safeguards actually work the way management claims.1AICPA & CIMA. System and Organization Controls: SOC Suite of Services For companies that handle data, process transactions, or run technology on behalf of other businesses, having a current SOC report has become a near-universal condition of doing business.

The Report Types and Which One You Need

The AICPA offers several SOC report types. The right one depends on what your service touches and who is asking for assurance.

SOC 1

A SOC 1 report focuses on controls that could affect a client’s financial reporting. If your organization processes payroll, handles insurance claims, or performs any function that feeds into someone else’s financial statements, this is the report clients will ask for. SOC 1 examinations are performed under AT-C Section 320 of the AICPA’s attestation standards, and the primary audience is your clients’ external auditors.

SOC 2

A SOC 2 report takes a broader look at how you protect data and keep systems running. It evaluates controls against up to five Trust Services Criteria: security, availability, processing integrity, confidentiality, and privacy. SOC 2 reports are restricted-use documents. They can be shared with management, existing clients, and prospective clients performing due diligence, but not posted publicly.2AICPA & CIMA. SOC 2 Reporting on an Examination of Controls at a Service Organization Relevant to Security, Availability, Processing Integrity, Confidentiality, or Privacy

SOC 3

A SOC 3 covers the same Trust Services Criteria as a SOC 2 but produces a general-use summary suitable for public distribution. Organizations that want to display compliance on a website use this version. It leaves out the detailed control descriptions and test results found in a SOC 2.

Specialized Frameworks

Beyond the core three, the AICPA offers SOC for Cybersecurity, which evaluates an enterprise-wide cybersecurity risk management program rather than specific service controls,3AICPA & CIMA. SOC for Cybersecurity and SOC for Supply Chain, which examines controls over production, manufacturing, or distribution systems.4AICPA & CIMA. SOC for Supply Chain

Type I vs. Type II

SOC 1 and SOC 2 examinations both come in two varieties, and the difference matters more than most first-timers realize.

A Type I report evaluates whether controls are properly designed at a single point in time. It is essentially a photograph of the control environment on one day. The auditor reviews each control and determines whether it is capable of meeting its objective, but does not test whether it actually worked consistently. Type I reports are common for a first examination because they establish a baseline without requiring months of operating history.

A Type II report is the version most clients want. It evaluates both the design and the operating effectiveness of controls over a defined period. The minimum observation window is three months, though standard practice extends this to a full twelve months after the first cycle to avoid coverage gaps between reports. During the observation period, the auditor tests whether controls functioned as intended throughout the entire window, not just on a good day.

The practical difference is significant. A Type I tells a client the controls look like they should work. A Type II tells them the controls actually worked, consistently, for months. Most enterprise clients and regulated industries require the Type II version for vendor approval.

The Five Trust Services Criteria

SOC 2 and SOC 3 examinations evaluate controls against the Trust Services Criteria, a framework maintained by the AICPA’s Assurance Services Executive Committee. The current version dates to 2017 with revised points of focus published in 2022.5AICPA & CIMA. 2017 Trust Services Criteria with Revised Points of Focus 2022

Security is the only category required in every SOC 2 examination. Often called the Common Criteria, it evaluates whether systems are protected against unauthorized access and damage. The remaining four categories are included only when relevant to the services you provide:

  • Availability: whether the system is operational and accessible as promised in service level agreements.
  • Processing integrity: whether the system processes data completely, accurately, and on time.
  • Confidentiality: whether information designated as confidential is properly protected from inappropriate disclosure.
  • Privacy: whether personal information is collected, used, retained, and disposed of in line with the organization’s privacy commitments.

A cloud hosting provider would almost certainly include availability and confidentiality alongside security. A company that collects consumer personal data would add privacy. The selection defines what the auditor will test, and clients in regulated industries often expect specific categories to be covered.

How the Examination Works

Readiness Assessment

A readiness assessment is an optional but strongly recommended first step, especially for organizations approaching their first examination. The auditor performs a gap analysis comparing existing controls against the Trust Services Criteria you plan to include. The process moves through scoping, walkthrough meetings with control owners, evidence collection, and a gap report identifying what needs to change before the formal audit begins.

The deliverable from a readiness assessment is for internal use only. No opinion is issued and no report is distributed to clients. Gaps found here are opportunities to fix problems quietly rather than having them documented in a formal report. Organizations that skip this step and go directly to a Type II examination sometimes discover control gaps midway through the observation period, when it is too late to remediate without restarting the clock.

Documentation and Scoping

Once scope is defined, the organization prepares two foundational documents that will end up in the final report. The system description is a narrative explaining the infrastructure, software, people, and procedures involved in delivering the service. Management also produces a formal assertion stating that the controls described are suitably designed and operating effectively.

Gathering evidence for the auditor means compiling access control logs, change management records, incident response documentation, employee training records, and written policies covering each in-scope control area. Assigning clear ownership of each control internally matters because those individuals will be interviewed during fieldwork. Organizations that have not done this tend to produce inconsistent evidence and struggle during walkthroughs.

Fieldwork

Once preparation is complete, the CPA firm begins fieldwork. Auditors interview staff responsible for specific controls to confirm they understand the documented processes and follow them in practice. They also observe control activities directly, such as watching how a technician provisions user access or how the team responds to a security alert. The point is to verify that what happens in practice matches what the documentation claims.

For a Type II examination, the auditor tests whether each in-scope control functioned consistently throughout the observation period. This involves sampling transactions, reviewing logs, and examining evidence from multiple points during the window. Fieldwork can run from a few weeks to several months depending on complexity and the number of controls in scope. After testing, the auditor drafts the report and issues the formal opinion.

What the Report Contains

A completed SOC report is a structured document with five standard sections.

  • Auditor’s opinion. The most important section, sitting at the front. It states whether the controls met their objectives and identifies any material exceptions.
  • Management’s assertion. A formal statement from the service organization claiming that the system description is accurate and that controls were suitably designed and operating effectively.
  • System description. A detailed narrative of the infrastructure, software, people, procedures, and data involved in delivering the service. This section defines the boundaries of what the audit covered.
  • Control testing and results. A detailed accounting of each control tested, the testing methods used, and the outcomes. In a Type II report, this shows whether each control operated effectively throughout the observation period.
  • Other information. An optional section where management can provide additional context outside the formal audit scope.

The Four Auditor Opinions

An unqualified opinion is the goal. It means the auditor found controls were suitably designed and operating effectively. This does not require zero findings; minor exceptions can appear without changing the overall opinion, as long as they were not severe enough to prevent controls from achieving their objectives.

A qualified opinion means the auditor identified material issues affecting specific control objectives, but those issues were not pervasive across the entire scope. The report will typically use language like “except for” a particular deficiency. Qualified opinions are not uncommon, and the practical impact depends on which controls failed and whether they matter for a given client.

An adverse opinion is the worst outcome. It signals fundamental, pervasive flaws in the control environment that prevent the auditor from concluding the system is reliable. Clients should not rely on the system as described.

A disclaimer of opinion means the auditor could not form an opinion at all, typically because management restricted access to information or evidence was unavailable. This signals an incomplete assessment rather than confirmed failure, but it raises equally serious concerns about transparency.

Subservice Organizations

Most service organizations rely on third parties for at least some part of their operations. A SaaS company might run on AWS infrastructure. A payroll processor might use a third-party tax filing service. These downstream providers are called subservice organizations, and how you handle them is a decision the auditor will ask about early.

The carve-out method excludes the subservice organization’s controls from your audit scope. Your system description acknowledges the subservice organization and its role, but the auditor does not test its controls. Instead, you rely on the subservice organization’s own SOC report and implement monitoring controls on your end, such as an annual review of that report. This is the standard approach when your provider already has its own SOC 2 and your clients are comfortable reviewing it separately.

The inclusive method brings the subservice organization’s controls into your audit scope. The auditor tests those controls alongside yours, and the results appear in your report. This requires the subservice organization’s cooperation, including a formal assertion and a representation letter. It is more common when the subservice organization’s controls are deeply intertwined with yours or when the provider does not have its own SOC report. It also significantly increases scope and cost.

Complementary User Entity Controls

A SOC report does not just describe what the service organization does. It also identifies controls the client must implement on its own end for the service organization’s controls to function as intended. These are complementary user entity controls, or CUECs.

A cloud provider’s access controls, for example, work only if the client organization actually manages its own user accounts properly. If the provider’s SOC report lists “client enforces strong password policies” as a CUEC and you are not doing that, the protections described in the report are not fully operational for your environment. Ignoring CUECs is one of the most common mistakes organizations make when reviewing a vendor’s SOC report. The right approach is to assign each CUEC to a specific internal team, verify that your own controls address it, and document that assessment.

Report Validity and Bridge Letters

SOC reports carry no formal expiration date, but industry practice treats them as current for twelve months from the end of the observation period. After that, clients and auditors expect a fresh report. Most organizations undergo a SOC examination annually as a result.

Sometimes a gap develops between the end of one report’s coverage period and the issuance of the next. When that happens, the service organization can issue a bridge letter, also called a gap letter. This is a management-authored document that self-attests no material changes have occurred to controls since the last report. Bridge letters are not an official AICPA deliverable and carry no auditor opinion, so they offer limited assurance. The general expectation is that a bridge letter should cover no more than three months. Longer gaps invite questions.

Cost

SOC examination costs vary widely based on organization size, system complexity, and the number of Trust Services Criteria in scope. For a SOC 2 engagement, industry estimates for auditor fees alone fall roughly in these ranges:

  • Type I, small to midsize organization: $7,500 to $15,000
  • Type I, large organization: $20,000 to $60,000
  • Type II, small to midsize organization: $12,000 to $20,000
  • Type II, large organization: $30,000 to $100,000 or more

These figures cover the audit firm’s fees only. Internal costs are often larger and easier to underestimate. Preparing for a SOC examination diverts engineering and compliance staff from normal work for weeks. Many organizations also spend on compliance automation platforms, annual penetration testing, and security tool upgrades that the examination process reveals are necessary. Internal team time frequently runs into hundreds of hours across preparation and fieldwork.

After the initial examination, SOC compliance becomes a recurring budget item. Annual re-audits, ongoing security tool subscriptions, employee training, and potential consultant support all contribute. Organizations that invest in continuous monitoring between audit cycles tend to reduce both the total cost and the disruption of each subsequent examination.