Financial Services + AI: GLBA, FFIEC, and Securities Compliance for ChatGPT and Claude in 2026
Team Sonomos · Sonomos
The Sonomos research team writes about AI privacy, data protection, and how to use generative AI safely at work.
Short answer: Banks, broker-dealers, RIAs, and other financial institutions can use ChatGPT, Claude, and similar AI tools — but the GLBA Safeguards Rule, FFIEC IT guidance, FINRA Regulatory Notice 24-09, SEC Regulation S-P and the SEC's examination priorities collectively raise the bar well above "the vendor is SOC 2." This guide explains, in plain English, what financial-services regulators actually expect of an AI deployment in 2026, the specific risks unique to financial workflows, and the controls that hold up under examination.
The five regulatory regimes that touch every AI decision
For a US financial institution, generative-AI use rarely sits under a single regulator. In practice, the relevant regimes overlap:
- GLBA Safeguards Rule (16 CFR §314 / FRB & OCC equivalents) — requires a written information security program with risk assessment, access controls, encryption, vendor oversight, and incident response. The October 2023 amendment (effective May 2024) requires non-bank financial institutions to notify the FTC within 30 days of discovering unauthorized acquisition of unencrypted customer information involving 500 or more consumers (16 CFR 314.4(j)).
- FFIEC IT Examination Handbook — supervisory expectations covering risk management, third-party relationships, and information security. The August 2024 "Development, Acquisition, and Maintenance" booklet replaced the 2004 booklet and addresses supply-chain risk; the FFIEC's August 2021 statement on "Authentication and Access to Financial Institution Services and Systems" governs access controls.
- OCC Bulletin 2023-17 / SR 23-4 / FDIC FIL-29-2023 (Interagency Guidance on Third-Party Relationships, June 2023) — sets the baseline for vendor due diligence, contracts, ongoing monitoring, and termination, and replaced OCC Bulletin 2013-29. The guidance is technology-neutral and applies to AI vendors as it does to any third party.
- FINRA Regulatory Notice 24-09 (June 2024) — reminds broker-dealers that FINRA rules are technology-neutral and apply to generative AI, naming supervision (Rule 3110) and communications with the public (Rule 2210); books-and-records (Rule 4511) and Reg BI obligations apply through the same principle.
- SEC Regulation S-P (amended 16 May 2024) — broker-dealers, investment advisers and funds must maintain a written incident response program and notify affected customers as soon as practicable, and not later than 30 days after becoming aware of unauthorized access to customer information; the compliance dates (3 December 2025 for larger entities, 3 June 2026 for others) have passed, and the Division of Examinations' 2026 priorities say examiners will test for the new provisions. The SEC's 2023 predictive-data-analytics proposal, which would have required firms to eliminate or neutralize AI-related conflicts of interest, was withdrawn in June 2025; existing fiduciary and Reg BI conflict obligations continue to apply.
In addition, state regimes (NY DFS Part 500, California CCPA/CPRA, similar laws in CO, CT, UT, VA, TX) layer on top, and the EU AI Act applies extraterritorially when an AI system's output is used in the EU.
Why financial workflows are higher-risk than the average AI use case
Three properties of financial work make casual AI use risky in a way generic productivity tools are not:
- Customer NPI is regulated at the point of disclosure. Under GLBA, "nonpublic personal information" — names tied to account numbers, balances, transaction histories — is regulated when shared with non-affiliated third parties. Pasting a portfolio summary into an AI tool that is not under a service-provider contract restricting its use of the data can be a disclosure the rule regulates.
- MNPI / insider information is categorical. Material non-public information about issuers (an unannounced earnings figure, a pending M&A target) is subject to securities laws. Prompts containing MNPI to a tool with retention or training rights raise insider-trading and Reg FD concerns that no after-the-fact remediation can fully cure.
- Books-and-records obligations make every AI interaction a potential record. SEC Rule 17a-4 and FINRA Rule 4511 require firms to preserve communications related to their business. Since September 2022 the SEC's off-channel communications sweeps have produced roughly $1.9 billion in penalties, including more than $1.1 billion against 16 firms in 2022 and more than $560 million against 54 firms in 2024 alone (26 firms, $392.75 million, in August 2024); AI chats raise the same recordkeeping questions.
What examiners look for in 2026
Based on public exam priorities (the SEC Division of Examinations' fiscal-year 2026 priorities, FINRA Regulatory Notice 24-09, the OCC Semiannual Risk Perspective) and bank-regulator guidance, the recurring questions are:
- Inventory. Does the firm know which AI tools its workforce uses, including unsanctioned ones?
- Risk assessment. Has the firm assessed each AI use case against confidentiality, integrity, availability, accuracy, and consumer protection?
- Vendor due diligence. For each material AI provider, does the firm have a current SOC 2, a DPA, evidence of training-opt-out / zero-retention, and a clear path to terminate?
- Customer NPI controls. What technical controls prevent NPI from reaching non-approved AI tools?
- MNPI / insider information controls. What controls prevent MNPI from being entered into AI tools at all?
- Recordkeeping. Are AI prompts and outputs preserved per Rule 17a-4 / 4511, retrievable, and tamper-evident?
- Communications with the public. Is AI-generated marketing or client-facing content reviewed and approved per FINRA Rule 2210?
- Model risk management. For AI used in decisions (fraud, AML, lending), does the firm follow the agencies' model-risk-management guidance (SR 26-2, which replaced SR 11-7 in April 2026)?
- Incident response. Is "AI prompt-leakage incident" in the IR runbook, with notification timelines that match GLBA, Regulation S-P, NYDFS Part 500, and applicable state laws?
A firm that cannot answer most of those clearly will struggle in an exam regardless of how strong its AI vendor's marketing is.
The product-tier reality for financial workflows
As of the November 2026 review, the practical lay of the land is (OpenAI's ChatGPT tier pages could not be re-read from primary sources; confirm those rows against OpenAI's current documentation):
- OpenAI ChatGPT Free / Plus / Pro (consumer) — Prompts are used for training by default unless the user opts out; no enterprise data-processing addendum (DPA). Materially harder to defend for any workflow involving NPI or MNPI.
- OpenAI ChatGPT Business (formerly Team) — Business plan with a DPA available; not used for training. Confirm residency and retention options on OpenAI's current documentation.
- OpenAI ChatGPT Enterprise / Edu / API — Not used for training; enterprise DPA; Zero Data Retention available on the API subject to OpenAI's approval, with retention controls on ChatGPT Enterprise. Workable for customer NPI under proper configuration; MNPI use still requires firm policy.
- Anthropic Claude — Team, Enterprise and API content is excluded from training under the Commercial Terms, with a DPA and zero-data-retention options; since late 2025 consumer Free, Pro and Max users choose whether their chats are used for training.
- Google Gemini (consumer) — May retain and human-review prompts on the free tier; Workspace and Vertex AI under separate enterprise terms.
- Microsoft 365 Copilot / Copilot Chat (enterprise data protection) — Prompts not used to train foundation models when signed into an eligible commercial account; supports audit of interactions.
Every one of these products is configurable in ways that change the regulatory analysis. The firm's compliance position depends on the specific tier, contract, and configuration — not on the product family.
Real-world workflow patterns financial firms are actually using
The patterns below are illustrative of how firms are deploying these tools:
- Research and summarization with redacted input. Analysts use enterprise AI to summarize SEC filings, broker reports, and internal research — with client identifiers masked locally before transmission and MNPI kept out by policy. Locke runs on the user's device as a desktop app; its companion browser extension screens AI websites, and a local proxy screens command-line, script and SDK traffic. Locke 1.0 detects entity categories such as customer names, account numbers and contact details and replaces them with one-way placeholders before the prompt leaves the device; reversible tokenization is planned shortly after 1.0, and coverage depends on the app, platform and settings.
- Marketing and communications drafting. Wholesalers and marketing teams use AI to draft public-facing content. Outputs go through the firm's standard FINRA Rule 2210 review queue before publication; AI-generated drafts are flagged in the workflow.
- Compliance and surveillance assistance. Compliance teams use AI to triage alerts, summarize transcripts, and draft case narratives — with strict isolation from production data and a human-in-the-loop signoff before any action.
- Internal Q&A on policy. AI assistants trained on (or grounded in) the firm's own policy documents answer staff questions, reducing the temptation to paste sensitive context into consumer tools.
In each pattern the principle is the same: keep regulated data inside the firm or with vendors bound by contractual data-processing terms, and use technical controls to make the safe path the easiest path.
Examples: what is and is not defensible
| Scenario | Defensible? | Why |
|---|---|---|
| Advisor pastes a client's full account statement into ChatGPT Plus to "explain the holdings" | No | NPI to a non-DPA, non-zero-retention account |
| Advisor uses ChatGPT Enterprise (DPA, retention controls) to summarize the same statement, with the client's identifiers masked locally via Locke 1.0 | Yes | Detected identifiers are replaced on the device before the prompt is sent; the DPA governs whatever does reach the vendor |
| Trader pastes an unannounced earnings figure into Claude to "draft talking points for the call" | No | MNPI to a third party; Reg FD and insider-trading exposure regardless of vendor |
| Compliance analyst uses an enterprise AI tool to draft a SAR narrative from anonymized facts | Defensible with controls | Strict scope, audit log, human signoff, books-and-records preservation |
| Marketing copywriter uses ChatGPT to brainstorm headlines from public data | Yes | No NPI / MNPI; outputs go through Rule 2210 review |
| Wealth team uses a private LLM grounded on the firm's policies to answer staff Q&A | Yes | Properly governed internal use case |
Frequently asked questions
Does signing a DPA make ChatGPT GLBA-compliant?
A DPA is necessary but not sufficient. GLBA requires a written information security program, risk assessment, vendor oversight, encryption, access controls, and incident response. A DPA addresses one slice — what the vendor may do with your data. The firm is responsible for the rest.
Are AI-generated client communications subject to FINRA recordkeeping?
Yes, if they relate to the firm's business and are sent to or received from clients or counterparties. FINRA Rule 4511 and SEC Rule 17a-4 do not exempt content because an AI helped draft it. Retain inputs and outputs in the same media-neutral retention system you use for email and chat.
What about MNPI in agentic AI workflows?
Agentic systems that browse, read documents, or call internal APIs can encounter MNPI as a side effect. Treat the agent's runtime as a privileged context: limit its tool surface, isolate per-user identity, and apply egress controls. Logging and replay help with both supervision and incident response.
How does the EU AI Act affect a US financial firm?
If the firm or its vendor places an AI system on the EU market, or the system's output is used in the EU, the AI Act's risk-tier obligations can apply. Article 50 transparency duties applied from 2 August 2026; following Regulation (EU) 2026/1744, Annex III high-risk obligations (which include creditworthiness assessment) apply from 2 December 2027 and Annex I product-embedded obligations from 2 August 2028. For most generative-AI use in US firms, the practical impact is on documentation, transparency, and human oversight. Coordinate with EU counsel before assuming the regime does not reach you.
What does a defensible AI inventory look like?
A spreadsheet (or tool-managed registry) listing each AI system used by the firm, its owner, its data classification, vendor, contract status, training/retention configuration, last risk assessment date, and approved-vs-prohibited use cases. Keep it current; examiners ask for it as a starting point.
Is browser-level redaction enough on its own?
It is one layer, not the whole program. Masking NPI on the device before it reaches an AI tool, as Locke does, reduces the chance that customer information reaches a non-approved AI account and supports a defensible minimisation posture; whether it is a reasonable safeguard in a given program is the firm's assessment under its written information security program. It complements — does not replace — that program.
A short checklist for compliance, IT, and risk teams
- Maintain a current AI inventory, including unsanctioned tools observed in usage data.
- Map each AI use case to GLBA, FFIEC, FINRA, SEC, and applicable state requirements.
- Choose enterprise tiers with DPAs and zero-retention configurations; block consumer endpoints.
- Mask customer identifiers on the device before prompts reach AI tools, for the workforces that handle NPI.
- Preserve AI prompts and outputs per Rule 17a-4 / 4511, including for unsanctioned-tool incidents.
- Add AI-prompt-leakage scenarios to the incident-response runbook with GLBA / Regulation S-P / NYDFS / state notification timelines.
- Update the firm's communications policies (FINRA Rule 2210; advertising rules) to address AI-generated content.
- For AI used in decisions, apply the agencies' model-risk-management guidance (SR 26-2).
- Run an annual independent assessment of the AI program, not just the underlying vendors.
Related guides
- PCI DSS and AI: Can You Use ChatGPT With Cardholder Data? for card data specifically.
- AI in Insurance: NAIC Model Bulletin and Colorado Regulation 10-1-1 for insurers and underwriting.
The bottom line
For financial services in 2026, "AI compliance" is not a single conversation; it is GLBA, the FFIEC handbook, FINRA notices, SEC priorities, state law, and (often) the EU AI Act all interacting with each AI use case. Firms that succeed in examinations are not the ones with the most expensive AI vendor — they are the ones that have inventoried what the workforce actually does, made the safe path the easy path with technical controls, and can produce documentation on demand. Generative AI is genuinely useful inside a well-governed program. Outside of one, it is an enforcement case waiting for a trigger.
Sources and primary references
Reviewed November 2, 2026. Regulations are cited to their official text. Vendor statements are cited to the vendor's own documentation as it read on that date; vendors revise these pages, so confirm before relying on them.
- 15 U.S.C. § 6801 — Protection of nonpublic personal information — the GLBA duty to protect customer information and the mandate for safeguards standards.
- 16 CFR § 314.4 — Elements of an information security program — risk assessment, access controls, encryption, service-provider oversight, incident response and the 30-day FTC notification in 314.4(j).
- 16 CFR § 314.2 — Definitions — "notification event" as acquisition of unencrypted customer information without authorization.
- 16 CFR § 313.3 — Definitions (Privacy of Consumer Financial Information) — the definition of nonpublic personal information.
- FTC — Safeguards Rule breach-notification amendment (27 October 2023) — 500-consumer threshold, 30-day deadline, effective 180 days after publication.
- 12 CFR Part 30, Appendix B — Interagency Guidelines Establishing Information Security Standards — the bank-regulator equivalent of the Safeguards Rule, including service-provider oversight.
- OCC Bulletin 2023-17 — Interagency Guidance on Third-Party Relationships — the June 2023 guidance that rescinded OCC Bulletin 2013-29.
- Federal Reserve SR 23-4 — Interagency Guidance on Third-Party Relationships — the Federal Reserve issuance of the same guidance.
- FDIC FIL-29-2023 — Interagency Guidance on Third-Party Relationships — the FDIC issuance.
- OCC Bulletin 2024-26 — FFIEC Development, Acquisition, and Maintenance Booklet — the 2024 IT Handbook update, replacing the 2004 booklet.
- OCC Bulletin 2021-36 — FFIEC Statement on Authentication and Access — the August 2021 authentication guidance.
- Federal Reserve SR 26-2 — Revised Guidance on Model Risk Management — supersedes SR 11-7 as of 17 April 2026.
- FINRA Regulatory Notice 24-09 — FINRA rules are technology-neutral and apply to generative AI; Rules 3110 and 2210 named.
- FINRA Rule 4511 — General Requirements (Books and Records) — preservation in a format compliant with SEA Rule 17a-4.
- FINRA Rule 2210 — Communications with the Public — fair-and-balanced content standards and principal approval of retail communications.
- 17 CFR § 240.17a-4 — Records to be preserved by brokers and dealers — preservation of business communications for at least three years.
- SEC — Predictive data analytics proposal, File No. S7-12-23 — proposed 26 July 2023; withdrawn 12 June 2025.
- SEC press release 2024-58 — Regulation S-P amendments — incident response program and 30-day customer notification, adopted 16 May 2024.
- SEC press release 2022-174 — 16 firms, more than $1.1 billion and 2024-98 — 26 firms, $392.75 million — the off-channel recordkeeping sweeps.
- SEC Division of Examinations — Fiscal Year 2026 Examination Priorities (PDF) — AI-related security controls and Regulation S-P incident-response examinations.
- SEC — Statement on the renaming of OCIE as the Division of Examinations (17 December 2020) — current name of the examinations unit.
- OCC — Semiannual Risk Perspective — the OCC's semiannual statement of supervisory risk priorities.
- NYDFS — 23 NYCRR Part 500, Second Amendment — effective 1 November 2023; 72-hour incident notice in § 500.17.
- NYDFS Industry Letter — Cybersecurity Risks Arising from Artificial Intelligence (16 October 2024) — how Part 500 applies to AI risks and third-party providers.
- OpenAI API — Your data — API content not used for training; Zero Data Retention subject to approval.
- Anthropic — Updates to Consumer Terms and Privacy Policy (28 August 2025) — consumer training choice; commercial products excluded.
- Anthropic Commercial Terms of Service — "Anthropic may not train models on Customer Content from Services."
- Google — Gemini Apps Privacy Hub — human review and up to three-year retention of reviewed consumer chats.
- Microsoft Learn — Enterprise data protection in Microsoft Copilot — prompts not used to train foundation models; audit support.
Sonomos publishes this blog and makes Locke, which detects and masks sensitive information on your device before it reaches an AI model. How Locke works
This article is general information about privacy and AI, not legal advice, and reading it does not create a solicitor–client or attorney–client relationship. Regulatory requirements turn on your specific facts and jurisdiction and change over time. Consult qualified counsel before relying on anything here, and check the publication and last-reviewed dates above. We may revise posts, but we do not undertake to keep any post current as the law changes.
Reference pages for this post
Related Articles
Best Privacy-Focused AI in 2026: Chatbots That Keep Your Data Private
The most private AI runs locally, via Ollama or LM Studio. Lumo, Brave Leo and Venice say they keep no chat logs; Duck.ai hides your IP. Compared, Nov 2026.
Can My Employer See My AI Chats? ChatGPT, Claude, Gemini and Copilot
Yes, if your employer controls the account, the computer or the network. Work accounts on ChatGPT, Claude, Gemini and Copilot let it read or keep chats. A side-by-side table of what each vendor documents, as of November 2026.
Can My Employer See My Copilot Chats? Work vs Personal Accounts
Copilot chats on a work account sit in your mailbox, where your employer can search, hold and export them with Purview. A personal account sits outside the tenant, but a work laptop can still capture it. What Microsoft documents, as of November 2026.