SEC cyber incident 8-Ks, 2023 to 2026: few Item 1.05 reports, more voluntary ones

We counted every Form 8-K filed under Item 1.05 and screened voluntary Item 8.01 incident reports to see how public companies disclose cyber incidents, quarter by quarter and by industry.

What the rule asks, and the staff statement that changed practice

The SEC adopted its cybersecurity disclosure rules in Release 33-11216, effective September 5, 2023 [4]. For incidents, the rule added Item 1.05 to Form 8-K: all registrants other than smaller reporting companies had to comply from December 18, 2023, and smaller reporting companies from June 15, 2024 [4]. The current Form 8-K, revision SEC 873 (02-25), requires a registrant that experiences a cybersecurity incident it determines to be material to describe the material aspects of its nature, scope and timing and its material or reasonably likely material impact, within four business days of that determination [5]. The materiality determination must be made without unreasonable delay after discovery, and the U.S. Attorney General can authorize a delay for national security or public safety [5].

On May 21, 2024 the Director of the Division of Corporation Finance issued a statement saying Item 1.05 is for incidents the registrant has determined to be material, and encouraging companies that want to disclose other incidents, or incidents not yet assessed, to use a different item, such as Item 8.01, because disclosing immaterial or unassessed incidents under Item 1.05 could confuse investors [6]. Item 8.01, Other Events, lets a registrant disclose at its option any event it deems of importance to security holders [5]. The statement also said that a company that first discloses under Item 8.01 and later determines the incident is material should file an Item 1.05 report within four business days of that determination [6].

That gives two public series to count: Item 1.05 reports, which are mandatory and by definition material, and voluntary Item 8.01 reports about incidents [5] [6]. This report counts both from EDGAR's own full-text search, quarter by quarter from December 18, 2023 to November 15, 2026.

Data and method

Source: the EDGAR full-text search service, which covers filings submitted electronically since 2001, including exhibits, and supports exact phrases in quotation marks [3]. We called its search API (https://efts.sec.gov/LATEST/search-index) on November 16, 2026, 100 results per page, with the date range December 18, 2023 to November 15, 2026 and forms=8-K, which also returns 8-K/A amendments [1] [2]. Each result is one document; we grouped documents into filings by accession number (the adsh field) and used the items field, which lists the Form 8-K items the filer tagged, and the sics field, the filer's SIC code [1].

  • Item 1.05 series: the queries q="Item 1.05" and q="1.05", for example https://efts.sec.gov/LATEST/search-index?q=%22Item%201.05%22&forms=8-K&dateRange=custom&startdt=2023-12-18&enddt=2026-11-15 [1]. Every filing whose items field includes 1.05 was counted; both queries returned the same 85 filings [1]. Originals are form 8-K and amendments form 8-K/A in the form field [1].
  • Item 8.01 series: the query q="cybersecurity incident" with the same dates and form [2]. We kept filings whose items field includes 8.01 and not 1.05 and in which the phrase appears in the main 8-K document rather than an exhibit, which gave 81 candidates [2]. We then read each candidate's main document on sec.gov and kept it only if the text describes a cybersecurity incident that the filer or a provider serving it actually experienced; 26 that used the phrase only in general risk language, mostly forward-looking statement warnings in merger, financing and earnings filings, or without describing an incident affecting the filer, were dropped, leaving 55 [2]. Of the 55, 5 originals are follow-ups that mention an earlier incident while reporting litigation, a settlement or recovered funds; without them the count is 50 [2].
  • Quarters are calendar quarters of the filing date. Industry is the SIC code on each company's first counted filing, grouped by us into ranges of the SEC's SIC code list: 6000 to 6799 covers its banking, credit, securities, insurance and real estate codes, from 6021 national commercial banks to 6799 investors not elsewhere classified [7].

Limits. The 8.01 series is a lower bound: it misses filings that use other words (the query q="cyber incident" found 9 more candidate filings we did not screen) or put the description only in an exhibit [2]. The screening is a reading of each filing's text, not a legal judgment, and filings near the line could reasonably be classed either way. Foreign private issuers report on Form 6-K and are not counted [4]. The SEC asks automated users to declare a User-Agent and to stay under 10 requests a second [10]; our requests to the search API and for the filing documents did both.

Material incident reports: a short spike, then a steady trickle

Form 8-K filings tagged Item 1.05 (material incidents) and screened Item 8.01 cyber incident filings (voluntary), by quarter filed [1] [2]
QuarterMaterial incident reports: originals (amendments)Voluntary incident reports: originals (amendments)
Q4 2023 (from December 18)2 (1) [1]0 [2]
Q1 20249 (6) [1]2 (3) [2]
Q2 20246 (4) [1]6 (1) [2]
Q3 20246 (4) [1]6 [2]
Q4 20243 [1]7 [2]
Q1 20252 (2) [1]1 [2]
Q2 20256 (1) [1]3 [2]
Q3 20253 [1]4 [2]
Q4 20254 (1) [1]2 [2]
Q1 20263 (1) [1]2 [2]
Q2 20267 (2) [1]6 [2]
Q3 20267 (4) [1]10 [2]
Q4 2026 (to November 15)1 [1]2 [2]
Total59 (26) [1]51 (4) [2]

From December 18, 2023 to November 15, 2026, EDGAR shows 85 filings tagged Item 1.05: 59 original reports and 26 amendments, from 58 companies [1]. By calendar year there were 24 original reports in 2024, 15 in 2025 and 18 in 2026 through November 15 [1]. The busiest quarter was the first full one, Q1 2024, with 9 originals [1].

The staff statement of May 21, 2024 marks a clear break [6]. In the 155 days from December 18, 2023 to May 20, 2024 there were 17 original Item 1.05 reports, about 3.3 every 30 days; in the 909 days from May 21, 2024 there were 42, about 1.4 every 30 days [1]. The drop came even though smaller reporting companies became subject to the item on June 15, 2024 [4].

The totals are far below what the SEC itself planned for. The adopting release estimated 200 Form 8-K responses a year under Item 1.05 for its paperwork burden calculation [4], against 24 original reports filed in 2024 [1].

Amendments are common. Of the 57 companies that filed an original Item 1.05 report, 19 later filed at least one 8-K/A under the item [1], as the form's instruction requires when information was not determined or unavailable at the first filing [5].

Moraph's view

Moraph's view: the early spike was partly a learning curve. Once the SEC staff said Item 1.05 was for incidents already judged material, companies stopped using it as a precaution. The small rise in mid-2026 came with no change in the form or the staff guidance, so we read it as more serious incidents rather than a change in practice.

Voluntary reports: the other channel now carries as much as the mandatory one

We found 55 Item 8.01 filings that describe a cybersecurity incident the filer or a provider experienced, from 48 companies: 51 originals and 4 amendments [2]. Only 3 of the originals came before May 21, 2024; 48 came after, about 1.6 every 30 days [2]. Since the statement, original voluntary 8.01 reports have at least matched original Item 1.05 reports: 48 to 42, or 43 to 42 without the 5 follow-ups [1] [2]. In 2026 through November 15 there were 20 original 8.01 incident reports (18 without follow-ups) against 18 under Item 1.05 [1] [2].

The two series reach mostly different companies: 5 companies appear in both, and 101 companies appear in one or the other [1] [2]. Several 8.01 filings describe an incident at a provider rather than at the filer, which is how one outage at a shared service can surface in several filings in the same week [2].

Moraph's view

Moraph's view: for a reader of filings, an Item 8.01 incident report now means "something happened and we are telling you before deciding whether it is material," and an Item 1.05 report means "we have decided it is." Counting only Item 1.05 leaves out a voluntary channel about as large as the mandatory one.

Which industries file

Companies filing, by SIC code range of the company's first counted filing [1] [2] [7]
SIC code rangeCompanies with material incident reportsCompanies with voluntary incident reports
2000 to 3999 (manufacturing industries) [7]20 [1] [7]15 [2] [7]
6000 to 6799 (banking, credit, securities, insurance, real estate) [7]13 [1] [7]9 [2] [7]
7000 to 8999 (services, including software and health services) [7]13 [1] [7]11 [2] [7]
5200 to 5999 (retail) [7]5 [1] [7]7 [2] [7]
4000 to 4999 (transportation, communications, utilities) [7]4 [1] [7]4 [2] [7]
5000 to 5199 (wholesale) [7]2 [1] [7]1 [2] [7]
1000 to 1799 (mining) [7]1 [1] [7]1 [2] [7]
Total companies58 [1]48 [2]

No single industry dominates. Filers with SIC codes from 6000 to 6799 were 13 of the 58 Item 1.05 companies and 9 of the 48 Item 8.01 companies, 22 of the 101 companies across both series [1] [2] [7]. Within that range, the Item 1.05 filers include 4 companies coded 6022, state commercial banks, 5 in credit, finance services, brokerage and investment advice codes, 3 in insurance codes and 1 real estate investment trust [1] [7]. The Item 8.01 filers in the range include 3 bank and savings institution codes, 2 credit and finance codes and 4 insurance codes, among them accident and health insurance and hospital and medical service plans [2] [7]. Medical device makers (SIC 3841 to 3845) account for 6 Item 1.05 companies and 5 Item 8.01 companies [1] [2] [7].

Moraph's view

Moraph's view: nothing in these counts suggests that banks and insurers file more often than other industries, though we did not measure their share of all public companies. Their trade groups argue that public incident filings conflict with the confidential reporting they already owe regulators [8], and their filing pattern gives no sign that they treat the 8-K as the first notice of an incident.

Pressure to change the rule

On May 22, 2025 the American Bankers Association, the Bank Policy Institute, the Securities Industry and Financial Markets Association, the Independent Community Bankers of America and the Institute of International Bankers petitioned the SEC to rescind Item 1.05 and the matching Form 6-K requirement [8]. As checked on 16 November 2026, the SEC's petitions page lists it as File No. 4-856 with a link to comments received [9]; that page does not record Commission decisions, and we found no SEC proposal to change Item 1.05. As checked on the same date, the Form 8-K on sec.gov still contains Item 1.05 [5].

Moraph's view

Moraph's view: a proposal to narrow or remove Item 1.05 is plausible within two years, given the petition from the largest bank and securities trade groups, but a final change takes longer. Even if the item goes, voluntary reports are likely to continue, because a visible outage or customer data breach is public news anyway.

What to watch

  • Any SEC proposal on Item 1.05, its four-business-day clock or the definition of a cybersecurity incident, and the Commission's response to petition 4-856 [9].
  • Whether the mid-2026 rise in Item 1.05 originals, 14 in the second and third quarters [1], continues into 2027.
  • Amendment rates: an original report is often followed by an 8-K/A that fills in impact, as the form requires [5]; the follow-up is where investors learn the cost.
  • Clusters of voluntary incident filings that point to one provider [2], which show concentration risk in shared services more directly than any survey.

What this means for you

  • CISOs and general counsel at listed banks and insurers: Decide in advance which incidents go out under Item 8.01 and how they are escalated to a materiality decision; the SEC staff expects an Item 1.05 report within four business days if a disclosed incident is later judged material [6]. Record the date and basis of each materiality decision, since the clock runs from it [5].
  • Disclosure committees: Plan for the amendment: 19 of 57 companies that filed an original Item 1.05 report later amended it [1], as the form requires when facts were not known at first [5]. Assign an owner for the follow-up before the first filing.
  • Third-party risk teams: Watch Item 8.01 filings by peers and providers. Several describe an incident at a shared provider rather than the filer [2], and the same outage can appear in many filings within days; a list of which public providers serve the institution makes these filings an early warning.
  • Boards and audit committees: Do not read a low count of Item 1.05 filings as a low rate of serious incidents: over the period studied, voluntary Item 8.01 incident reports were about as common as Item 1.05 reports [1] [2]. Ask management for both kinds when benchmarking against peers.

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.

  1. P1 By Confidence 85% Open

    Fewer than 30 original Form 8-K reports (form 8-K, not 8-K/A) tagged Item 1.05 are filed with a filing date in calendar year 2027.

    How we will check: Run the EDGAR full-text search API query q="Item 1.05" with forms=8-K and dates 2027-01-01 to 2027-12-31 in January 2028, group results by accession number, and count filings whose form is 8-K and whose items field includes 1.05. Right if fewer than 30.

    Basis: Original Item 1.05 reports numbered 24 in 2024, 15 in 2025 and 18 in 2026 through November 15 [1].

  2. P2 By Confidence 55% Open

    The SEC publishes a proposed rule that would rescind or amend Form 8-K Item 1.05 by December 31, 2027.

    How we will check: Search the SEC's proposed rules page and the Federal Register for a Commission proposing release, dated on or before December 31, 2027, whose text would remove Item 1.05 or change its trigger, deadline or content. Right if one exists.

    Basis: Five trade groups petitioned on May 22, 2025 to rescind Item 1.05 [8]; as checked on 16 November 2026 the SEC lists the petition as File No. 4-856 [9] and the Form 8-K still contains Item 1.05 [5].

  3. P3 By Confidence 80% Open

    Item 1.05 is still part of Form 8-K, with its four-business-day deadline after a materiality determination, on December 31, 2027.

    How we will check: On or after December 31, 2027, open the current Form 8-K on sec.gov (or 17 CFR 249.308 and its General Instructions in the eCFR). Right if Item 1.05 is present and still requires a report within four business days after the registrant determines it has had a material cybersecurity incident.

    Basis: As checked on 16 November 2026 the Form 8-K, revision SEC 873 (02-25), contains Item 1.05 with that deadline [5], and the rescission petition is listed as File No. 4-856 [9]; a final rule normally follows a proposal and comment period.

  4. P4 By Confidence 55% Open

    In calendar year 2027, screened Item 8.01 cyber incident filings (originals) are at least as many as original Item 1.05 filings.

    How we will check: In January 2028, repeat both counts in this report's Data and method section for filing dates 2027-01-01 to 2027-12-31, including the reading of each Item 8.01 candidate by the same rule (follow-ups on earlier incidents included). Right if the 8.01 originals count is equal to or greater than the Item 1.05 originals count.

    Basis: Since May 21, 2024 there have been 48 original 8.01 incident filings (43 without follow-ups on earlier incidents) against 42 original Item 1.05 reports, and 20 against 18 in 2026 through November 15, but 10 against 15 in 2025 [1] [2].

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.

  • SEC
  • Form 8-K
  • Item 1.05
  • Item 8.01
  • cyber incident disclosure
  • materiality
  • EDGAR