SOC 2 in due diligence: what investors and buyers read

Updated

Reviewers in an investment or an acquisition read a SOC 2 report to see how much security work is left, and the two sources fetched for this page agree on what they read: the report type and scope, the period covered, the auditor's opinion, and the exceptions table (Agency) (Compass IT Compliance). Agency adds two more: whether the system description matches the product being bought, and how you monitor the vendors your controls depend on. Both sources sell compliance services, and neither is a rule from the AICPA.

What reviewers read first

WhatAgency (updated 1 Nov 2026)Compass IT Compliance (22 May 2026)
Type and scopeType 1 or Type 2, criteria in scope, systems covered (listed first)System description: is the service being bought in scope (listed second)
PeriodThe period covered and the gap to today (second)How recent the period is, and any gap since it ended (fifth)
OpinionUnqualified, qualified, adverse or disclaimer (third)Whether controls were suitably designed and operating effectively (first)
ExceptionsRepeated exceptions are the main concern (fourth)Scanned in the controls and test results section (fourth)
VendorsHow you oversee subservice organizations (sixth)Subservice organizations should be named in the system description; no more detail

The orders differ, so do not read either list as a ranking from the AICPA. What they share is that the exceptions table gets read. To see what an opinion and an exception look like, read how to read a SOC 2 report and exceptions and qualified opinions.

Which report each stage is described as accepting

Agency treats a Type 1 report as a milestone, not a full answer. Its stage table says Series A commonly accepts "Type I plus a dated Type II plan", Series B and later expects "Type II with a bridge letter if the window has lapsed", and M&A technical diligence is the least flexible reviewer, asking for "multi-year report history and exception trend" (Agency). Compass says a Type 2 report typically covers six or twelve months and that most buyers accept it for up to twelve months past the period end, especially with a current bridge letter (Compass). These are sellers' views of what buyers do; the two sources do not cite a survey. If you are choosing between the reports, see Type 1 or Type 2 first, and for the bridge letter, the bridge letter template.

The standing folder, mapped to free tools

Agency lists nine items to keep ready in a standing folder (Agency). Here is each one and where a Policyseed page helps.

Folder item (Agency)Where to start
Current SOC 2 reportIssued by your CPA firm; see choosing an auditor
Current bridge letterBridge letter template
Latest penetration test report and attestation letterPenetration test scope
Approved policy set with review datesPolicy generator and the annual policy review
Vendor and subprocessor inventoryVendor review sheet
Most recent access review evidenceAccess review sheet
Incident historyIncident response plan
Business continuity and disaster recovery test resultsRestore test log
Insurance certificatesFrom your insurer; nothing on this site

Be upfront about exceptions

Compass advises being open about issues the auditor found instead of hoping the buyer misses them, and says the report's section for other information provided by the service organization is the place for a management response with the root cause and the fix (Compass). It also says the kind of exception matters: a missed quarterly access review with clear remediation reads differently from a recurring MFA failure on production systems. Agency says the same exception across consecutive reports is the clearest signal that a control was documented rather than fixed, and advises tracking the trend across years yourself (Agency). The exception register is where that trend lives, and year two is where it tends to break.

What the generated policies say

Policyseed sells a kit, so read these as wording you can adopt, not as a requirement from any reviewer. They show the records a reviewer can ask for: the vendor inventory, dated policy approvals, and incident reviews.

Northwind Cloud Inc maintains a vendor inventory recording, for every vendor, the business owner, service provided, data shared and its classification, systems accessed, tier, contract and renewal date, last review date and outcome, and assurance evidence held, and reviews it for completeness at least annually.

Vendor and Third-Party Risk Management Policy, item 4.1

Every policy in this set has a named owner role, an approver, a version number and an effective date, and is reviewed on the annual cycle and after any significant change to the business, the technology stack or the threat landscape.

Information Security Policy, item 4.5

Every SEV1 and SEV2 incident receives a blameless post-incident review within five business days of closure that produces a root cause, impact statement and corrective actions with owners and due dates, tracked to closure and reported to Executive Management.

Incident Response Policy, item 4.11

Where the sources are thin

  • Two sellers. Agency and Compass IT Compliance both sell compliance or audit services. Neither gives survey data on how often investors or acquirers ask for a Type 2 report.
  • Not a pass or fail. Neither source says a report decides a deal. What a buyer does with a weak finding is not covered by either.
  • Different orders. The two lists above are ordered differently; this page does not pick one.

Frequently asked questions

Do investors require a SOC 2 report at Series A?
The sources here do not say it is required. Agency (a seller of compliance services) says Series A commonly accepts a Type 1 report plus a dated Type 2 plan, and expects a Type 2 report, with a bridge letter if the window has lapsed, from Series B on. That is one vendor's view of the market, not a rule, and neither source gives survey data on how often investors ask.
What do acquirers look at in a SOC 2 report?
Agency says M&A technical diligence is the least flexible reviewer and asks for multi-year report history and the exception trend. Compass IT Compliance, which employs SOC 2 auditors, lists the opinion, the system description, the criteria covered, the tested controls and exceptions, and the period covered.
Should we mention exceptions in the report before the buyer finds them?
Compass IT Compliance says to be upfront and to use the report's section for other information provided by the service organization to add a management response with the root cause and remediation. It says the kind of exception matters: a missed quarterly access review with clear remediation reads differently from a recurring MFA failure on production systems.
How old can the report be?
Compass says most buyers accept a Type 2 report for up to twelve months past the period end, especially with a current bridge letter. Agency lists freshness as the second thing reviewers check. Both are vendor-side views; a buyer's own policy decides.
Does a SOC 2 report make due diligence pass?
No. Both sources describe a report as something reviewers read and question, not a pass or fail stamp. A report that excludes your core production environment tells the buyer little (Compass). Policyseed provides policy templates, not a compliance guarantee.

Policyseed provides governance policy templates and AI tailoring. It is not legal advice and not a compliance guarantee. Management adopts the policies; the CPA firm performs the SOC 2 examination.