Certa is named a Leader in the 2026 Gartner® Magic Quadrant™ for Third-Party Risk Management Tools. Get the report

Blog/Vendor Risk Management

How to review a vendor's SOC 2 report

Read past the opinion page

A step-by-step review for security and third-party risk teams: what to confirm, what to test, which controls land on your side of the line and when to ask for a bridge letter.

  • 50% Lower Costs at Uber50% Lower Costs
  • 130+ Integrations130+ Integrations
  • Gartner® MQ Leader, 2026Gartner® MQ Leader
  • Onboarding up to 3x Faster3x Faster Onboarding
CertaNovember 19, 2026 · 15 min read
A hand holding a magnifying glass over printed reports beside a calculator and a pen

The vendor sent the SOC 2. Someone saved the PDF, ticked "SOC 2 received" and moved the assessment to complete. Eighty pages of scope limits, tested controls and assumptions about your own team went unread.

Examiners know the difference. The Interagency Guidance on Third-Party Relationships (88 FR 37920, June 9, 2023) says a banking organization may consider reviewing SOC reports, and in the same passage says to consider "whether the scope and the results of the SOC reports, certifications, or assessments are relevant to the activity to be performed or suggest that additional scrutiny of the third party or any of its contractors may be appropriate." Scope and results. Collecting the report covers neither.

The steps below take a reviewer from the cover page to a documented conclusion: who should do the reading, what to confirm on the first pages, how to weigh exceptions, which controls the vendor has assigned to you, where the report stops at a subservice organization, and how to cover the months since the audit period closed.

The Short Answer

Confirm that the report is a SOC 2 Type 2 covering the service you buy, for a recent period, with an unmodified opinion. Then check that the trust services categories match your use case, weigh every exception in the tests of controls, assign each complementary user entity control to an owner on your side, read what was carved out to subservice organizations, and get a bridge letter for the months after the period ended. Write the conclusion down with page references.

What you need before you review a SOC 2 report

Five things on the desk first

Most guidance on how to review a SOC 2 report starts at page one of the PDF. Start one step earlier. A SOC 2 report describes a system and tests the controls around it, and you can only judge it against what you bought and what you send the vendor.

The full reportThe complete document under NDA, including the system description and the tests of controls. A summary, a badge on a trust page or a SOC 3 does not show you exceptions or the controls expected of you.
The contract & service inventoryThe products and modules you use, the legal entity that provides them and the regions that host your data. You will match these to the system the report describes.
The inherent risk tier & data classificationWhat data the vendor holds or touches, whether the service is critical, and what your policy requires for that tier. This sets how deep the review goes.
A named reviewer & an approverSomeone who can read control testing, and someone with authority to accept residual risk or require remediation.
Last year's reviewThe prior report, your findings and whatever the vendor promised to fix. Repeat exceptions tell you more than new ones.

If the vendor will only release the report after a signature, sign the NDA. Use of a service auditor's report is restricted to people with enough context to understand it, which is why vendors gate it. A refusal to share the full report with a customer under NDA is a finding in its own right.

Step 1 of 7

Who owns the review: security, TPRM or both

Security reads it. TPRM runs it.

Both, with a clean split. Security or IT risk owns the technical judgment: whether the tested controls address the threats that matter for this service, and whether an exception is tolerable. Third-party risk owns the process: requesting the report on schedule, tracking the period it covers, routing findings, recording the decision and keeping the file an examiner can open.

Your business owner for the vendor relationship has a part too. Many of the controls the report assigns to customers are things only the business can do, like approving who gets access. Certa's post on SOC 2 reports in TPRM cybersecurity places the report inside the wider security assessment. This split keeps it from falling between teams.

TaskOwnerOutput
Request the report, bridge letter & subservice reportsTPRMDated evidence in the vendor record
Read scope, opinion, criteria & exceptionsSecurity or IT riskReview worksheet with page references
Map customer-side controls to ownersSecurity with the business ownerControl mapping, signed off
Decide: accept, accept with conditions or escalateRisk approver for the tierDocumented rationale
Track remediation & the next report dateTPRMOpen items with due dates
Scale the depth to the tierA critical vendor holding regulated data gets every step here. A low-risk tool with no sensitive data can stop after the first step, as long as your policy says so in writing.

Step 2 of 7

Confirm the report type, period, scope & opinion

Four checks before you read further

Four facts on the first pages decide how much the rest is worth. Confirm them before you spend an hour on control tables.

Type. Settle the SOC 1 report vs SOC 2 question first. A SOC 1 addresses controls relevant to user entities' internal control over financial reporting. A SOC 2 addresses controls measured against the trust services criteria. Certa's SOC 1 vs SOC 2 explainer covers when each applies. Then check Type 1 or Type 2. AICPA description criteria set out the difference: a type 1 examination covers the system description and the suitability of the design of controls as of a date, and a type 2 adds the operating effectiveness of those controls over a period. A SOC 2 Type 1 report tells you controls were designed and in place on one day. It is reasonable from a vendor in its first audit cycle, and thin as the only evidence for a critical service.

Period. Find the start and end dates in the auditor's opinion. Note how many months the period covers, how long ago it ended and whether it runs on from the prior report without a gap. A gap between two report periods is a question for the vendor.

Scope. Read the system description for the service name, legal entity, locations and infrastructure. Compare them with your contract. Vendors with several products often have one in scope and another outside it, and an acquired product line can sit outside the audited system for years. Management must also disclose in the description any significant changes to the system during the period, and incidents that resulted from control failures or caused a significant failure to meet service commitments. Read both disclosures.

Opinion. Here the service auditor gives an opinion on whether the description is presented in accordance with the description criteria, whether controls were suitably designed and, in a type 2, whether they operated effectively. An unmodified opinion says yes in all material respects. A qualified opinion carves out a problem, usually with the words "except for." Adverse opinions and disclaimers are more serious still. Any modification means you read the basis paragraph in full and send it to the approver.

  • The report is a SOC 2, Type 2, issued by a licensed CPA firm you can identify
  • The period ended within the window your policy sets, and follows the last report without a gap
  • The product, entity and hosting regions you use appear in the system description
  • The opinion is unmodified, or the modification is understood and escalated
  • Disclosed incidents and significant changes have been read and noted

Step 3 of 7

Match the trust services criteria to your use case

Security alone may fall short

A SOC 2 covers the categories the vendor chose. AICPA trust services criteria define five: security, availability, processing integrity, confidentiality and privacy. Common criteria, the CC series that runs from the control environment through logical and physical access controls, change management and risk mitigation, apply to all five and are the complete set for security. Each of the other four adds its own criteria on top.

So ask what you depend on the vendor for, and check the category is there.

If the vendor...Look forWhy
Runs a service your operations stop withoutAvailabilityCovers whether systems are available for operation and use to meet the vendor's objectives, including capacity, backup and recovery
Calculates, transforms or moves your transactionsProcessing integrityCovers whether processing is complete, valid, accurate, timely and authorized
Holds contracts, designs, pricing or other restricted dataConfidentialityCovers protection of information designated confidential through to its final disposition
Collects or processes personal information for youPrivacyApplies only to personal information: collection, use, retention, disclosure and disposal

Two cautions. Availability in a SOC 2 does not promise an uptime number. On this point the criteria state that the availability objective "does not, in itself, set a minimum acceptable performance level." Your SLA does that. And a missing category is not always a gap: the description criteria require management to explain any criterion that is not relevant to the system, so read the explanation before you raise it.

If your team has never read one cover to cover, the AICPA publishes a SOC 2 report example: an illustrative Type 2 report with management's assertion, the system description, the service auditor's report and the tests of controls and results (a member download). Working through a sample SOC 2 report once makes every real one faster. The AICPA SOC 2 guidance page links the criteria and the description criteria.

Check which criteria the report citesReports today cite the 2017 trust services criteria, with points of focus revised in 2022. Meanwhile, the AICPA's Assurance Services Executive Committee has issued exposure drafts of proposed 2027 revisions to both the trust services criteria and the description criteria. Note the version on each report so next year's comparison is like for like.

Step 4 of 7

Test exceptions in the SOC 2 type II report

A clean opinion can still hide findings

The section that separates a SOC 2 Type 2 report from a Type 1 is the tests of controls: each control, what the auditor did to test it and what the auditor found. Most rows end in "no exceptions noted." Rows that don't are where the review earns its keep.

An unmodified opinion does not mean zero exceptions. An auditor judges whether deviations, taken together, stop the criteria from being met. You judge something narrower: whether a specific failure touches your data or your service. Go through every exception in the SOC 2 Type II report and ask five questions.

  1. Which control failed, and does it sit between an attacker and your data? A missed access removal for a terminated engineer weighs more than a late policy acknowledgment.
  2. How often? One deviation in a large sample reads differently from several in a small one. Look for both figures, or a description of the extent.
  3. What did the vendor say? Management's response usually sits in a section the auditor's opinion does not cover. Treat it as a claim to verify.
  4. Was there a compensating control, and was it tested? A later access review that caught the missed removal counts only if that review passed its own test.
  5. Did it appear last year? A repeat exception means the fix did not hold.
Exception patternTypical response
Isolated, low-impact, remediated in periodNote it and close
Access, change management or monitoring control, single periodAsk for remediation evidence, set a due date
Same control failed in consecutive reportsEscalate to the approver, consider contract remedies
Control did not operate at all in the period, so it could not be testedTreat as untested, seek other evidence
Qualified opinion tied to a criterion you rely onFormal risk acceptance or a remediation plan before renewal
Read the incident disclosure tooVendors have to disclose in the system description any incidents that came from control failures or caused a significant failure to meet commitments. If the press reported a breach in the period and the description is silent, ask the vendor why.

Step 5 of 7

Map complementary user entity controls to your team

The vendor's assumptions about you

Every SOC 2 comes with fine print addressed to you. The AICPA's description criteria define complementary user entity controls (CUECs) as controls that service organization management assumed, in the design of the system, would be implemented by user entities and that are necessary, in combination with the vendor's controls, for its service commitments and system requirements to be achieved.

Put plainly, the opinion holds only if you do your part. Take CC6.2, which covers registering and authorizing users before credentials are issued. The vendor can run that process, but only your team can say who should be on the list of authorized users. If nobody on your side removes leavers from that list, the vendor's control passes its audit and your former contractor still has a login.

Nobody audits your side of that bargain. So list each CUEC and give it an owner, a control of your own and a place where the evidence lives.

CUEC in the report (typical wording)Your ownerYour controlEvidence
User entities approve & remove their own users' accessBusiness owner with IAMJoiner, mover, leaver process covers the vendor app, SSO enforcedQuarterly access review export
User entities configure password & MFA settingsSecurity engineeringTenant baseline with MFA requiredConfiguration screenshot or API pull
User entities report incidents & suspected compromise to the vendorSecurity operationsVendor contact in the incident runbookRunbook entry, test date
User entities review output reports for accuracyProcess ownerMonthly reconciliationSigned reconciliation
User entities keep contact details currentVendor managerAnnual contact confirmationVendor record timestamp

Any CUEC without an owner is your gap, not the vendor's. Record it, fix it or accept it. Then carry the mapping forward and compare the list each year, because vendors add CUECs when they move responsibility to customers.

Step 6 of 7

Check subservice organizations & carve-outs

Where the report stops

Your SaaS vendor almost certainly runs on someone else's cloud. When that provider's controls are necessary for the vendor to meet its commitments, the provider is a subservice organization and the report has to say how it is handled. There are two methods.

  • Inclusive. The relevant parts of the subservice organization's infrastructure, software, people, procedures and data are treated as part of the vendor's system and described and tested with it.
  • Carve-out. The description states the nature of the subservice organization's service and the types of controls the vendor assumes it has in place, called complementary subservice organization controls (CSOCs). Those controls are excluded from the examination.

Vendors often use carve-out for cloud hosting, and it means the SOC 2 Type 2 audit report in your hands gives no opinion on the data center, the hypervisor or the managed database underneath the application. Per the description criteria, the vendor's commitments can be achieved only if the CSOCs are suitably designed and operating effectively. They also leave it to management to consider whether to name the subservice organization at all.

For each carved-out provider:

  • Get its name. If the report does not give it, ask.
  • Read how the vendor monitors it. CC9.2 in the common criteria reads: the entity assesses and manages risks associated with vendors and business partners. Look for that control and its test result.
  • For critical services, obtain the subservice organization's own SOC 2 and run the first three steps of this review on it.
  • Add the provider to your fourth-party inventory and check it against other critical vendors for concentration.

Regulated readers have a direct hook here. Under the interagency guidance, reliance on subcontractors is a due diligence factor, including how the third party selects and oversees its subcontractors and ensures they implement effective controls.

Step 7 of 7

Request a SOC 2 bridge letter for coverage gaps

Cover the months since the period closed

A Type 2 report is historical the day it is issued. If the period ended on September 30 and you are reviewing in February, four months have no audit coverage. A SOC 2 bridge letter, also called a gap letter, is the vendor's statement about that stretch.

Know what it is before you rely on it. Grant Thornton UK's 2025 guidance on bridge letters describes them as brief, management-signed statements, and is blunt about their limits: "bridge letters are not audit deliverables." No service auditor prepares, signs or validates them, and they contain no independent testing. The same guidance says there is no formal rule on length, but notes that a statutory auditor generally would not wish to support a bridging letter of more than three months as evidence, and that the letters should not be used when internal controls have changed significantly.

A usable letter has five things:

  • The report it extends, with the audit period and the auditor's name
  • The exact dates the letter covers
  • A statement that there were no material changes to the system or controls, or a description of the changes
  • A statement on incidents in the gap period
  • The signature of an accountable officer, and the expected date of the next report

If the gap is long, the letter is vague or the vendor has changed platforms, a letter is not enough. Ask for the next report date in writing and fill the gap with other evidence: a targeted questionnaire, penetration test summaries, or continuous third-party monitoring of the vendor's external posture.

This is the point where a platform helps more than a calendar reminder. Certa pulls live data from BitSight, Black Kite, Rapid Ratings and Interos to keep vendor risk profiles current between reassessments, and periodic assessments are scheduled by each vendor's risk tier. Your SOC 2 stays the anchor. Live signals tell you whether something moved after it was signed.

CertaSee third-party monitoring in Certa

Common mistakes in vendor SOC 2 reviews

Where reviews go wrong

Seven errors show up in programs of every size. Each has a fix that costs little.

  1. Treating receipt as review. A stored PDF is evidence that you asked. Record who read it, what they concluded and on which pages.
  2. Accepting a certificate, a logo or a SOC 3. None of them shows exceptions, CUECs or carve-outs. Ask for the full report.
  3. Missing a scope mismatch. The report covers the vendor's flagship product and you bought the other one. Match the system description to the contract every year.
  4. Stopping at the opinion. Unmodified opinions sit on top of exceptions all the time. Read the tests of controls.
  5. Filing CUECs without owners. An unowned customer control is a control that is not operating.
  6. Ignoring carve-outs. If the cloud provider is excluded, your assurance over hosting comes from somewhere else or from nowhere.
  7. Letting the report replace the assessment. A SOC 2 says little about financial health, sanctions exposure, resilience planning or contract terms. It is one input among several, as Certa's guide to vendor risk assessment best practices lays out.

One more, for banks: get the report into the contract. The interagency guidance says it is appropriate to consider whether contract provisions describe the types and frequency of audit reports you are entitled to receive, and names SOC reports as an example. A vendor that owes you the report annually is easier to chase than one doing you a favor.

Reading is the smaller share of the work at scale. Requesting, tracking and re-keying evidence across hundreds of vendors is where the hours go. A global life sciences leader with 50,000+ third parties automated 1,000+ monthly third-party requests on Certa, using the Data Agent to pre-fill DDQs across 20 risk domains, which leaves analysts free for the judgment calls in this review.

SOC 2 report review FAQ

Short answers to the questions reviewers ask most.

What Is the Difference Between SOC 2 Type I & Type II?

A Type I (type 1) report covers the vendor's system description and whether controls were suitably designed as of a single date. A Type II (type 2) report adds whether those controls operated effectively over a period, and includes the auditor's tests and results. For any vendor that matters, ask for the Type II.

What Is a SOC 2 Bridge Letter?

A SOC 2 bridge letter is a statement signed by the vendor's management that covers the time between the end of the last audit period and today. It typically says whether controls changed materially and whether incidents occurred. It is the vendor's own representation: the service auditor does not test or sign it, so weigh it accordingly.

How Old Can a Vendor's SOC 2 Report Be?

No standard sets an expiry date, so your policy has to. A common program threshold is a period that ended within the last 12 months, with a bridge letter for the months since. Grant Thornton UK's guidance notes that, absent formal rules, a statutory auditor generally would not wish to support a bridging letter of more than three months as evidence, which is a useful marker for when to push for the next report.

What If a Vendor Has No SOC 2 Report?

Ask for equivalent independent evidence, then test what is missing yourself. The interagency guidance mentions conformity assessments and certifications against domestic or international standards alongside SOC reports, with ISO and NIST given as examples. Where nothing independent exists, use a security questionnaire sized to the risk tier, request supporting evidence, and for critical services consider your contractual right to audit.

Vendor Risk Management Articles

Keep reading

Third-Party OSBook a Demo
Get In Touch

By clicking “Accept”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. “Reject” keeps only the cookies the site needs to work. View our Privacy Policy for more information.

We use cookies for analytics and advertising, which stay on unless you choose “Reject”. “Accept” also allows session analytics and company identification. You can change this at any time under Your Privacy Choices. View our Privacy Policy for more information.