SEC cyber enforcement, 2015 to 2026: steady firm cases, no disclosure cases since 2024
We built the list of SEC actions under Regulation S-P, Regulation S-ID and cyber disclosure rules from the SEC's own pages, and read what the 2024 Regulation S-P dates mean now.
The question
A sibling report counts the cyber incident reports public companies file with the SEC. This one looks at the other side of the record: the enforcement actions in which the Securities and Exchange Commission charged a firm over how it protected customer information, prevented identity theft, or described and escalated cyber incidents. It covers actions dated from January 2015 to November 16, 2026, and then reads the 2024 amendments to Regulation S-P, whose compliance dates passed in December 2025 and June 2026 [30] [31].
Data and method
We built the case list ourselves from the SEC's own pages, read on November 16, 2026, in three passes:
- Every SEC press release listed for 2015 to 2026, 2,974 in all, read in full and searched for "Regulation S-P", "Regulation S-ID", "Identity Theft Red Flags", "Rule 30(a)", "Safeguards Rule", "cyber", "ransomware", "data breach", "hack", "personally identifiable" and "customer records and information" [2].
- Every entry in the SEC's administrative proceedings listing for the same years, 8,428 in all, and every Administrative Summary linked from them, 886 entries with a summary, searched for the same terms [3].
- The SEC enforcement division's own list of cyber-related actions, under "Regulated Entities – Cybersecurity Controls and Safeguarding Customer Information" and "Public Company Disclosure and Controls", checked against both passes [1].
Rules for counting:
- An action is counted when the SEC's release says the order found, or the complaint alleged, a violation of Regulation S-P (Rule 30(a), the safeguards rule, or Rule 30(b), the disposal rule), Regulation S-ID (Rule 201), or a disclosure, disclosure controls or internal controls provision in connection with a cybersecurity incident or cyber risk. A third group holds actions against other market firms charged with failing to protect client assets, keep books and records, or notify the SEC, where the release ties that failure to a cyber intrusion or ransomware attack.
- One SEC order or one complaint is one action, however many respondents it names. The order against five affiliated Cetera firms counts once; the three 2022 Regulation S-ID orders count three times, because the SEC issued three orders [12] [13].
- Year and date are those of the order or the complaint as the SEC lists them. Settled means the respondent consented to an administrative order or judgment; litigated means the SEC filed a contested complaint.
- Penalties are recorded as the SEC states them, for the firm, without adjusting for inflation. Penalties on individuals are left out, and individuals are not named here; Southwind's $50,000, which the firm and its owner owe jointly, is counted as the firm's [7]. Where one order covers other violations too, the SEC gives one penalty and we do not split it.
- Left out, though some appear on the SEC's cyber list: actions against hackers and fraudsters themselves; crypto-related cases, including the NVIDIA (2022) and Silvergate (2024) disclosure cases; the 2018 report of investigation on business email fraud, which charged no one [1]; Regulation SCI and clearing agency risk management cases with no cyber incident, such as Virtu Americas (2019), the Options Clearing Corporation (2019 and 2023) and OTC Link (September 2026) [38] [37] [39] [40]; and the 2021 GWFS Equities order, which charged failures to file suspicious activity reports about attempts to take over customer accounts, a reporting rule outside the three groups [36]. The 2023 complaint against Virtu, whose release says it also concerned failures to protect sensitive customer information, is left out because the SEC charged Securities Act Section 17(a) and Exchange Act Section 15(g) violations, not Regulation S-P, and described no intrusion [29].
Limits: administrative orders announced with neither a press release nor a summary are not text-searched, so a small Regulation S-P case issued only as an order could be missing. Releases say what the SEC found or alleged; they are not findings by a court.
A small record that peaked in 2024
The count by year, with every respondent as the SEC names it [2] [3] [1]:
| Year of order or complaint | Actions | Respondents as the SEC names them (rules) |
|---|---|---|
| 2015 | 1 [4] | R.T. Jones Capital Equities Management (Rule 30(a)) [4] |
| 2016 | 2 [5] [6] | Craig Scott Capital (Regulation S-P); Morgan Stanley Smith Barney (Rule 30(a)) [5] [6] |
| 2017 | 1 [7] | Southwind Associates of NJ (Rule 30(a) with Advisers Act charges) [7] |
| 2018 | 2 [9] [8] | Voya Financial Advisors (Safeguards Rule and S-ID); Altaba (disclosure) [9] [8] |
| 2019 | 0 [2] [3] [1] | none found [2] [3] [1] |
| 2020 | 0 [2] [3] [1] | none found [2] [3] [1] |
| 2021 | 5 [10] [11] [12] | First American Financial (disclosure controls); Pearson (disclosure); Cetera entities, Cambridge, KMS (Rule 30(a)) [10] [11] [12] |
| 2022 | 4 [13] [14] | J.P. Morgan Securities, UBS Financial Services, TradeStation (S-ID); Morgan Stanley Smith Barney (Safeguards and Disposal Rules) [13] [14] |
| 2023 | 2 [15] [16] [17] | Blackbaud (disclosure); SolarWinds (litigated, later dismissed) [15] [16] [17] |
| 2024 | 9 [18] [19] [20] [21] [22] [23] | Intercontinental Exchange (Regulation SCI notice); R.R. Donnelley (controls); Equiniti Trust (transfer agent safeguarding); Unisys, Avaya, Check Point, Mimecast (disclosure); ICBC Financial Services (books and records); Flagstar (disclosure) [18] [19] [20] [21] [22] [23] |
| 2025 | 2 [24] [25] | Robinhood Securities and Robinhood Financial (Rule 30(a) and S-ID, among others); M Holdings Securities (Rule 30(a) and S-ID) [24] [25] |
| 2026 (to November 16) | 1 [26] | TAG Associates (S-ID and custody rule) [26] |
The 15 broker and adviser cases charge Regulation S-P, Regulation S-ID or both; three of them charge both, Voya in 2018, Robinhood in 2025 and M Holdings in 2025 [9] [24] [25]. The 11 public-company cases charge disclosure or controls provisions after a cyber incident, from Altaba's 2018 order over the Yahoo breach to Flagstar's in December 2024 [8] [23]. All 29 but one were settled; the exception, SolarWinds, was filed as a litigated complaint on October 30, 2023 and dismissed with prejudice on a joint stipulation on November 20, 2025, the SEC saying its decision "does not necessarily reflect the Commission's position on any other case" [16] [17].
Moraph's view
Moraph's view: the record is small, which makes each order a template. Most of the safeguards cases since 2018 describe the same pattern: a known attack route (password resets by phone, email account takeovers, a remote access weakness, devices sold without wiping) and policies that existed on paper but were not applied across the firm. Firms reading this list should look at which control was missing, not at the penalty.
Safeguards and red flags: the cases keep coming
The safeguards cases describe what went wrong in plain operational terms. R.T. Jones had no written policies at all when its web server was attacked, and paid $75,000 [4]. Voya's intruders called its support line to reset contractors' passwords, reaching information on 5,600 customers; the SEC called its order the first under the Identity Theft Red Flags Rule [9]. The 2021 orders found that cloud email accounts at the Cetera entities, Cambridge and KMS were taken over by outsiders between 2017 and 2021, exposing information on at least 4,388, at least 2,177 and about 4,900 customers respectively, with penalties of $300,000, $250,000 and $200,000 [12]. Morgan Stanley Smith Barney paid $35 million in 2022 after a moving and storage company it hired sold thousands of its devices, some still holding customer data that later turned up on an internet auction site [14].
The Regulation S-ID cases are about the program rather than an attack: in 2022 the SEC found that three firms' identity theft programs did not identify red flags, respond to them or get updated, with penalties of $1.2 million, $925,000 and $425,000 [13]. The two most recent cases are smaller. M Holdings, with 120 branch offices, adopted its first information security policy in September 2020, and a significant number of branches still lacked controls such as multi-factor authentication and written incident response policies through March 2024 [25]. TAG Associates did not review or update its identity theft program between June 2014 and December 2023 [26].
Penalty figures are lumpy. Leaving out Robinhood, the 14 safeguards and red flags orders add up to $41,025,000 in firm penalties, and one order, Morgan Stanley's in 2022, is $35 million of it; the median order is $312,500 [4] [5] [6] [7] [9] [12] [13] [14] [24] [25] [26]. Robinhood's January 2025 order is left out of that sum because its $45 million covers more than ten provisions, from Regulation SHO to recordkeeping; four of the 14 (Craig Scott, Southwind, Cetera and TAG) also charged other provisions, and their single penalties are counted whole [5] [7] [12] [26] [24].
No public-company disclosure case since Flagstar
The public-company cases rest on what a company told investors after an incident. The SEC found that Pearson described a data privacy incident as a hypothetical risk in a July 2019 report when its 2018 intrusion had already occurred [11], that Blackbaud's quarterly report omitted that a ransomware attacker had taken donor bank account data, which its staff had learned within days of the company saying otherwise [15], and that four companies whose systems the threat actor likely behind the SolarWinds Orion hack had accessed negligently minimized those incidents, with penalties from $990,000 to $4 million [21]. Two cases charged only controls: First American paid $487,616 over disclosure controls [10], and R.R. Donnelley paid $2,125,000 over disclosure and internal accounting controls, including alerts of unusual activity it did not assess and respond to in time [19]. The 10 settled public-company orders total $52,147,616 in penalties, $35 million of it from Altaba [8] [10] [11] [15] [19] [21] [23].
No order or complaint of this kind is dated after Flagstar's on December 16, 2024 [23] [2] [3] [1]. The SEC created a Cyber and Emerging Technologies Unit on February 20, 2025, and its list of priority areas still includes "regulated entities' compliance with cybersecurity rules and regulations" and "public issuer fraudulent disclosure relating to cybersecurity" [27]. In fiscal year 2026 the SEC filed 348 enforcement actions, and its annual results release named the M Holdings order among them [28].
Moraph's view
Moraph's view: two things changed at once. The SEC dropped the one case that tested how far internal controls law reaches into security programs, and it has brought no new disclosure case for nearly two years, while firm-side Regulation S-P and S-ID orders continue at a pace of about one a year. We read that as a narrower enforcement posture for public companies, not as a change in the rules, which still apply; a later commission could return to disclosure cases.
What the 2024 amendments add, and when
The amended Regulation S-P requires brokers, funds, registered advisers, funding portals and transfer agents to have a written incident response program, and to notify affected individuals "as soon as practicable, but not later than 30 days" after becoming aware of unauthorized access to sensitive customer information [30]. Covered institutions must also require their service providers to notify them within 72 hours of becoming aware of a breach [30]. The rule took effect on August 2, 2024 [30]. The SEC's compliance guide sets December 3, 2025 for larger entities and June 3, 2026 for smaller ones, 18 and 24 months after Federal Register publication [31]. Larger means, among others, advisers with $1.5 billion or more in assets under management and fund groups with $1 billion or more in net assets [30].
The SEC has treated the dates as fixed. It announced three compliance outreach events, scheduled according to each group's compliance deadline [35], its examination priorities for fiscal year 2026 named the amendments as a new rule to examine [33], and its fiscal year 2027 priorities list "operational resiliency, cybersecurity, and protection of customer information" [34]. A Federal Register search for SEC documents mentioning Regulation S-P since June 2024 returns 21 results on November 16, 2026, and none extends or postpones the compliance dates [32].
The case record shows how long the road from an incident to an order is: Voya's intrusion was in 2016 and its order in 2018 [9], the Cetera takeovers began in November 2017 and the order came in August 2021 [12], Robinhood's unauthorized access was in November 2021 and its order in January 2025 [24], and M Holdings' conduct ran to March 2024 with an order in November 2025 [25].
Moraph's view
Moraph's view: the first action charging the new notice duty is likely to follow an exam finding or an incident from 2026, and on the record's lags of roughly two to four years that points to 2028 or later. Firms should not read the absence of cases in 2026 and 2027 as a sign the notice rule is not being checked; examinations come first.
What to watch
- Any order citing the amended Rule 30(a) incident response or customer notice provisions, the first test of the 30-day clock [30].
- Whether the SEC brings another public-company cyber disclosure case, the first since December 2024 [23].
- The SEC enforcement division's annual results release for fiscal year 2027, which in 2026 listed the year's safeguards case by name [28].
What this means for you
- Broker-dealers and investment advisers: Test the controls the orders name, not only the written policy: multi-factor authentication on email at every branch or member firm, checks on phone password resets, and device disposal records [9] [12] [14] [25]. Regulation S-ID cases turned on whether the program was reviewed and updated and whether the board or senior management oversaw it [13] [26].
- Smaller advisers and funds: The June 3, 2026 compliance date for smaller entities has passed [31]; check that the incident response program, the 30-day notice procedure and service provider contracts with the 72-hour notice term are in place and documented, since examiners named the amendments as a priority [30] [33].
- Transfer agents: The amendments bring transfer agents under the safeguards rule for the first time [30], and the 2024 Equiniti order shows the SEC already charging a transfer agent over cyber losses under its own safeguarding rule [20].
- Public companies, including bank holding companies: The disclosure orders turned on gaps between what security staff knew and what filings said, and on whether incident information reached disclosure decision makers [15] [23] [19]; those controls remain required even with no new case since December 2024 [23].
Moraph predictions
Every prediction is Moraph's view, not a fact. Each has a date, a confidence level (70% means we expect to be wrong about three times in ten) and a test anyone can apply. We score them on this page when the date comes and never remove one. How we make and score predictions.
P1 By Confidence 75% Open
The SEC announces at least one new enforcement action charging a violation of Rule 30(a) of Regulation S-P or Rule 201 of Regulation S-ID, dated between November 17, 2026 and December 31, 2027.
How we will check: An SEC press release, administrative summary, administrative order or litigation release dated from November 17, 2026 to December 31, 2027 states that an order found, or a complaint alleged, a violation of 17 CFR 248.30(a) or 248.201. Right if at least one exists.
Basis: Orders charging one or both rules are dated January 13, 2025, November 25, 2025 and October 23, 2026 [24] [25] [26]; the SEC's cyber unit lists regulated entities' compliance with cybersecurity rules as a priority area [27].
P2 By Confidence 80% Open
No SEC order or complaint dated on or before December 31, 2027 charges a violation of the customer notification or incident response program requirements added to Regulation S-P in 2024.
How we will check: Search SEC press releases, administrative summaries and litigation releases dated to December 31, 2027 for an order or complaint citing 17 CFR 248.30(a)(3) or (a)(4), or describing a failure to notify affected individuals under the amended rule. Right if none exists.
Basis: Compliance dates were December 3, 2025 and June 3, 2026 [31]; past safeguards orders came about two to four years after the incident or conduct [9] [12] [24] [25].
P3 By Confidence 70% Open
The SEC brings no new enforcement action against a public company charging misleading cybersecurity incident disclosures or cyber-related disclosure controls failures, dated between November 17, 2026 and December 31, 2027.
How we will check: No SEC press release, administrative summary or litigation release dated from November 17, 2026 to December 31, 2027 announces an order or complaint against a public company over cybersecurity incident or risk disclosures or related disclosure or internal controls. Wrong if one does.
Basis: The last such order found is dated December 16, 2024 [23]; the SEC dismissed the SolarWinds case with prejudice on November 20, 2025 [17].
P4 By Confidence 80% Open
By December 31, 2028, the SEC has not published a proposed or final rule that removes the 30-day customer notification requirement from Regulation S-P.
How we will check: Search the Federal Register and the SEC rulemaking pages for an SEC release dated on or before December 31, 2028 that would delete or replace the 30-day notice in 17 CFR 248.30(a)(4). Right if none exists.
Basis: As checked on November 16, 2026, no Federal Register document changes the amendments or their compliance dates [32]; the SEC held compliance outreach for each group of firms and named the amendments in its 2026 exam priorities [35] [33].
Facts on this page link to their sources. Text marked "Moraph's view", and every prediction, is our own analysis, not a fact or advice. Methodology.
Spotted an error? Tell us and we will check it and correct the piece where needed.