For a bank, credit union or lender, a vendor's SOC 2 report is the most useful single document in a due diligence file, but only if you read it as evidence and not as a badge. The report is an independent auditor's opinion on a vendor's description of its system and the controls around it. It tells you what was tested, over what period, and where the tests found problems. It does not tell you that the vendor is safe for your institution, and your regulators do not treat it that way either.
This guide covers what to ask vendors for, how to read what comes back, and how to fold the report into the ongoing oversight that examiners expect.
TL;DR
Automate Regulatory Model Risk Governance
Examine models against 32 qualitative criteria and resolve risk Tiers with pre-deployment checklists per OCC 2011-12 guidelines.
- A SOC 2 report is an auditor's opinion on a vendor's controls for security, availability, processing integrity, confidentiality or privacy. It is restricted to specified parties and is not a general-use document.
- Ask for a Type II report. Type I covers control design at a point in time, while Type II also tests whether controls operated effectively across a period.
- Read the opinion, the period, the system scope, the exceptions, the subservice organizations and the complementary user entity controls (CUECs), in that order.
- Regulators expect you to use additional verification and monitoring, not to rely solely on the report.
- Assign the review to someone with an information security background, and keep a record of what you concluded and why.
Table of Contents
- What a SOC 2 report tells you about a vendor
- SOC 2 Type I vs. Type II
- How to read the report: seven checks
- What SOC 2 does not cover
- What US regulators expect
- A practical process for requesting and reviewing reports
- How we think about SOC 2 at RiskInMind
- Evaluating a risk platform vendor with us
- Common mistakes in vendor SOC 2 reviews
- FAQ
- Sources
What a SOC 2 report tells you about a vendor
A SOC 2 report addresses controls at a service organization that are relevant to security, availability, processing integrity, confidentiality or privacy, and it gives users detailed information and reasonable assurance about those controls. Those five areas are the Trust Services Criteria. A vendor chooses which ones to include, and security is the baseline.
Structurally, the report contains management's description of the system and its assertion, plus the service auditor's opinion on that description and the controls, measured against the applicable criteria. In practice, the report usually also carries the auditor's tests and results, which is where the useful detail sits.
The value for you is independence. Without a report, you are relying on the vendor's own statements in a questionnaire. With one, a licensed third party has examined the claims and put an opinion on paper.
The limit is audience. SOC 2 reports help specified parties evaluate their own internal-control risks arising from a service organization; they are not general-use reports. That is why vendors usually release them under a nondisclosure agreement, and why the report is a starting point for your risk assessment, not its conclusion.

SOC 2 Type I vs. Type II
Both types contain a system description, a management assertion and an auditor's opinion. The difference is time. A Type I report addresses the description and the design of controls as of a point in time. A Type II report addresses them throughout a period and also covers whether the controls operated effectively, including the auditor's tests and results.
For a critical vendor, Type II is the right ask. A Type I report says the vendor designed sensible controls on a given day. A Type II report says those controls kept working over months. A young vendor may only have Type I at first, which is reasonable if the contract commits to a Type II within a defined window and you cover the gap with your own testing.
| Question | Type I | Type II |
|---|---|---|
| Time frame | A single date | A period of time |
| Tests control design | Yes | Yes |
| Tests operating effectiveness | No | Yes |
| Includes auditor's test results | No | Yes |
| Best use | Early-stage vendors, interim evidence | Critical and high-risk vendors |
How to read the report: seven checks
The FFIEC IT Examination Handbook says institutions using third-party reviews should ensure the auditor is qualified, the scope satisfies their audit objectives, and significant reported deficiencies are corrected. That gives a practical order of work.
1. The opinion
Start with the auditor's opinion. An unqualified opinion means the auditor found the description fair and the controls suitably designed (and, for Type II, operating effectively) in all material respects. A qualified or adverse opinion is a finding in itself, and you need to understand the reason before going any further.
2. The auditor
Confirm the report is signed by a licensed CPA firm with relevant experience in system and organization controls work. Qualification of the auditor is one of the explicit points the FFIEC handbook raises, so record your conclusion.
3. The period
Check the dates. A report whose period ended 14 months ago does not describe today's environment. Ask for a bridge letter covering the gap between the period end and today, in which management states whether controls have changed materially. Treat a bridge letter as management's statement, not as an audit.
4. The scope
Review the system scope, the Trust Services Criteria, the locations and the infrastructure, software, people, procedures and data that the report includes. The SIFMA guide on SOC reports lists these items as the things institutions should review. The most common mistake is to accept a report that covers a different product, region or environment than the one you are buying. If your data will live in a service the report does not describe, the report tells you little.
5. Exceptions
Read every exception in the tests of controls and the vendor's management response. Ask whether the exception touches data you will send, whether it recurred, and whether remediation has evidence behind it. A few documented exceptions with credible responses are normal; what matters is whether they affect the controls you depend on. A report that is spotless across hundreds of controls is not automatically better, but it is fair to ask how the testing was scoped.
6. Subservice organizations
Most vendors run on a cloud provider or other fourth parties. These are subservice organizations, and the report handles them in one of two ways: under the inclusive method their controls are part of the report, while under the carve-out method they are excluded. With carve-out, you need the subservice provider's own assurance or a clear account of how the vendor monitors it. SSAE 18 requires service organizations to monitor the effectiveness of controls at subservice organizations when the carve-out method is used, so ask to see how they do it.
7. Complementary user entity controls
CUECs are the controls the vendor assumes you operate on your side: reviewing user access, approving changes, reconciling outputs. The SIFMA guide says these should be evaluated to determine whether they are in place and operating effectively in your organization. This is the section most often skipped, and it is where your own examiner may look first. Map each CUEC to an owner and an internal control, and note any you cannot meet.
What SOC 2 does not cover
A clean SOC 2 report is not a complete vendor risk assessment. Four gaps matter in practice.
It does not assess your contract. The report describes controls; it does not decide liability, breach notification timing, audit rights, data return or exit terms. Those belong in the agreement.
It does not assess financial or operational resilience. A vendor with strong security controls can still be thinly capitalized or dependent on a single data center. Your due diligence should cover those separately.
It is limited to the stated system and period. Anything outside the described boundary is unexamined.
It is not the same as other certifications. The FFIEC handbook notes that certifications such as ISO or PCI DSS are often point-in-time assessments and do not replace audit reports. Ask for the report itself, not a logo on a website.
The FFIEC is direct on the broader point: users of audit reports or reviews should not rely solely on the report and should use additional verification and monitoring procedures. Examples include reviewing incident history, testing access reviews, sampling vendor outputs and tracking service levels.

What US regulators expect
For banks, the FFIEC handbook states that financial institutions are required to effectively manage relationships with key technology service providers. They may audit the provider directly, use external auditors, or review sufficiently detailed independent audit reports. A SOC 2 report fits the third path, provided it is detailed enough for your purpose.
The OCC's supplemental examination procedures say examiners can use third-party reviews to help scope supervisory activities, and that management's due diligence may include reviewing SOC 2 reports. Then there is the 2023 interagency guidance from the Federal Reserve, FDIC and OCC, which says sound third-party risk management should reflect the level of risk, complexity and size of the banking organization and the nature of the relationship. That is a proportionality principle: a payroll vendor and a loan origination platform do not warrant the same depth of review.
If you are a credit union, check the expectations of your own regulator and examiner for the specifics; the same disciplines of scoping, reviewing and monitoring apply. For a fuller view of the lifecycle, see our overview of third-party risk management for U.S. financial institutions.
A practical process for requesting and reviewing reports
A repeatable process saves time and gives examiners a clear record.
- Tier the vendor. Rank by data sensitivity, operational criticality and substitutability. Only the higher tiers need a full Type II review.
- Request the right documents. The current Type II report, the bridge letter, the subservice organization list, and the vendor's responses to any exceptions.
- Assign a qualified reviewer. The SIFMA guide recommends giving the review to personnel with relevant information security background. A procurement analyst alone will miss scoping and exception issues.
- Document a conclusion. Record the opinion, period, scope fit, exceptions and your decision on each, with open follow-ups and owners.
- Map CUECs. Assign each to an internal control owner and test it.
- Set a refresh cycle. Collect a new report annually, and earlier after a material incident, acquisition or change in hosting.
- Escalate gaps. If scope does not match your use, or an exception touches your data, require remediation evidence or compensating controls before renewal.
A short worked example: a credit union evaluates a loan origination vendor. The Type II report covers security and confidentiality, but the vendor's document-processing module runs on a subservice provider that is carved out. The reviewer notes that the exception list includes one access-review lapse, closed by management within the period. The CUECs require the credit union to approve user provisioning, which today happens by email. The conclusion is not "pass" or "fail"; it is acceptance with three actions: request the subservice provider's assurance, confirm remediation evidence for the access lapse, and formalize the credit union's provisioning approvals.
How we think about SOC 2 at RiskInMind
We sit on both sides of this conversation. Our customers are credit unions, community banks and lenders who send us sensitive loan and portfolio data, and we know what they need to show their examiners. Our approach is documented on our SOC 2 security and compliance page and in our security policy, and we explain why we pursued the report in our SOC 2 announcement.
Three convictions shape our view. First, the report is only as useful as the evidence behind it, so we favor granular audit trails and in-house AI processing with no third-party data exposure, which shrinks the number of subservice organizations a reviewer has to chase. Second, the strongest vendors welcome scrutiny of scope and exceptions instead of steering reviewers to the summary page. Third, AI vendors deserve a sharper question than most: where does your data go when a model touches it? That question belongs in your review alongside the report, and we cover its audit-trail side in our piece on governance-first AI loan underwriting.
If you want to see how fintech controls connect to audit evidence, our article on SOC 2 controls that link GLBA and PCI to audit evidence goes deeper.
— Raj
Evaluating a risk platform vendor with us
If you are assessing a risk platform, loan underwriting, regulatory monitoring or portfolio tools, apply this same discipline to us. Ask for our security documentation, walk through scope and controls, and test the workflow in a live session. Our platform demo evaluation checklist lists what to ask in a demo, and the RiskInMind platform brings loan application, regulatory, fraud detection, CECL and portfolio tools together under one audit-ready environment. Plans and what each includes are on our pricing page.

Compliance officers can see how the platform supports their workflow on our compliance officer solutions page, and risk leaders can start from the solutions page for chief risk officers.
Common mistakes in vendor SOC 2 reviews
- Accepting the cover letter. A vendor's summary or trust-center badge is not the report. Read the auditor's section.
- Ignoring the period. Stale reports describe a past environment.
- Skipping CUECs. Unmapped CUECs leave a hole on your side of the relationship, and a gap between the report's CUECs and contract terms can create compliance risk for you.
- Treating Type I as Type II. Design at a date is not effectiveness over time.
- Reviewing once. Oversight is ongoing. Tie the report to your wider step-by-step risk assessment so findings feed your risk register.
FAQ
What is a SOC 2 report?
It is an auditor's report on a service organization's controls relevant to security, availability, processing integrity, confidentiality or privacy. It includes management's system description and assertion, plus the auditor's opinion. It is intended for specified parties, such as customers and their auditors, not for general distribution.
Should I require Type I or Type II from vendors?
Require Type II for vendors that handle sensitive data or support critical operations, because it tests whether controls worked over a period. Accept Type I only as interim evidence from newer vendors, with a contract commitment to deliver Type II and your own compensating checks in the meantime.
Does a SOC 2 report satisfy regulators?
Not by itself. Regulatory guidance allows institutions to review sufficiently detailed independent audit reports, but it also says not to rely solely on them. Combine the report with contract terms, ongoing monitoring and your own testing of CUECs.
How much does a SOC 2 report cost the vendor, and who pays?
The vendor normally pays for its own audit, and costs vary with scope and auditor, so we do not quote a figure. As a buyer, your cost is the review effort: the time to read, map CUECs and follow up. Plan for it in your vendor onboarding budget.
How often should I collect a new report?
Annually is the usual rhythm, matching the vendor's audit cycle. Ask for a bridge letter in between, and request an updated report sooner after a security incident, a change in hosting provider or an acquisition.
Sources
- What Asset Managers Need to Know About SOC Reports (SIFMA)
- Contents of the SOC 2 Report (PwC Viewpoint)
- Comparison of SOC for Supply Chain, SOC 2 and related reports (PwC Viewpoint)
- FFIEC IT Examination Handbook: Third-Party Reviews of Technology Service Providers
- FFIEC IT Examination Handbook: Internal Audit, Independent Reviews and Certification Processes
- OCC Supplemental Examination Procedures for Risk Management of Third-Party Relationships
- Interagency Guidance on Third-Party Relationships: Risk Management (Federal Register)
- The new US assurance standard SSAE 18 (Compact)
- SOC 2 Type II Transfer MSSP M&A (Acquisition Stars)
