A SOC 2 report is useful to a bank or credit union only when you read its scope, its period and its exceptions against the activity you are outsourcing. No federal rule requires a vendor to hold one. Examiners expect you to do due diligence proportionate to risk, and an independent report is one of the best inputs. Choose vendors whose report is current, covers the system you will actually use, and ties to your contract and monitoring program. We are RiskInMind, and we have earned a SOC 2® report ourselves, so we know what a risk team should ask any technology vendor.
TL;DR
- No US banking regulation we found makes SOC 2 mandatory for vendors. Interagency guidance says a bank may consider reviewing SOC reports and should judge whether their scope and results fit the activity.
- Type 2 matters more than Type 1 for cloud services that handle customer data, because it tests controls over a period and not on a single date.
- Read five things in every report: system boundary, Trust Services Criteria, period covered, subservice organizations and the customer controls you must run yourself.
- Tier vendors by risk, write control and reporting standards into the contract, and re-review the report on a cycle that matches the vendor's criticality.
- If a vendor has no report or a gap, document the limitation and add controls, monitoring or an alternative provider.
Maintain 100% NCUA & OCC Audit Readiness
Monitor regulatory updates 24/7, check internal credit policies, and generate compliance trails with Erina (AI Regulatory Agent).
Table of Contents
- What SOC 2 means when a bank evaluates a vendor
- Does US banking regulation require a SOC 2 report?
- Type 1 or Type 2: which should you accept?
- How to read a vendor's SOC 2 report
- Fitting SOC 2 into vendor tiering, contracts and monitoring
- When a vendor has no SOC 2 report, or the report leaves a gap
- What this means when the vendor is an AI risk platform
- Perspective
- Where RiskInMind fits
- FAQ
- Sources
What SOC 2 means when a bank evaluates a vendor
SOC 2 is an attestation report on controls at a service organization. It covers some or all of five categories: security, availability, processing integrity, confidentiality and privacy (SIFMA guide to SOC reports). Independent CPAs perform the audit. Management provides an assertion about its system, and the auditor opines on how the controls were designed and whether they operated effectively during the audit period (TN Bankers guide to SOC reports, 2026).
The report comes in two types. Type 1 examines controls as of a specific date. Type 2 evaluates the design and the operating effectiveness of those controls over a period (American Banker). A SOC 3 report is a general-use summary for readers who only need assurance that controls exist. It lacks the detail a risk officer needs for due diligence.
SOC 2 is not a seal of approval. It is a body of evidence, and its value depends on what the report covers and what you do with it.

Does US banking regulation require a SOC 2 report?
Not by name. The interagency guidance on third-party relationships, issued in June 2023 by the Federal Reserve, FDIC and OCC, does not make a SOC 2 report a condition of doing business. It treats SOC reports as one possible due-diligence input alongside an evaluation of the third party's overall risk management and independent testing (Interagency Guidance on Third-Party Relationships). The Federal Reserve's supervisory letter on that guidance says a banking organization may consider reviewing SOC reports and independent certifications, and should consider whether their scope and results are relevant to the activity and whether additional scrutiny of the third party or its contractors is appropriate (SR 23-4).
The Federal Reserve's community bank guide on fintech due diligence goes further in practice. It lists SOC reports, independent assessments and industry certifications among the items to use when assessing third parties (Conducting Due Diligence on Financial Technology Companies).
State rules point the same way. New York's Department of Financial Services guidance from October 2025 says ongoing assessments of third-party service providers may consider security attestations such as SOC 2 and ISO 27001, penetration testing summaries and compliance audits (NYDFS industry letter).
The practical result: no statute demands SOC 2, but a bank that skips an available independent report will struggle to show examiners that it did proportionate diligence. For most core, cloud and data-handling vendors, a current report is the expected baseline in vendor risk management programs. Our overview of third-party risk management for US financial institutions covers the wider lifecycle.

Type 1 or Type 2: which should you accept?
For a vendor that processes customer information in the cloud, Type 2 carries more weight. A Type 1 report tells you the controls were suitably designed on one day. A Type 2 report tests whether they kept working. American Banker commentary makes the same practical point for credit unions that rely on cloud-delivered services (American Banker).
A young vendor may have only a Type 1 report. That does not disqualify it, but treat it as a starting point and ask when the Type 2 period begins and ends. Type 2 periods commonly run 12 months, and SIFMA recommends assessing operating effectiveness more closely when coverage is shorter than that (SIFMA).
How to read a vendor's SOC 2 report
SIFMA describes scope as the combination of the system covered, the period covered and the trust services categories included, and calls understanding scope key to assessing the risks of using the service organization (SIFMA). Work through the report in this order.
1. System boundary
Confirm the audited system is the one you will use. A vendor may hold a report on its hosting platform while the product you are buying sits outside it. Match product names, modules and data flows in the system description to your own use case. If you plan to send loan files, bank statements or member data through a particular module, that module must be inside the boundary.
2. Trust Services Criteria
Security is the baseline. Add availability if the vendor supports a process you cannot do without, confidentiality if it holds sensitive underwriting or member files, and processing integrity if its output feeds decisions such as credit scoring or reserve calculations. A report that includes only security may be fine for a low-risk tool and thin for a critical one.
3. Period and currency
Note the report dates. A report that ended long ago leaves a gap before today. Ask for a bridge letter covering the time since the period end, and plan your re-review for when the next report is due.
4. Exceptions and the auditor's opinion
Read the opinion first, then the tested controls and any exceptions. An unqualified opinion with several exceptions in access management is a different finding from one with none. For each exception, read management's response and ask whether it touches the data you will send.
5. Subservice organizations and customer controls
SIFMA tells reviewers to identify subservice organizations and their complementary controls (CSOCs), and the complementary user entity controls (CUECs) that the customer must evaluate in its own environment (SIFMA). Since SSAE 18 replaced SSAE 16 on May 1, 2017, the audited company must identify the additional subservice providers needed to deliver its services (TN Bankers). A carve-out method means the subservice provider's controls are not tested in the report, so you need to see what covers them. The CUECs are your homework: if the report assumes you enforce multifactor authentication or review user access, your own team has to do that, and examiners may ask for evidence.
Fitting SOC 2 into vendor tiering, contracts and monitoring
A report is an input, not the end of the process. Federal Reserve guidance says ongoing monitoring should be commensurate with the risk and complexity of the relationship, and that critical activities warrant more comprehensive or frequent monitoring. Typical activities include reviewing reports on the third party's performance and the effectiveness of its controls, periodic meetings, and regular testing of your own controls for managing the relationship (Interagency Guidance).
In practice, that means a simple tiering rule:
| Vendor tier | Example | Report expectation | Review cadence |
|---|---|---|---|
| Critical | Core processor, lending or underwriting platform, anything holding member files | Current Type 2 with relevant criteria, subservice and CUEC review | At least annually, with interim check-ins |
| Moderate | Tools that touch internal data but not customer records | Type 2 or equivalent independent assessment | Annual or on report renewal |
| Low | No access to sensitive data | Lighter diligence, public security documentation | Periodic, risk-based |
The tiers are an illustration of how to apply the guidance, not a regulatory table. Set your own according to your risk assessment.
Contracts matter as much as reports. The FFIEC IT Examination Handbook says management should verify that providers maintain controls sufficient to mitigate risks, and should include minimum control and reporting standards and access for evaluation in contracts. Where a provider stores, transmits, processes or disposes of customer information, the contract should require measures designed to meet the institution's information security standards (FFIEC IT Handbook). Write in an obligation to deliver each new SOC report on time and to notify you of qualified opinions or significant exceptions.
If you operate in New York, the NYDFS guidance adds that policies must cover periodic assessments and ongoing monitoring once a relationship is active, and that due diligence should consider whether providers use unique, traceable accounts and keep audit trails that meet Section 500.6 (NYDFS). Audit trails are a good question for any vendor: can you trace who did what, and when, inside the system?
If you want to automate part of this workflow, our guide to vendor risk assessment with AI shows how banks and credit unions can structure intake and review.
When a vendor has no SOC 2 report, or the report leaves a gap
The Federal Reserve's guidance describes the path: document the limitations of your due diligence, understand the risks they create, and consider alternative information, additional controls or monitoring, or another provider. It also advises assessing the SOC scope and considering additional scrutiny where appropriate (Interagency Guidance).
In a real review, that looks like this:
- Record exactly what is missing: no report, a report that excludes the relevant system, a stale period or an unfavorable opinion.
- Ask for alternative evidence such as another independent assessment, penetration test summaries or a completed security questionnaire.
- Limit the data and the activity the vendor can touch until the gap is closed.
- Set a deadline for remediation and a decision date in the contract.
- Escalate to the board or committee that owns vendor risk when the vendor is critical.
The point is a documented decision, not a particular answer.
What this means when the vendor is an AI risk platform
AI vendors raise the same questions with a few additions. Ask where your data is processed, whether it is exposed to third-party models, how long it is retained, and whether the audit trail records each automated decision. A loan underwriting or compliance platform sits close to member data and credit decisions, so it belongs in your critical tier and deserves a Type 2 review with attention to processing integrity and confidentiality. Our article on SOC 2 audit trails and governance-first AI loan underwriting explains what examiners tend to look for, and our risk platform demo checklist turns it into questions for a demo.
Perspective
Most banks we talk with treat SOC 2 as a filing exercise: collect the PDF, tick the box, move on. That wastes the best part of the report. The system description, the exceptions and the CUECs tell you how a vendor really operates and what your own team still owes.
We built RiskInMind for credit unions, community banks and lenders, and we hold a SOC 2® report because we expect to be examined by the same standard we apply to others. Our position is simple: AI that touches underwriting, compliance and portfolio monitoring should come with bank-grade security, granular audit trails and real-time workflows with response times under half a second, so risk teams get speed without losing evidence.
When you evaluate any vendor, ours included, ask what is inside the audited boundary and how the audit trail supports your own exam file. That is the conversation we want to have.
Raj
Where RiskInMind fits
RiskInMind is an AI risk management platform for financial institutions, covering loan underwriting, regulatory compliance, credit memo generation, document fraud detection, CECL modeling and portfolio monitoring through specialized AI agents coordinated by a central AI director, Ava. Our security posture includes SOC 2® certification and bank-grade security, and you can read the details on our SOC 2 security and compliance page and in our announcement of the SOC 2 report. For control mapping to GLBA and PCI, see our post on SOC 2 for fintech.
If you are building a shortlist, review the Starter, Professional and Enterprise plans or start from the RiskInMind platform overview.

FAQ
Is SOC 2 legally required for vendors that serve banks?
No US banking rule we found names SOC 2 as a requirement. Federal Reserve guidance says a bank may consider reviewing SOC reports and should judge whether their scope and results fit the activity. In practice, examiners expect documented due diligence, and a current SOC 2 report is a common way to show it.
Is a SOC 2 Type 1 report enough?
It is a reasonable starting point for a new vendor, but Type 2 gives more assurance for cloud services that handle customer data because it tests controls over a period. If a vendor offers only Type 1, ask when its Type 2 observation period ends and consider added monitoring in the meantime.
How often should we review a vendor's SOC 2 report?
Review it each time a new report is issued, which is typically annually, and more often for critical vendors. Federal Reserve guidance ties the frequency and depth of monitoring to the risk and criticality of the activity, so set the cadence by vendor tier.
What if the vendor's report excludes a subservice provider?
Identify which controls the carve-out leaves untested and ask what evidence covers them, such as the subservice provider's own report. SIFMA advises reviewers to identify subservice organizations and their complementary controls so those risks can be assessed and, if needed, addressed in the contract or monitoring plan.
Sources
- Interagency Guidance on Third-Party Relationships (Federal Reserve, June 2023)
- SR 23-4 Supervisory Letter (Federal Reserve)
- Conducting Due Diligence on Financial Technology Companies (Federal Reserve, May 2024)
- FFIEC IT Examination Handbook: Oversight of Third-Party Service Providers
- NYDFS Guidance on Managing Risks Related to Third-Party Service Providers (October 2025)
- What Asset Managers Need to Know About SOC Reports (SIFMA, 2019)
- Guide to Understanding SOC Reports (TN Bankers, 2026)
- CUs shouldn't ignore risks posed by cloud-based vendors (American Banker)
