SEC cybersecurity disclosure rule

On this page 8

The SEC cybersecurity disclosure rule is the set of amendments adopted by the US Securities and Exchange Commission in July 2023 that requires public companies to disclose material cybersecurity incidents within four business days and to describe their cybersecurity risk management, strategy and governance every year. In cybersecurity law, it stands out because it is a securities disclosure duty, not a security standard: it tells investors what happened and how risk is overseen, without prescribing any specific technical control.

The rule sits within Tech regulation alongside sector and infrastructure regimes such as NIS2, DORA and CIRCIA, but its trigger is different. Those regimes protect networks and services, while the SEC rule protects investors from information asymmetry about cyber risk at listed companies.

What the SEC cybersecurity disclosure rule requires

The rule creates two distinct obligations: an event-driven incident report and a periodic description of the cyber program. Both apply to domestic registrants filing under the Securities Exchange Act of 1934, and parallel versions apply to foreign private issuers.

The table below summarizes the core components and where each one is filed.

ComponentFilingWhat must be disclosed
Form 8-K Item 1.05Current reportMaterial incident: nature, scope, timing and material impact
Regulation S-K Item 106(b)Annual Form 10-KProcesses to assess, identify and manage cyber risk
Regulation S-K Item 106(c)Annual Form 10-KBoard oversight and management roles and expertise
Form 6-KForeign private issuersMaterial incidents disclosed in home jurisdiction
Form 20-F Item 16KForeign private issuersAnnual risk management and governance disclosure
Core components of the rule

The incident report must describe the material aspects of the incident and its reasonably likely material impact on financial condition and results of operations. It does not require technical details that would impede response, such as specific vulnerabilities or system configurations.

How the four-business-day clock works

The deadline runs from the materiality determination, not from discovery of the incident. Companies must make that determination without unreasonable delay after discovery, so a deliberately slow assessment does not postpone the filing obligation.

Materiality follows the familiar securities law standard: information is material if there is a substantial likelihood that a reasonable investor would consider it important. The analysis is both quantitative and qualitative, covering harm to reputation, customer relationships, competitiveness and the likelihood of litigation or regulatory action.

The following table sets out the main stages and the time limits attached to each.

StageTime limitPractical note
Discovery of incidentNone setStarts the assessment, not the filing clock
Materiality determinationWithout unreasonable delayDocumented by a disclosure committee
Form 8-K filingFour business daysCounted from the determination
National security delayUp to 30 days, extendableOnly on request of the US Attorney General
Amended filing (8-K/A)Four business days after new factsCovers information unknown at first filing
Timeline from discovery to disclosure

The Attorney General delay is narrow. It can be extended by a further 30 days and, in extraordinary circumstances, by 60 more, but the company cannot invoke it on its own initiative and ransom or reputational concerns do not qualify.

Annual governance disclosure under Item 106

Item 106 requires a narrative description of the cyber program in the annual report. Companies must explain how cybersecurity processes are integrated into overall enterprise risk management, whether they engage assessors, consultants or auditors, and how they oversee risks from third-party service providers.

On governance, the company must describe how the board oversees cyber risk, which committee holds that responsibility and how it is informed. It must also name the management positions responsible, typically a chief information security officer, and describe their relevant expertise. A proposed requirement to disclose board-level cyber expertise was dropped from the final rule.

Disclosure must also state whether any risks from previous incidents have materially affected or are reasonably likely to affect the business strategy, results or financial condition. Boilerplate statements tend to attract staff comment letters.

How the rule compares with other incident reporting regimes

The SEC rule is often confused with operational reporting duties, but it differs in audience, trigger and content. Operational regimes send confidential reports to authorities so they can coordinate defense; the SEC rule produces a public filing for investors.

The comparison below shows how it differs from neighboring regimes in the same field.

RegimeAudienceTriggerFirst deadline
SEC ruleInvestors, publicMaterial incidentFour business days after determination
CIRCIACISA, confidentialCovered cyber incident72 hours
NIS2CSIRT or authoritySignificant incident24-hour early warning
DORAFinancial supervisorMajor ICT incidentHours after classification
State breach lawsAffected individualsPersonal data breachVaries by state
Comparison with related reporting regimes

One incident can trigger several regimes at once. A listed bank with European operations may file a DORA report, a confidential federal notice and a public Form 8-K, each with different content and clocks, so a single incident response playbook should map every duty.

Practical compliance and common mistakes

Effective compliance depends on an escalation path from the security team to the disclosure committee. Security staff detect and contain; lawyers and finance determine materiality; executives certify filings. Gaps between these groups are the most frequent source of late or inaccurate reports.

The table lists typical errors and how mature programs avoid them.

MistakeConsequenceRemedy
Filing immaterial incidents under Item 1.05Dilutes the signal to investorsUse Item 8.01 for voluntary reports
Delaying the materiality decisionPossible enforcement exposureSet internal assessment time targets
Generic risk factor languageStaff comment lettersDescribe actual processes and roles
Ignoring vendor incidentsMissed disclosure dutyInclude third-party breaches in scope
Overstating program maturityMisleading statement claimsAlign text with verified controls
Frequent errors and remedies

SEC staff guidance issued in 2024 clarified that companies should reserve Item 1.05 for incidents determined to be material and use Item 8.01 for other voluntary disclosures. The SolarWinds enforcement action also showed that public security statements can create liability when they diverge from internal reality, although most of that case was later dismissed.

Critics argue that public disclosure within days can alert attackers, complicate ransom negotiations and conflict with confidential reporting expected by law enforcement. Supporters reply that the rule only requires material impact, not technical detail, and that investors previously learned of breaches months after they occurred.

The rule applies only to SEC registrants, so private companies, even very large ones, are outside its scope unless they issue registered securities. Industry groups have petitioned for rescission of the incident disclosure item, so its future scope may change, but the annual governance disclosure remains a stable part of US public company reporting.

Put simply

Companies whose shares trade on US stock markets must tell their investors about serious cyberattacks. Once a company decides that a hack really matters to its business, it has four working days to announce it publicly.

Every year, the same companies must also explain who is in charge of cybersecurity and how the board keeps an eye on it. Think of it as a health report for the company’s digital defenses, written for the people who own a piece of the business. The rule does not tell companies how to protect themselves; it tells them to be honest about the risk.

In practice

A mid-sized listed logistics company detects ransomware on a Monday that has encrypted its shipment tracking systems. The security team contains the attack within a day, but the disclosure committee learns that deliveries in three regions will be disrupted for about two weeks and that some customer contracts include penalty clauses.

On Wednesday, the committee concludes that a reasonable investor would consider the revenue loss and contractual exposure important, and records that materiality determination. The company files a Form 8-K under Item 1.05 the following Monday, describing the operational impact and expected financial effect without naming the exploited vulnerability. Six weeks later, after forensic work confirms the scope of stolen data, it files an 8-K/A amendment, and its next annual report describes the improvements to vendor access controls and board reporting.