Skip to content

What Is SOC 2? The Complete Guide to Reports, Trust Services Criteria and Audits

What SOC 2 is, the five Trust Services Criteria, Type 1 vs Type 2, the audit process and who may perform it, sourced to AICPA criteria, guides and peer review rules.

Omar KhandakerBy , Senior Security Consultant19 min read

Web Application Penetration TestingFrom $5,200Fixed scope, free retest, no hourly billing.

Get my fixed price

SOC 2 is an attestation report in which a licensed CPA firm gives an opinion on a service organization’s controls over security and, optionally, availability, processing integrity, confidentiality and privacy. This guide covers the standards behind it, the five Trust Services Criteria, Type 1 vs Type 2, the audit process, evidence, who may perform the audit, how it compares with SOC 1, ISO 27001 and HITRUST, bridge letters and penetration testing. Each rule is sourced to the AICPA’s own criteria, guides and peer review material.

How to cite: link to this page or to the primary source beside each fact. Figures carry their source and year.

Key points at a glance

1. What is SOC 2?

SOC stands for System and Organization Controls, which the AICPA describes as a suite of service offerings that CPAs may provide on the controls of a service organization. SOC 2 is the member of that suite that reports on controls relevant to security, availability, processing integrity, confidentiality or privacy.

Three layers of standards sit behind every SOC 2 report:

Layer What it is Source
Attestation standards SSAE No. 18 recodified the attestation standards into AT-C sections. AT-C 105 covers concepts common to all attestation engagements and AT-C 205 covers examinations. Effective for reports dated on or after May 1, 2017 Journal of Accountancy, April 2016
The SOC 2 guide The AICPA guide auditors apply to SOC 2 and SOC 3 examinations, updated as of October 15, 2022 for SSAE No. 20 and No. 21 AICPA SOC 2 guide
Criteria The 2017 Trust Services Criteria (revised points of focus, 2022) for controls, and the 2018 Description Criteria (DC 200) for the system description AICPA SOC 2 guide

You will still see “SSAE 18 SOC 2” in contracts. It is shorthand for the attestation standards above, not a separate report.

SOC 2 is an attestation, not a certification: management makes written claims (the assertion), and the CPA firm gives an opinion on them. SOC 2 engagements are required to be examinations, not reviews or agreed-upon procedures (AICPA Peer Review Q&A, 2026). AICPA staff also note that a SOC 2 does not opine on whether you comply with laws and regulations, only on the controls that support compliance (AICPA FAQ, 2020).

2. Who needs SOC 2, and why buyers ask for it

A SOC 2 is written for a service organization: an organization, or a segment of one, that provides services to user entities (AICPA comparison of SOC examinations, 2020). In practice that means SaaS vendors, cloud and hosting providers, managed service providers, data processors and any vendor that stores or touches customer data. Our page on SaaS penetration testing covers why software vendors meet the request first.

The demand comes from the customer side. The AICPA says SOC 2 reports can play an important role in oversight of the organization, vendor management programs, internal corporate governance and risk management, and regulatory oversight (AICPA SOC 2 page, 2022 archive). Its peer review Q&A adds that the primary users of a SOC 2 are generally not auditors but the management of user entities, who use the report to make operational decisions (AICPA Peer Review Q&A, 2026).

In practice, one independent report answers most of a security questionnaire and gives procurement a vendor due diligence record. SOC 2 is not a law: you get one because customers or contracts require it, and when a contract names the report type, only that type satisfies it.

3. The five Trust Services Criteria

The Trust Services Criteria are set by the AICPA’s Assurance Services Executive Committee and aligned to the 17 principles of the COSO 2013 internal control framework, plus supplemental criteria for logical and physical access, system operations, change management and risk mitigation (AICPA TSC 2022). Security is always in scope, because its criteria (the common criteria) also apply to every other category.

Category AICPA definition, in short Criteria When to include it
Security Information and systems are protected against unauthorized access, unauthorized disclosure and damage 33 common criteria, CC1.1 to CC9.2 Always
Availability Information and systems are available for operation and use to meet objectives 3 (A1.1 to A1.3) You commit to uptime, recovery or capacity
Processing integrity System processing is complete, valid, accurate, timely and authorized 5 (PI1.1 to PI1.5) Customers rely on your processing results (payments, payroll, claims)
Confidentiality Information designated as confidential is protected 2 (C1.1 to C1.2) Contracts define confidential data you must protect and dispose of
Privacy Personal information is collected, used, retained, disclosed and disposed of to meet objectives 18 (P1.1 to P8.1) You handle personal information under privacy commitments

Counts are taken from the criteria table in the AICPA TSC 2022 and total 61. The common criteria are grouped as CC1 control environment, CC2 communication and information, CC3 risk assessment, CC4 monitoring, CC5 control activities, CC6 logical and physical access, CC7 system operations, CC8 change management and CC9 risk mitigation.

Two scoping rules: points of focus are illustrative, since “use of the trust services criteria does not require an assessment of whether each point of focus is addressed” (paragraph .07); and every criterion in an included category is addressed unless, in limited circumstances, it is not relevant to the service. The 2022 revisions changed points of focus only and, in the AICPA’s words, do not alter the criteria (AICPA TSC 2022; EY To the Point, November 2022).

The AICPA publishes criteria, not controls; you design controls that meet each criterion. Our SOC 2 controls list maps all 61 criteria to example controls and evidence.

See what a real pentest finds. Read our sample report, then get a fixed quote in writing.

4. SOC 2 Type 1 vs Type 2

The AICPA defines two report types. A Type 1 reports on management’s description of the system and the suitability of the design of controls. A Type 2 reports on the description and the suitability of design and the operating effectiveness of controls (AICPA SOC 2 page, 2022 archive).

Type 1 Type 2
Opinion covers Description and design of controls Description, design and operating effectiveness
Time covered A single date (the “as of” date) A period
Auditor’s tests Confirms controls exist and are suitably designed on that date Samples evidence from across the whole period
Buyer reading A starting point The report most procurement teams expect

How long should the Type 2 period be? AICPA staff state that the SOC 2 guide does not prescribe a minimum period; the period is a business decision for management. The same FAQ cites a guide example in which a Type 2 period of less than two months may leave the auditor unable to obtain enough evidence for an opinion (AICPA FAQ, 2020). A CPA writing for the Cloud Security Alliance (2024) notes that periods usually run three to twelve months, that many first reports cover three months, and that annual 12-month periods are viewed as best practice.

The full comparison, including when the penetration test should land in each, is in SOC 2 Type 1 vs Type 2.

5. What is inside a SOC 2 report

A Type 2 SOC 2 report contains four core parts (AICPA comparison of SOC examinations, 2020):

  1. The service auditor’s report, with the opinion on the description and on the design and operating effectiveness of controls.
  2. Management’s written assertion about the description and the controls.
  3. The system description, prepared against the 2018 Description Criteria (DC 200). It also covers complementary user entity controls (what your customers must do themselves) and how subservice organizations, such as your cloud provider, are handled. Management can include subservice organizations’ controls (the inclusive method) or leave them out (the carve-out method).
  4. The auditor’s tests of controls and their results, including any exceptions.

Use of the report is restricted to specified parties, such as customers, prospective customers, business partners and regulators who understand the system, which is why vendors share it under NDA. There is no pass or fail score: the auditor issues an opinion, which can be modified (for example, qualified) when controls fall short, an outcome AICPA staff discuss in their FAQ.

Two related reports often come up:

  • SOC 3 uses the same criteria and subject matter as a SOC 2 but leaves out the detailed tests and results, so it is a general use report that you can publish and use in marketing (AICPA Peer Review Q&A, 2026).
  • SOC 2+ adds other subject matter and suitable criteria to the same examination, with the auditor also reporting against those additional criteria (AICPA, 2019), and the 2022 SOC 2 guide includes an illustrative SOC 2+ report (AICPA SOC 2 guide).

6. The SOC 2 audit process and timeline

The sequence is the same at most firms. Durations depend on your readiness, scope and auditor, so treat any fixed timeline you are quoted as an estimate to confirm in the engagement letter.

Step What happens Who owns it
1. Scope Choose the system, the categories, Type 1 or Type 2, and the date or period Management
2. Readiness Gap assessment against the criteria, then fix the gaps (section 7) Management, often with an adviser
3. Engage a CPA firm Engagement letter, fee, timeline and evidence platform agreed Management and auditor
4. Write the description and assertion System description against DC 200, management’s assertion Management
5. Operate controls Type 1: in place on the as-of date. Type 2: operating through the whole period Management
6. Fieldwork Inquiry, inspection of evidence, observation and re-performance; sampling across the period for Type 2 Auditor
7. Report Draft review, management response to exceptions, final report Auditor issues; management responds
8. Repeat Next period starts; bridge letters cover the gap (section 11) Management

For a first Type 2, add the observation period to readiness and fieldwork; first periods are often three months (section 4). Budget detail for every step, including auditor fees, tooling and testing, is in our SOC 2 cost guide.

7. SOC 2 readiness

A readiness assessment compares your controls with the scoped criteria and lists the gaps before the auditor arrives. Common first-time gaps: missing policies, no documented risk assessment, informal access reviews, no change management trail, no vendor reviews and no recent independent security testing. Start with a written security risk assessment, because CC3 requires one and most other controls follow from it.

Readiness work can be done by your own team, a consultant or a compliance platform, but there is an independence limit if your auditor does it. Under the AICPA’s nonattest services rules, the CPA cannot assume management’s responsibilities (Journal of Accountancy, 2016): an auditor can point at a gap, but should not design and run the control and then test it.

8. The evidence auditors ask for

SOC 2 evidence is whatever proves a control existed (Type 1) or ran every time it should have (Type 2). Common examples by criteria group:

Criteria Typical controls Evidence auditors sample
CC1, CC2 Code of conduct, security training, org chart Signed acknowledgments, training completion records
CC3 Annual risk assessment, risk register Dated risk assessment with owners and treatment
CC4 Independent evaluations, control monitoring Penetration test report, internal audit or monitoring records
CC5 Policies and procedures Approved, versioned policies
CC6 Access provisioning, quarterly access reviews, MFA, encryption Access tickets, review sign-offs, configuration screenshots
CC7 Vulnerability scanning, logging and alerting, incident response Scan reports and remediation tickets, alert records, incident tickets
CC8 Change management Pull requests with approvals, deployment records
CC9 Vendor management, business continuity Vendor reviews (including their SOC reports), continuity and recovery test results

The 2022 points of focus added data flows, asset inventory and information classification (EY To the Point, November 2022), so expect requests for an asset inventory and data-flow diagrams. For testing evidence, our SOC 2 penetration testing evidence checklist lists what to hand the auditor and when, and our guide to vulnerability management programs covers the scanning and remediation records CC7.1 relies on.

9. Who can perform a SOC 2 audit

Only a licensed CPA firm can perform a SOC 2 examination and sign the opinion. The AICPA describes SOC as services CPAs may provide, and SOC 2 engagements fall under AICPA peer review: they must be examinations, they are subject to a System Review, and a peer review should select at least one SOC 1 or SOC 2 engagement for review (AICPA Peer Review Q&A, 2026).

Before you sign an engagement letter, check three things:

  • License. NASBA’s CPAverify searches licensed CPAs and accounting firms across 53 participating jurisdictions (NASBA, March 2026).
  • Peer review. Ask for the firm’s most recent peer review report and whether a SOC engagement was reviewed.
  • Tailoring. In May 2026 the AICPA told peer reviewers that reviewing one SOC 2 file is often insufficient, to check timelines and use of third-party SOC platforms, and, when risk is elevated, to compare several engagements, often about five, for identical risk assessments, sample sizes and procedures (Journal of Accountancy, May 2026).

Consultants, compliance platforms and penetration testers can prepare you but cannot issue the opinion. Our comparison of SOC 2 audit firms lists licensed firms and the verification steps in detail.

10. SOC 2 vs SOC 1 vs ISO 27001 vs HITRUST at a glance

SOC 2 SOC 1 ISO 27001 HITRUST
What it is Attestation on controls relevant to security and the other trust services categories Attestation on controls relevant to customers’ internal control over financial reporting Certification of an information security management system to ISO/IEC 27001:2022 Certification against the HITRUST framework
Standard AT-C 205 and the SOC 2 guide AT-C 320 and the SOC 1 guide ISO/IEC 27001:2022 (Edition 3) HITRUST e1, i1 or r2 assessment
Who issues it Licensed CPA firm Licensed CPA firm Certification body (ISO itself does not certify) HITRUST, based on testing by an authorized external assessor
Output Opinion plus detailed report, restricted use Opinion plus detailed report, restricted to user entities and their auditors Certificate Certification report
Time covered Type 1 date or Type 2 period Type 1 date or Type 2 period Three-year cycle with annual surveillance audits e1 and i1: one year; r2: two years with an interim assessment

Sources: SOC 1 and SOC 2 from the AICPA Peer Review Q&A (2026); ISO from the ISO/IEC 27001 page and ISO’s certification page; the three-year cycle as described by certification body Amtivo; HITRUST from its e1, i1 and r2 pages.

HITRUST’s e1 uses 43 foundational controls and its i1 uses 182 curated controls (HITRUST e1; HITRUST i1). ISO says over 70,000 ISO/IEC 27001 certificates were reported in 150 countries in its ISO Survey 2022 (ISO). The AICPA publishes a mapping of the Trust Services Criteria to ISO 27001 (2018) for organizations that run both.

For the detailed choices, see SOC 1 vs SOC 2, ISO 27001 vs SOC 2 and HITRUST vs SOC 2.

11. Bridge letters

A SOC 2 covers a fixed date or period and carries no expiry date, so the question buyers ask is how long ago the period ended. A bridge letter (also called a gap letter) covers the time between the end of your last report period and the date a customer asks.

A bridge letter is not a SOC report. As described by Linford & Company, a CPA firm, it is signed by the service organization’s management, not by the service auditor, and the auditor gives no assurance over the gap period. It typically states the period the last report covered, whether there have been material changes to the system or controls since, and that the letter is not a replacement for the SOC report. The same firm notes that most bridge letters cover no more than three months (Linford & Co, updated June 2026). Keeping Type 2 periods back to back keeps that gap short.

12. Is a penetration test required for SOC 2?

Not by name. Penetration testing appears once in the Trust Services Criteria, in a CC4.1 point of focus that lists the types of ongoing and separate evaluations management may use: first- and second-line monitoring and control testing, internal audit, compliance and resilience assessments, vulnerability scans, security assessment, penetration testing and third-party assessments. CC7.1 has a separate point of focus on infrastructure and software vulnerability scans, run periodically and after significant changes, with timely remediation (AICPA TSC 2022). Points of focus are not mandatory (paragraph .07).

In practice, most auditors expect a recent independent penetration test as evidence for CC4.1 and the CC7 criteria, and enterprise buyers often ask for the report too. To count as evidence, the test should cover the systems in the SOC 2 boundary, land before the Type 1 as-of date or inside the Type 2 period, be run by testers independent of the systems, and end with a retest showing findings were closed.

The detail is in SOC 2 penetration testing requirements, and the scanning versus testing distinction is in penetration testing vs vulnerability scanning. Invadel is a penetration testing company, not a CPA firm, so we do not issue SOC 2 reports; our SOC 2 penetration testing is scoped to your system description and usually built around a web application penetration test. To compare testing firms, see our list of SOC 2 penetration testing providers.

What to expect in 2027

The AICPA has proposed new SOC 2 criteria. On October 28, 2026 the AICPA announced exposure drafts, issued by its Assurance Services Executive Committee, of a proposed 2027 SOC 2 Trust Services Criteria and Description Criteria (AICPA press release, October 28, 2026; AICPA exposure drafts). According to the AICPA’s announcement and the Journal of Accountancy:

Until a final version is issued, the 2017 criteria with the 2022 points of focus remain in use. If your product has AI features, the proposed points of focus suggest auditors will ask how you test them; our AI and ML penetration testing covers prompt injection and other attacks on LLM features.

Sources

  • AICPA, 2017 Trust Services Criteria for Security, Availability, Processing Integrity, Confidentiality, and Privacy (With Revised Points of Focus, 2022), TSP section 100. aicpa-cima.com (free AICPA account required)
  • AICPA, Questions and Answers About the AICPA Peer Review Program, February 2026. aicpa-cima.com
  • AICPA, SOC 2 Reporting on an Examination of Controls at a Service Organization (SOC 2 guide), updated as of October 15, 2022. aicpa-cima.com
  • AICPA, SOC 2: SOC for Service Organizations: Trust Services Criteria page, archived May 2022. web.archive.org
  • AICPA staff, Frequently Asked Questions: SOC 2 and SOC 3 Examinations, November 2020 (nonauthoritative). web.archive.org
  • AICPA, Comparison of SOC for Supply Chain, SOC 2, and SOC for Cybersecurity Examinations and Related Reports, 2020. web.archive.org
  • AICPA, System and Organization Controls: SOC Suite of Services. aicpa-cima.com
  • AICPA, Addressing additional subject matter and criteria in a SOC 2 engagement, 2019. aicpa-cima.com
  • AICPA, Mapping: 2017 Trust Services Criteria to ISO 27001, 2018. aicpa-cima.com
  • AICPA, AICPA Exposure Drafts: Proposed 2027 SOC 2 Trust Services Criteria and Description Criteria, October 2026. aicpa-cima.com
  • AICPA, AICPA proposes update of SOC 2 Trust Services Criteria, press release, October 28, 2026. aicpa-cima.com
  • Journal of Accountancy, AICPA proposes improvements to SOC 2 Trust Services Criteria, October 28, 2026. journalofaccountancy.com
  • Journal of Accountancy, AICPA guides peer reviewers to address SOC 2 risks, May 14, 2026. journalofaccountancy.com
  • Journal of Accountancy, Clarified attestation standards issued (SSAE No. 18), April 5, 2016. journalofaccountancy.com
  • Journal of Accountancy, Maintaining independence with nonattest services, November 1, 2016. journalofaccountancy.com
  • EY, To the Point No. 2022-13: AICPA revises guidance on applying its Trust Services Criteria and SOC 2 Description Criteria, November 2, 2022. ey.com
  • NASBA, All about CPAverify, March 12, 2026. nasba.org
  • Cloud Security Alliance, What should the scope period be for my SOC 2 Type 2 report?, March 25, 2024. cloudsecurityalliance.org
  • Linford & Company LLP, What are bridge (gap) letters and how do they relate to SOC reports?, updated June 5, 2026. linfordco.com
  • ISO, ISO/IEC 27001:2022 Information security management systems: Requirements and Certification. iso.org/standard/27001, iso.org/certification
  • Amtivo, The three-year certification cycle. amtivo.com
  • HITRUST, e1, i1 and r2 assessment pages. e1, i1, r2

Frequently asked questions

Is SOC 2 a certification?

No. It is an attestation examination performed under AT-C section 205 (AICPA Peer Review Q&A, 2026). The output is an auditor’s opinion and report, not a certificate. ISO 27001 and HITRUST are certifications.

How long does a SOC 2 audit take?

A Type 1 depends mostly on readiness and fieldwork. A Type 2 also includes its observation period: the AICPA sets no minimum, but under two months may not support an opinion (AICPA FAQ, 2020), and periods usually run three to twelve months (Cloud Security Alliance, 2024).

Who can perform a SOC 2 audit?

Only a licensed CPA firm, which is subject to AICPA peer review for its SOC 2 work (AICPA Peer Review Q&A, 2026). You can check a firm’s license on CPAverify, which covers 53 jurisdictions (NASBA, 2026).

Does SOC 2 require a penetration test?

Not explicitly. Penetration testing is listed as an example in a CC4.1 point of focus, and points of focus are not mandatory (AICPA TSC 2022). Most auditors and enterprise buyers still expect a recent independent test; see SOC 2 penetration testing requirements.

How much does SOC 2 cost?

It depends on scope, report type, auditor, readiness work and testing. Our SOC 2 cost guide breaks down auditor fees, tooling and penetration testing line by line, with sources.

Omar Khandaker

Written by

Omar Khandaker, Senior Security Consultant

11+ years in the field. Focus: PCI DSS, ISO 27001, ISO 9001 & CMA. Part of the team that scopes, tests, and reports for our clients. Full profile →

Find out what an attacker sees.

Tell us what to test and see your fixed price.

Prefer the full scoping questionnaire? 
Start the conversation

Get a quick proposal

We are online