New U.S. SEC Cybersecurity Rules Require Prompt Disclosures
6:56
author photo
By Cam Sivesind
Thu | Aug 28, 2025 | 1:28 PM PDT

The U.S. Securities and Exchange Commission (SEC) has finalized a landmark set of rules requiring public companies to disclose cybersecurity incidents with unprecedented transparency and speed. These disclosures—and disclosure governance—are now mandatory and not just recommended. Here's what cybersecurity professionals need to understand.

Key provisions of the SEC's final cybersecurity disclosure rules include the following.

1. Time-sensitive incident reporting via Form 8-K (Item 1.05)

Public companies must file a Form 8‑K within four business days of determining a cybersecurity incident is material. The report must detail the nature, scope, timing, and material—or reasonably likely material—impact of the incident on financial condition or operations.

  • Crucially, organizations must determine materiality without undue delay.

  • Updates must be filed via amended Form 8‑Ks as more information becomes available.

  • In exceptional circumstances, disclosure may be delayed, but only with written authorization from the U.S. Attorney General, typically for national security or public safety concerns.

2. Annual disclosures on risk management, strategy & governance (Item 106, Reg S-K)

Public companies' annual reports (Form 10‑K) must now include:

  • Their processes for assessing, identifying, and managing cybersecurity risks, including integration into broader risk frameworks and use of external advisors

  • Whether cybersecurity risks have materially affected—or are likely to affect—their business strategy, financial condition, or results of operations

  • How the board oversees cybersecurity, including committee involvement and management's role, expertise, and internal communication processes

Foreign private issuers must provide comparable disclosures via Forms 6‑K and 20‑F.

3. Inline XBRL tagging

All disclosures—both incident reports and annual risk governance—must be tagged in Inline XBRL, enabling structured, machine-readable reporting.

The SEC adopted the final rules on July 26, 2023 (with some amendments to follow). Most companies began complying in December 2023, with smaller reporting companies granted a grace period until June 2024. Inline XBRL tagging reached full effect in 2024–2025.

This marks a shift from earlier, more discretionary cybersecurity guidance (2011/2018) to mandatory, standardized reporting—reflecting growing investor demand for clarity on cyber risk.

Inconsistent historical disclosures—e.g., only 43% of 2021 cyber breaches were reported via SEC filings, with average delays of 79 days—underscored the need for reform.

With the new rules, there are some challenges around enforcement, compliance and market response, including:

  • Market impact: Early disclosures show minimal stock price movements—typically around a 0.7% dip one day post-8-K and 2.1% after five days. Markets seem to treat cyber incidents as routine rather than catastrophic.

  • Disclosure detail shortfalls: Even a year after implementation, many Form 8‑Ks lacked sufficient detail. A study revealed that just 17% of filings included specific material impact information.

  • Enforcement in motion: The SEC has begun acting—most prominently against SolarWinds—for inadequate or misleading cybersecurity disclosures, signaling that enforcement is more than theoretical.

"I like the statistic on the impact of cybersecurity incidents on stock prices," said Richard Halm, Senior Attorney, Clark Hill PLC. "To me, it really highlights how commonplace and normalized cybersecurity incidents are these days. A cybersecurity incident isn't a long-lasting stain on a company's reputation."

"I can't stress enough that the timeline trigger is the determination of materiality, not when the incident occurs," Halm added. "You have time to take a breath, survey where things stand, and then decide whether this meets the materiality threshold.”

"These SEC cybersecurity disclosure rules are critical legal requirements for public companies and essential components of their cyber risk management and incident response planning," said Shawn Tuma, Co-Chair, Data Privacy & Cybersecurity Practice, Spencer Fane LLP. "Public companies must ensure their incident response preparations specifically address who will be responsible for making the materiality determination, what factors will be considered in that assessment, who must approve the recommendation, and how and when that determination will be communicated to the Board. Then, they should practice it."

As Tuma says, it is imperative for cybersecurity teams to up their compliance and disclosure policies and actions. Some tips:

A. Strengthen materiality assessment and reporting protocols

  • Develop a playbook for rapid materiality analysis.

  • Ensure coordination across Legal, IR, and Security teams for swift Form 8‑K filing.

B. Integrate cybersecurity into enterprise risk & governance frameworks

  • Embed cybersecurity into ERM programs (e.g., aligning with NIST, ISO frameworks).

  • Clarify roles for management and board reporting mechanisms.

C. Build robust disclosure controls and documentation

  • Document data lifecycles, incident detection, escalation, and disclosure chains.

  • Map ownership and communication flow between security teams and executive leadership.

D. Prepare for enforcement scrutiny

  • Conduct internal audits of recent Form 8-Ks and 10-Ks for completeness and consistency.

  • Develop a remediation plan for gaps, whether related to timeliness, detail, or governance coverage.

The SEC's cybersecurity disclosure rules mark a pivotal leap toward formalizing how institutions report cyber risk. For security professionals, the immediate task is to ensure that detection, response, and disclosure processes are tightly aligned.

"The SEC's shift is in alignment with what I'm seeing in the broader data protection regulatory environment: regulators are demanding heightened transparency following data security events," said Jeremy Rucker, Partner & Attorney, Pierson Ferdinand LLP. "The new reporting requirements will inevitably force organizations facing cybersecurity incidents to undertake a thoughtful analysis to determine whether a cybersecurity event is considered material."

Rucker continued, "Consequently, organizations must take a holistic approach to carefully assess the impact of an incident—considering factors such as financial loss, legal impact, operational hinderances, etc. A critical key to overcoming regulatory scrutiny is to maintain thorough documentation of the circumstances supporting your decisions to help regulators arrive at your determination."

Comments