The CTO of a Polish SaaS company receives a security questionnaire from a US customer. Question one reads: “Please provide your most recent SOC 2 Type 2 report.” The company runs penetration tests, uses multi-factor authentication and has a well-configured cloud, but it has no report. Sales asks whether one can be “done” by the end of the quarter.
A SOC 2 Type 2 report is an independent auditor’s opinion on whether the system’s security controls operated throughout the examination period. For a company selling software into the United States, it is how a customer checks its cybersecurity without running an audit of its own. Whichever you need in the SOC 2 Type 1 vs Type 2 choice, neither report can be bought off the shelf: you have to build evidence for the whole period and then hand it to a firm that is entitled to issue the report.
What is a SOC 2 report, and what is it not?
A SOC 2 report is the opinion of a licensed US certified public accountant (CPA) on the controls of a service organisation’s system, issued under the AICPA attestation standards. It is not a certificate. Amy Pawlicki of the AICPA said so plainly in the Journal of Accountancy podcast of 30 April 2026: SOC 2 is an attestation engagement signed off by a licensed CPA, not a certification.
According to the Journal of Accountancy article of 1 February 2026, SOC reports were established in 2011. SOC 1 covers controls relevant to customers’ financial reporting, while SOC 2 covers controls relevant to the security, availability and processing integrity of the system and the confidentiality and privacy of the information it processes. The same article notes that “compliance” is a term never used in SOC 2 examinations. The report therefore does not say the company is compliant; it describes the system, the controls and the result of their assessment.
A SOC 2 report has restricted use: it is intended for readers who understand the system and the nature of the service. Providers therefore share it in a controlled way; Microsoft, citing AICPA requirements, makes its Office 365 SOC reports available only to customers with a subscription or a trial account, as it explains in its SOC 2 documentation on Microsoft Learn. For a definition of the standard and the five criteria categories, see the SOC 2 glossary entry.
How does SOC 2 Type 1 differ from Type 2?
Type 1 assesses control design as of a specified date, while Type 2 also assesses whether controls operated effectively throughout the examination period. Microsoft, in the description of its SOC 2 reports, puts it this way: a Type 2 examination evaluates whether controls are designed appropriately, were in operation on a specified date and operated effectively over a specified time period. Of Type 1 examinations it says that they do not look back over a period of performance.
The difference is easiest to see on a single control. For a quarterly review of access rights to the production environment, a Type 1 report requires a procedure, a named owner and evidence that the mechanism exists on the examination date. In a Type 2 report, the auditor checks whether the reviews actually took place in every quarter of the period, who approved them and what happened to the accounts the review flagged.
Type 1 therefore answers the question of whether the company knows what to do. Type 2 answers whether it does it regularly, including in the months when nobody is watching. A customer asking for Type 2 is really asking about the team’s habits, not its documentation.
Key points:
- SOC 2 is a licensed CPA’s opinion, not a certificate.
- Type 1 assesses control design on one date; Type 2 assesses operation over a whole period.
- The report has restricted use: it reaches customers in a controlled way, not via a website.
Which report type should you choose when a customer asks for one?
Choose the type the customer requires, and if the contract says Type 2, establish whether they will accept a Type 1 report as an interim step. The report has to convince a specific reader, so their requirements are the starting point.
Before you talk to an audit firm, ask the customer five questions. Which report type does the contract or their vendor management policy require? Which criteria categories do they expect: security alone, or availability or confidentiality as well? Which service or system should the report cover? Will they accept a Type 1 report while the first Type 2 period runs? By when do they need the document?
The answers change the plan. A customer who accepts Type 1 with a Type 2 schedule gives the company time to build a history of control operation. A customer who requires Type 2 immediately forces a different order: controls and evidence collection first, and only then the examination period and the report. Get these arrangements in writing, because they determine scope and deadlines.
Who can issue a SOC 2 report?
Only a licensed CPA performing the examination under the AICPA attestation standards can issue a SOC 2 report. In the podcast cited above, Amy Pawlicki explains that state law in the US requires such attest engagements to be performed by licensed CPAs. Microsoft states that its services are examined by an independent CPA firm under SSAE No. 18 and the AICPA guide for SOC 2.
nFlo does not issue SOC 2 reports and cannot issue them: the report is signed by a licensed CPA firm. Nor do providers of evidence automation platforms issue them. The Journal of Accountancy notes in its February article that most of the new tool providers are not CPA firms, so they cannot attest to the effectiveness of controls and instead refer customers to partner audit firms.
For the buyer, the conclusion is simple. A tool can organise evidence and an adviser can help build controls, but the opinion in the report is always signed by a specific CPA firm. Its qualifications and its approach to the examination are what you need to check before signing the contract.
How do you set the scope of the system and the Trust Services Criteria?
The scope of the examination comes down to two decisions: which system the report covers and which Trust Services Criteria categories are assessed. The AICPA publishes the criteria as the “2017 Trust Services Criteria (With Revised Points of Focus – 2022)” for five categories: security, availability, processing integrity, confidentiality and privacy. According to Amy Pawlicki, an examination can cover one, several or all five categories in any combination.
A system is more than an application: in practice it also includes the infrastructure, people, procedures and data that support the service sold to the customer. Management prepares the system description, and the auditor evaluates it against the AICPA’s 2018 description criteria. Too broad a scope means more controls to test. Too narrow a scope means the service the customer is asking about stays outside the report.
The scope can also be extended with requirements beyond the AICPA criteria. The AICPA guide for SOC 2, updated in October 2022, contains an illustrative report for a “SOC 2+” examination, and Microsoft states that its Office 365 SOC 2 Type 2 report also addresses the Cloud Security Alliance’s Cloud Controls Matrix and the German BSI’s C5 catalogue.
How do you prepare a company for its first SOC 2 examination?
Preparation means making sure every control in scope has an owner, a description and an evidence source before the examination period begins. The work falls into six steps:
- Agree with the customer on the report type, the criteria categories and the service covered.
- Describe the system: components, boundaries, data flows and the subcontractors the service depends on.
- Carry out a risk assessment and map controls to the criteria and to the risks they address.
- Assign control owners and establish where evidence is produced: an event log, a change ticket, an approved review, a restore test report.
- Run a readiness review on a sample of evidence and close gaps before the auditor counts them.
- Select a CPA firm and agree the Type 1 examination date or the start and end of the Type 2 period.
Step four demands discipline throughout the period. For a Type 2 report, evidence has to exist for the whole period, not just on the day of the auditor’s visit. A control introduced halfway through the period has no history for the first half, and a review that someone performed but did not record did not happen as far as the examination is concerned. An internet policy template will not solve this, for the reasons set out in the article on security policies written from templates.
How can you use ISO 27001 when preparing for SOC 2?
ISO 27001 gives a company risk assessment, controls and evidence discipline that will also serve a SOC 2 examination, but it does not replace the report. They are two different documents. An ISO/IEC 27001:2022 certificate (with the Amd 1:2024 amendment) is issued by a certification body, and the rules for transitioning accredited certificates to the 2022 edition were set out in IAF MD 26:2023. A SOC 2 report is a CPA firm’s opinion on the controls of a specific system, including a description of the tests performed.
In practice, the shared elements are the risk register, the mapping of controls to risks, access reviews, change management, incident response and backups. Build the control map once and link each control both to the ISO requirements and to the AICPA criteria. A single access review then becomes evidence in both examinations.
They differ in audience and in the form of the result. A certificate with its scope can be shown to anyone, whereas a SOC 2 report goes to specified readers and describes the control tests, which a certificate does not. For the broader picture of what enterprise customers expect from SaaS providers, see the article on the security audit for a SaaS company; for the management system itself, see the ISO 27001 guide.
How do you recognise a SOC 2 offer that may fail the customer’s review?
Be wary of an offer that promises a report within days, guarantees a clean opinion or says nothing about scope and sampling. In February 2026, the Journal of Accountancy described a market in which tool vendors may promise “compliance” in weeks or even hours. A member of the AICPA SOC 2 Working Group quoted in the article described reports that, when you compare five of them, turn out identical except for the customer’s logo.
The AICPA responded through its oversight of CPA firms. The Journal of Accountancy of 14 May 2026 describes a May 2026 reviewer alert: engagements with identical reports, risk assessments, sample sizes and testing procedures are not performed in accordance with professional standards. In such cases, reviewers may select several engagements, often about five, from different partners and compare the reports with one another and with prior years.
Before signing, ask the audit firm the questions from the February article: what is its size and capacity, what experience and peer review results does it have, how will it set the scope and sample sizes, and how does it maintain independence. Another working group member put it bluntly in the same article: a rejected report “is not worth the paper it’s on”. For Type 2, a new report requires another examination period.
What happens after your first Type 2 report?
After the first report, the next period begins, because a SOC 2 examination is repeated every year. Amy Pawlicki stressed in the podcast that the service should be performed annually, because the system and its risks change over time.
Microsoft describes its own practice for Office 365 as follows: its Type 2 examinations cover consecutive periods without gaps, and the report is usually issued a few months after the period ends. For the time between the end of a period and the new report, Microsoft issues so-called bridge letters. It points out itself that these are its own self-attestations, not reports based on an auditor’s examination.
For a smaller company, the practical conclusion is that evidence collection does not stop on the day a period closes. If the team stops documenting reviews and changes after the first report, the next period starts with a gap that cannot be filled retrospectively.
How do you plan the path from zero to a Type 2 report?
The safest approach is to plan backwards from the date the customer needs the report and, for each stage, know the decision, the evidence and the signal that something is going wrong. The table sets out that plan.
| Stage | Decision to make | Evidence the auditor will see | Warning sign |
|---|---|---|---|
| Conversation with the customer | Report type, criteria categories, service, deadline | Record of the customer’s requirements | Nobody knows whether the customer will accept Type 1 |
| System scope | System boundaries, subcontractors, data | System description prepared by management | The description covers “the whole company” or omits the customer’s service |
| Control map | Control → criterion → risk → owner | Risk register and control matrix | Controls without an owner or without an evidence source |
| Readiness review | Which gaps to close before the examination | Sample of evidence from recent weeks | Evidence is produced by hand just before the audit |
| Type 1 report (optional) | Examination date | System description and control design as of that date | Date chosen before gaps are closed |
| Type 2 period | Start and end of the period | Evidence from every month of the period | A periodic control skipped in one quarter |
| Choice of CPA firm | Scope, sampling, schedule | Contract describing the examination scope | Promise of a report within days or of a clean opinion |
| Next period | Continuity of periods | Evidence without a gap between periods | Evidence collection stopped after the first report |
Key points:
- The plan runs backwards from the customer’s deadline, and the end of the Type 2 period sets the earliest possible report date.
- Evidence that was not produced during the period will not appear later.
- Judge a CPA firm’s offer by scope, sampling and independence, not by turnaround time.
How can nFlo help before a SOC 2 examination?
nFlo does not issue SOC 2 reports. In the area of governance, risk and compliance, nFlo provides ISMS review, audit and advisory, which covers a gap analysis against the ISO/IEC 27001:2022 requirements, a review of management system documentation, verification of control effectiveness based on evidence and an assessment of risk management.
For a company building a management system to ISO 27001 while answering US customers’ questions about SOC 2, this is the same groundwork: controls mapped to risks and evidence that can be shown to an auditor. If you want to check the state of your controls and documentation before engaging a CPA firm, talk to us.
What else should you know about SOC 2 Type 1 and Type 2 reports?
Is SOC 2 a certification?
No. SOC 2 is an attestation examination that ends with a licensed CPA’s opinion on the controls of a specific system. The AICPA stresses that the report is not a certification. A company does not hold SOC 2 permanently; it has a report covering a specified date or period.
Can you start with a Type 1 report?
Yes, if the customer accepts it. Type 1 shows control design on a single date and is sometimes a step before the first Type 2 period. If the contract requires Type 2, a Type 1 report will not satisfy it on its own, so agree with the customer whether they will accept it while the examination period runs.
Can you publish a SOC 2 report on your website?
A SOC 2 report has restricted use: it is intended for readers who understand the system and the nature of the service, so it is shared in a controlled way, for example after a customer signs in or under a non-disclosure agreement. For general use, the AICPA provides the SOC 3 report.
Will an ISO 27001 certificate replace a SOC 2 report?
Only if the customer accepts it. An ISO/IEC 27001 certificate is issued by a certification body and covers the management system, while a SOC 2 report is a CPA firm’s opinion on a system’s controls, including a description of the tests. Risk assessment, controls and evidence are shared, so one preparation effort can serve both.
How often should you repeat a SOC 2 examination?
Every year. In a Journal of Accountancy podcast, the AICPA stressed that the service should be performed annually because the system and its risks change over time. Plan consecutive examination periods without gaps so that the assessment of controls does not break.
