🏛️ Issues and Advocacy Training™
Courses › Large Organization Security Programs, Governance and Compliance™

Lesson 5 of 14 · about 55 minutes · Updated November 15, 2026

SOC Reports and Attestations

You'll be able to

  • Explain what an attestation is, how it differs from a certification and an audit, and who may legally issue a SOC report.
  • Choose the right SOC report (SOC 1, SOC 2, SOC 3, SOC for Cybersecurity, SOC for Supply Chain) and type (Type 1 or Type 2) for a given question.
  • Read a SOC report section by section, including the opinion type, exceptions, carve-outs, complementary user entity controls and management responses.
  • Run a vendor SOC report review program that maps every complementary user entity control to an internal owner and tracks opinions over time.
  • Plan a first SOC 2 for a service organization, with realistic scope, timeline and cost, and judge report quality in light of the 2026 AICPA warnings.
  • Describe the limits of SOC reports and the proposed 2027 Trust Services Criteria.

Start here: the short version

  • A SOC report is an opinion, not a certificate. It is a licensed CPA firm's examination report, issued under the AICPA's attestation standards, on whether a service organization described its system fairly and whether its controls were designed (Type 1) or also worked over a period (Type 2). In Idaho, as in other states, only licensed CPAs working through registered firms may perform attest work of this kind.12
  • Pick the right report for the question. SOC 1 covers controls that matter to a customer's financial statements; SOC 2 covers security, availability, processing integrity, confidentiality and privacy; SOC 3 is a short public version of a SOC 2; SOC for Cybersecurity covers a whole organization's cyber program; SOC for Supply Chain covers production and distribution systems.13
  • Type 2 is the one that tests over time. A Type 1 looks at design as of one date and contains no test results. A Type 2 also tests whether controls operated effectively over a period, and is usually what auditors and vendor risk teams need.4
  • The report assumes you do your part. Most reports list complementary user entity controls (CUECs), the controls the vendor assumes its customers run, and many carve out subservice organizations such as the cloud host. If you do not run your CUECs, or nobody reviews the carved-out vendors, the vendor's clean opinion does not cover your risk.45
  • Read the whole report, not the cover letter. The opinion type (unmodified, qualified, adverse or disclaimer), the period, the scope, the exceptions in the test results, the carve-outs and the CUECs are where the real information is. Management responses to exceptions are not tested by the auditor.45
  • Quality varies, and the profession said so in 2026. The AICPA warned about "fast and easy" SOC 2 offerings, told peer reviewers to scrutinize high-volume SOC 2 firms, and issued ethics guidance on firms' business ties to compliance software vendors. Anonymous allegations about one compliance startup, reported in March 2026 (denied by the company, with no official finding) put the issue in front of buyers.678
  • The criteria are about to change. On Oct. 28, 2026 the AICPA proposed revised 2027 Trust Services Criteria with new points of focus on AI; comments are due Jan. 15, 2027, and if adopted they would apply to engagements beginning on or after Dec. 31, 2027.9

Standards and rules described: AICPA Statements on Standards for Attestation Engagements, SSAE No. 18 (effective May 1, 2017) as amended through SSAE No. 21 (effective for reports dated on or after June 15, 2022), including AT-C sections 105, 205, 206 and 320; the AICPA Guide SOC 2 Reporting on an Examination of Controls at a Service Organization (updated as of Oct. 15, 2022); the 2017 Trust Services Criteria with revised points of focus (2022) and the 2018 SOC 2 description criteria with revised implementation guidance (2022); the AICPA exposure drafts of proposed 2027 SOC 2 criteria (released October 2026, comments due Jan. 15, 2027); PCAOB AS 2601 as amended by PCAOB Release No. 2024-004; GAO-25-107731 (Sept. 18, 2025); the Interagency Guidance on Third-Party Relationships (June 2023); and Idaho Code 54-206, 54-214, 54-221, 74-105 and 74-107 as in force after the 2026 session. All read or checked Nov. 15, 2026. Attestation standards, criteria and regulator expectations change; check the current text of the standard or rule before relying on any point.

Before you change anything. Plan changes to production systems, test them first, keep a way back, and follow your change management process. For clinical, plant-floor or other safety systems, involve the vendor, your safety lead and qualified engineers (see modules 109 and 111).

The vendor risk analyst at a regional health system has 41 renewals due this quarter. Each vendor has sent a PDF with "SOC 2 Type 2" on the cover. One covers a period that ended eleven months ago. One is a Type 1 issued three weeks after the vendor's founding. One excludes the cloud company that actually hosts the data. One lists nineteen controls the vendor expects the hospital to run, including approving every user account and turning on multifactor sign-in, and nobody at the hospital knows whether those controls exist. One has a qualified opinion on page four that the sales team described as "a clean audit." All of them carry the same logo.

This lesson is about reading, buying and producing those reports at the scale of a large or regulated organization. It is written for the people who rely on them (vendor risk managers, CISOs, internal auditors, controllers and CFOs, audit committee members, procurement staff, compliance officers and public agency managers), the people who commission them (service organizations' security, compliance and finance leaders), and the reporters, advocates and legislators who want to know what a "SOC 2" claim really proves.

Two earlier lessons set the base. Vendors and Supply Chain in module 108 explains vendor tiering, contracts and the regulators' third-party expectations, and The Standards Map places SOC 2 among NIST, ISO, PCI DSS, CMMC and FedRAMP. Small and medium businesses reading a SOC 2 for the first time should start with Vendors, Contracts and Third-Party Risk. This lesson does not repeat them. It goes into how the reports are built, what each section means, how a large organization runs a review program that actually uses them, what it costs and takes to produce one, and where they fall short. Certifications such as ISO/IEC 27001, HITRUST, PCI DSS, FedRAMP and CMMC are covered in lesson 6; how internal and external auditors use SOC 1 reports in Sarbanes-Oxley work is covered in lesson 8.

What an attestation is, and who may issue one

Attestation, certification and audit are different things

People use "audit," "certification" and "attestation" as if they meant the same thing. They do not, and the difference matters when a contract or a regulator asks for one.

  • An attestation is a report in which an independent practitioner gives an opinion (or a lower level of assurance) about a subject matter, or about someone else's statement about it, measured against stated criteria. SOC reports are attestation engagements performed under the AICPA's Statements on Standards for Attestation Engagements (SSAEs). The AICPA describes the SOC suite as "a suite of service offerings CPAs may provide."1
  • A certification is a decision by a certification body that an organization's management system conforms to a standard, usually with a certificate, a scope statement and a cycle of surveillance audits. ISO/IEC 27001 is the main example in security; certification bodies are themselves accredited by national accreditation bodies that work under International Accreditation Forum rules.10
  • A financial statement audit is an opinion on financial statements under auditing standards (the AICPA's for private entities, the PCAOB's for public companies). SOC 1 reports exist mainly to support those audits.11

So "SOC 2 certified" is wrong in a precise way: nobody certifies anything in a SOC 2. A CPA firm gives an opinion on management's description of its system and on its controls, for a stated period, against stated criteria. That opinion can be clean or modified, and it expires in practical terms as soon as the period it covers is old.

The standards behind SOC reports

The standards have a lineage worth knowing, because older vendors and contracts still use the old names:

  • SAS 70 (Statement on Auditing Standards No. 70, April 1992) covered reports on service organizations' transaction processing for decades. Contracts that still say "SAS 70" are at least fifteen years out of date.12
  • SSAE 16 (April 2010) replaced SAS 70 for service organization reporting.12
  • SSAE 18, "Attestation Standards: Clarification and Recodification," was issued in April 2016 and most of it took effect May 1, 2017. It reorganized the attestation standards into "AT-C" sections, including AT-C 105 (concepts common to all attestation engagements), AT-C 205 (examination engagements) and AT-C 320 (examinations of controls at a service organization relevant to user entities' internal control over financial reporting, that is, SOC 1).12
  • SSAE 21, issued Sept. 30, 2020 and effective for reports dated on or after June 15, 2022, created direct examination engagements (new AT-C 206) and replaced AT-C 205 with a revised section that still governs assertion-based examinations.13 SOC 2 examinations are assertion-based examinations under AT-C 105 and AT-C 205; Microsoft's description of its Azure SOC 2 examination, for example, names exactly those sections, the AICPA SOC 2 guide and the 2017 Trust Services Criteria.14
  • Outside the United States, the equivalent of SOC 1 is ISAE 3402, issued by the International Auditing and Assurance Standards Board in December 2009; non-financial controls reports are often issued under ISAE 3000. Global vendors frequently issue a combined report that satisfies both sets of standards.12

The AICPA's SOC 2 guide, updated as of Oct. 15, 2022, is the authoritative how-to for practitioners. It reflects SSAE No. 20 (materiality) and No. 21, the 2017 Trust Services Criteria with revised points of focus (2022), the 2018 description criteria with revised implementation guidance (2022), and an illustrative "SOC 2+" report for engagements that add other frameworks.3 The guide is sold (about $100 to $125 as an e-book); the criteria themselves are free downloads from the AICPA with a free account.31516

Who may issue a SOC report

A SOC report is attest work, and state accountancy laws reserve attest work to licensed CPAs practicing through registered firms. Idaho's law is a good example of how this works:

  • Idaho Code 54-206(3) defines "attest" to include "any examination, review or agreed-upon procedures engagement to be performed in accordance with the statements on standards for attestation engagements."17 That covers SOC 1, SOC 2, SOC 3, SOC for Cybersecurity and SOC for Supply Chain examinations.
  • Idaho Code 54-214 says "A firm must be registered with the board in order to provide attest services," requires annual registration with the Idaho State Board of Accountancy, sets ownership rules (a simple majority of ownership must belong to licensed CPAs), and requires that the licensee supervising attest services meet the competency requirements of professional standards. The same section governs peer review.18
  • Idaho Code 54-221(1) says "Only licensees shall ... offer to render or render any attest or compilation service," and 54-221(3) bars licensees from performing attest services through a business that is not a registered firm in Idaho or another state.2

Two practical points follow. First, a "SOC 2 report" signed by a consulting company, a software platform or an individual who is not a licensed CPA working through a registered firm is not a SOC report at all. Second, every legitimate SOC report names the CPA firm, the city it signed in and the report date, so a buyer can check the firm's license and registration with the state board where it practices. Firms that perform attest work are also subject to the profession's peer review program, which the AICPA uses to check whether firms' engagements conform to standards (more on that below).6

The SOC family: which report answers which question

The AICPA's SOC suite has five main members. They share the same attestation standards but answer different questions for different readers.1

ReportWhat it coversCriteria or objectivesWho it is forDistribution
SOC 1 (AT-C 320)Controls at a service organization that are likely to be relevant to customers' internal control over financial reporting: payroll, claims processing, trust and custody, loan servicing, revenue systemsControl objectives the service organization specifies (for example, "logical access is restricted to authorized users")The customer's controller and its financial statement auditorsRestricted to the service organization, its customers and their auditors
SOC 2 (AT-C 105 and 205)Controls relevant to security, availability, processing integrity, confidentiality or privacy of a system2017 Trust Services Criteria (revised points of focus, 2022); description criteria DC 200 (2018, revised 2022)Customers' security, vendor risk, compliance and audit staff, and regulators who examine those customersRestricted; usually shared under a nondisclosure agreement or through a customer portal
SOC 3The same examination as a SOC 2, reported in short form without the detailed description of tests and resultsTrust Services CriteriaAnyone; often posted publiclyGeneral use
SOC for CybersecurityAn entity's whole cybersecurity risk management program, not one serviceDescription criteria for an entity's cybersecurity risk management program; Trust Services Criteria as control criteriaBoards, investors, business partners, regulatorsAs stated in the report
SOC for Supply ChainControls in a system that produces, manufactures or distributes goodsTrust Services Criteria applied to a production, manufacturing or distribution systemCustomers and business partners of manufacturers and distributorsAs stated in the report

Sources: AICPA SOC suite, SOC 2 guide, SOC for Cybersecurity guide (2024 edition) and SOC for Supply Chain guide (2024 edition); Microsoft's published SOC 2 and SOC 3 pages for distribution practice.1319201421

SOC 1: the report for the financial statement auditors

If a vendor processes transactions that end up in your financial statements, your auditors care about its controls as if they were yours. A SOC 1 Type 2 report lets the vendor's auditor test those controls once and lets every customer's auditor rely on the results instead of sending its own team. The Government Accountability Office put it plainly in its September 2025 report on the Defense Department: customers and their financial statement auditors "can rely on the testing performed by the service auditor if controls are found to be operating effectively," which lets the auditors "reduce the scope of their internal control testing and focus on other audit areas."4

For public companies, the PCAOB's AS 2601 governs how the company's external auditor uses a service auditor's report. The user auditor must judge whether the report is satisfactory, including by asking about the service auditor's professional reputation, decide whether the tests are relevant to significant assertions, and "remains responsible for evaluating the evidence presented by the service auditor." The user auditor may not cite the service auditor's report as a basis for its own opinion.11 How SOC 1 reliance fits into Sarbanes-Oxley Section 404 testing and IT general controls is covered in lesson 8.

SOC 1 control objectives are written by the service organization. A good SOC 1 for a payroll processor will have objectives for logical access, program changes, computer operations, data input, calculation and output. The Treasury report described later in this lesson has fourteen control objectives, six of them general computer controls (system software changes, vendor software changes, program change control, physical access, logical access and computer operations).5 A SOC 1 is not a security report, even though it contains security-relevant controls: its scope stops at what matters to financial reporting. Security teams that accept a SOC 1 in place of a SOC 2 are usually reading a document built for someone else.

SOC 2 and SOC 3: the security reports

A SOC 2 is the report most vendor risk teams ask for. It covers one or more of five Trust Services Criteria categories: security, availability, processing integrity, confidentiality and privacy. Security (the "common criteria") is required in every SOC 2; the other four are optional additions, and a CPA firm that performs these examinations describes privacy as "an expensive add-on."22 A vendor that chooses only security has not been examined on availability, so a customer that needs uptime assurance has to look elsewhere (the contract's service levels and the vendor's continuity testing).

The 2017 Trust Services Criteria are organized so that the common criteria begin with the control environment, communication, risk assessment, monitoring and control activities, following the structure of the COSO 2013 Internal Control framework, then add criteria for logical and physical access, system operations, change management and risk mitigation. Each criterion has "points of focus," which are illustrative characteristics, not a checklist the auditor must find. The AICPA revised the points of focus in 2022 without changing the criteria.15 The criteria are copyrighted; this lesson describes them and does not reproduce them.

A SOC 3 is the short, general-use version of the same examination: the opinion, management's assertion and a short system description, without the detailed tests and results. Microsoft, for example, says its Azure SOC 3 report "is publicly available," while its SOC 1 and SOC 2 reports require a subscription or trial account to download "in accordance with AICPA requirements."2114 A SOC 3 is useful for a first screening and for the public. It is not a substitute for a SOC 2 in a risk review, because the things a reviewer needs most (exceptions, carve-outs, CUECs) are in the parts a SOC 3 leaves out.

Two variations matter for large buyers:

  • SOC 2+ ("SOC 2 plus") adds criteria from another framework (for example, HIPAA Security Rule requirements, the NIST Cybersecurity Framework or the Cloud Security Alliance Cloud Controls Matrix) to the same examination. The 2022 SOC 2 guide includes an illustrative SOC 2+ report.3
  • CSA STAR Attestation is a SOC 2 that also examines the Cloud Security Alliance's Cloud Controls Matrix, which has 197 control objectives in 17 domains. The CSA released an illustrative Type 2 SOC 2 report incorporating the matrix on Aug. 9, 2022, with AICPA input.23 Microsoft's Azure SOC 2 Type 2 report, for example, also addresses the matrix and Germany's C5:2020 cloud criteria.14

SOC for Cybersecurity and SOC for Supply Chain

SOC for Cybersecurity is the one SOC report about an organization rather than a service. A CPA examines management's description of the entity's whole cybersecurity risk management program and the effectiveness of its controls. Management uses the AICPA's description criteria for a cybersecurity risk management program to write the description, and the 2017 Trust Services Criteria serve as the control criteria. The current AICPA guide is dated 2024 and reflects SSAE No. 20 and 21.19 It was designed for boards, investors and business partners who want an independent view of the program, but it has not become a common market requirement; most buyers still ask for a SOC 2 on the specific service they buy. Organizations weighing it against the board reporting described in lesson 3 should ask who would read it and what decision it would change.

SOC for Supply Chain applies the same approach to a system that produces, manufactures or distributes goods. The AICPA guide (2024 edition) frames it around organizations whose ability to meet their goals depends on "events, processes, and controls that are not visible and are often beyond their control, such as a supplier's controls."20 Manufacturers dealing with supplier risk should read it alongside Remote Access, Vendors and Supply Chain in module 111.

New in 2026: assurance for AI systems

On Oct. 19, 2026 the Journal of Accountancy reported that the AICPA had partnered with the Artificial Intelligence Underwriting Company on a joint offering that pairs a SOC 2 report with the company's AIUC-1 certification in one CPA-led engagement covering AI systems and agents. The offering was in a pilot phase, with full launch expected in early 2027.24 Separately, the AICPA's proposed 2027 Trust Services Criteria add points of focus on AI governance, model monitoring, prompt manipulation, data poisoning, transparency of AI-generated outputs, training data management and automated decision-making.925 AI governance more broadly is the subject of lesson 13.

AICPA attestation standardsSSAE 18 as amended through SSAE 21; AT-C 105SOC 1(AT-C 320)Controls relevant tocustomers' financialreportingUsers: controllersand their auditorsRestricted useSOC 2(AT-C 205)Security, plus up tofour more criteriacategoriesUsers: vendor risk,security, auditRestricted useSOC 3Same examinationas a SOC 2, shortform without testdetailsUsers: anyoneGeneral useSOC for Cyber(entity-wide)Whole organization'scyber risk programUsers: boards,investors, partnersSOC Supply Chain(guide, 2024 ed.)Production,manufacturing anddistribution systemsUsers: customersof manufacturersType 1: design, as of one dateNo test results; a first step onlyType 2: design and operationTests and results over a period (often 12 months)SOC 1 and SOC 2 come in Type 1 and Type 2. Only licensed CPA firms may issue any of them.
The five members of the AICPA SOC suite and the two report types. Original graphic for this module; content from the AICPA SOC suite page and SOC guides, the Idaho accountancy act (Idaho Code 54-206 and 54-221) and GAO-25-107731, read Nov. 15, 2026.

Type 1, Type 2 and the period a report covers

Design versus operation

GAO's 2025 report gives a clear plain-language version of the distinction. A type 1 examination evaluates the fairness of management's description and the suitability of the design of controls "as of a specific date," and a type 1 report "does not include service auditor's testing results." A type 2 examination "evaluates both the suitability of the design and the operating effectiveness of the controls" "over a specified period."4 The older PCAOB standard uses different names for the same pair: a report on controls "placed in operation" as of a date, and a report that adds tests of operating effectiveness during a period. Only the second kind can support reducing the user auditor's assessed control risk.11

Put simply: a Type 1 says the locks were installed. A Type 2 says someone checked, many times over months, that the doors were actually locked. Type 1 reports have a place: a new service, a vendor's first year, or a mid-year report on services launched since the last Type 2. Microsoft, for example, commissions mid-year SOC 1 Type 1 and SOC 2 Type 1 examinations for new Microsoft 365 services launched since the last Type 2 audit.14 A Type 1 should be a step toward a Type 2, not a permanent substitute.

How long the period is

No single rule sets the length of a SOC 2 period. Practice runs from about three to twelve months, with twelve the norm for established vendors; one compliance software vendor puts the observation period for a Type 2 at "3-12 months" and the whole Type 2 process at six to twelve months.26 For SOC 1 reports used in public company audits, PCAOB AS 2601 says a report on operating effectiveness should ordinarily cover a minimum period of six months.11 Large providers run back-to-back twelve-month periods with no gaps. Microsoft says its Microsoft 365 SOC Type 2 examinations cover a rolling twelve-month period from Oct. 1 through Sept. 30 and that it "doesn't allow any gaps in the consecutive periods of examination from one examination to the next." For Azure, new reports are issued twice a year (periods ending March 31 and Sept. 30), about six weeks after each period ends.14

The period matters because the customer's need is tied to its own fiscal year or review date. GAO explained that "it is important that SOC 1 examinations be performed annually," because the customer's financial statement auditor "cannot rely on tests of internal controls that are performed outside the financial statement audit period."4 The same logic applies to security: a report whose period ended a year ago says nothing about the vendor's controls since then.

Bridge letters (gap letters)

The gap between the end of a vendor's report period and the customer's year-end or review date is usually covered by a bridge letter, also called a gap letter. Microsoft's description is exact: bridge letters are "self-attestations by Microsoft, not reports based on examinations by the auditor," issued at the end of each quarter to cover the prior three months.14 A bridge letter is management saying nothing material has changed and no significant control failures occurred. It has no auditor's opinion behind it. It is useful because it puts the vendor's management on record, and a false bridge letter is a misrepresentation the customer can act on. But it is not evidence of operating effectiveness, and an internal auditor or a regulator should not see it treated as such. If the gap is longer than about three months, or the vendor had an incident or a major change in the gap, ask for more: the incident report, the change details, or a Type 2 that covers the new period.

Illustrative example: a vendor's SOC 2 Type 2 period and a customer with a June 30 fiscal year-endJan 2026AprJulOctJan 2027AprJul 2027Type 2 period tested: Jan. 1 to Dec. 31, 2026Type 1 (if issued): design as of one date onlyReport issued about6 weeks after period endBridge 1Bridge 2Customeryear-endBridge letters are the vendor's own statements, not auditor opinions. Anything after Dec. 31, 2026has no independent testing until the next Type 2 report covers it.
Type 1, Type 2 and the gap that bridge letters cover. Dates are illustrative. Original graphic for this module; the six-week issuing time and quarterly bridge letters follow Microsoft's published description of its SOC reports, and the reliance point follows GAO-25-107731 and PCAOB AS 2601, read Nov. 15, 2026.
The AICPA offices in an office park in Durham, North Carolina
Offices of the American Institute of Certified Public Accountants in Durham, North Carolina, in 2009. The AICPA sets the standards that SOC 1 and SOC 2 examinations are performed under. Photo: Ildar Sagdejev (Specious). Wikimedia Commons, CC BY-SA 4.0.

Subservice organizations and complementary controls: who does what

No service organization runs its whole system alone. A software company runs on a cloud provider; a payroll processor uses a print-and-mail vendor and a bank; a claims administrator uses a data center. And every service assumes the customer does certain things, such as approving its own users. The report handles these two facts with four terms that a reviewer must understand.

Carve-out and inclusive methods

A subservice organization is a vendor's vendor whose services are likely to be relevant to the customer's controls. Management's description must say which subservice organizations are used and "whether the carve-out method or the inclusive method has been used in relation to them," in the words of the Treasury report quoted below.5

  • Carve-out method: the description and the auditor's testing exclude the subservice organization's controls. The report says which controls the service organization assumes the subservice organization performs. The customer must get assurance on the subservice organization some other way, usually that vendor's own SOC report. Carve-out is by far the more common method, especially for cloud hosting.
  • Inclusive method: the subservice organization's relevant controls are included in the description and tested by the service auditor, with the subservice organization's agreement. It is more complete and much less common, because the large subservice providers rarely let a customer's auditor test them.

The Treasury Department's Funds Management Branch report shows a carve-out in plain words. KPMG's opinion says the description "includes only the control objectives and related controls of Fiscal Service and excludes the control objectives and related controls of the subservice organizations," and "Our examination did not extend to controls of the subservice organizations."5

Complementary subservice organization controls (CSOCs) and complementary user entity controls (CUECs)

GAO's definitions, written for the Defense Department but true of every SOC report, are the clearest available:

  • CUECs "are customer controls that service organization management assumes, as a part of the design of its system," its customers will implement.4
  • Complementary subservice organization controls "are controls that management of the service organization assumes, in the design of its system, will be implemented by the subservice organizations."4

These assumptions are written into the opinion itself. The Treasury report's opinion says the controls were suitably designed and operated effectively "if complementary subservice organization controls and complementary program entity controls, assumed in the design of Fiscal Service's controls, operated effectively throughout the period" (a "program entity" is that report's word for a user entity).5 The word "if" carries the weight. The report goes on: "In order for program entities to rely on the controls reported on herein, each program entity must evaluate its own internal control to determine whether the identified complementary program entity controls have been implemented and are operating effectively." Its list starts with "Access to FedInvest is restricted to properly authorized individuals" and "Only authorized receipts are deposited into the Trust Funds."5

GAO drew the consequence: auditors "may not be able to rely on the report" if the customer "has not designed and implemented controls to address the CUECs," and "relevant internal controls, including those of the service organization, any subservice organizations, and the customer, must function effectively for the internal controls in the SOC 1 report to be relied on."4

Typical CUECs in a SOC 2 for a cloud application include: approving and removing the customer's own user accounts; reviewing user access periodically; enforcing multifactor sign-in if the service offers it as a setting; protecting API keys and integration credentials; reviewing audit logs the service makes available; telling the vendor promptly about departed administrators or suspected compromise; configuring data retention and sharing settings; and checking the accuracy of data the customer sends in. These are exactly the controls a busy customer forgets it owns.

The 2024 cloud data platform thefts: a CUEC failure at national scale

In June 2024, Google's Mandiant unit reported that a financially motivated group it tracks as UNC5537 was "systematically compromising Snowflake customer instances using stolen customer credentials," mostly obtained from information-stealing malware on systems Snowflake did not own. Mandiant and Snowflake notified "approximately 165 potentially exposed organizations." The affected accounts "were not configured with multi-factor authentication enabled, meaning successful authentication only required a valid username and password." Mandiant said its investigation "has not found any evidence to suggest that unauthorized access to Snowflake customer accounts stemmed from a breach of Snowflake's enterprise environment."27

Whatever any provider's own attestation says, this is the shape of a customer-side failure: sign-in protection for the customer's own accounts was a setting the customer controlled, and many customers had not used it. A vendor risk program that read the provider's report, saw a clean opinion and filed it, without mapping each CUEC to an internal owner and checking that the control was in place, would not have found the gap. Identity controls themselves are covered in Identity and Access.

Subservice organization(for example, the cloud host)Carved out: not testedData center physical accessHardware and powerHost and hypervisor patchingEvidence: its own SOC reportService organization(the vendor)Tested by the CPA firmApplication access controlsChange managementLogging and monitoringBackups and recoveryUser entity (you)(the customer)CUECs: assumed, not testedApprove and remove usersTurn on multifactor sign-inReview access and logsProtect API keysThe opinion covers the middle column, and only IF the controls in both outer columns operate.Left: complementary subservice organization controls. Right: complementary user entity controls.Map every CUEC to an owner in your organization; get the cloud host's own report.
Who does what under the carve-out method. Example controls are illustrative. Original graphic for this module; definitions from GAO-25-107731 (Sept. 18, 2025), wording of conditional opinions from Treasury OIG-25-004 (Oct. 31, 2024).

How to read a SOC report, section by section

Most SOC 1 and SOC 2 reports follow the same layout, because the attestation standards and the AICPA guides prescribe the content. The Treasury Funds Management Branch SOC 1 Type 2 report for Aug. 1, 2023 to July 31, 2024, published by the Treasury Inspector General on Oct. 31, 2024, is a free public example that anyone can download and follow along with.5

SectionWritten byWhat to read forI. Service auditor's opinionCPA firmType, period, system, criteria, opinion type, carve-outsII. Management's assertionVendorMirrors the opinion; who signed itIII. System descriptionVendorBoundary, subservice orgs, CUECs, incidents, changesIV. Controls, tests, resultsCPA firmExceptions: are they in areas you rely on?V. Other informationVendorNot examined: management responses, plansSections I to III are covered by the opinion; section V is not. Management responses to exceptionsare the vendor's own words, not tested by the auditor.
How a SOC report is laid out. Original graphic for this module; structure follows the Treasury Funds Management Branch SOC 1 Type 2 report (OIG-25-004, Oct. 31, 2024) and the AICPA description criteria.

Section I: the independent service auditor's report (the opinion)

Read this first, all of it. Check:

  • The firm, the signing city and the date. Confirm it is a CPA firm. The Treasury report was performed by KPMG LLP under a contract monitored by the Inspector General, under both AICPA attestation standards and the Government Auditing Standards.5
  • The type, the period and the system name. Is this the service you actually buy? Many vendors have several products and only some are in scope.
  • The criteria. For a SOC 2, which Trust Services Criteria categories are covered. For a SOC 1, the control objectives are the vendor's own.
  • Carve-out and complementary control paragraphs. These tell you what was not examined and what you must do.
  • The opinion paragraph and its type.

An unmodified opinion (often called "clean" or "unqualified") says, in all material respects, that the description is fairly presented and the controls were suitably designed and (for Type 2) operated effectively throughout the period. The Treasury report's version reads, in part, that "the Description fairly presents the system that was designed and implemented throughout the period" and that the controls "operated effectively to provide reasonable assurance that the control objectives stated in the Description were achieved throughout the period," conditioned on the complementary controls.5

A modified opinion is issued when there are scope limitations or material misstatements. GAO summarizes the three forms: "if the effects are not pervasive, the opinion will be qualified"; for "a scope limitation with a pervasive effect, the opinion will be a disclaimer of opinion"; and for "a material misstatement with a pervasive effect, the opinion will be adverse."4 In a SOC report a "misstatement" usually means that the description is not fairly presented, or that controls were not suitably designed or did not operate effectively to meet a control objective or criterion. A qualified opinion is often issued "except for" one control objective or criterion. That one area may be exactly the one you care about.

Opinions change from year to year. GAO looked at eight Defense Department SOC 1 reports and found one consistently unmodified, two modified and five that "fluctuated" between modified and unmodified; "most of the SOC 1 audit opinions changed at least once" over the period it studied, and the deficiencies clustered in logical access, configuration management, segregation of duties and processing.4 A vendor risk program should record the opinion type every year and treat a change as an event.

Section II: management's assertion

Management states that its description is fairly presented and its controls were suitably designed and operating effectively, based on the criteria. It mirrors the opinion. Read it to confirm the scope and to note who signed it. In a SOC 2, management's assertion is a statement the vendor's executives own; a materially false assertion is a misrepresentation by the vendor, not just an auditing problem.

Section III: the system description

This is the vendor's own account of the system: services, infrastructure, software, people, data, procedures, subservice organizations and the methods used for them, complementary controls, significant changes during the period and (for SOC 2) system incidents and commitments. For SOC 2 it is written against the AICPA's 2018 description criteria, with revised implementation guidance issued in 2022.16 The Treasury SOC 1 assertion lists the elements that must be described, including "services performed by a subservice organization, if any, including whether the carve-out method or the inclusive method has been used in relation to them," and "relevant details of changes" to the system during the period.5

Read the description for: the boundary (which products, data centers, regions and teams are in scope); the list of subservice organizations; the CUEC list; disclosures of incidents during the period; and significant changes, such as a migration to a new cloud platform or an acquisition. A description that names no incidents and no changes in a fast-growing company deserves a question.

Section IV: the controls, tests and results

In a Type 2 report this is the longest section: each criterion or control objective, the vendor's controls that address it, the auditor's test (inquiry, observation, inspection or reperformance) and the result. Results usually read "No exceptions noted." The Treasury report says that 14 times and reports no exceptions at all.5 When the result is an exception, it describes the deviation; an illustrative example would be that access for 2 of 25 sampled departing employees was not removed within the required time.

Exceptions are not automatically bad. A Type 2 with zero exceptions across hundreds of tests in a large, changing organization can mean a mature vendor, or a thin examination. What matters is whether exceptions are in controls that matter to you, whether they are isolated or systemic, whether there are compensating controls, and whether the auditor still concluded the criterion was met. The opinion tells you whether the auditor judged the exceptions serious enough to modify the opinion; the exceptions tell you what to ask about anyway.

Section V: other information, including management responses

Many reports end with information the auditor did not examine, such as management's responses to exceptions, continuity plans or future plans. The Treasury report's opinion says its Section V information on contingency planning and network performance "has not been subjected to the procedures applied in the examination" and "accordingly, we express no opinion on it."5 A management response saying "this has been fixed" is the vendor's statement, not the auditor's. If the fix matters to you, ask for evidence or confirm it in the next period's results.

Reading for what is missing

Reviewers who read many reports learn to look for what is absent:

  • Scope gaps: the product you use, the region that holds your data, or the support team that can access your data is not in the boundary.
  • Category gaps: no availability criteria for a service you depend on hour to hour; no confidentiality or privacy criteria for a vendor holding personal data.
  • Period gaps: the period ended long ago, or a Type 1 is offered where a Type 2 should exist by now.
  • Carve-outs with no follow-up: the critical subservice organization is carved out, and nobody has its report.
  • Generic text: a description and control set that could describe any company, with no mention of the vendor's actual products, tools or incidents. The AICPA's peer review program warned in 2026 about engagements with identical reports, risk assessments, sample sizes and testing procedures (below).6

The proposed 2027 Trust Services Criteria

The criteria in force today date from 2017, with revised points of focus from 2022.15 On Oct. 26, 2026 the AICPA's Assurance Services Executive Committee posted exposure drafts of "Proposed 2027 SOC 2" Trust Services Criteria and description criteria, with a redlined version.1 The AICPA's announcement says the update is meant to enhance "the relevance, usability and value of CPAs' reports."9 The AICPA's Oct. 28, 2026 announcement and the Journal of Accountancy report on it add the details:925

  • Comment deadline: Jan. 15, 2027.
  • Proposed effective date: if approved, the 2027 criteria would apply to engagements beginning on or after Dec. 31, 2027, with early adoption permitted.
  • Restructuring: merging overlapping concepts, removing some criteria, adding others that need more clarity or emphasis, and rewording for consistency.
  • AI and emerging technology: new points of focus on AI governance, model monitoring, prompt manipulation, data poisoning, transparency of AI-generated outputs, training data management and the risks of automated decision-making.

The AICPA's Amy Pawlicki said the revisions "are intended to improve the usability of SOC 2 reports."9 The full drafts require a free AICPA account and were not reviewed line by line for this lesson. For planning: vendors whose report periods begin in 2028 should expect auditors to ask about the new criteria; customers should expect a transition year in which some reports use the 2017 criteria and some the 2027 version, and should note which version each report uses.

Exterior of an audit office building in Kolkata
A government audit office in Kolkata, India, photographed in 2013. Independent examination by people outside the organization is the core idea behind every attestation. Photo: Sujay25. Wikimedia Commons, CC BY-SA 4.0.

Producing a SOC 2: the service organization's side

Large organizations are on both sides of SOC reports. A bank buys dozens; its trust department may issue its own SOC 1. A hospital system buys hundreds; its revenue cycle subsidiary may sell services to other hospitals and need a SOC 2. A state agency that processes payroll or benefits for other agencies may issue a SOC 1, as the Treasury example shows. This section is for the leaders who must commission a report.

Steps to a first report

  1. Decide whether you need one, and which one. Start from customer contracts and the questions you are being asked. Financial reporting effects point to SOC 1; security and availability questions point to SOC 2; some customers need both. Check whether a certification (ISO/IEC 27001, HITRUST) or a government authorization (FedRAMP, GovRAMP, CMMC) would answer the same customers; see lesson 6.
  2. Set the scope. Name the system: the services, products, infrastructure, locations, teams and data covered. Choose the Trust Services Criteria categories. Every added system, location and category adds cost, and the CPA firm Linford & Co. lists the scope of the assessment, Type 1 or Type 2, the nature of the services, the organization's size and maturity, the number of locations and reliance on subservice providers as the main drivers of fees.22
  3. Run a readiness assessment. Compare current controls to the criteria and the description criteria, list gaps, and assign owners and dates. This can be done by internal audit, a consulting firm or the CPA firm that will not be performing the examination (independence rules limit what the examining firm itself may do).
  4. Remediate. Write missing policies, implement missing controls and, above all, make sure controls produce evidence: tickets, approvals, logs, review sign-offs. A control that works but leaves no record cannot be tested. Where remediation changes production systems (for example, turning on multifactor sign-in for administrators or changing logging), plan the change, test it and have a way back.
  5. Choose the CPA firm. Confirm license and firm registration, ask for the firm's most recent peer review results, ask how many SOC engagements it performs a year and how long fieldwork takes, and ask whether it has any business arrangement with your compliance software vendor (see the next section).718
  6. Write the system description. Management writes it, not the auditor. It must meet the description criteria, name subservice organizations and the carve-out or inclusive method, list complementary controls, and disclose significant incidents and changes.16
  7. Type 1 or straight to Type 2. Many first-time vendors issue a Type 1 to answer customers quickly, then start a Type 2 period. If customers will accept a short first period (three to six months), going straight to Type 2 can save a cycle.26
  8. Operate the controls through the period and collect evidence continuously. Most exceptions come from controls that lapsed in the middle of the period: a quarterly access review skipped during a reorganization, a departed employee whose access lingered.
  9. Fieldwork, exceptions and the report. The auditor samples evidence across the period, discusses exceptions, and drafts the report. Management prepares responses to exceptions. Expect several weeks from period end to report; Microsoft says its Azure reports take about six weeks after each period ends.14
  10. Run it as an annual cycle. Start the next period the day after the last one ends, issue quarterly bridge letters, keep a report distribution log and a nondisclosure agreement process, and brief the board or audit committee on the opinion and the exceptions.

What it costs and how long it takes

No official source publishes SOC report prices. The figures below come from firms that sell these services, which have an interest in the answer; treat them as rough estimates, not market data.

ItemEstimateSource (and its interest)
SOC audit fees, general range"$20,000 to $150,000, with a median price around $30,000"Linford & Co., a CPA firm that performs SOC examinations (updated Feb. 4, 2026)22
Largest audit firmsFees "start in the low six figures and go into the millions of dollars"Linford & Co.22
SOC 2 Type 1 audit fee, large organizations$20,000 to $60,000Drata, a compliance automation software vendor (page dated March 25, 2026)26
SOC 2 Type 2 audit fee, large organizations$30,000 to $100,000 or moreDrata26
Readiness (gap) assessment$5,000 to $25,000Drata26
Type 2 observation period3 to 12 monthsDrata26
Internal costs"will often exceed audit fees"Linford & Co.22

For a context check on the public sector, the Defense Department Inspector General reported that the department spent over $15.5 million in fiscal year 2023 on 30 SSAE 18 engagements, more than $500,000 per engagement on average, for very large financial systems.28 Large commercial providers with many products and regions are in the same range or higher.

Report quality: quick-turn reports, software platforms and the 2026 warnings

Since about 2020, compliance automation platforms have made it much faster to prepare for a SOC 2: they connect to cloud accounts and HR systems, collect evidence automatically, supply policy templates and refer customers to partner CPA firms. Used well, they cut the clerical work. The risk is that the speed carries over into the examination itself. In 2026 the profession said so publicly, several times.

  • February 2026. The Journal of Accountancy ran an article titled "Promises of 'Fast and Easy' Threaten SOC Credibility."6
  • April 13, 2026. The AICPA's ethics staff published an Ethics Staff Insight on business arrangements with SOC 2 tool providers. It says "AICPA members increasingly enter business arrangements with SOC 2 tool providers" and that these relationships "can raise significant threats to compliance with the Code of Professional Conduct," naming "potential threats to independence and objectivity."7
  • April 30, 2026. A Journal of Accountancy podcast covered "The risks of quick-turn SOC engagements and what CPAs should know."29
  • May 14, 2026. The AICPA Peer Review Board, after monitoring firms doing SOC 2 work "including high-volume providers using third-party platforms," issued guidance to peer reviewers. It says reviewing a single SOC 2 file is often not enough, that reviewers may select about five SOC 2 engagements from different partners, and that engagements with identical reports, risk assessments, sample sizes and testing procedures may not conform to professional standards. An AICPA official is quoted: "Some firms are leaning too heavily on third-party SOC platforms." Beginning June 1, 2026, AICPA staff planned to identify scheduled peer reviews of SOC 2 firms, contact the review team captains early and offer support, and the guidance refers to the Peer Review Board's enhanced oversight program.6
  • Through November 2026. The AICPA's SOC page carries a notice that it "is looking into allegations published anonymously about the business practices of a compliance vendor."1

The allegations that notice refers to were published by an anonymous writer and reported by the research firm IANS on March 24, 2026. As IANS summarized them, the writer alleged that a venture-funded compliance automation startup generated "fabricated SOC 2 and ISO 27001 evidence," that audit conclusions were written before observation periods ended, and that most customers were steered to a small set of audit firms; an analysis of a leaked spreadsheet cited in the allegations reportedly found near-identical boilerplate in 493 of 494 SOC 2 reports and identical auditor conclusions across 259 Type 2 reports. The company denied the claims; as IANS summarized its response, it does not issue compliance reports, independent auditors give the opinions, that its materials are standard templates, and that customers choose their own auditors. IANS reported no finding by any regulator, court or professional body, and as of Nov. 15, 2026 this lesson found none.8 These are allegations, not findings. They matter here because they show what a buyer cannot see from a report's cover and what questions to ask, whoever the vendor is.

What a large buyer can do, drawn from the AICPA guidance and IANS's recommendations:68

  • Check the CPA firm's license, registration and peer review results, and whether it has a referral or revenue arrangement with the vendor's compliance platform.
  • Look for signs of a tailored engagement: a description that names the vendor's real products and tools, exceptions that look like a real company's, sample sizes that fit the population, and an engagement timeline that makes sense.
  • For critical vendors, spot-check a handful of controls directly (ask to see a recent access review or change ticket), and compare the report with the vendor's questionnaire answers and trust page.
  • If a report later proves unreliable, treat everything that relied on it as unproven: re-review access, logging, incident response and change management for that vendor, and correct any assurance you passed to your own customers or regulators.

SOC 2 versus ISO/IEC 27001 for customers

Global vendors often offer both, and buyers often ask which is better. They answer different questions.

QuestionSOC 2 Type 2ISO/IEC 27001:2022 certificate
What is it?A CPA's opinion on a system description and on controls against the Trust Services CriteriaA certification body's decision that the information security management system conforms to the standard
Who issues it?A licensed CPA firm under AICPA attestation standardsA certification body accredited by a national accreditation body (in the U.S., commonly ANAB)
What do you receive?A long report with the description, tests and results, exceptions, carve-outs and CUECsA certificate with a scope statement; the Statement of Applicability and audit reports on request, if the vendor agrees
Does it test operation over a period?Yes, with the tests and results shownAudits sample evidence, but the results are not published in detail
CycleUsually annual, back-to-back periodsThree-year certificate with annual surveillance audits
Where it is most asked forU.S. customers, auditors and regulatorsInternational customers and public tenders
Version issue in 2025 to 20272017 criteria now; proposed 2027 criteria would apply to engagements beginning on or after Dec. 31, 2027Certificates to the 2013 edition had to be transitioned by Oct. 31, 2025

Sources: AICPA SOC materials; Irish National Accreditation Board transition notice applying IAF MD 26; AICPA 2027 proposal.1109 For a vendor risk team, the SOC 2 Type 2 usually gives more usable evidence, because it shows test results and lists the customer's responsibilities. The ISO certificate shows that a management system exists and is being audited on a cycle, which says more about whether the program will keep working. Many large buyers ask for either, then use questionnaires to fill what the chosen document leaves out. Health care buyers may also ask for HITRUST, which is covered in lesson 6.30

Running a SOC report review program in a large organization

A large organization may receive several hundred SOC reports a year. Reading each one well takes hours; reading none of them well is the usual failure. The answer is a program with tiers, owners and records.

What regulators expect

  • Banks. The federal banking agencies' Interagency Guidance on Third-Party Relationships (June 2023) applies the full relationship life cycle to vendors.31 Their May 2024 guide for community banks names "System and Organization Controls (SOC) reports, independent assessments, and industry certifications to assess the third party's operational risk management and internal controls" as due diligence sources, and in ongoing monitoring lists "Review and testing of control effectiveness to assess whether the third party's control environment remains sound, including SOC reports and self-assessments to industry standards."32 A SOC report is one input among several, reviewed before signing and again as the relationship continues.
  • Financial institutions under the FTC Safeguards Rule must oversee service providers, including "[p]eriodically assessing your service providers based on the risk they present and the continued adequacy of their safeguards."33
  • New York-regulated entities. 23 NYCRR 500.11 requires a third-party service provider policy, and the Department of Financial Services wrote on Oct. 21, 2025 that covered entities "may not delegate responsibility for compliance" to a vendor.34
  • Broker-dealers, investment advisers and other firms under SEC Regulation S-P must have written policies for oversight of service providers, including a service provider's notice of a breach no later than 72 hours after becoming aware of it; larger firms had to comply by Dec. 3, 2025 and smaller ones by June 3, 2026.35
  • Public companies. Regulation S-K Item 106(b) asks whether the company has processes to oversee and identify risks from cybersecurity threats associated with its use of third-party service providers, disclosed in the 10-K's Item 1C.36 Board-level duties are covered in Governance: Boards, Officers and Disclosure.

None of these rules says "get a SOC 2." They all say, in different words, that the organization keeps responsibility and must have evidence that it checked. A filed, unread SOC report is weak evidence of that.

The review workflow

  1. Tier the vendor first. Use the vendor tiers from 108 lesson 8. Critical and high-risk vendors get a full report review every year; lower tiers get a lighter check.
  2. Request the right report. SOC 2 Type 2 for security; SOC 1 Type 2 if the service affects financial reporting (coordinate with the controller and external auditors); both where both apply. Ask for bridge letters to cover the gap to your review date.
  3. Log the basics. Report type, period, CPA firm, opinion type, criteria covered, system name, number of exceptions, subservice organizations and method, number of CUECs. A spreadsheet or GRC tool field for each makes trends visible.
  4. Read the opinion and the exceptions. Decide whether any modification or exception touches your use of the service. Ask the vendor for an explanation and remediation evidence where it does.
  5. Map every CUEC to an internal owner. For each complementary user entity control, record who in your organization performs it, how, and where the evidence is. This is the step most often skipped, and GAO and the Defense Department Inspector General found it skipped at the Defense Department (see Common mistakes).428
  6. Follow the carve-outs. For each carved-out subservice organization that matters (usually the cloud host), get that provider's report or confirm the vendor reviews it. The Treasury Funds Management Branch, for example, documents that it "obtains relevant SOC 1 reports from subservice organizations" and reviews them on a memorandum.5
  7. Record a conclusion and the reviewer. Accept, accept with conditions (follow-up items with dates), or escalate. The record is what an examiner, internal auditor or board will ask for.
  8. Feed results into the contract and the risk register. Repeated exceptions, a modified opinion or a refusal to provide a report should affect renewal decisions, contract terms and the vendor's risk rating; see lesson 4 for exceptions and risk acceptance.
  9. Report the program upward. Coverage (percentage of critical vendors with a current Type 2 reviewed), open follow-ups and modified opinions belong on the board or audit committee dashboard described in lesson 3.

When the vendor has no report, or will not share it

Some critical vendors have no SOC report: a small specialized software maker, a regional hospital's transcription service, a local government's records vendor. Options include an ISO/IEC 27001 certificate, a HITRUST or PCI DSS attestation where relevant, a detailed questionnaire with evidence, a contractual right to audit, an on-site or remote review by your own team, a requirement to obtain a report within a stated time, or compensating controls on your side (for example, limiting the data the vendor receives). A vendor that has a report but refuses to share it even under a nondisclosure agreement is telling you something.

A worker at an office accounting machine in 1954
A Seattle City Light worker at an office machine in 1954. SOC 1 reports grew out of auditors' need to rely on service organizations that process financial records. Photo: Seattle Municipal Archives. Wikimedia Commons, CC BY 2.0.

The limits of a SOC report

A SOC report is valuable evidence. It is also easy to read for more than it says. Its limits, which the reports themselves state:

  • It is about the past. The Treasury report's "Inherent Limitations" paragraph warns that "the projection to the future of any evaluation" is subject to the risk that controls may become inadequate or fail.5
  • Management chooses the scope. The vendor decides which system, which categories and (for SOC 1) which control objectives. A clean report on a narrow scope is still clean.
  • It is written for many customers. The Treasury report says the description "is prepared to meet the common needs of a broad range of program entities and their auditors" and "may not, therefore, include every aspect of the System that each individual program entity may consider important."5
  • Controls can be circumvented. The same paragraph notes that controls "may not prevent, or detect and correct, all misstatements."5 A Type 2 tests samples, not every event, and does not test for every way an attacker might get in.
  • It does not cover your side. CUECs and your own configuration of the service are outside the opinion, as the 2024 cloud data platform thefts showed.27
  • It does not prove compliance with a law. A SOC 2 is not a HIPAA, GLBA or state privacy law compliance finding. A SOC 2+ can map criteria to another framework, but the opinion is still an opinion on controls, not a legal conclusion.3

So a vendor can have a clean SOC 2 and still suffer a breach. The report may have been accurate about the period it covered, the breach may have come through something out of scope, a control may have failed after the period, or the failure may have been on the customer's side. None of that makes SOC reports worthless; it means they are one source of evidence, to be combined with contracts, monitoring, incident notice terms and your own controls. 108 lesson 8 covers those other parts.

Sample: SOC Report Review Checklist

Sample only. Adapt it to your organization's risks, systems and laws, have qualified people review it, and do not treat it as a substitute for a risk assessment.

Follows: GAO-25-107731 (Sept. 18, 2025) on type 1 and type 2 reports, CUECs, complementary subservice organization controls and modified opinions; PCAOB AS 2601; the AICPA SOC 2 guide (Oct. 15, 2022) and 2018 description criteria (revised 2022); the federal banking agencies' Third-Party Risk Management guide for community banks (May 2024); FTC Safeguards Rule 16 CFR 314.4(f); the AICPA Peer Review Board guidance of May 2026.

Part A: Report identification

  • Vendor: [name]. Service(s) we use: [list]. Vendor tier: [critical / high / moderate / low].
  • Report type: [SOC 1 / SOC 2 / SOC 3 / SOC 2+ / other]. Type: [1 / 2]. Period: [start] to [end], or "as of" date: [date].
  • CPA firm: [name, city, report date]. License and firm registration checked with state board on [date]. Peer review results obtained: [yes / no]. Any known business ties between the firm and the vendor's compliance platform: [describe or "none disclosed"].
  • Criteria covered (SOC 2): [security / availability / processing integrity / confidentiality / privacy]. Criteria version: [2017 TSC (revised 2022) / 2027 TSC]. Additional frameworks (SOC 2+): [list].
  • System covered matches the service we use: [yes / no / partly, explain]. Regions or data centers holding our data in scope: [yes / no].

Part B: Opinion and results

  • Opinion: [unmodified / qualified / adverse / disclaimer]. If modified, the criterion or objective affected: [describe] and its relevance to us: [describe].
  • Number of exceptions: [n]. Exceptions in areas relevant to us (access, change management, logging and monitoring, incident response, backup, encryption, vendor management): [list].
  • Management responses reviewed (not audited): [yes / no]. Evidence of remediation requested: [yes / no, date].
  • Incidents and significant changes disclosed in the description: [list]. Our follow-up questions: [list].
  • Change in opinion type or exception count from last year: [describe].

Part C: Subservice organizations

  • Subservice organizations listed: [names]. Method for each: [carve-out / inclusive].
  • For each carved-out subservice organization that matters to us: report obtained and reviewed by [us / vendor], period [dates], opinion [type].
  • Complementary subservice organization controls listed: [n]; any concerns: [describe].

Part D: Complementary user entity controls (CUECs)

  • Number of CUECs: [n].
  • For each CUEC: control text [copy]; internal owner [name, role]; how performed [describe]; evidence location [system or file]; last checked [date]; gap [yes / no].
  • CUECs not in place: [list], with remediation owner and date: [ ]. Note: until a CUEC is in place, the vendor's opinion does not cover the related risk for us.

Part E: Period coverage and bridge

  • Months between period end and our review date or fiscal year-end: [n].
  • Bridge letter received covering [dates]; signed by [name, title]. Bridge letter is management's statement, not an auditor's opinion.
  • If the gap exceeds [3] months, or the vendor had an incident or major change in the gap: additional evidence requested [describe].

Part F: Quality signals

  • Description specific to this vendor's actual products and tools: [yes / no].
  • Test procedures and sample sizes appear tailored and proportionate: [yes / no / unclear].
  • Engagement timeline reasonable for the scope: [yes / no / unclear].
  • For critical vendors, direct spot-check of [2 to 5] controls completed on [date] with result [ ].

Part G: Conclusion

  • Conclusion: [accept / accept with conditions / escalate]. Conditions and due dates: [list].
  • Risk register entry updated: [ID]. Contract or renewal actions: [describe].
  • Reviewer: [name, role], date [ ]. Approver for critical vendors: [name, role], date [ ].
  • Next review due: [date]. Report stored at [location] under the nondisclosure terms of [agreement].

Pictures, Numbers and Infographics

The numbers in this table are the ones most worth remembering from this lesson. Each comes from the source in its note; estimates from interested sellers are labeled.

Number or dateWhat it isSource
April 1992; April 2010; May 1, 2017SAS 70 issued; SSAE 16 replaces it; most of SSAE 18 takes effectSummary of AICPA history12
June 15, 2022SSAE 21 effective (reports dated on or after); adds direct examinations, revises AT-C 205Journal of Accountancy, 202013
Oct. 15, 2022Date the current AICPA SOC 2 guide was updated as ofAICPA3
6 monthsMinimum period a SOC 1 operating effectiveness report should ordinarily cover for public company auditsPCAOB AS 2601.5311
About 6 weeks; quarterlyTime from period end to Azure SOC report; frequency of Microsoft bridge lettersMicrosoft14
27 examinations, 8 organizations, about 85 customersDefense Department SOC 1 examinations in fiscal 2024GAO-25-1077314
43 percentShare of Defense Department customers with service organization monitoring processes, as of December 2024GAO-25-1077314
Over $15.5 million; 30 engagementsDefense Department spending on SSAE 18 engagements, fiscal 2023DoD Inspector General, DODIG-2025-04428
14 control objectives; 14 "No exceptions noted"Treasury Funds Management Branch SOC 1 Type 2, Aug. 1, 2023 to July 31, 2024Treasury OIG-25-0045
$20,000 to $150,000; median about $30,000General SOC audit fee range (estimate from a CPA firm that sells them)Linford & Co., 202622
$30,000 to $100,000 or more; 3 to 12 monthsSOC 2 Type 2 fee for large organizations; observation period (estimate from a software vendor)Drata, 202626
About 165Organizations notified as potentially exposed in the 2024 cloud data platform credential theftsMandiant, June 202427
About 5SOC 2 engagements, from different partners, peer reviewers may select at a high-volume firmAICPA Peer Review guidance, May 20266
493 of 494; 259Alleged near-identical reports and identical Type 2 conclusions in the March 2026 anonymous allegations (denied; no official finding)IANS, March 24, 20268
197 objectives, 17 domainsCloud Controls Matrix examined in a CSA STAR AttestationCloud Security Alliance, 202223
Oct. 31, 2025Deadline to transition ISO/IEC 27001 certificates from the 2013 to the 2022 editionINAB, applying IAF MD 2610
Jan. 15, 2027; Dec. 31, 2027Comment deadline for proposed 2027 Trust Services Criteria; proposed effective date (engagements beginning on or after)AICPA, Oct. 28, 20269
The Defense Department's SOC 1 program in numbers27SOC 1 examinationsfiscal 2024 (GAO)8DoD service organizationsundergoing them (GAO)about 85customers servedfiscal 2024 (GAO)43%customers with monitoringprocesses, Dec. 2024 (GAO)$15.5M+spent on 30 SSAE 18engagements, fiscal 2023 (IG)28DoD material weaknessesfiscal 2024 (GAO)Reliance on shared reports only saves money when customers run their own complementary controls.
A public example of a large SOC 1 program and its weak point. Original graphic for this module; data from GAO-25-107731 (Sept. 18, 2025) and DoD OIG DODIG-2025-044 (Nov. 26, 2024).

The SOC family map, the Type 1 and Type 2 timeline, the responsibility split for complementary controls and the report anatomy diagram appear earlier in this lesson, next to the sections they explain. Photographs for this lesson are placed where they fit the text.

Common mistakes

Not running the complementary user entity controls

The Defense Department Inspector General reported on Nov. 26, 2024 that the department did not "prioritize the designing and implementing of effective complementary user controls," that service organizations did not consistently include all relevant controls in their documentation, and that auditors therefore did not consistently rely on SOC 1 reports and performed extra testing, which the Inspector General said is inefficient and raises audit cost. The department had spent over $15.5 million on 30 such engagements in fiscal 2023.28 GAO followed in September 2025, finding that only 43 percent of the department's customers had service organization monitoring processes in place as of December 2024, and that when customers have not implemented the CUECs, auditors "may not be able to rely on the report."4 Paying for a report and then not doing the customer's part wastes the money.

Assuming the provider's controls cover the customer's settings

In the 2024 cloud data platform thefts, attackers used stolen customer passwords against accounts that "were not configured with multi-factor authentication enabled," and Mandiant found no evidence that the provider's own enterprise environment had been breached.27 Multifactor sign-in for the customer's own users was the customer's control to turn on. Organizations that treated the provider's assurance as covering their own accounts learned otherwise.

Filing the report without tracking the opinion

GAO found that most Defense Department SOC 1 opinions it examined "changed at least once," and that the service organizations behind three of the eight SOC 1 reports in its sample did not consistently perform or document their own root cause analyses of deficiencies; the department updated its guidance in January 2025 to require that documentation.4 A program that records only "SOC report received" will not notice that a vendor moved from unmodified to qualified, or that the same exception is back for the third year.

Accepting a fast, templated report without question

The AICPA's own peer review program said in May 2026 that engagements with identical reports, risk assessments, sample sizes and testing procedures may not conform to standards, and that some firms "are leaning too heavily on third-party SOC platforms."6 The March 2026 allegations about one compliance startup, which the company denied and which no authority has resolved, describe the worst case: reports whose conclusions were allegedly written before the testing period ended.8 A buyer that accepts any report with the right words on the cover takes on that risk.

Treating a bridge letter as audit evidence

Bridge letters are management's self-attestations, "not reports based on examinations by the auditor," in Microsoft's description of its own letters.14 Using a stack of bridge letters to stretch an old Type 2 across a whole year, or across a period with a known incident, leaves the organization with no independent evidence for that time. PCAOB AS 2601 makes the same point for auditors: the further a test is from the period under audit, the less support it gives.11

Accepting the wrong report

A SOC 1 offered in answer to a security questionnaire, a SOC 3 offered in place of a SOC 2, a SOC 2 covering a different product, or a report that carves out the cloud host where the data actually lives: each looks like compliance and leaves the real question unanswered. Regulators' guidance treats SOC reports as one input to be evaluated, not a box to tick.32

Questions people ask

Is a SOC 2 a certification?

No. It is a CPA firm's attestation report: an opinion on management's description and controls, for a period, against the Trust Services Criteria. Nobody is "SOC 2 certified." Under Idaho law, as in other states, SOC examinations are attest services reserved to licensed CPAs practicing through registered firms.172

Should we ask a vendor for a SOC 1 or a SOC 2?

Ask what question you need answered. If the vendor processes transactions that flow into your financial statements (payroll, benefits administration, claims, custody, billing), your controller and auditors need a SOC 1 Type 2. If you need assurance about security, availability, confidentiality or privacy, you need a SOC 2 Type 2. Many critical vendors need to provide both.14

How old can a report be?

No rule sets a single limit, but the logic of GAO and the PCAOB is that tests outside your period give less support as the gap grows.411 A common practice is to accept a Type 2 whose period ended within the last twelve months, with a bridge letter for the remainder, and to ask for more when the gap exceeds about three months or something significant happened in it.

Can we share a vendor's SOC 2 with our own customers or regulators?

Usually only as the report's use restrictions and your nondisclosure agreement allow. SOC 2 reports are restricted-use documents; SOC 3 reports are general use. Microsoft, for example, requires a subscription or trial account to download its SOC 1 and SOC 2 reports "in accordance with AICPA requirements," while its Azure SOC 3 report is public.1421 Regulators who examine you can generally see what you relied on; check the agreement.

Does a SOC 2 mean the vendor complies with HIPAA (or GLBA, or state privacy law)?

No. It is evidence about controls, which helps show the vendor has safeguards, but it is not a legal compliance finding. A SOC 2+ can map additional criteria, such as HIPAA Security Rule requirements, into the same examination.3 Health care organizations still need business associate agreements and their own risk analysis; see Business Associates, Cloud and AI Vendors.

Do government agencies issue or use SOC reports?

Yes. Federal shared service providers issue SOC 1 reports so agency auditors can rely on them; the Treasury Inspector General publishes reports such as the Funds Management Branch SOC 1 Type 2, and the Defense Department runs about 25 to 30 SOC 1 examinations a year.54 State and local agencies are mostly buyers, reviewing SOC reports from software and cloud vendors, but a state agency that processes transactions for other agencies may need to issue one too.

What do we do if a critical vendor has no SOC report?

Use another source of assurance (ISO/IEC 27001 certificate, HITRUST, PCI DSS attestation, a detailed questionnaire with evidence, a right to audit, your own review), add contract terms requiring a report by a date, and limit the data and access the vendor gets until you have evidence. Record the decision as a risk acceptance with an owner and an end date.32

Hard questions

Is self-regulation by the accounting profession enough to keep SOC 2 reports reliable?

The case that it is: SOC reports are attest work, so only licensed CPAs through registered firms may issue them, under enforceable professional standards. State boards can discipline licensees, peer review checks engagements, and the profession moved in 2026 with ethics guidance on tool providers and a targeted peer review program for SOC 2 firms.1876 Public company financial audits have a federal overseer (the PCAOB) because investors rely on them; SOC 2 reports are private contracts among sophisticated parties who can choose their auditors.

The case that it is not: buyers cannot see peer review working papers, the volume of SOC 2 work has grown rapidly with software platforms, and the profession's own warnings in 2026 show quality problems serious enough to need special attention. Peer review samples a few engagements every few years; a high-volume firm may issue hundreds of reports in that time.68

What the evidence shows: the profession identified the risk itself and took steps in 2026, but those steps were new as of this writing and their results were not yet public. Large buyers cannot wait for that answer; they can check firms, ask questions and spot-check controls now.

Do compliance automation platforms make SOC 2 reports better or worse?

For: continuous evidence collection catches lapses during the period instead of at the end, makes reports possible for smaller vendors that could not otherwise afford one, and frees auditors to focus on judgment. Against: the AICPA's ethics staff said business arrangements between CPA firms and tool providers "can raise significant threats" to independence and objectivity, and its peer review guidance warns against templated engagements and overreliance on platforms.76 What the evidence shows: the tools themselves are neutral; the risk is in referral and revenue arrangements and in examinations that accept platform output without independent testing. Buyers should ask about both.

Should regulators and auditors rely on SOC reports instead of doing their own reviews?

For reliance: testing a shared service once and letting every customer rely on it saves enormous cost and duplication, which is exactly why the Defense Department and its auditors use SOC 1 reports, and why bank guidance lists SOC reports among due diligence sources.432 Against: reliance only works when the report is scoped right, the customer runs its CUECs and the opinion is clean; the Defense Department's experience shows how often those conditions fail, forcing auditors to retest anyway.28 What the evidence shows: reliance is efficient when the customer does its part, and wasteful when it does not. The rules already require the relying party to evaluate the report, not just receive it.11

Should SOC 2 reports be public?

For: customers, patients, investors and the press would see exceptions and carve-outs, vendors would have reason to fix them, and buyers would not have to sign agreements to see a report. Against: detailed descriptions of controls and exceptions can help attackers, the reports are written for informed users who understand their limits, and the SOC 3 already provides a public, general-use version.21 What the evidence shows: the current split (restricted SOC 2, public SOC 3) is a judgment the profession made, not a law. Public agencies face the same tension under public records laws, which in Idaho exempt records about cybersecurity systems and trade secrets.3738

For reporters and advocates

What "SOC 2 compliant" means in a press release or a sales claim. It means a CPA firm issued a report. Ask: which type, which period, which system, which criteria, which firm, and was the opinion unmodified? A company that will not answer those five questions has told you something.

Public records that exist:

  • SOC 3 reports, which many large providers post publicly; Microsoft's Azure SOC 3, for example, is public.21
  • Federal SOC 1 reports and audit reports. Inspectors general publish SOC 1 reports on federal shared services (for example, Treasury OIG-25-004) and audit work on how agencies use them (DoD IG DODIG-2025-044); GAO's September 2025 report explains the Defense Department's reliance on 27 SOC 1 examinations.5284
  • SEC filings. 10-K Item 1C describes each public company's processes for overseeing third-party service providers' cyber risks, under Regulation S-K Item 106(b); 8-K Item 1.05 filings describe material incidents, including vendor-caused ones. Search EDGAR.36
  • State boards of accountancy. Idaho Code 54-214 requires CPA firms providing attest services in Idaho to register annually with the Idaho State Board of Accountancy; license and firm registration status is a public question.18
  • AICPA statements. The AICPA's SOC page, the Journal of Accountancy and the peer review program publish guidance and notices, including the 2026 notice that the AICPA is looking into allegations about a compliance vendor.16
  • Court dockets on PACER and CourtListener, where vendor breach suits sometimes quote SOC reports or the vendor's representations about them.

Questions to ask a public agency, hospital, school district or company about its vendors:

  • For your most critical vendors, do you have a current SOC 2 Type 2 (or SOC 1 Type 2) report, and when did someone last review it?
  • Were any opinions modified, and what did you do about it?
  • How many complementary user entity controls do your critical vendors list, and who in your organization performs each one?
  • Which of your vendors' reports carve out the cloud provider that holds your data, and do you have that provider's report?
  • Do your contracts require a current report and prompt notice of incidents?

The Idaho angle. Under the Idaho Public Records Act, a request to a state agency, county, city or school district for a vendor's SOC 2 report may be refused: Idaho Code 74-105(21) exempts records, other than public expenditure records, about the "nature, location, or function of cybersecurity devices, programs, or systems," 74-105(4)(b) covers vulnerability assessments for critical infrastructure in some cases, and 74-107(1) exempts trade secrets.3738 You can still ask for records the exemptions do not reach: the contract clause requiring a report, the date the agency received and reviewed it, the reviewer's conclusion, the number of follow-up items, and spending on the vendor. Idaho state agencies follow Idaho Technology Authority policies for risk and vendor management, covered in 108 lesson 2; the Legislative Services Office audit division's reports are another place to look for findings on vendor oversight (see lesson 8). Idaho companies that sell software or processing services to banks, hospitals or other states will usually need SOC reports themselves, and their CPA firms must be registered with the Idaho board if they perform attest services in Idaho.18

Related reading in this module: cyber insurance (underwriters ask about vendor controls), security in mergers and acquisitions (a target's SOC reports are diligence documents) and the program maturity checklist.

Where to go next

  • GAO-25-107731: Role of Service Organization Reports: Free. A short, plain-language government explanation of SOC 1 reports, Type 1 and Type 2, CUECs and opinion types, with the Defense Department's experience. Good first reading for finance staff and internal auditors.
  • Treasury OIG-25-004: a complete SOC 1 Type 2 report: Free. A real, public SOC 1 Type 2 report from a federal shared service, with opinion, assertion, description, carve-outs, complementary controls and test results. Use it to practice reading a report section by section.
  • AICPA Trust Services Criteria and description criteria: Free with an AICPA account. The criteria and points of focus that SOC 2 reports are measured against; needed by anyone preparing for or reviewing a SOC 2.
  • AICPA SOC Suite of Services: Free. The AICPA's hub for SOC news, guides, exposure drafts (including the proposed 2027 criteria, comments due Jan. 15, 2027) and notices. Guides are sold separately (about $100 to $130).
  • Third-Party Risk Management: A Guide for Community Banks (May 2024): Free. The federal banking agencies' practical guide; shows where SOC reports fit in due diligence and ongoing monitoring. Useful beyond banking for any vendor risk program.
  • Microsoft SOC 2 compliance offering page: Free. An example of how a very large provider runs back-to-back SOC periods, Type 1 reports for new services and quarterly bridge letters; useful for setting expectations with any cloud vendor.
  • Idaho Code Title 54, Chapter 2 (Accountants): Free. Idaho's accountancy act, including the definition of attest services, firm registration and peer review, and who may issue reports. Use it to check a SOC provider's standing in Idaho.
Still being checked (7 items)

These points could not be fully confirmed against a primary source when this lesson was written and fact checked in November 2026. The text above states each one as uncertain.

  • The full texts of the AICPA attestation standards (AT-C 105, 205, 320), the SOC 2 guide, the 2017 Trust Services Criteria and the 2018 description criteria sit behind AICPA accounts or purchase and were not read line by line; descriptions of their structure (including that the common criteria follow the COSO 2013 framework and that the 2022 revision changed points of focus, not criteria) come from the AICPA product pages, Microsoft's published descriptions, GAO and the Treasury report.
  • Historical dates for SAS 70, SSAE 16, SSAE 18 and ISAE 3402 come from a Wikipedia summary, not the AICPA or IAASB originals.
  • The proposed 2027 Trust Services Criteria were described from the AICPA announcement and Journal of Accountancy report; the exposure drafts themselves were not reviewed.
  • The allegations about a compliance automation startup, reported by IANS on March 24, 2026, are anonymous and denied; this lesson relied on the IANS summary and did not review the original post, whose exact publication date is not stated by IANS. As of Nov. 15, 2026, no finding by any authority was found, but this could not be exhaustively checked.
  • Cost and timeline figures are estimates published by a CPA firm and a compliance software vendor with an interest in the market; no independent survey of SOC fees was found.
  • The DoD Inspector General figures and the quoted finding are taken from the report's summary page (rechecked Nov. 15, 2026); the full PDF was not read.
  • The claim that SOC for Cybersecurity has not become a common market requirement is the writer's judgment from the absence of such requirements in the rules reviewed, not from a survey.

Last verified November 15, 2026. General education, not legal, compliance, audit or other professional advice; rule versions and dates are stated in the text, and the sources used are listed in the Notes and Sources below. Check the regulator's current text before relying on any point.

Notes

  1. AICPA and CIMA, System and Organization Controls: SOC Suite of Services landing page ("a suite of service offerings CPAs may provide"; notice that the AICPA "is looking into allegations published anonymously about the business practices of a compliance vendor"; listing dated Oct. 26, 2026 for the exposure drafts of proposed 2027 SOC 2 criteria) (read Nov. 15, 2026). Read it online. ↩
  2. Idaho Code 54-221, "Issuance of a report," subsections (1) and (3), as in force after the 2026 session (read Nov. 15, 2026). Read it online. ↩
  3. AICPA, SOC 2 Reporting on an Examination of Controls at a Service Organization Relevant to Security, Availability, Processing Integrity, Confidentiality, or Privacy (AICPA Guide), product page: "Updated as of October 15, 2022," reflecting SSAE No. 20 and No. 21, with an illustrative SOC 2+ report, the 2017 trust services criteria (revised points of focus, 2022) and the 2018 description criteria (revised implementation guidance, 2022); e-book $100 to $125; also covers SOC 3 (read Nov. 15, 2026). Read it online. ↩
  4. U.S. Government Accountability Office, GAO-25-107731, DOD Financial Management: Role of Service Organization Reports in Assessing the Effectiveness of Internal Controls, Sept. 18, 2025 (type 1 and type 2 definitions and endnote 7; CUECs, endnote 5; complementary subservice organization controls, endnote 8; modified opinions, endnote 10; 27 SOC 1 examinations at eight DOD service organizations serving about 85 customers in fiscal 2024; 25 to 30 reports a year in fiscal 2020 to 2024; 43 percent of customers with monitoring processes as of December 2024; 28 material weaknesses; sample of eight reports; root cause analyses not consistently performed or documented for three of the eight reports; quotations checked against the report PDF) (read Nov. 15, 2026). Read it online. ↩
  5. U.S. Department of the Treasury, Office of Inspector General, OIG-25-004, Report on the Bureau of the Fiscal Service's Funds Management Branch's Description of its Trust Funds Management Services and the Suitability of the Design and Operating Effectiveness of its Controls for the Period August 1, 2023 to July 31, 2024 (SOC 1 Type 2, examined by KPMG LLP; 14 control objectives; "No exceptions noted" 14 times), Oct. 31, 2024 (read Nov. 15, 2026). Read it online. ↩
  6. Tim Kindem, "AICPA guides peer reviewers to address SOC 2 risks," Journal of Accountancy, May 14, 2026 (May 2026 reviewer alert; about five SOC 2 engagements from different partners; outreach starting June 1; cites the Feb. 1, 2026 article "Promises of 'Fast and Easy' Threaten SOC Credibility") (read Nov. 15, 2026). Read it online. ↩
  7. AICPA and CIMA, Ethics Staff Insights: Business arrangements with SOC tool providers, Apr. 13, 2026 (full text requires a free download) (read Nov. 15, 2026). Read it online. ↩
  8. Dan Maloof, with Jeff Brown and Summer Craze Fowler, "Delve Allegations Expose Weak Points in Modern Compliance," IANS, March 24, 2026 (summarizes anonymous allegations and the company's denial; reports no finding by any authority). The anonymous post itself was not reviewed for this lesson (read Nov. 15, 2026). Read it online. ↩
  9. AICPA and CIMA, "AICPA proposes update of SOC 2 Trust Services Criteria to enhance the relevance, usability and value of CPAs' reports," Oct. 28, 2026 (comments through Jan. 15, 2027; effective for engagements beginning on or after Dec. 31, 2027 if approved, early adoption permitted; quote of Amy Pawlicki) (read Nov. 15, 2026). Read it online. ↩
  10. Irish National Accreditation Board, "Transition requirements for ISO/IEC 27001:2022," applying IAF MD 26 (certified clients to be transitioned by Oct. 31, 2025) (read Nov. 15, 2026). Read it online. ↩
  11. Public Company Accounting Oversight Board, AS 2601, Consideration of an Entity's Use of a Service Organization, paragraphs .02, .12 to .21, .24, .31, .46 and .53; amendment to paragraph .32 adopted in PCAOB Release No. 2024-004, effective for fiscal years beginning on or after Dec. 15, 2024 (read Nov. 15, 2026). Read it online. ↩
  12. Wikipedia, "SSAE No. 18" (secondary summary used only for dates: SAS 70, April 1992; SSAE 16, April 2010; SSAE 18, April 2016, most sections effective May 1, 2017; AT-C 320; ISAE 3402, December 2009) (read Nov. 15, 2026). Read it online. ↩
  13. Journal of Accountancy, news report on SSAE No. 21, Direct Examination Engagements, Sept. 30, 2020 (effective for reports dated on or after June 15, 2022; adds AT-C 206; supersedes and revises AT-C 205; amends AT-C 105) (read Nov. 15, 2026). Read it online. ↩
  14. Microsoft Learn, "System and Organization Controls (SOC) 2 Type 2" compliance offering pages for Microsoft 365 and Azure (bridge letters "self-attestations by Microsoft, not reports based on examinations by the auditor"; rolling 12-month periods; no gaps between periods; Azure reports about six weeks after period end; SOC 1 and SOC 2 download "in accordance with AICPA requirements"; CSA CCM and C5:2020; SSAE 18 with AT-C 105 and 205 as described on the Germany C5:2020 page) (read Nov. 15, 2026). Read it online. ↩
  15. AICPA, 2017 Trust Services Criteria for Security, Availability, Processing Integrity, Confidentiality, and Privacy (With Revised Points of Focus, 2022), download page (free account required) (read Nov. 15, 2026). Read it online. ↩
  16. AICPA, 2018 SOC 2 Description Criteria (With Revised Implementation Guidance, 2022), download page dated July 9, 2025 (free account required) (read Nov. 15, 2026). Read it online. ↩
  17. Idaho Code 54-206, "Definitions," subsection (3), definition of "attest," as in force after the 2026 session (read Nov. 15, 2026). Read it online. ↩
  18. Idaho Code 54-214, "Firm registration, peer review," subsections (1) to (3), as in force after the 2026 session (read Nov. 15, 2026). Read it online. ↩
  19. AICPA, Reporting on an Entity's Cybersecurity Risk Management Program and Controls (Attestation Guide, SOC for Cybersecurity), product page, 2024 edition (product AAGCYB24E), reflecting SSAE No. 20 and No. 21 (read Nov. 15, 2026). Read it online. ↩
  20. AICPA, AICPA Guide SOC for Supply Chain: Reporting on an Examination of Controls Relevant to Security, Availability, Processing Integrity, Confidentiality, or Privacy in a Production, Manufacturing, or Distribution System, product page, 2024 edition (product AAGSSC24E) (read Nov. 15, 2026). Read it online. ↩
  21. Microsoft Learn, "System and Organization Controls (SOC) 3" (Azure SOC 3 attestation report "is publicly available") (read Nov. 15, 2026). Read it online. ↩
  22. Linford & Co., "SOC 1 & SOC 2 Audit Costs: What Really Drives the Price," originally published June 13, 2018, updated Feb. 4, 2026 (a CPA firm that performs SOC examinations; estimates, not market data) (read Nov. 15, 2026). Read it online. ↩
  23. Cloud Security Alliance, press release, "Cloud Security Alliance Releases Illustrative Type 2 SOC 2 Report that Incorporates its Cloud Controls Matrix Criteria," Aug. 9, 2022 (197 control objectives in 17 domains; STAR Attestation) (read Nov. 15, 2026). Read it online. ↩
  24. "AICPA partners on new offering that assures AI systems and agents," Journal of Accountancy, Oct. 19, 2026 (joint SOC 2 and AIUC-1 engagement; pilot phase; full launch expected early 2027) (read Nov. 15, 2026). Read it online. ↩
  25. "AICPA proposes improvements to SOC 2 Trust Services Criteria," Journal of Accountancy, Oct. 28, 2026 (comment period through Jan. 15, 2027; AI points of focus) (read Nov. 15, 2026). Read it online. ↩
  26. Drata, "How much does a SOC 2 audit cost?" (a compliance automation software vendor; page dated March 25, 2026; estimates, not market data) (read Nov. 15, 2026). Read it online. ↩
  27. Mandiant (Google Cloud), "UNC5537 Targets Snowflake Customer Instances for Data Theft and Extortion," June 10, 2024, updated June 17, 2024 (read Nov. 15, 2026). Read it online. ↩
  28. Department of Defense Office of Inspector General, DODIG-2025-044, Management Advisory: Improvements Needed in DoD's Planning for and Use of SSAE 18 Engagements, Nov. 26, 2024, as summarized on the Inspector General's report page (over $15.5 million on 30 SSAE 18 engagements in fiscal 2023; complementary user controls not prioritized) (read Nov. 15, 2026). Read it online. ↩
  29. Journal of Accountancy podcast, "The risks of quick-turn SOC engagements and what CPAs should know," Apr. 30, 2026, as listed on the AICPA SOC page (not listened to for this lesson) (read Nov. 15, 2026). Read it online. ↩
  30. HITRUST Alliance, "Assessments and Certifications" (e1, i1 and r2 assessments) (read Nov. 15, 2026). Read it online. ↩
  31. Board of Governors of the Federal Reserve System, FDIC and OCC, Interagency Guidance on Third-Party Relationships: Risk Management, 88 FR 37920, June 9, 2023 (read Nov. 15, 2026). Read it online. ↩
  32. Federal Reserve, FDIC and OCC, Third-Party Risk Management: A Guide for Community Banks, May 2024, transmitted by OCC Bulletin 2024-11 (May 3, 2024), due diligence (p. 10) and ongoing monitoring sections (read Nov. 15, 2026). Read it online. ↩
  33. FTC Standards for Safeguarding Customer Information, 16 CFR 314.4(f)(1) to (3), eCFR text as of Nov. 1, 2026 (read Nov. 15, 2026). Read it online. ↩
  34. New York State Department of Financial Services, Industry Letter, Guidance on Managing Risks Related to Third-Party Service Providers, Oct. 21, 2025; 23 NYCRR 500.11 (read Nov. 15, 2026). Read it online. ↩
  35. U.S. Securities and Exchange Commission, Regulation S-P: Small Entity Compliance Guide for the amendments adopted May 16, 2024 (service provider oversight; 72-hour service provider notice; compliance Dec. 3, 2025 and June 3, 2026); 17 CFR 248.30 (read Nov. 15, 2026). Read it online. ↩
  36. 17 CFR 229.106(b)(1)(iii) (Regulation S-K Item 106), eCFR text as of Nov. 1, 2026: "Whether the registrant has processes to oversee and identify such risks from cybersecurity threats associated with its use of any third-party service provider" (read Nov. 15, 2026). Read it online. ↩
  37. Idaho Code 74-105, subsections (4)(b) and (21), records exempt from disclosure, as in force after the 2026 session (read Nov. 15, 2026). Read it online. ↩
  38. Idaho Code 74-107(1), trade secrets exempt from disclosure, as in force after the 2026 session (read Nov. 15, 2026). Read it online. ↩

Check yourself

1. What is the main difference between a SOC 2 Type 1 and a SOC 2 Type 2 report?

2. Under Idaho law, who may perform a SOC 2 examination for an Idaho client?

3. What are complementary user entity controls (CUECs)?

4. Under the carve-out method, what happens to a subservice organization's controls?

5. According to GAO, what kind of opinion results from a scope limitation with a pervasive effect?

6. What is a bridge letter?

7. Which SOC report is intended for general use and is often posted publicly?

8. What did GAO report about Defense Department customers' service organization monitoring as of December 2024?

9. If approved, when would the proposed 2027 SOC 2 Trust Services Criteria take effect?

10. In the May 2026 peer review guidance, what did the AICPA say about SOC 2 engagements with identical reports, risk assessments, sample sizes and testing procedures?

Terms in this lesson

Attestation engagement
An engagement in which a licensed CPA gives an opinion or other assurance on a subject matter, or on management's assertion about it, against stated criteria, under the AICPA's Statements on Standards for Attestation Engagements (SSAEs).
SSAE 18
The AICPA attestation standards clarification and recodification issued in April 2016 and mostly effective May 1, 2017, which organized the standards into AT-C sections such as AT-C 105, 205 and 320.
Service organization
An organization that provides services to customers (user entities) that are likely to be relevant to those customers' controls, for example a payroll processor or a cloud application provider.
Service auditor
The CPA firm that examines and reports on a service organization's description and controls.
Subservice organization
A vendor used by a service organization whose services are likely to be relevant to the user entities' controls, such as the cloud host behind a software service.
Carve-out method
A way of handling a subservice organization in which its controls are excluded from the description and the service auditor's testing; the report lists the controls the service organization assumes it performs.
Inclusive method
A way of handling a subservice organization in which its relevant controls are included in the description and tested by the service auditor.
Complementary user entity controls (CUECs)
Customer controls that the service organization assumes, in the design of its system, its customers will implement; the opinion holds only if they operate.
Complementary subservice organization controls (CSOCs)
Controls that the service organization assumes, in the design of its system, its subservice organizations will implement.
Unmodified opinion
A clean opinion that the description is fairly presented and the controls were suitably designed (and, in Type 2, operated effectively) in all material respects.
Modified opinion
A qualified, adverse or disclaimer opinion issued when there is a scope limitation or a material misstatement in the description or controls.
Bridge letter
Also called a gap letter: a statement by the service organization's management covering the time between the end of the last report period and a later date; it is not examined by the auditor.
Trust Services Criteria
The AICPA criteria used in SOC 2 examinations for security, availability, processing integrity, confidentiality and privacy; the current version is the 2017 criteria with revised points of focus (2022).
Peer review
The accounting profession's program for checking whether CPA firms' accounting and attest engagements conform to professional standards, used by state boards in licensing firms.

Full glossary

Sources