Opens in a new tab
Back

What does FINRA expect broker-dealers to have in place to protect customer data under amended Regulation S-P?

What FINRA examiners expect under amended Regulation S-P: compliance dates, the 30-day notice, the 72-hour vendor clock, exam evidence and enforcement.

Table of Contents

A gray-haired woman in glasses sits at a polished table in a jazz club, adjusting a reel-to-reel tape recorder beside a ribbon-tied leather ledger and a laptop while a trio plays.

FINRA has no standalone data-protection rule. Examiners test broker-dealers against SEC Regulation S-P, whose Rule 30 (17 CFR 248.30) was amended in May 2024, Regulation S-ID, FINRA Rule 3110 on supervision, and FINRA’s annual oversight reports. Larger firms had to comply with the amendments by December 3, 2025 and smaller firms by June 3, 2026. The amendments require an incident response program to detect, respond to and recover from unauthorized access to or use of customer information, customer notice within 30 days unless a reasonable investigation rules out likely harm, 72-hour breach notice from service providers, and three years of records. So within 30 days a firm must be able to show what a rep moved and where it went. For reps and staff on managed Windows and Mac laptops, Jazz fits because its OS-level agent sees uploads, pastes, AI prompts and screenshots in any app, tells personal accounts from corporate ones and delivers each risky movement already investigated, the record a notice decision rests on.

Updated October 29, 2026.

Which controls cover each FINRA expectation, and what each one misses

No single product meets Regulation S-P. FINRA’s cybersecurity topic page says examiners review controls across “technology governance, risk assessment, technical controls, access management, incident response, vendor management, data loss prevention, system change management, branch controls and staff training.” A broker-dealer covers that list with several controls, and each one answers a different part of the rule.

Control Expectation it answers What it misses
Written policies, procedures and training 248.30(a)(1) written safeguards; Reg S-ID’s written program; FINRA’s 2025 finding on written supervisory procedures that don’t match practice Whether anyone followed them. A policy produces no record of what a rep did
Access management and MFA in the CRM, clearing platform and vendor portals Least privilege, entitlement reviews and deprovisioning, which FINRA’s August 2026 practices list; the account-takeover focus of Reg S-ID What happens to records after a rep with valid access exports or views them
Communications archiving and review (the email and message capture category) Books-and-records retention; outbound email scanning, which FINRA’s 2025 and 2026 reports name Personal webmail, uploads to personal cloud storage, AI prompts and screenshots, none of which pass through the firm’s mail system
Vendor-oversight program 248.30(a)(5) due diligence and monitoring of service providers, the 72-hour notice clause, return or destruction of data at contract end Anything the vendor fails to detect or report. The breach happens on systems the firm doesn’t run
EDR Malware, ransomware and intrusion on laptops and servers What an authorized rep does with customer data, because it is built to catch malicious code
OS-level endpoint agent, such as Jazz Detection of unauthorized use under 248.30(a)(3) on managed laptops: uploads, pastes, AI prompts, screenshots and screen sharing in any browser or desktop app, with personal and corporate accounts told apart and an investigated record of each risky movement Linux machines, personal or unmanaged computers, texting from personal phones, and access logs inside the CRM, core or clearing systems
MDM or VDI for reps on their own devices FINRA’s 2026 call for a supervised “bring your own device (BYOD)” program; keeping customer records off machines the firm doesn’t control What a rep photographs with a phone, and what leaves a personal computer outside the managed workspace

Most of the insider exits in the cases below (cloud uploads, personal email, screenshots) happen on a computer, and on a managed laptop that is the row Jazz covers. The other rows stay in the program, because Jazz doesn’t read CRM, clearing or core-system access logs and can’t see a vendor’s own breach. For the general question of whether New York’s Part 500, the GLBA Safeguards Rule and other financial regulations require DLP, see Do financial regulations require DLP?

Regulation S-P amendments: what a broker-dealer has to build

The SEC adopted the amendments in Release 34-100155, dated May 16, 2024, and published them at 89 FR 47688 on June 3, 2024. They took effect August 2, 2024. The operative text is 17 CFR 248.30, and it applies to every broker-dealer, investment company, and registered investment adviser and transfer agent.

Regulation S-P compliance date, and which tier a broker-dealer is in

The SEC’s small entity compliance guide states the dates: “Larger entities must comply with the amendments by December 3, 2025,” and “smaller entities must comply with the amendments by June 3, 2026.” For broker-dealers the line is capital, not headcount. The adopting release treats a broker-dealer as small only if it had total capital under $500,000 at its last audited fiscal year-end and isn’t affiliated with a larger entity, and it estimated that about 77% of broker-dealers fell in the larger tier. Registered advisers are larger at $1.5 billion or more in assets under management. FINRA’s November 14, 2025 reminder warns that these tiers “do not correspond with FINRA’s definitions of large and small firms,” which count registered representatives. Both dates have now passed.

The incident response program: detect, respond, recover

Section 248.30(a)(3) requires written policies to include “a program reasonably designed to detect, respond to, and recover from unauthorized access to or use of customer information, including customer notification procedures.” The program must have procedures to assess the nature and scope of an incident and identify the systems and types of customer information involved, to contain and control it, and to notify affected individuals. The adopting release says “any instance of unauthorized access to or use of customer information will trigger” the program. A rep emailing account files to a personal address against firm policy can be unauthorized use, and the release’s own example of an incident is an employee who leaves unshredded customer files in a public dumpster.

What counts as sensitive customer information

Notice turns on “sensitive customer information,” defined in 248.30(d)(9) as any component of customer information “the compromise of which could create a reasonably likely risk of substantial harm or inconvenience” to the person it identifies. The rule’s examples include Social Security, driver’s license, passport and taxpayer numbers, biometric records, and a name, account number or online user name combined with authenticating details such as an access code, a security question and answer, or a date of birth. A client list carrying account numbers and dates of birth qualifies, and so does an account application.

The 30-day notice, and when a reasonable investigation removes the duty

A firm must notify affected individuals “as soon as practicable, but not later than 30 days, after becoming aware that unauthorized access to or use of customer information has occurred or is reasonably likely to have occurred.” The only delay is a written determination by the US Attorney General that notice poses a substantial risk to national security or public safety. Notice is not required if the firm “determines, after a reasonable investigation of the facts and circumstances of the incident,” that the sensitive customer information “has not been, and is not reasonably likely to be, used in a manner that would result in substantial harm or inconvenience.”

The release calls this “a presumption of notification.” The firm notifies unless its investigation supports not notifying. Among the facts that shape that investigation, the release lists “whether the incident is the result of internal unauthorized access or use of sensitive customer information or an external intrusion” and “whether and what type of customer information may have been copied, transferred, or retrieved without authorization.” If the firm can’t tell whose records were involved, it must notify everyone whose sensitive customer information “resides in the customer information system that was, or was reasonably likely to have been, accessed.” The notice must describe the incident and the data involved, give the incident date where it can be determined, and tell customers how to place a fraud alert and report identity theft to the FTC.

Service providers and the 72-hour notice

Under 248.30(a)(5), the program must include written policies “reasonably designed to require oversight, including through due diligence and monitoring, of service providers.” Firms must ensure each provider protects customer information and notifies the firm “as soon as possible, but no later than 72 hours after becoming aware that a breach in security has occurred resulting in unauthorized access to a customer information system maintained by the service provider.” The firm may contract the provider to send customer notices, but the obligation “rests with the covered institution.” A clearing firm, a CRM host, an archiving vendor and a back-office outsourcer are all service providers if they receive or can access customer information.

Customers of other institutions are now in scope

“Customer information” now covers records about individuals with whom the firm has a customer relationship and “the customers of other financial institutions where such information has been provided to the covered institution.” A broker-dealer that receives account data from another financial institution, for example as its service provider, has to safeguard that data and, if it leaks, handle it under the incident response program.

Records: three years for broker-dealers

Broker-dealers keep these records under Exchange Act Rule 17a-4(e)(14), not under 248.30 itself. Written documentation of any detected unauthorized access and the response, and of “any investigation and determination made regarding whether notification is required,” including “the basis for any determination made” and a copy of any notice, must be kept for three years from when each record was made. The policies, service-provider contracts and disposal procedures are kept until three years after the firm stops using them. FINRA’s August 2026 Cybersecurity Effective Practices adds that firms relying on security logs to meet Rule 30 should note Rule 17a-4(e)(14)(ii) “requires a minimum three-year retention period.”

Disposal now covers customer information

Section 248.30(b) used to cover only consumer report information. It now requires every covered institution, other than notice-registered broker-dealers, to dispose of “consumer information and customer information” with reasonable measures against unauthorized access, under written policies. Laptops returned by departing reps, retired servers and paper files all fall under it.

FINRA cybersecurity requirements: what the 2025 and 2026 oversight reports single out

FINRA publishes its expectations in its annual oversight reports, topic pages and notices. Its Customer Information Protection page calls protecting customer information “a key responsibility and obligation of FINRA member firms” and points to Reg S-P, Reg S-ID and Rule 3110, though its text doesn’t yet mention the incident response program or the 30-day notice. They don’t create new requirements, and the notices and the August 2026 practices say so explicitly, but they show what examiners look for.

  • The 2025 report’s technology management section lists as a finding “Not establishing and maintaining a supervisory system reasonably designed to safeguard customer records and information per Regulation S-P,” alongside inaccurate privacy notices and Reg S-ID program gaps. Its observations include “Not monitoring network activity to identify unauthorized copying or deletion of customer or firm data, and not monitoring outbound emails to identify sensitive customer data in text or attachments,” and branch offices running their own email or application servers without firm-set controls. As an effective practice it suggests retaining log data for “a minimum of 24 months.”
  • The 2026 report’s cybersecurity section, published December 9, 2025, names insider threats: “firm employees who purposely or inadvertently use their access to firms’ systems to cause harm to firms and their customers.” Its effective practices include scanning outbound email “to identify and block exfiltration of sensitive customer information,” MFA for systems used by associated persons and customers, and a supervised BYOD program.
  • The 2026 third-party risk section reports “an increase in the reporting of cyberattacks and outages at firms’ third-party vendors.” It suggests an “inventory of firm data types accessed or stored by the firm’s vendors,” procedures to “return or destroy firm data” when a contract ends, revoking vendor access when the relationship ends, and contract language that keeps firm or customer sensitive information out of a vendor’s open-source GenAI tool.
  • FINRA’s August 2026 Cybersecurity Effective Practices tells firms to “Use data loss prevention or similar safeguards to prevent unauthorized transmission of sensitive data (via email or otherwise) and monitor for unauthorized data transfers or exfiltration (unauthorized data removal or theft) attempts.” It also asks firms to deprovision access “when employees change roles or leave the organization” and to watch for “unusual access patterns, data exfiltration, or system changes that may indicate insider or external threats.”

Departing reps don’t get their own section in either report. They show up in FINRA’s disciplinary actions instead, covered below, and in the deprovisioning practice above. The rules on what a departing advisor may take under the Broker Protocol are covered in the guide to departing advisors and client data.

Branch, remote and residential supervisory locations

Since June 1, 2024, Rule 3110.19 has let a firm treat a rep’s home as a residential supervisory location, inspected on a schedule “presumed to be at least every three years” instead of annually (Regulatory Notice 24-02). The rep may not meet customers there, and “neither customer funds nor securities are handled at that location.” The firm must determine that its technology tools are appropriate to supervise the location’s risks, and the rule text lists “system tools such as secure network connections and effective cybersecurity protocols.” The remote inspections pilot under Rule 3110.18, effective July 1, 2024, carries the same tools language. A firm using either should be able to show what protects customer records on a home-office laptop.

Generative AI

Regulatory Notice 24-09 (June 27, 2024) says FINRA’s rules are “technology neutral” and apply when firms use GenAI, including “through embedded features in existing third-party products,” and that a firm should evaluate GenAI tools before deploying them. The 2026 report’s GenAI section adds that GenAI use “can implicate rules regarding supervision, communications, recordkeeping and fair dealing,” and warns that AI agents working on sensitive data “may unintentionally store, explore, disclose or misuse sensitive or proprietary information.” A rep pasting a client’s account details into a personal ChatGPT account, outside any approved tool, can be unauthorized use of customer information under 248.30. Which AI rules apply to staff at broker-dealers and banks is covered in AI use rules for banks and financial firms.

What SEC examiners say they will test

FINRA examines for Reg S-P, and so does the SEC. The SEC Division of Examinations’ fiscal 2026 priorities (November 17, 2025) put “particular attention” on policies covering “governance practices, data loss prevention, access controls, account management,” and said that after the compliance dates the Division “will examine whether firms have developed, implemented, and maintained policies and procedures in accordance with the rule’s new provisions.” The fiscal 2027 priorities, released October 23, 2026, repeat data loss prevention and add: “In accordance with the amended rule, staff will evaluate response program policies and procedures for unauthorized access to or use of customer information, including customer notification procedures and oversight of service providers.”

FINRA cybersecurity checklist: the evidence examiners ask for, and the control that produces it

FINRA’s own Small Firm Cybersecurity Checklist was “last reviewed and updated, as needed, on February 21, 2024” and “does not reflect any regulatory changes since that date,” so it predates the amendments. FINRA doesn’t publish an examination request list for Reg S-P. The evidence column below lists the records the rule requires or that FINRA’s reports and the SEC’s priorities name.

Expectation Evidence examiners ask for Control that produces it
Written safeguards, 248.30(a)(1) Current written supervisory procedures that match how the firm works, and the risk assessment behind them Policy program with an annual review
Incident response program, 248.30(a)(3) The written plan, test or tabletop records, and the log of incidents with response and recovery documented (kept three years under 17a-4(e)(14)(ii)) Incident response plan, plus the detection tools that feed it
Detecting unauthorized use by insiders Records of risky data movements by reps and staff, and how each was closed OS-level endpoint agent on managed laptops (Jazz); access logs in CRM, core and clearing systems
Notice decision, 248.30(a)(4) The investigation file, the basis for notifying or not, the list of affected individuals and a copy of the notice (three years under 17a-4(e)(14)(iii)) A forensic record of what left, where it went and whether it was opened or shared
Service-provider oversight, 248.30(a)(5) Vendor inventory including data types each vendor holds, due-diligence files, contracts with the 72-hour clause Vendor-oversight program
Access and offboarding Entitlement reviews and deprovisioning records that cover every system and vendor portal Identity and access management, MFA, an offboarding checklist
Outbound email Scanning configuration and the results reviewed Email security and archiving
Branch and residential locations Branch security standards, the 3110.19 technology-tools determination, BYOD policy MDM, VDI, branch standards
Disposal, 248.30(b) Written disposal procedures, destruction certificates, oversight of the disposal vendor Asset disposal process with vendor oversight
Identity theft, Reg S-ID Written identity theft prevention program, red flags, staff training Account-takeover controls, red-flag procedures
GenAI use AI policy, approved-tool list, a record of what customer data went to which AI tool and account Enterprise AI settings for sanctioned tools; an endpoint agent for prompts and uploads into any AI tool

Whether a firm can produce records of employee AI use when asked is covered in can you produce records of employee AI use.

Regulation S-P enforcement: what the SEC and FINRA cases show

Date Case What happened Sanction
June 8, 2016 SEC, Morgan Stanley Smith Barney Employee Galen Marsh took data on about 730,000 customer accounts from internal portals to a personal server at home between 2011 and 2014; portions were later posted online $1 million penalty, censure, Rule 30(a) violation
September 20, 2022 SEC, Morgan Stanley Smith Barney A moving company with no data-destruction expertise decommissioned two data centers in 2016 and sold about 4,900 devices, some with unwiped customer data; 42 local devices went missing; about 15 million customers were notified in 2020 $35 million penalty, Rules 30(a) and 30(b)
November 25, 2025 SEC, M Holdings Securities Email accounts of 17 reps and employees at 13 of its 120 “member firms” were taken over and used to send credential-harvesting emails to about 8,500 people; a significant number of member firms lacked required security controls such as MFA $325,000, Reg S-P and Reg S-ID
October 1, 2025 FINRA, Cash App Investing Offboarding missed a trade reconciliation database the firm didn’t monitor for unauthorized access; a departed rep downloaded names and account numbers for about 8.2 million customers, undetected for about three months Censure, $375,000
May 19, 2025 FINRA, Wells Fargo Clearing Services Miscategorized departing reps kept access to customers’ variable annuity accounts on insurance carriers’ portals Censure, $150,000

The 2016 order is the closest match to a modern insider case. The firm blocked copying to removable media, but its web filter let staff reach “uncategorized” sites, and Marsh moved the data through his own website. The SEC faulted the firm for missing “monitoring and analysis of employee access to and use of the Portals.”

FINRA’s cases against individual reps show the exits a laptop gives them:

  • Days after learning her firm was ending her association, Danielle Freeman copied thousands of files with Social Security, tax ID and account numbers to her personal cloud storage and shared access with a former colleague. She kept them until the firm detected the removal. One-month suspension and a $5,000 deferred fine, January 2025 (FINRA, March 2025).
  • After accepting an offer from another firm, Jason Poschinger downloaded customer data, sent it to two non-firm email addresses he controlled and gave it to the new firm. Six-month suspension and a $20,000 deferred fine, March 2025 (FINRA, May 2025).
  • Preparing to leave, Sam Nevels emailed client contact lists to his personal address and kept “five photographs of information on the firm’s computer system screens and four screen shots of firm emails.” Four-month suspension and a $10,000 fine, December 2025 (FINRA, February 2026).
  • Guy Young texted friends phone photos showing customers’ names, balances, account numbers and dates of birth. One-month suspension and a $5,000 deferred fine, December 2025, in the same February 2026 report.

An agent on a managed laptop would have seen the cloud upload, the emails to personal addresses and the screenshots. Nevels’ five photographs of his screen and Young’s texts came from phones, which no laptop control sees.

How a firm proves what a rep moved inside the 30-day window

The clock starts when the firm becomes aware that unauthorized access or use “has occurred or is reasonably likely to have occurred.” In an insider case that is often a resignation, a tip from a client or a manager’s suspicion. Within 30 days the firm has to answer four questions, and each one needs its own evidence.

  1. What did the rep access? The CRM, the clearing platform and core systems hold the queries and exports. These logs come from those systems, not from the laptop.
  2. What left the laptop, and where did it go? This is the gap the 2016 order describes and the cases above repeat: an upload to personal Gmail or Dropbox, a paste into a personal ChatGPT account, a screenshot, a file synced to a personal drive. An endpoint agent on the managed laptop holds that record.
  3. Whose sensitive customer information was in it? If the firm can name the records, it notifies those people. If it can’t, 248.30(a)(4)(ii) requires notice to everyone whose sensitive information resides in the affected system.
  4. Is misuse reasonably likely? A file uploaded to a personal account that the firm then had deleted, with a signed affidavit, is a different case from a list shared with a competitor. The firm documents the basis either way and keeps it three years.

Without the second answer, the presumption of notification decides for the firm. An investigation that can show a rep uploaded one spreadsheet to a personal drive, and nothing else, supports narrowing the notice to the clients in that spreadsheet. An investigation that can show nothing about the laptop has little to narrow with. How far back to look before a resignation is covered in how to tell if a departing employee is taking company data.

For a firm whose reps and staff work on managed Windows and Mac laptops, Jazz fits this step because its agent records copy and paste, screenshots, GenAI prompts, screen sharing and file uploads at the operating-system level, in desktop apps and in any browser without a browser extension, and keeps the forensic detail in an encrypted rolling buffer on each laptop. Its investigator, Melody, reconstructs each risky movement across the data involved, where it came from and went, who moved it and whether it fits that person’s role, and hands the compliance officer that answer. That is the material the 17a-4(e)(14)(iii) file needs.

Independent broker-dealers and reps who own their computers

Many independent broker-dealer reps run their own offices on computers they bought. An endpoint agent can’t protect a laptop the firm doesn’t manage, and installing one on a rep’s personal machine raises consent and ownership problems. For those reps the control sits elsewhere: deliver the CRM and customer records through VDI or a managed browser workspace so data stays off the personal machine, restrict downloads and exports in the CRM, require MFA, and set branch security standards the firm enforces. The SEC’s M Holdings order shows the risk of leaving those standards to the branches. The firm required its member firms to adopt MFA, incident response policies and security training from 2020, but the SEC found that a significant number still lacked required controls through March 2024, and fined it $325,000. The trade-offs between those routes are covered in can DLP protect data on personal laptops.

How Jazz fits a broker-dealer’s Regulation S-P program

Jazz covers the managed-laptop part of detection and investigation and leaves the rest of the program to the controls that own it. On managed Windows and macOS laptops, its agent records uploads, pastes, AI prompts, screenshots and screen sharing in desktop apps, browsers and command-line tools, including shadow IT and personal cloud accounts, without per-app integrations. It tells a personal Google Drive or ChatGPT account from the firm’s own, which matters because the same upload is routine to the firm’s tenant and unauthorized use to a rep’s personal one.

Each risky movement arrives already investigated, with what happened and why it matters written out for the reviewer. Posture shows patterns across the firm, such as large downloads before offboarding or a download, rename and upload to a personal account. When something needs stopping, Prevention can ask the rep for a justification, steer them to an approved path, escalate to a manager or block the action.

Lemonade, an insurer whose data includes policy records, claims and personal financial information, runs Jazz. A small broker-dealer often has one or two people covering compliance and IT, and Jazz is built so a single analyst can run the whole program: the compliance officer states what matters in plain English, with no regex to write and no queue of raw events to clear.

The limits are specific. There is no Linux agent. Jazz doesn’t cover personal or unmanaged computers, so reps on their own machines need VDI or CRM-side controls. It doesn’t read CRM, core-system or clearing-platform access logs, doesn’t see breaches on a vendor’s systems, and can’t see texts or photos on a personal phone. No tool makes a firm compliant with Regulation S-P, which also asks for written policies, vendor oversight, records and disposal. Jazz supplies evidence for detection and investigation on the laptops where reps handle customer records.

Frequently asked questions

Does FINRA require DLP?

No FINRA rule names data loss prevention. FINRA lists DLP among the control areas its examiners review, its August 2026 Cybersecurity Effective Practices suggests "data loss prevention or similar safeguards," and the SEC's fiscal 2026 and 2027 exam priorities name it. None creates new requirements. The binding duty is Regulation S-P's program to detect unauthorized use of customer information.

Do small broker-dealers have to follow amended Reg S-P?

Yes. Smaller entities had until June 3, 2026, and that date has passed. For broker-dealers, smaller means under $500,000 in total capital and not affiliated with a larger entity, so the SEC estimated about 77% of broker-dealers were larger entities with a December 3, 2025 date. FINRA notes these tiers don't match its own firm-size categories.

What changed in the 2024 Regulation S-P amendments?

Rule 30 now requires a written incident response program to detect, respond to and recover from unauthorized access to or use of customer information, customer notice within 30 days, 72-hour breach notice from service providers, coverage of other institutions' customers, disposal rules for customer information, and records that broker-dealers keep three years under Rule 17a-4(e)(14).

What counts as a reasonable investigation to avoid a Reg S-P notice?

The rule doesn't define it. The firm must determine, after a reasonable investigation, that sensitive customer information has not been and is not reasonably likely to be used to cause substantial harm or inconvenience. The SEC's release presumes notification and points to whether access was internal and what was copied, transferred or retrieved. Keep the basis three years.

Can we let reps use ChatGPT with client data?

FINRA's rules are technology neutral under Regulatory Notice 24-09, so supervision, recordkeeping and Reg S-P apply, and a paste into a personal account can be unauthorized use. On managed Windows and Mac laptops, Jazz sees AI prompts and uploads in any browser or desktop app and tells personal from corporate accounts. It can't see personal phones.

How do we know whether a departing rep took client data?

Check CRM and clearing logs for exports, then review what left the laptop before the resignation. On managed Windows and Mac laptops, Jazz records uploads to personal cloud storage and email, pastes and screenshots, and delivers each as an investigated incident. It doesn't cover personal computers, phones or CRM logs. See departing advisors and client data.

Does Jazz work if our reps use their own computers?

No. Jazz's agent runs on managed Windows and Mac laptops and doesn't cover personal or unmanaged computers or Linux. For independent reps on their own machines, keep customer records inside VDI or a managed workspace, restrict CRM downloads and exports, require MFA and enforce branch security standards, the gap the SEC's 2025 M Holdings order penalized.

What do examiners ask to see for Regulation S-P?

FINRA doesn't publish a request list. Expect current written procedures, the incident response plan and test records, incident and notice-decision files kept three years under Rule 17a-4(e)(14), a vendor inventory and contracts with the 72-hour clause, access and offboarding records, disposal procedures and the Reg S-ID program.

Keep exploring