Prolepsia forecastYes / no
Will the SEC amend or repeal its rule requiring public companies to disclose material cyber incidents by 31 December 2027?
As of 17 November 2026, Prolepsia puts the chance of yes at 38%.
38%chance of yes
How Prolepsia reasons
The report Prolepsia wrote with this forecast.
How forecasts are made · Track record
TL;DR
The forecast is 37.9% Yes and 62.1% No for a qualifying SEC final rule adopted between November 17, 2026, and December 31, 2027. No is favored because evidence of willingness to reform disclosure is stronger than evidence of an incident-reporting amendment ready for timely adoption.
Key evidence
- The legal baseline remains intact. Published Form 8-K retains the general requirement to disclose a material cybersecurity incident within four business days after the company determines it is material—not after discovering the intrusion.
- Industry has made a specific request. The May 22, 2025 petition seeks rescission of Item 1.05 and corresponding Form 6-K requirements. This establishes organized demand, not SEC agreement.
- A plausible reform vehicle exists. Chairman Atkins launched a comprehensive Regulation S-K review on January 13, 2026. His November 13 statement reports progress toward business, risk, and governance recommendations, but does not explicitly commit to incident-reporting changes.
- The visible pipeline remains the main constraint. The 2026 rulemaking index, containing actions through November 13, identifies no qualifying incident-amendment proposal. Historical completed rulemakings show that proposal-to-adoption can take much of the remaining window, although those examples do not establish a representative completion rate.
Uncertainties
The strongest route to Yes is a focused amendment included in a broader disclosure package. Extending the reporting deadline, expanding meaningful delay exceptions, narrowing covered incidents, or reducing required information could qualify without repealing Item 1.05. A substantive change to the incident definition incorporated from Item 106(a) is another route under the existing rule.
The strongest route to No is reform that stops at annual governance disclosures, guidance, or a proposal. None meets the resolution criteria. Internal drafting is unknown, so the absence of a published proposal does not establish inactivity. The decisive evidence will be the scope and timing of an actual proposal, followed by formal final-rule adoption—not its effective date.
Read the full report
TL;DR
The forecast is 37.9% Yes and 62.1% No for SEC adoption of a qualifying final rule between November 17, 2026, and December 31, 2027. No is the leading outcome because broad disclosure reform has not yet produced a verified incident-reporting amendment proposal. For planning, treat the current obligations as the baseline and watch for binding changes to incident definitions, deadlines, exemptions, or required information rather than announcements of reform.
Context
The SEC adopted its cybersecurity disclosure rule on July 26, 2023. It created mandatory reporting of material cybersecurity incidents under Form 8-K Item 1.05, related requirements for foreign private issuers under Form 6-K, and broader risk-management and governance disclosures under Regulation S-K Item 106. The domestic incident-reporting requirement generally runs for four business days after a company determines that an incident is material, not after discovery; the materiality determination must be made without unreasonable delay (final rule).
The question concerns a substantive final rule, not a change in regulatory tone. A significant amendment to incident-reporting scope, timing, or content qualifies, even if reporting remains mandatory. A proposal, guidance, enforcement retreat, or governance-only reform does not. Formal adoption by December 31, 2027, is decisive; a later effective date does not disqualify an otherwise qualifying rule.
Evidence
The historical backbone is the time needed to turn a proposal into a final rule. The available comparisons cover several completed disclosure reforms and a rollback. They show that timely completion is feasible, but far from automatic.
| Completed rulemaking | Proposal date | Adoption date | Calendar days |
|---|---|---|---|
| Disclosure Update and Simplification | July 13, 2016 | August 17, 2018 | 765 |
| Regulation S-K Items 101/103/105 modernization | August 8, 2019 | August 26, 2020 | 384 |
| MD&A simplification | January 30, 2020 | November 19, 2020 | 294 |
| Proxy-voting-advice rollback | November 17, 2021 | July 13, 2022 | 238 |
| Original cybersecurity disclosure rule | March 9, 2022 | July 26, 2023 | 504 |
These are selected completed actions, not a representative sample of all proposals or petitions. They cannot establish an adoption base rate because they leave out stalled and abandoned efforts. Their useful message is narrower: an early proposal leaves room for ordinary rulemaking, while a proposal late in the forecast window creates substantial deadline risk. A focused relaxation also need not take as long as creating the original framework.
The current public record places this issue before the proposal stage, at least visibly. The SEC’s 2026 rulemaking index, containing actions through November 13, identifies no qualifying incident-reporting amendment proposal. The published Form 8-K still contains the four-business-day requirement. Together, these facts support continuity as the baseline. They do not reveal whether staff has drafted unpublished changes.
Pressure for change is concrete. The May 22, 2025 financial-industry petition explicitly asks the SEC to rescind Item 1.05 and the corresponding Form 6-K requirements. The associations renewed their request in April 2026, including alternatives to outright rescission. This matters because leadership has specific policy options to consider, rather than only a general complaint about compliance burdens. But advocacy establishes demand, not the merits of every claimed harm or the agency’s willingness to act.
There is also a credible vehicle. Chairman Atkins directed a comprehensive Regulation S-K review on January 13, 2026. The regulatory agenda lists “Rationalization of Disclosure Practices,” with an October 2026 proposal target and no legal deadline. Its description does not explicitly promise cybersecurity incident changes, and the agenda reflects an earlier planning vintage rather than a current adoption commitment (official agenda).
The strongest recent leadership signal is Atkins’s November 13, 2026 statement. It accompanies executive-compensation reform and says staff is progressing toward recommendations on business, risk, and governance disclosures. That is evidence that the wider program is moving. It is not an explicit commitment to change Item 1.05 or Form 6-K. The distinction keeps broader deregulatory momentum from being mistaken for a near-final incident rule.
Commissioner Uyeda’s statements illustrate the same split. His July 26, 2023 dissent criticized incident-impact disclosures and constrained disclosure delays. Those concerns map directly onto amendments that could qualify. His more recent January 26, 2026 remarks, however, specifically emphasized simplifying Item 106 policy and governance narratives. That reform could reduce cybersecurity disclosure burdens without changing mandatory incident reporting at all.
Institutional capacity does not point in only one direction. Peirce’s departure effective October 2, 2026 means her earlier opposition cannot be treated as a current vote. Yet the September 30 quorum amendment permits action when fewer than three commissioners remain. Vacancies therefore are not an automatic legal blockade. Staffing losses and competing rulemaking demands create execution risks, but do not establish paralysis (financial audit and management assessment).
The wider policy environment supplies another supporting signal. The administration’s March 2026 Cyber Strategy calls for reducing cybersecurity regulatory burdens. Government research also documents potentially duplicative reporting requirements across sectors (GAO review). These facts strengthen the case for harmonization. They do not establish that public investor disclosure will be changed, or that a qualifying SEC rule will finish by the deadline.
What's non-obvious
The practical choice is not simply repeal versus no repeal. Item 1.05 incorporates the cybersecurity-incident definition in Item 106(a). A substantive narrowing of that definition could change mandatory incident reporting even if Item 1.05 remains visibly intact (existing rule). Significant changes to deadlines, delay exceptions, or required information offer other qualifying paths. This is why the prospect of complete rescission understates the range of routes to Yes.
The reverse is equally important. A large cybersecurity disclosure reform can still resolve No if it changes only annual governance narratives. Likewise, a deregulatory speech or a proposed rule can attract attention while leaving the legal reporting obligation unchanged. The analysis therefore turns on two separate questions: whether the reform reaches incident reporting, and whether the SEC adopts the final text on time. Favorable leadership preferences answer neither by themselves.
Uncertainties
The largest gap is the contents of the next disclosure package. Public statements establish a broad review, but not an incident-specific drafting instruction or adoption schedule. A formal proposal naming Item 1.05, Form 6-K, or the incorporated incident definition would close much of that scope gap. Its actual regulatory text would matter more than its title.
Timing is the next gap. An early proposal would leave more room for comments, analysis, revisions, and adoption. A later proposal would compress those steps. The historical examples show what has been possible, but do not provide a reliable completion frequency for this particular project.
The public record also cannot settle the state of internal work. No identified proposal is not proof of no drafting. Conversely, a petition and sympathetic leadership do not establish that a proposal is imminent. Evidence of staff work specifically directed at incident obligations would help distinguish an active project from an available policy option.
Finally, the substance of any final amendment must cross the resolution threshold. Minor procedural changes, narrow exceptions, and interpretive clarifications are insufficient. A meaningful change to binding incident obligations qualifies, including one embedded in a broader package. The saved forecast reflects both realities: there are credible routes to substantive amendment, but timely final adoption remains the central obstacle.
Forecast history
| Date | Forecast |
|---|---|
| 38% chance of yes |
Sources Prolepsia read
- SEC.gov | Cybersecurity Risk Management, Strategy, Governance, and Incident Disclosurewww.sec.gov
- Reforming Regulation S-K's Cybersecurity Disclosures (Joint Trades) - SIFMAwww.sifma.org
- Federal Register, Volume 91 Issue 156 (Friday, August 14, 2026)www.govinfo.gov
- GAO-27-108840, Financial Audit: Securities and Exchange Commission’s FY 2026 and 2025 Financial Statementswww.gao.gov
- March 2026 Cyber Strategywww.whitehouse.gov
- SEC Proposes Significant Amendments to Cybersecurity Disclosure Rules — Merrick & Stantonwww.merrickandstanton.com
- Federal Register :: Registered Offering Reformwww.federalregister.gov
- www.reginfo.govwww.reginfo.gov
The question
This question asks whether the U.S. Securities and Exchange Commission (SEC) will formally adopt an amendment or repeal of its mandatory material cybersecurity incident disclosure requirements between November 17, 2026, and December 31, 2027, inclusive. On July 26, 2023, the SEC adopted its Cybersecurity Risk Management, Strategy, Governance, and Incident Disclosure rule (Release Nos. 33-11216 and 34-97989). The rule introduced Item 1.05 of Form 8-K, requiring public companies subject to the provision to disclose cybersecurity incidents they determine to be material, generally within four business days of that determination. Companies must disclose material aspects of the incident's nature, scope, timing, and actual or reasonably likely impact. The rule also established related disclosure requirements for foreign private issuers under Form 6-K and cybersecurity risk management and governance disclosures under Regulation S-K Item 106. The incident reporting requirements generally became applicable beginning December 18, 2023. ([sec.gov](https://www.sec.gov/rules-regulations/2023/07/s7-09-22)) The requirements have attracted criticism from industry groups concerned about compliance costs, premature disclosure of sensitive cybersecurity information, and potential interference with incident response. On May 22, 2025, a coalition of financial industry associations submitted a formal petition to the SEC requesting rescission of Form 8-K Item 1.05 and the parallel Form 6-K cybersecurity incident reporting requirements. This petition provides a concrete basis for forecasting potential regulatory changes. ([sec.gov](https://www.sec.gov/files/rules/petitions/2025/petn4-856.pdf)) As of November 17, 2026, the available information does not establish that the SEC has adopted a final rule rescinding or materially amending these incident disclosure requirements. The question concerns whether the SEC will take such formal action by the end of 2027, rather than whether it will merely consider, discuss, or propose changes. For this forecast, an amendment means a substantive change to the mandatory cybersecurity incident reporting obligations established by the 2023 rule. A repeal means the elimination of those obligations, either in full or for a substantial category of previously covered registrants or incidents. The question focuses on material cybersecurity incident reporting, not the broader cybersecurity governance and risk management disclosure framework.
How it resolves
The question resolves YES if, between November 17, 2026, and December 31, 2027, inclusive, the SEC formally adopts a final rule that substantively amends, rescinds, or replaces the mandatory material cybersecurity incident disclosure requirements established by its July 26, 2023 Cybersecurity Risk Management, Strategy, Governance, and Incident Disclosure rule. Qualifying changes include eliminating Form 8-K Item 1.05; removing or substantially narrowing the corresponding Form 6-K incident reporting requirements; extending the general reporting deadline beyond four business days; materially changing the criteria governing which cybersecurity incidents must be disclosed; significantly expanding exemptions or permissible disclosure delays; reducing the substantive information companies must report; or otherwise materially altering the scope, timing, or content of mandatory material cybersecurity incident disclosures. A final rule replacing Item 1.05 with a different mandatory incident reporting framework also qualifies if it materially changes the existing reporting obligations. An amendment that strengthens or expands the existing incident disclosure requirements qualifies, provided it substantively changes the obligations rather than merely clarifying their interpretation. The question resolves NO if the SEC has not formally adopted any qualifying final rule by December 31, 2027. In particular, it resolves NO if the SEC only publishes a proposed rule, requests public comments, announces an intention to revise or repeal the requirements, includes the issue on its regulatory agenda, or receives or grants consideration to a rulemaking petition without adopting a qualifying final rule. The question also resolves NO if the SEC issues only interpretive guidance, staff statements, enforcement policy changes, technical corrections, or administrative adjustments that do not substantively modify the legally binding incident disclosure obligations. Changes limited to Regulation S-K Item 106 concerning general cybersecurity risk management, strategy, and governance disclosures do not qualify unless they also substantively affect mandatory material cybersecurity incident reporting. The decisive event is formal adoption of a qualifying final rule by the SEC, rather than the rule's effective date or compliance date. A final rule adopted by December 31, 2027, qualifies even if its effective date falls in 2028 or later. A rule proposed by the deadline but adopted afterward does not qualify. The primary resolution sources will be the SEC's official final rule releases and the Federal Register. The SEC's official announcement and adopting release will establish the adoption date, while the Federal Register publication and accompanying regulatory text will establish the substance of the changes. If the sources differ on timing, the formal SEC adoption date documented in the final adopting release will control. The assessment will be made once the SEC's official records and Federal Register publications covering actions through December 31, 2027, are available. If a final rule was adopted by the deadline but published afterward, it will still count. If authoritative records are temporarily unavailable, resolution will be deferred until they can be examined. The question will be annulled only if an extraordinary circumstance makes it permanently impossible to determine whether the SEC adopted a qualifying rule by the deadline.
Fine print
The deadline is December 31, 2027, using the calendar date in Washington, D.C. The forecast begins on November 17, 2026. Amendments or repeals adopted before the start date do not count as new qualifying actions. The SEC must itself adopt the qualifying rule. A court decision invalidating or vacating the 2023 rule, congressional legislation overriding it, or an executive action affecting its implementation does not independently qualify as an SEC amendment or repeal. However, a subsequent SEC final rule adopted within the forecast window in response to such an event can qualify if it substantively changes the incident reporting requirements. A temporary SEC enforcement suspension or decision not to pursue violations does not qualify unless implemented through a formally adopted rule that substantively changes the underlying legal requirements. A change affecting only a very narrow group of registrants, an isolated reporting circumstance, or a minor procedural detail will not qualify unless it materially alters the cybersecurity incident disclosure framework. By contrast, a significant change to reporting deadlines, disclosure thresholds, exemptions, or required information qualifies even if Item 1.05 remains in force. The question does not require the SEC to eliminate incident disclosure obligations entirely. Adoption of a substantive amendment is sufficient for YES, regardless of whether the amendment makes disclosure requirements more or less stringent. The forecast concerns final regulatory action, not whether the resulting policy improves cybersecurity, investor protection, or corporate compliance.
More public forecasts
Will the SEC adopt rules allowing semiannual reporting for US public companies before 31 December 2027?
90%chance of yes
Prolepsia forecast
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?
9median
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 the EU AI Act general-purpose AI rules lead to a formal fine against any AI company before 31 December 2028?
75%chance of yes
Prolepsia forecast
Will global cyber insurance premiums exceed $20 billion in 2027, as estimated by Munich Re?
10%chance of yes
Prolepsia forecast
Will US cyber insurance prices fall in the fourth quarter of 2027, as reported by Marsh's Global Insurance Market Index?
39%chance of yes
Prolepsia forecast