Who needs a SOC 2 report?
SOC 2 is designed for service organizations: companies that store, process, or transmit data on behalf of customers. SaaS providers, cloud and managed service providers, payment and data processors, and outsourced IT firms are the most common. The report goes to customers, prospects, and their auditors, who use it to assess the risk of relying on the vendor.
SOC 2 sits in the AICPA's System and Organization Controls (SOC) family. SOC 1 covers controls relevant to a customer's financial reporting. SOC 2 covers the Trust Services Criteria and is intended for users with enough knowledge to interpret it, so it is usually shared under NDA. SOC 3 covers the same criteria in a shorter general-use report that can be posted publicly.
Because no law mandates it, the trigger is almost always commercial: a security questionnaire or contract clause from a customer that asks for a current SOC 2 Type 2 report.
What are the SOC 2 trust services criteria?
The AICPA publishes the criteria as the 2017 Trust Services Criteria, most recently updated with revised points of focus in 2022. They are organized into five categories. The organization chooses which of the four optional categories to include based on the commitments it makes to customers.
| Category | In scope | What it covers |
|---|---|---|
| Security | Always in scope | Protection against unauthorized access, disclosure, and damage. Assessed through the common criteria CC1 to CC9. |
| Availability | Optional | Whether the system is available for operation and use as committed, including capacity, backup, and recovery. |
| Processing Integrity | Optional | Whether system processing is complete, valid, accurate, timely, and authorized. |
| Confidentiality | Optional | Protection of information designated as confidential, from collection through disposal. |
| Privacy | Optional | Collection, use, retention, disclosure, and disposal of personal information. |
The Security category is built from nine common criteria series: CC1 control environment, CC2 communication and information, CC3 risk assessment, CC4 monitoring activities, CC5 control activities, CC6 logical and physical access, CC7 system operations, CC8 change management, and CC9 risk mitigation. The criteria describe outcomes, not specific technologies, so each company designs its own controls to meet them.
What is the difference between SOC 2 type 1 and type 2?
| Dimension | Type 1 | Type 2 |
|---|---|---|
| Timeframe | As of a single date | Over a period, commonly 3 to 12 months |
| Auditor opinion covers | System description and suitability of control design | Description, design, and operating effectiveness |
| Testing | Walkthroughs to confirm controls exist | Sampling of evidence across the whole period |
| Typical use | First report, to unblock early deals | Ongoing annual report most customers expect |
A common path is a Type 1 first, then a Type 2 once the controls have run long enough to be tested. The Type 2 is where evidence volume grows: the auditor samples access reviews, change tickets, alerts, and onboarding records from across the whole period, so gaps in the middle of the year show up as exceptions.
How much does SOC 2 cost?
There is no fixed price. CPA firms quote based on scope and effort, and the audit fee is only one part of the total. The main cost drivers are:
- Report type and period: A Type 2 requires more testing than a Type 1, and a longer period means more samples.
- Criteria in scope: Each optional category beyond Security adds criteria to design, operate, and test.
- System size and complexity: More applications, cloud accounts, locations, and subservice organizations expand the audit.
- Readiness work: Gap assessments, policy writing, and control remediation before the audit starts.
- Supporting services: Penetration testing, security awareness training, and compliance tooling.
- Internal time: Engineering and GRC hours spent gathering and explaining evidence, often the largest hidden cost.
Internal time is the cost automation reduces most directly, because the same evidence is requested every year.
How GRC engineers automate SOC 2
Much of the audit evidence for SOC 2 already exists as configuration and log data. GRC engineers collect it from the source instead of taking screenshots:
- CC6 access evidence: A script uses the AWS IAM credential report and your identity provider's API to export users, MFA status, and last login, then flags accounts of terminated employees.
- CC7 monitoring evidence: AWS Config rules and Security Hub findings show that logging, encryption, and alerting stay enabled across the whole audit period, not only on the day of a walkthrough.
- CC8 change management: The GitHub API exports branch protection settings and merged pull requests with approvals, proving every production change was reviewed.
- Preventive controls in CI: Policy-as-code checks (Open Policy Agent, Checkov) run on Terraform plans and block noncompliant infrastructure before deployment.
- Evidence storage: Outputs land as timestamped JSON in a versioned, write-protected bucket, giving the auditor a complete population to sample from.
Step-by-step guides: how to automate SOC 2 evidence and SOC 2 compliance automation.
Frequently asked questions
What is SOC 2 in simple terms?
SOC 2 is an independent report, issued by a licensed CPA firm, that describes a service organization's system and gives an opinion on whether its controls meet the AICPA Trust Services Criteria. Companies share it with customers to show how they protect customer data. It is an attestation report, not a certification.
What are the five SOC 2 Trust Services Criteria?
The five categories are Security, Availability, Processing Integrity, Confidentiality, and Privacy. Security, made up of the common criteria CC1 through CC9, is included in every SOC 2 examination. The other four are added when they are relevant to the services and commitments the organization makes to customers.
What is the difference between SOC 2 Type 1 and Type 2?
A Type 1 report evaluates the system description and whether controls are suitably designed as of a single date. A Type 2 report also tests whether those controls operated effectively over a period of time, commonly between three and twelve months. Most enterprise customers ask for a Type 2.
Is SOC 2 required by law?
No law requires SOC 2. It is driven by customer contracts and procurement reviews, especially for SaaS, cloud, and data processing vendors. In practice it often becomes a condition of closing deals with larger customers.
How much does a SOC 2 audit cost?
Cost varies widely with scope, the number of Trust Services Criteria in scope, report type, company size, and the CPA firm. Beyond the audit fee, budget for readiness work, tooling, penetration testing, and the internal staff time spent collecting evidence. Get quotes from several CPA firms with the same scope before deciding.
How long is a SOC 2 report valid?
A SOC 2 report does not have a formal expiration date, but it only covers the period or date it describes. Customers generally expect a new Type 2 report every year so there is no large gap in coverage.