





SOC 1 covers controls that matter to customers' financial reporting, SOC 2 covers security and related controls against the Trust Services Criteria, and SOC 3 is a general-use report built on the same criteria as SOC 2. All three come from the AICPA's attestation framework, and a software or cloud company that handles customer data most often needs SOC 2.
SOC 1 | SOC 2 | SOC 3 | |
Subject | Controls at a service organization that are relevant to its customers' internal control over financial reporting | Controls relevant to security, availability, processing integrity, confidentiality or privacy | The same subject matter as SOC 2, summarized |
Criteria | Control objectives defined by management and evaluated under AT-C section 320 | The Trust Services Criteria, with a system description prepared against DC section 200 | The Trust Services Criteria |
Main audience | Customers and their financial statement auditors | Management, customers, prospects and partners who understand the service | Anyone |
Use | Restricted use | Restricted use, usually shared under NDA | General use, can be published |
Detail | Full description, controls and test results | Full description, controls and test results | Auditor's opinion and management's assertion, without the detailed controls and test results |
Report types | Type 1 and Type 2 | Type 1 and Type 2 | No Type 1 or Type 2 label |
Typical providers | Payroll, payment processing, billing and similar services that can affect customers' financial statements | SaaS, cloud, hosting, data processing and managed services | Companies that want a public trust signal after a SOC 2 |
A SOC 1 report is written for the people who audit your customers' financial statements. It tests controls that could affect how a customer records or reports its finances, so the control objectives are tailored to your service. A payroll provider, for example, would show controls over payroll calculations and the accuracy of files it sends.
A SOC 2 report is about how you protect and run the system customers depend on. Instead of control objectives you write yourself, the benchmark is the AICPA's Trust Services Criteria. Because the report contains detailed descriptions of your systems and the auditor's test results, it is a restricted-use document. You normally share it with customers and prospects under an NDA.
With Cstream: a SOC 2 report is only as strong as the evidence behind it. Automated evidence collection and continuous control monitoring keep that evidence current, so the examination starts from a strong position rather than a scramble.
A SOC 3 report is a short, general-use version that carries the auditor's opinion and management's assertion but not the detailed controls, tests and results. That makes it safe to publish on a website or hand to anyone, and it is often prepared alongside a SOC 2 examination. It is a marketing and trust tool, not a substitute: customers who run security reviews will still ask for the full SOC 2.
Many software companies need only a SOC 2.
If your service can affect customers' financial reporting, ask whether customers' auditors expect a SOC 1 as well. Some providers hold both.
A SOC 1 is not a prerequisite for a SOC 2, and neither is the other way round.
A SOC 3 is an optional add-on once you have a SOC 2.
What are customers asking for in security reviews and contracts?
Does our service touch customers' financial reporting, or only their data security?
Do we want something we can publish publicly, or only a detailed report under NDA?
Which report will our target customers' procurement teams accept?
The AICPA also publishes SOC for Cybersecurity, which reports on an organization's cybersecurity risk management program, and SOC for Supply Chain, which covers production, manufacturing and distribution systems. Most SaaS buyers will not ask for these, but they exist.
With Cstream: Multi-framework Mapping reuses one control set across standards, so work done for SOC 2 carries over to ISO 27001, HIPAA, GDPR and others. The Trust Center gives you a shareable page that shows your security posture, a useful complement to a detailed report shared under NDA.
Cstream is the trusted GRC platform that supports startups through every stage of the SOC 2 journey, from planning and control implementation to audit preparation and ongoing compliance. Cstream keeps one data model for IT operations and compliance, so the assets, people, vendors, policies and control test results you use every day are the same ones that support your audit.
Cstream's SOC 2 capabilities include key features supporting preparation and audit, such as:
Cstream works directly with your audit firm to keep reviews moving. Multi-framework Mapping also lets the same controls support ISO 27001, HIPAA and other frameworks later.
Schedule a demo to see how Cstream supports your SOC 2 journey.

