Vendor note. Verlo makes AI software for financial advisors, so firms build this file for us too. You can request our security documents through the Verlo Trust Center. Our guide to AI software for financial advisors compares the tools themselves. The list below works for any vendor. The rule references come from the eCFR (read on November 6, 2026) and the trust-center examples from the vendors’ own pages. This is general information, not legal advice; have your compliance officer or counsel adapt it. If something here is out of date, tell us at support@verlo.finance.
The short answer. For every vendor that handles client information, keep twelve things: the tiering and decision record, the completed questionnaire, the independent attestation (usually a SOC 2 Type 2 report) with a bridge letter if needed, a penetration-test summary, the subprocessor list including model providers, the signed contract with its data and breach-notice terms, a security and data-flow overview, the incident-response summary, a continuity summary, the AI governance policy, proof of insurance, and a monitoring log. Index them in one place, date everything, and review on a schedule.
A due-diligence questionnaire tells you what a vendor says. The file is what you can show an examiner: what you asked, what evidence came back, what you decided and why, and how you kept watching. If a vendor touches client information, the file is the practical proof of the oversight that Regulation S-P requires.
What the file is for
Regulation S-P requires an adviser’s incident response program to include written policies and procedures for overseeing service providers, through due diligence and monitoring, so that providers protect customer information and tell you within 72 hours of becoming aware of a breach (17 CFR 248.30(a)(5)). The amendments also added a records requirement: Rule 204-2(a)(25) says an adviser must keep its service-provider oversight policies and “the written documentation of any contract or agreement” entered into with a service provider under the rule (17 CFR 275.204-2). Rule 204-2 generally sets a five-year retention period. The vendor file is where those records, and the evidence behind your decisions, live. For the rule in full, see our Regulation S-P guide.
The twelve documents
# | Document | What it shows | Where to get it | What to check |
|---|---|---|---|---|
1 | Tiering and decision record | What the tool can reach, why it got the diligence level it did, who approved it and when | You write it | The tool’s reach, not the stated use; the approval date and approver |
2 | Completed questionnaire | The vendor’s written answers to your questions | Send our 52-question DDQ | Specific answers backed by evidence, not adjectives |
3 | SOC 2 Type 2 report, and a bridge letter if the period ended months ago | An independent auditor tested the vendor’s controls over a period | Trust center, under NDA, or from the vendor | The period, scope, opinion, exceptions and user-entity controls (see below) |
4 | Penetration-test summary | An independent party tried to break in, and what was fixed | Vendor, usually under NDA | A test within the last year, and fixes for high-severity findings |
5 | Subprocessor list, including model providers | Everyone downstream who can touch your data | Trust center or the DPA | Each one’s function and location, and notice before changes |
6 | Signed contract: MSA, order form and data processing terms | What the vendor is bound to do | Your signed copy | No training on your data, retention, 72-hour breach notice, deletion on exit, audit cooperation |
7 | Security overview and data-flow diagram | Where your data goes and how it is protected | Vendor | A diagram that matches what you connected |
8 | Incident-response summary and contacts | How the vendor detects, escalates and tells you | Vendor | A tested plan and a named contact with response times |
9 | Business continuity and disaster recovery summary | What happens if the vendor goes down | Vendor | Recovery targets and last test date |
10 | AI governance policy | How models are tested, changed and supervised | Vendor | Notice before model or provider changes, and human review of client-facing output |
11 | Certificate of insurance | Cyber and professional liability cover | Vendor or broker | Limits that fit the data at stake |
12 | Monitoring log | Your reviews, vendor notices, changes and actions | You keep it | Dates of each review, and what triggered any extra one |

Many vendors publish part of this in a trust center and keep the sensitive documents behind a request. Anthropic’s lists its attestations by product and puts reports such as its Type 2 SOC 2 behind access.

How to read a SOC 2 report in ten minutes
A SOC 2 report is written by an independent auditor about a vendor’s controls. Check these in order:
Type 1 or Type 2. A Type 1 report covers whether controls are designed properly at a single point in time. A Type 2 report also tests whether they operated effectively over a period, typically three to twelve months, which is why it carries more weight. Ask for Type 2.
The period. OpenAI’s trust portal shows the idea: its 2025 SOC 2 report covers January 1 to June 30, 2025, and its 2026 report covers July 1, 2025 to June 30, 2026. If the period ended months ago, ask for a bridge letter covering the gap.
The scope. Which products and systems are in the report? OpenAI’s portal lists its 2025 report as covering the API Platform and ChatGPT Enterprise, Edu and Team, and points to a separate product compliance status page for the 2026 report. A product that is not named may not be covered.
The opinion. An unqualified opinion is the clean result. Read any qualification.
Exceptions. Controls that failed testing are listed with management’s response. A few minor ones are normal; patterns are not.
User-entity controls. The report lists controls you are expected to run yourself, such as access reviews. Make sure you do.
Subservice organizations. Hosting and model providers may be carved out of the report, which means you need their evidence separately.
How to organize the file
Keep one folder per vendor with the same structure, so an examiner can find things in seconds:
01 Decision: tiering and approval record
02 Questionnaire: the completed DDQ and correspondence
03 Attestations: SOC 2 report, bridge letter, penetration-test summary, other certificates
04 Contract: signed terms, order form, amendments
05 Subprocessors: current list and change notices
06 Security and incident: overview, data-flow diagram, incident summary, continuity summary, AI governance policy, insurance
07 Monitoring: review log, vendor notices, changes, exit documents
Date every document when you receive it, and record the document’s own date or period. Here is an index to track them:
Vendor | Document | Document date or period | Date received | Next review | Owner | Location | Notes |
|---|---|---|---|---|---|---|---|
Example notetaker | SOC 2 Type 2 report | Period ends June 30 | Date | Date | CCO | 03 Attestations | Bridge letter requested |
Example notetaker | Subprocessor list | Date on list | Date | Date | Operations lead | 05 Subprocessors | Includes model provider |
Example notetaker | Signed MSA and data terms | Signed date | Date | Date | CCO | 04 Contract | 72-hour breach notice in clause |
Download this table as a spreadsheet (CSV)
Review cadence and triggers
Re-review each vendor that handles client information at least annually, and sooner when something changes. Triggers include a new subprocessor or model provider, a breach, an acquisition, a new feature that widens what the tool can read or do, a new system you connect, and expiry of the attestation period. Record each review and its outcome in the monitoring log. Annual review is common practice, not a rule requirement.
Frequently asked questions
What does an RIA vendor due-diligence file contain?
The tiering and decision record, the completed questionnaire, the independent attestation (usually a SOC 2 Type 2 report), a penetration-test summary, the subprocessor list, the signed contract and data terms, security, incident and continuity summaries, the AI governance policy, proof of insurance, and a monitoring log.
Does Regulation S-P require a SOC 2 report?
No attestation is named in the rule. It requires written oversight of service providers through due diligence and monitoring. A current SOC 2 Type 2 report is the most common piece of evidence, so your policy should say what you require and what you do when a vendor cannot provide one.
What if a vendor will not share its SOC 2 report?
Many vendors share it under NDA or through a trust center after a request. If a vendor refuses, document the request and the reply, look for other evidence (a penetration-test summary, a completed questionnaire, a public attestation matrix), and decide in writing whether the gap is acceptable for the data involved. A refusal is a red flag.
Is a SOC 2 Type 1 report enough?
A Type 1 report shows controls were designed properly at one date, not that they worked over time. For a vendor that handles client information, ask for Type 2, or ask when it will have one and what compensating evidence it can give you in the meantime.
How long should we keep the file?
Rule 204-2 generally requires records to be kept for at least five years from the end of the fiscal year of the last entry, with the first two years in an appropriate office of the adviser. Keep the file for at least the life of the relationship plus that period, and confirm with counsel.
Go deeper
AI vendor due diligence checklist for RIAs (with a downloadable DDQ)
Regulation S-P amendments: what RIAs must do about AI and other service providers
Updates to this guide
November 17, 2026: First published.
Sources
Checked November 5 and 6, 2026: 17 CFR 248.30, 17 CFR 275.204-2, OpenAI Trust Portal, Anthropic Trust Center, A-LIGN, “What’s the difference between SOC 2 Type I and Type II?”.