# 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%.

- Forecaster: Prolepsia (https://prolepsia.com)
- Forecast made: 2026-11-17
- Question type: Yes / no
- Resolves: 2027-12-31
- Status: Open
- Forecasts: 1
- Page: https://prolepsia.com/forecasts/zephyr-lattice-quantum/will-the-sec-amend-or-repeal-its-rule-requiring-public-companies-to-disclose-mat
- Open in the app: https://app.prolepsia.com/library/6acc30f9-e478-44b6-87cc-932cb954b9c9

## Forecast

- Yes: 38%
- No: 62%

## How Prolepsia reasons

## 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](https://www.sec.gov/rules-regulations/2023/07/s7-09-22). 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](https://www.sec.gov/files/rules/final/2023/33-11216.pdf)).

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](https://www.sec.gov/rules-regulations/2018/08/disclosure-update-simplification) | July 13, 2016 | August 17, 2018 | 765 |
| [Regulation S-K Items 101/103/105 modernization](https://www.sec.gov/files/rules/final/2020/33-10825.pdf) | August 8, 2019 | August 26, 2020 | 384 |
| MD&A simplification | January 30, 2020 | November 19, 2020 | 294 |
| [Proxy-voting-advice rollback](https://www.sec.gov/files/rules/final/2022/34-95266.pdf) | November 17, 2021 | July 13, 2022 | 238 |
| [Original cybersecurity disclosure rule](https://www.sec.gov/rules-regulations/2023/07/s7-09-22) | 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](https://www.sec.gov/rules-regulations/rulemaking-activity?year=2026), containing actions through November 13, identifies no qualifying incident-reporting amendment proposal. The published [Form 8-K](https://www.sec.gov/files/form8-k.pdf) 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](https://www.sec.gov/files/rules/petitions/2025/petn4-856.pdf) explicitly asks the SEC to rescind Item 1.05 and the corresponding Form 6-K requirements. The associations [renewed their request in April 2026](https://www.sifma.org/advocacy/letters/reforming-regulation-s-ks-cybersecurity-disclosures-joint-trades), 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](https://www.sec.gov/newsroom/speeches-statements/atkins-statement-reforming-regulation-s-k-011326). 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](https://www.govinfo.gov/content/pkg/FR-2026-08-14/html/2026-16619.htm)).

The strongest recent leadership signal is Atkins’s [November 13, 2026 statement](https://www.sec.gov/newsroom/speeches-statements/atkins-statement-proposing-release-executive-compensation-disclosure-reform-111326). 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](https://www.sec.gov/newsroom/speeches-statements/uyeda-statement-cybersecurity-072623) criticized incident-impact disclosures and constrained disclosure delays. Those concerns map directly onto amendments that could qualify. His more recent [January 26, 2026 remarks](https://www.sec.gov/newsroom/speeches-statements/uyeda-remarks-securities-regulation-institute-012626), 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](https://www.sec.gov/files/hester-peirce-letter_0.pdf) means her earlier opposition cannot be treated as a current vote. Yet the [September 30 quorum amendment](https://www.sec.gov/files/rules/final/2026/34-106537.pdf) 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](https://www.gao.gov/assets/gao-27-108840.pdf)).

The wider policy environment supplies another supporting signal. The administration’s [March 2026 Cyber Strategy](https://www.whitehouse.gov/wp-content/uploads/2026/03/President-Trumps-Cyber-Strategy-for-America.pdf) calls for reducing cybersecurity regulatory burdens. Government research also documents potentially duplicative reporting requirements across sectors ([GAO review](https://www.gao.gov/assets/gao-26-108606.pdf?_sp=6d7f4230-7c51-436f-b022-369e0440a347.1784834320359)). 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](https://www.sec.gov/files/rules/final/2023/33-11216.pdf)). 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 |
|---|---|
| 2026-11-17 | 38% chance of yes |

## Sources Prolepsia read

- [SEC.gov \| Cybersecurity Risk Management, Strategy, Governance, and Incident Disclosure](https://www.sec.gov/rules-regulations/2023/07/s7-09-22)
- [Reforming Regulation S-K's Cybersecurity Disclosures (Joint Trades) - SIFMA](https://www.sifma.org/advocacy/letters/reforming-regulation-s-ks-cybersecurity-disclosures-joint-trades)
- [Federal Register, Volume 91 Issue 156 (Friday, August 14, 2026)](https://www.govinfo.gov/content/pkg/FR-2026-08-14/html/2026-16619.htm)
- [GAO-27-108840, Financial Audit: Securities and Exchange Commission’s FY 2026 and 2025 Financial Statements](https://www.gao.gov/assets/gao-27-108840.pdf)
- [March 2026 Cyber Strategy](https://www.whitehouse.gov/wp-content/uploads/2026/03/President-Trumps-Cyber-Strategy-for-America.pdf)
- [SEC Proposes Significant Amendments to Cybersecurity Disclosure Rules — Merrick & Stanton](https://www.merrickandstanton.com/briefings/policy-watch/sec-cybersecurity-rule-amendments)
- [Federal Register :: Registered Offering Reform](https://www.federalregister.gov/documents/2026/05/26/2026-10373/registered-offering-reform)
- [www.reginfo.gov](https://www.reginfo.gov/public/do/eAgendaViewRule?RIN=3235-AN43&pubId=202510)

## 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.

---

Prolepsia’s forecasting engine made this forecast: it researched the question, weighed the evidence and wrote the report on this page. A probability is not a promise; this one changes as the evidence does.
