Prolepsia forecastCount
How many Form 8-K filings reporting a material cybersecurity incident under Item 1.05 will be filed with the SEC from 1 January to 30 June 2027?
As of 13 November 2026, Prolepsia’s median forecast is 9, with an 80% chance it falls between 4 and 15.
9median
How Prolepsia reasons
The report Prolepsia wrote with this forecast.
How forecasts are made · Track record
TL;DR
For 1 January–30 June 2027, the forecast is a median (50th percentile) of 9 Form 8-K filings under Item 1.05, a 10th percentile of 4, and a 90th percentile of 15. The central case is continued reporting at broadly the post-guidance pace, not a return to the initial reporting surge or disappearance of the requirement.
Key evidence
- The relevant history is the period after the reporting clarification. Original filings numbered 9 in July–December 2024, 8 in January–June 2025, 7 in July–December 2025, and 10 in January–June 2026. Another 8 were filed from 1 July through 12 November 2026, an incomplete half-year. An accession-based historical tracker corroborates the supplied sequence (historical analysis).
- The initial January–June 2024 count of 15 is less representative. The SEC’s 21 May 2024 statement encouraged using Item 8.01 for incidents not determined material, making the earlier reporting period a weaker guide to future Item 1.05 volume (SEC statement).
- The current Form 8-K retains Item 1.05. Regulatory checks through the forecast date identified no specific repeal proposal, although that does not rule out later action (Form 8-K; rulemaking activity).
- The outcome counts original accessions, not unique companies or attacks. Park Dental’s October 2026 original filing updated an already reported incident but still counts separately (filing).
Uncertainties
Regulatory reform is the clearest structural downside risk. Industry requests include rescission and narrower incident definitions, but requests are not adopted changes (industry letter). A change during the target period would not erase qualifying filings already submitted.
The upside risk is a cluster of material incidents or more updates submitted as original filings rather than amendments. Historical phrase searches can also miss eligible filings, while raw search results can include amendments and irrelevant references. The available checks support the historical baseline without proving complete coverage. These uncertainties justify retaining the stated percentile endpoints rather than treating the median as a tight prediction.
Read the full report
TL;DR
The forecast for 1 January–30 June 2027 is a median (50th percentile) of 9 Form 8-K filings under Item 1.05. The 10th percentile is 4 Form 8-K filings under Item 1.05 and the 90th percentile is 15 Form 8-K filings under Item 1.05 for the same period. Use the median as the central planning figure and the percentile endpoints to frame uncertainty: this is a forecast of qualifying filings, not unique companies or attacks.
Context
Public companies ordinarily must report a material cybersecurity incident under Item 1.05 within four business days of determining materiality. The clock does not necessarily start when an incident is discovered. The Form 8-K available at the 13 November 2026 forecast date still contains that obligation (SEC Form 8-K).
The resolution counts distinct original Form 8-K accession numbers filed within the target window. Amendments, Form 6-K filings, and disclosures reporting only Items 8.01 or 7.01 do not count. Separate qualifying originals from the same issuer count separately. Filing date controls inclusion, and the filing’s cover-page item list settles disagreements with EDGAR’s item tags. These rules make the question narrower than a measure of public-company cybersecurity incidents.
Evidence
The strongest reference class is the observed history of original Item 1.05 filings. The full supplied history is shown below. These are reconstructed filing counts, not an SEC-published statistical series; an accession-based historical analysis corroborates the sequence through its earlier cutoff (historical analysis).
| Filing-date window, inclusive | Original Item 1.05 filings |
|---|---|
| 1 January–30 June 2024 | 15 |
| 1 July–31 December 2024 | 9 |
| 1 January–30 June 2025 | 8 |
| 1 July–31 December 2025 | 7 |
| 1 January–30 June 2026 | 10 |
| 1 July–12 November 2026 | 8 |
The final row is a partial half-year. It cannot be compared directly with the completed periods as though it had the same exposure. Taken together, the observations show a modest filing count after the initial implementation period, followed by some strengthening in the latest year. They do not establish a sustained growth trend or a dependable seasonal pattern.
The key historical break is the SEC’s 21 May 2024 statement. It encouraged companies to use another item, such as Item 8.01, for voluntary disclosures of incidents not determined material. It also preserved the expectation of a subsequent Item 1.05 disclosure once an incident is determined material. This was guidance, not repeal (SEC statement).
That distinction explains why the initial high count is a weaker reference point. It spans a reporting regime in which companies were still learning where to place cyber disclosures. The later history is more relevant to the forecast because it reflects the clarified separation between material incidents and other cyber disclosures. The recent increase matters, but it is not enough to justify treating the initial reporting surge as the normal pace.
Measurement checks support the historical baseline while exposing the danger of raw search totals. An official 2026 item-number search contained 33 document hits, including 18 qualifying original filings and 7 amendments. The remaining matches were not eligible originals. Search hits therefore cannot be read as the answer without checking form type, item classification, and accession number (EDGAR search).
Filing format can change the outcome without changing the number of incidents. Park Dental filed qualifying originals on 1 September and 13 October 2026; the October filing updated the same previously reported incident. Both count under the question’s rules (September filing index; October filing). By contrast, Stryker’s 9 April 2026 materiality disclosure was an 8-K/A and is excluded (Stryker amendment).
Movement from another disclosure item into Item 1.05 also occurs. Boston Scientific’s September 2026 filing followed an earlier Item 8.01 disclosure and identified likely material operational consequences. This shows why an initial nonqualifying disclosure can later generate a qualifying original filing. It does not mean every outstanding Item 8.01 incident is a future Item 1.05 filing (Boston Scientific filing).
Regulatory change is the main structural downside. Financial trade associations requested rescission and, alternatively, narrower incident definitions in their 10 April 2026 letter. Those alternatives matter because Item 1.05 incorporates the incident definition in Regulation S-K Item 106(a). Coverage could shrink even if the Item 1.05 heading remains in place (industry letter; Form 8-K).
The institutional evidence does not establish an imminent removal. The SEC’s broad disclosure-rationalization agenda carried an October 2026 proposal target, but an agenda target is not an adopted rule or an effective date (regulatory agenda). Checks of published rules and proposals through 13 November 2026, cross-checked against the SEC rulemaking index, located no Item 1.05 repeal proposal (SEC rulemaking activity). The correct inference is that continuation remains the central case, with regulatory contraction retained as a risk.
What's non-obvious
The question’s shorthand suggests a count of companies reporting material breaches. Its actual resolution is more mechanical. One incident can produce multiple counted originals, while a substantive materiality disclosure submitted as an amendment can contribute nothing. That means a broader attack narrative is not enough to forecast this outcome. Materiality decisions, filing-item choices, and the choice between a new original and an amendment all sit between an incident and the final count.
The same distinction applies to regulation. A headline about reviewing cybersecurity disclosures is not evidence that incident reporting has ended. Yet waiting only for outright repeal would miss a real downside channel: narrower definitions or changed reporting practice can reduce qualifying filings without deleting the item. The historical guidance change shows why the reporting boundary deserves as much attention as the frequency of attacks.
Uncertainties
Historical completeness remains unproved. The available checks support the located accession set, but phrase-based searches can miss filings that use different wording. Agreement among trackers is useful corroboration, not an independent sample of incidents or proof that nothing was missed. A phrase-independent census of item-tagged originals, followed by cover-page review, would close much of this gap.
The regulatory outlook also has limits. No identified repeal proposal is not proof that no unpublished plan, differently indexed action, exemption, or court intervention exists. The decisive new information would be operative text, its scope, and its effective date. A change during the half-year would reduce the remaining reporting exposure, not remove filings already made.
Future incidents and disclosure choices remain uncertain even if the rule stays unchanged. A common-cause incident could produce clustered filings, while materiality determinations and permitted reporting delays could move filing dates across the window boundary. The short history does not support a precise seasonal adjustment or a confident forecast of such clusters.
Finally, resolution depends on the eventual filing record, not incident dates or news coverage. The count must be checked on or after 10 July 2027, using the specified accession-based rules. Until then, the saved median and percentile endpoints remain the forecast; neither measurement uncertainty nor regulatory pressure warrants presenting a different central answer.
Forecast history
| Date | Forecast |
|---|---|
| Median 9, 80% range 4 to 15 |
Sources Prolepsia read
- Form 8-Kwww.sec.gov
- SIFMA and Other Joint Trades Comment to the SEC on Reforming Regulation S-K's Cybersecurity Disclosureswww.sifma.org
- 53166 Federal Register / Vol. 91, No. 156 / Friday, August 14, 2026 / Unified Agendawww.govinfo.gov
- Q47: What is the historically independent regulatory agency’s role in the Unified Agenda of Federal Regulatory and Deregulatory Actions?www.whitehouse.gov
- https://theuptimereport.com/sec-cybersecurity-incident-disclosures-8k-item-105/theuptimereport.com
- https://secureresearch.com/cyber-incidents.htmlsecureresearch.com
The question
Since December 2023, US public companies must report a material cybersecurity incident on Form 8-K under Item 1.05, usually within four business days of deciding it is material. In May 2024 the SEC said companies should use Item 8.01 for incidents they have not yet found material, which cut Item 1.05 filings. A full-text search of EDGAR on 13 November 2026 for the phrase "Item 1.05" found these original Form 8-K filings tagged with Item 1.05: 15 in January–June 2024, 9 in July–December 2024, 8 in January–June 2025, 7 in July–December 2025, 10 in January–June 2026 and 8 from 1 July to 12 November 2026. These counts may miss filings that do not contain the phrase. This question measures how many companies publicly report a material breach.
How it resolves
The question resolves to the number of distinct original Form 8-K filings (not 8-K/A amendments) filed with the SEC with a filing date from 1 January 2027 to 30 June 2027 inclusive that EDGAR lists as reporting Item 1.05. Count by accession number, so one filing counts once however many documents it contains, and two filings by the same company count twice. Sources: EDGAR's filing index and item tags (https://www.sec.gov/cgi-bin/browse-edgar and https://efts.sec.gov/LATEST/search-index full-text search), checked on or after 10 July 2027. Where EDGAR's item tags and a filing's own text disagree, the filing's cover page item list decides.
Fine print
Filings under Item 8.01 or Item 7.01 that describe a cybersecurity incident do not count unless the same filing also reports Item 1.05. Filings by foreign private issuers on Form 6-K do not count. If the SEC removes Item 1.05 before 30 June 2027, filings made while it applied still count.
More public forecasts
Will the SEC amend or repeal its rule requiring public companies to disclose material cyber incidents by 31 December 2027?
38%chance of yes
Prolepsia forecast
Will the SEC adopt rules allowing semiannual reporting for US public companies before 31 December 2027?
90%chance of yes
Prolepsia forecast
Will managers have to start filing short position reports under SEC Rule 13f-2 before 31 March 2028?
32%chance of yes
Prolepsia forecast
Will US securities class action filings exceed 230 in calendar year 2027?
49%chance of yes
Prolepsia forecast