{"id":2168946,"date":"2026-11-19T03:21:57","date_gmt":"2026-11-19T02:21:57","guid":{"rendered":"https:\/\/kohenavocats.fr\/?p=2168946"},"modified":"2026-11-19T03:21:57","modified_gmt":"2026-11-19T02:21:57","slug":"cyber-attack-today-public-company-sec-disclosure-attack-outage","status":"publish","type":"post","link":"https:\/\/kohenavocats.fr\/en\/2026\/11\/19\/cyber-attack-today-public-company-sec-disclosure-attack-outage\/","title":{"rendered":"Cyber Attack Today: When a U.S. Public Company Must Disclose an Attack or Outage"},"content":{"rendered":"<p>By Reda Kohen, lawyer admitted to the Paris Bar<\/p>\n<p>The query <em>cyber attack today<\/em> became one of the fastest-rising searches in the United States on November 17, 2026: search trend data placed it in the 50,000+ volume band, with a rise reported at 1,000 percent and related searches such as <em>malware<\/em> and <em>hack<\/em>. Behind that curiosity sits a practical question that every company with securities registered with the Securities and Exchange Commission (SEC) must answer quickly when its systems are attacked or simply stop working: is this a reportable event, and how fast must investors be told? This article sets out, as information on United States federal securities law, the rule that answers it. Under <a href=\"https:\/\/www.sec.gov\/files\/form8-k.pdf\">Item 1.05 of Form 8-K<\/a>, a company that determines it has suffered a material cybersecurity incident must report it within four business days after that determination, and the determination itself must be made without unreasonable delay after discovery. The SEC defines an incident broadly enough to reach accidental events and systems run by vendors. Federal courts, for their part, have shown where the antifraud rules apply after an incident: in risk warnings and security statements that no longer match what management knows. The discussion that follows is general in scope: it describes checks useful in comparable situations and makes no finding about any company affected by the events behind the search. The author is a member of the Paris Bar and does not practice U.S. law.<\/p>\n<h2>I. When does an attack or an outage become a reportable cybersecurity incident?<\/h2>\n<h3>A. The definition: unauthorized occurrences, accidents and systems run by vendors<\/h3>\n<p>The analysis starts with a definition, not with the headlines. Under <a href=\"https:\/\/www.ecfr.gov\/current\/title-17\/section-229.106\">Item 106(a) of Regulation S-K, codified at 17 C.F.R. \u00a7 229.106<\/a>, a cybersecurity incident is &#8220;an unauthorized occurrence, or a series of related unauthorized occurrences, on or conducted through a registrant&#8217;s information systems that jeopardizes the confidentiality, integrity, or availability of a registrant&#8217;s information systems or any information residing therein.&#8221; The same definition governs the current report on Form 8-K, because Instruction 3 to Item 1.05 of <a href=\"https:\/\/www.sec.gov\/files\/form8-k.pdf\">Form 8-K<\/a> refers to it. Two elements matter for a company watching its services fail. The occurrence must be unauthorized, and it must take place on or through the company&#8217;s information systems. Availability appears in the definition next to confidentiality and integrity, so an event that takes systems offline can fall within it even when no data leaves the company.<\/p>\n<p>Many outages have ordinary causes, such as a faulty internal update or a configuration error, and the question whether such an event can count was raised during the rulemaking. The SEC answered it in the <a href=\"https:\/\/www.federalregister.gov\/documents\/2023\/08\/04\/2023-16194\/cybersecurity-risk-management-strategy-governance-and-incident-disclosure\">adopting release published in the Federal Register on August 4, 2023<\/a>: &#8220;In general, we believe that an accidental occurrence is an unauthorized occurrence.&#8221; The release adds that an accidental occurrence &#8220;may be a cybersecurity incident under our definition, even if there is no confirmed malicious activity,&#8221; and gives the example of customer data that are accidentally exposed. The practical consequence is that the absence of a hacker does not end the inquiry. It moves the analysis to the second step, materiality, which is the real trigger for a filing. A short outage that is fully reversed may well fall short of that test, while an accidental exposure of customer data may not; the answer depends on the facts of each event.<\/p>\n<p>The second element is drafted to reach beyond the company&#8217;s own servers. <a href=\"https:\/\/www.ecfr.gov\/current\/title-17\/section-229.106\">Item 106(a)<\/a> defines information systems as &#8220;electronic information resources, owned or used by the registrant, including physical or virtual infrastructure controlled by such information resources&#8221;. The <a href=\"https:\/\/www.federalregister.gov\/documents\/2023\/08\/04\/2023-16194\/cybersecurity-risk-management-strategy-governance-and-incident-disclosure\">adopting release<\/a> explains that the words &#8220;used by&#8221; were kept on purpose. Commenters had asked the SEC to limit the rule to systems owned or operated by the registrant; the Commission declined and wrote that &#8220;covering third party systems is essential to the working of Item 106 of Regulation S-K and Item 1.05 of Form 8-K.&#8221; It also stated that it was &#8220;not exempting registrants from providing disclosures regarding cybersecurity incidents on third-party systems they use&#8221;. An intrusion that reaches a company through a hosting provider, a software supplier or a script embedded in its website can therefore be the company&#8217;s own reportable incident, if its effect on the company is material.<\/p>\n<p>The SEC also recognized that a customer sees far less of a vendor&#8217;s systems than of its own. The <a href=\"https:\/\/www.federalregister.gov\/documents\/2023\/08\/04\/2023-16194\/cybersecurity-risk-management-strategy-governance-and-incident-disclosure\">release<\/a> states that registrants &#8220;should disclose based on the information available to them&#8221; and that the final rules &#8220;generally do not require that registrants conduct additional inquiries outside of their regular channels of communication with third-party service providers pursuant to those contracts and in accordance with registrants&#8217; disclosure controls and procedures.&#8221; Depending on the circumstances, it adds, disclosure &#8220;may be required by both the service provider and the customer, or by one but not the other, or by neither.&#8221; Read together, these passages make vendor contracts part of the disclosure system. The notice clauses and reporting channels negotiated with a provider largely determine what the company learns about an incident on the provider&#8217;s side, and when it learns it. The release does not treat limited visibility as a reason to stop the analysis; it asks the company to decide on the basis of what it actually knows through those channels.<\/p>\n<p>The definition also covers &#8220;a series of related unauthorized occurrences&#8221;. In Question 104B.09, dated June 24, 2024, the staff&#8217;s <a href=\"https:\/\/www.sec.gov\/rules-regulations\/staff-guidance\/corporation-finance-interpretations-cfis\/exchange-act-form-8-k\">Exchange Act Form 8-K interpretations<\/a> explain that a registrant facing several ransomware attacks, each immaterial on its own, &#8220;should consider whether any of those incidents were related, and if so, determine whether those related incidents, collectively, were material.&#8221;<\/p>\n<p>Not every issuer files Form 8-K: under paragraph (b) of <a href=\"https:\/\/www.ecfr.gov\/current\/title-17\/section-240.13a-11\">Rule 13a-11<\/a>, the current-report rule does not apply, among others, to foreign private issuers that report on Form 6-K. The obligation is also recent. The <a href=\"https:\/\/www.federalregister.gov\/documents\/2023\/08\/04\/2023-16194\/cybersecurity-risk-management-strategy-governance-and-incident-disclosure\">adopting release<\/a> set the start of compliance with Item 1.05 at December 18, 2023 for registrants other than smaller reporting companies, and at June 15, 2024 for smaller reporting companies, so the appellate case law discussed below was decided under the earlier framework of general antifraud rules and SEC guidance.<\/p>\n<h3>B. Materiality and the four-business-day clock<\/h3>\n<p>Item 1.05 turns on one threshold question. Its paragraph (a) applies &#8220;If the registrant experiences a cybersecurity incident that is determined by the registrant to be material&#8221;, and it then requires a description of &#8220;the material aspects of the nature, scope, and timing of the incident, and the material impact or reasonably likely material impact on the registrant, including its financial condition and results of operations.&#8221; General Instruction B.1 of <a href=\"https:\/\/www.sec.gov\/files\/form8-k.pdf\">Form 8-K<\/a> sets the clock: a report under Item 1.05 &#8220;is to be filed within four business days after the registrant determines that it has experienced a material cybersecurity incident.&#8221; Instruction 1 to the item prevents a company from postponing the decision that starts that clock: the &#8220;materiality determination regarding a cybersecurity incident must be made without unreasonable delay after discovery of the incident.&#8221; The rule therefore contains two time limits of different kinds, a flexible standard for the decision and a fixed period for the report.<\/p>\n<p>The rule does not define materiality by a number. In Question 104B.05, dated June 24, 2024, the staff&#8217;s <a href=\"https:\/\/www.sec.gov\/rules-regulations\/staff-guidance\/corporation-finance-interpretations-cfis\/exchange-act-form-8-k\">Form 8-K interpretations<\/a> restate the test adopted by the Commission: a registrant should determine &#8220;if there is a substantial likelihood that a reasonable shareholder would consider it important in making an investment decision, or if it would have significantly altered the total mix of information made available&#8221;. The same answer deals with a situation that follows many attacks. An incident that has stopped, including because a ransom was paid, still requires a materiality determination, and the registrant &#8220;cannot necessarily conclude that the incident is not material simply because of the prior cessation or apparent cessation of the incident.&#8221; Question 104B.07 adds that reimbursement of a ransom by an insurer does not, by itself, make the incident immaterial, and Question 104B.08 that the size of a ransom payment is only one of the facts to be weighed.<\/p>\n<p>The leading appellate discussion of cyber materiality predates the 2023 rule, but it addresses the same question. In <a href=\"https:\/\/www.courtlistener.com\/opinion\/4892309\/state-of-rhode-island-v-alphabet-inc\/\">In re Alphabet, Inc. Securities Litigation, 1 F.4th 687 (9th Cir. 2021)<\/a>, decided on June 16, 2021, the United States Court of Appeals for the Ninth Circuit reviewed the dismissal of a shareholder suit alleging that the company had not disclosed software vulnerabilities in a social network that exposed private profile data to third-party developers. The court held that the complaint plausibly alleged a material omission and rejected the argument that no sensitive financial or medical data had been exposed while revenue kept growing. In its words, &#8220;a cybersecurity incident may be material even if it does not compromise sensitive financial or medical information or have an immediate financial impact on the company.&#8221; It also rejected the argument that fixing the software glitch ended the problem, because the glitch and the company&#8217;s inability to measure its impact pointed to weaknesses in its security controls. For a company assessing an attack today, the application is direct: materiality cannot be closed by pointing to the type of data or to the absence of an immediate hit to revenue, and remediation does not erase what an incident reveals about controls. The ruling was made at the pleading stage, on the allegations of the complaint; it decided nothing about liability.<\/p>\n<p>That reasoning is still cited in the Ninth Circuit. In <a href=\"https:\/\/www.govinfo.gov\/content\/pkg\/USCOURTS-ca9-22-55641\/pdf\/USCOURTS-ca9-22-55641-0.pdf\">Zenoff v. Sorrento Therapeutics, Inc., No. 22-55641 (9th Cir. Mar. 25, 2024)<\/a>, an opinion filed on March 25, 2024, the United States Court of Appeals for the Ninth Circuit cited Alphabet, 1 F.4th 687, as a case that &#8220;concerned allegations that the defendants made materially misleading statements by failing to disclose security problems&#8221; and placed it among cases involving &#8220;critical information that was known only to corporate insiders.&#8221; The panel affirmed the dismissal of the claims before it, which concerned statements about a COVID-19 treatment candidate: it found the statements not misleading in context and the scienter allegations insufficient, noting in particular that no such undisclosed insider information was alleged. The contrast is useful for a public company: what turns a security problem into fraud exposure is a gap between what insiders know and what the market is told. The search of later citations on which this paragraph relies is a discovery tool, not a complete citator.<\/p>\n<p>Item 1.05 is reserved for incidents the company has found material. A statement by the Director of the Division of Corporation Finance on <a href=\"https:\/\/www.sec.gov\/newsroom\/speeches-statements\/gerding-cybersecurity-incidents-05212024\">the disclosure of cybersecurity incidents determined to be material and other cybersecurity incidents<\/a> encourages a company that wishes to speak about an incident it considers immaterial, or has not yet assessed, to use another item of Form 8-K, for example Item 8.01, so that investors can tell the two categories apart. The statement adds that if such a company &#8220;subsequently determines that the incident is material, then it should file an Item 1.05 Form 8-K within four business days of such subsequent materiality determination.&#8221; It also warns that the assessment should not be limited to financial results: possible harm to reputation, customer or vendor relationships and competitiveness, and the possibility of litigation or regulatory action, are part of it. The statement itself says that it has no legal force or effect. It is staff guidance, not a rule, but it shows how the SEC staff reads the rule.<\/p>\n<p>Two narrow routes allow a delay. Under Item 1.05(c) of <a href=\"https:\/\/www.sec.gov\/files\/form8-k.pdf\">Form 8-K<\/a>, if the United States Attorney General determines that disclosure &#8220;poses a substantial risk to national security or public safety&#8221; and notifies the SEC in writing, the registrant may delay for up to 30 days, a period that can be extended by up to 30 more days and, in extraordinary circumstances, by a final period of up to 60 days. The staff&#8217;s <a href=\"https:\/\/www.sec.gov\/rules-regulations\/staff-guidance\/corporation-finance-interpretations-cfis\/exchange-act-form-8-k\">Form 8-K interpretations<\/a> make clear that asking is not enough: under Question 104B.01, if the Attorney General declines or does not respond before the report is due, the registrant &#8220;must file the Item 1.05 Form 8-K within four business days of its determination that the incident is material.&#8221; Question 104B.04 adds that consulting the Department of Justice about a possible delay does not, by itself, mean that the incident is material. Item 1.05(d) of <a href=\"https:\/\/www.sec.gov\/files\/form8-k.pdf\">Form 8-K<\/a> contains a separate and short deferral for registrants subject to the data-breach rule at 47 C.F.R. \u00a7 64.2011, which cannot exceed seven business days after the notification that rule requires.<\/p>\n<p>Instruction 2 to Item 1.05 of <a href=\"https:\/\/www.sec.gov\/files\/form8-k.pdf\">Form 8-K<\/a> addresses the information gap that follows most incidents. Where information &#8220;is not determined or is unavailable at the time of the required filing&#8221;, the registrant says so in the report and then files an amendment &#8220;within four business days after the registrant, without unreasonable delay, determines such information or within four business days after such information becomes available.&#8221; Instruction 4 protects the response itself: a registrant &#8220;need not disclose specific or technical information about its planned response to the incident or its cybersecurity systems&#8221; in a level of detail that would impede the response or remediation. In practice, a first report describes the material aspects known at the time, avoids anything that would serve as a technical map for attackers, and is followed by amendments as facts settle.<\/p>\n<h2>II. What the company says before and after an incident: where antifraud exposure lies<\/h2>\n<h3>A. Risk factors that describe as hypothetical a risk that has already materialized<\/h3>\n<p>The four-business-day rule is not the only source of exposure. Paragraph (c) of <a href=\"https:\/\/www.ecfr.gov\/current\/title-17\/section-240.13a-11\">Rule 13a-11<\/a> provides that &#8220;No failure to file a report on Form 8-K that is required solely pursuant to Item 1.01, 1.02, 1.05&#8221; and several other items &#8220;shall be deemed to be a violation of&#8221; Section 10(b) of the Securities Exchange Act of 1934 and Rule 10b-5. The duty to file remains in paragraph (a) of the same rule, but a missed Item 1.05 deadline is not, on its own, deemed a violation of those antifraud provisions. What remains fully exposed is everything the company chooses to say. <a href=\"https:\/\/www.ecfr.gov\/current\/title-17\/section-240.10b-5\">Rule 10b-5(b)<\/a> makes it unlawful &#8220;To make any untrue statement of a material fact or to omit to state a material fact necessary in order to make the statements made, in the light of the circumstances under which they were made, not misleading&#8221;. The cases below show where that line falls after a cyber incident.<\/p>\n<p>The clearest risk concerns risk factors. In <a href=\"https:\/\/www.courtlistener.com\/opinion\/4892309\/state-of-rhode-island-v-alphabet-inc\/\">In re Alphabet, Inc. Securities Litigation, 1 F.4th 687 (9th Cir. 2021)<\/a>, decided on June 16, 2021, the United States Court of Appeals for the Ninth Circuit held that the complaint plausibly alleged that two quarterly reports on Form 10-Q were misleading. Those reports incorporated earlier risk factors warning that security and privacy concerns could harm the business, and they stated that there had been no material changes to those risk factors, at a time when, according to the complaint, the company already knew of the vulnerabilities. The court explained that risk disclosures that speak only of unrealized risks and do not &#8220;alert[] the reader that some of these risks may already have come to fruition&#8221; can mislead reasonable investors. The application for a company hit by an incident is concrete: the next periodic report should not repeat a purely hypothetical warning, or a statement that nothing has changed, about a risk that has already occurred. Here again, the court ruled on allegations at the motion-to-dismiss stage and did not decide liability.<\/p>\n<p>The Fourth Circuit has drawn the other side of the same line. In <a href=\"https:\/\/www.courtlistener.com\/opinion\/6461783\/construction-laborers-pension-trust-southern-ca-v-marriott-international\/\">In re Marriott International, Inc., 31 F.4th 898 (4th Cir. 2022)<\/a>, decided on April 21, 2022, the United States Court of Appeals for the Fourth Circuit affirmed the dismissal of a securities class action filed after malware affected a guest reservation database that the company had taken over through a merger. The investor argued that the company&#8217;s cybersecurity risk disclosures warned of risks that had already materialized. The court disagreed because, after learning of the breach, the company had updated its disclosure to state that &#8220;[W]e have experienced cyber-attacks, attempts to disrupt access to our systems and data, and attempts to affect the integrity of our data&#8221;. Applying the Ninth Circuit&#8217;s Alphabet standard, the court held that this admission ensured that the forward-looking warnings did not mislead investors about current or past challenges. For a company drafting its next filing after an incident, the application is to say plainly that attacks have occurred, in the risk factor itself, rather than leaving every warning in the conditional.<\/p>\n<p>The same Fourth Circuit formulation continues to be applied by district courts in that circuit. In <a href=\"https:\/\/www.govinfo.gov\/content\/pkg\/USCOURTS-mdd-1_17-cv-00388\/pdf\/USCOURTS-mdd-1_17-cv-00388-6.pdf\">In re Under Armour Securities Litigation, No. RDB-17-0388 (D. Md. Feb. 26, 2024)<\/a>, a memorandum opinion dated February 26, 2024, the United States District Court for the District of Maryland quoted Marriott, 31 F.4th 898, for the rule that a plaintiff must show that the defendant said something false or left out something that made its public statements misleading. The court also recalled that Section 10(b) and Rule 10b-5 &#8220;do not create an affirmative duty to disclose any and all material information.&#8221; That case did not involve a cyber incident; it concerned statements about consumer demand, and the court denied summary judgment on the record before it. Its reliance on Marriott confirms the starting point of any review after an incident: the question is not whether the company disclosed everything it knew, but whether what it chose to say was made misleading by what it left out.<\/p>\n<p>Two consequences follow for the period between discovery and full disclosure. First, the periodic reports and registration statements prepared during that period deserve a specific check of every risk factor that touches on information security, data protection, vendors and operational resilience, so that none of them describes as a future possibility something that has already happened. Second, the conditional tense is not a shield in itself. The Ninth Circuit&#8217;s reasoning in Alphabet focused on the contrast between a warning that harm &#8220;could&#8221; occur and internal knowledge that it had occurred, and the Fourth Circuit&#8217;s reasoning in Marriott focused on whether the company had acknowledged that attacks had already taken place. Neither decision required a company to publish technical details of its incident response, and the rule itself, as noted above, does not require them either.<\/p>\n<h3>B. Security statements, puffery, scienter and disclosure controls<\/h3>\n<p>Statements about security made outside the risk factors are judged on what they actually claim. In the Marriott decision discussed above, the Fourth Circuit held that statements stressing the importance of data protection were not misleading, because they said that security mattered without attributing to the company&#8217;s cybersecurity a quality it did not have, and the court noted that website privacy statements came with caveats, including a warning that no system for transmitting or storing data could be guaranteed to be completely secure. The same court recalled that the SEC itself advises companies not to make detailed disclosures that could compromise their cybersecurity efforts by providing a roadmap to attackers. The practical lesson is to describe processes and risks accurately, to avoid absolute assurances about security, and to keep technical details of defenses out of public documents.<\/p>\n<p>The Fourth Circuit returned to cyber risk later the same year. In <a href=\"https:\/\/www.courtlistener.com\/opinion\/8620485\/james-boykin-v-k12-inc\/\">Boykin v. K12, Inc., 54 F.4th 175 (4th Cir. 2022)<\/a>, decided on November 22, 2022, the United States Court of Appeals for the Fourth Circuit affirmed the dismissal of a securities suit against an online-education company. In a footnote, the court rejected the argument that the company had violated Rule 10b-5 by inadequately disclosing cybersecurity vulnerabilities, observing that the company &#8220;acknowledged at length in each 10-K filing its susceptibility to them&#8221; and that &#8220;The risk of cyberattacks is one that is common to many businesses and not something of which a reasonable investor would have been unaware.&#8221; The court added that strong cautionary language in the annual reports further undermined that claim, and it treated generic statements of competence and flexibility as non-actionable puffery or opinion. For a registrant, the application is that detailed and specific risk disclosure made before an incident is a significant protection against a later claim that the market was misled.<\/p>\n<p>A claim under Rule 10b-5 also requires scienter, which plaintiffs must plead with particularity under the Private Securities Litigation Reform Act. In Boykin, the Fourth Circuit noted that the plaintiffs alleged neither suspicious insider selling nor that the executives would personally benefit from a special bonus. In <a href=\"https:\/\/www.govinfo.gov\/content\/pkg\/USCOURTS-ca4-25-01188\/pdf\/USCOURTS-ca4-25-01188-0.pdf\">City of Southfield General Employees&#8217; Retirement System v. Advance Auto Parts, Inc., No. 25-1188 (4th Cir. Feb. 17, 2026)<\/a>, a published opinion decided on February 17, 2026, the United States Court of Appeals for the Fourth Circuit cited Boykin v. K12, Inc., 54 F.4th 175, 186, for the point that allegations that a defendant would personally benefit from a special bonus may support scienter, while adding that &#8220;motivations to &#8230; increase one\u2019s own compensation are common to every company and thus add little to an inference of fraud.&#8221; The court affirmed the dismissal of the accounting-related claims before it for failure to plead a strong inference of scienter. For a company managing an incident, the lesson is practical: trading by insiders and compensation decisions taken while an incident is being assessed are the kind of facts that later shape the scienter debate, and they call for a documented review.<\/p>\n<p>The rules and cases point to a working method rather than a single deadline. Paragraphs (b) and (c) of <a href=\"https:\/\/www.ecfr.gov\/current\/title-17\/section-229.106\">Item 106 of Regulation S-K<\/a> now require annual disclosure of the processes used to assess and manage material cybersecurity risks, including &#8220;Whether the registrant has processes to oversee and identify such risks from cybersecurity threats associated with its use of any third-party service provider&#8221;, together with the board&#8217;s oversight and management&#8217;s role. When an attack or an outage occurs, those processes are tested in real time, and the documents they produce become the evidence of how the company reasoned. A company facing an event can work through the following checks, each of which follows from the texts and decisions discussed above:<\/p>\n<ol>\n<li>Classify the event: is it an unauthorized occurrence, including an accidental one, on or through systems the company owns or uses, including a vendor&#8217;s systems, as the definition in <a href=\"https:\/\/www.ecfr.gov\/current\/title-17\/section-229.106\">Item 106(a)<\/a> and the <a href=\"https:\/\/www.federalregister.gov\/documents\/2023\/08\/04\/2023-16194\/cybersecurity-risk-management-strategy-governance-and-incident-disclosure\">adopting release<\/a> provide?<\/li>\n<li>Make and record the materiality determination without unreasonable delay after discovery, using qualitative as well as quantitative factors, and note its date, because under General Instruction B.1 of <a href=\"https:\/\/www.sec.gov\/files\/form8-k.pdf\">Form 8-K<\/a> the four business days run from that determination.<\/li>\n<li>If the incident is material, file under Item 1.05 within that period unless the Attorney General has made the determination described in Item 1.05(c); if it is not material or not yet assessed, consider a voluntary report under another item, as the <a href=\"https:\/\/www.sec.gov\/newsroom\/speeches-statements\/gerding-cybersecurity-incidents-05212024\">staff statement<\/a> suggests.<\/li>\n<li>Plan amendments for information that is not yet determined, under Instruction 2 to Item 1.05 of <a href=\"https:\/\/www.sec.gov\/files\/form8-k.pdf\">Form 8-K<\/a>, and keep technical details of the response out of the report.<\/li>\n<li>Review every risk factor and public security statement that will be repeated in the next filing, and review insider trading and compensation decisions made during the assessment period.<\/li>\n<\/ol>\n<p>Groups that also own companies in France face a separate set of French corporate-law questions, which the firm&#8217;s page on <a href=\"https:\/\/kohenavocats.fr\/en\/company-law-lawyer-paris\/\">company law in Paris<\/a> describes; that page concerns French law only and says nothing about SEC reporting.<\/p>\n<h2>Conclusion<\/h2>\n<p>For a company with securities registered with the SEC, the question behind <em>cyber attack today<\/em> is answered in two steps. The first is classification: an unauthorized occurrence on systems the company owns or uses is a cybersecurity incident, and the SEC has said that an accidental occurrence can qualify even without confirmed malicious activity, including when the systems belong to a vendor. The second is materiality, judged by the reasonable-investor standard with qualitative and quantitative factors, and decided without unreasonable delay after discovery. Once a company determines that an incident is material, <a href=\"https:\/\/www.sec.gov\/files\/form8-k.pdf\">Form 8-K<\/a> requires a report under Item 1.05 within four business days, subject only to the narrow delay that a determination by the Attorney General allows, with amendments as information becomes available. A late Item 1.05 report is not deemed, on its own, a violation of the antifraud rules, but what the company says is fully exposed to them. Federal appellate courts have treated as plausibly misleading a risk warning written in the conditional when the risk had already materialized, and have rejected claims where the company acknowledged that attacks had occurred, described its risks at length and avoided absolute assurances. Whether a particular event is material remains a question of fact for the company to resolve and, if a dispute follows, for a court to decide.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Cyber attack today: under SEC rules, a U.S. public company must report a material cybersecurity incident on Form 8-K within four business days of deciding it is material, and accidental or vendor-side events can count.<\/p>\n","protected":false},"author":251031309,"featured_media":16508,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_kj_source_type":"","_kj_official_id":"","_kj_official_url":"","_kj_judilibre_id":"","_kj_jur":"","_kj_lieu":"","_kj_chambre":"","_kj_rg":"","_kj_date":"","activitypub_content_warning":"","activitypub_content_visibility":"","activitypub_max_image_attachments":4,"activitypub_interaction_policy_quote":"anyone","activitypub_status":"federated","footnotes":""},"categories":[80336,80333],"tags":[],"class_list":["post-2168946","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-us-uk-corporate-law","category-us-uk-law"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v28.2 (Yoast SEO v28.2) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Cyber Attack Today: When a U.S. Public Company Must Disclose an Attack or Outage<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/kohenavocats.fr\/en\/2026\/11\/19\/cyber-attack-today-public-company-sec-disclosure-attack-outage\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Cyber Attack Today: When a U.S. Public Company Must Disclose an Attack or Outage\" \/>\n<meta property=\"og:description\" content=\"Cyber attack today: under SEC rules, a U.S. public company must report a material cybersecurity incident on Form 8-K within four business days of deciding it is material, and accidental or vendor-side events can count.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/kohenavocats.fr\/en\/2026\/11\/19\/cyber-attack-today-public-company-sec-disclosure-attack-outage\/\" \/>\n<meta property=\"og:site_name\" content=\"Reda KOHEN\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-19T02:21:57+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/kohenavocats.fr\/wp-content\/uploads\/2024\/11\/allison-saeng-FimlRcXllbw-unsplash-scaled.webp\" \/>\n\t<meta property=\"og:image:width\" content=\"4000\" \/>\n\t<meta property=\"og:image:height\" content=\"3000\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/webp\" \/>\n<meta name=\"author\" content=\"Kohen\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Kohen\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"20 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/2026\\\/11\\\/19\\\/cyber-attack-today-public-company-sec-disclosure-attack-outage\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/2026\\\/11\\\/19\\\/cyber-attack-today-public-company-sec-disclosure-attack-outage\\\/\"},\"author\":{\"name\":\"Kohen\",\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/#\\\/schema\\\/person\\\/6254a643e6239d803134a01c800381bd\"},\"headline\":\"Cyber Attack Today: When a U.S. Public Company Must Disclose an Attack or Outage\",\"datePublished\":\"2026-11-19T02:21:57+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/2026\\\/11\\\/19\\\/cyber-attack-today-public-company-sec-disclosure-attack-outage\\\/\"},\"wordCount\":4074,\"publisher\":{\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/2026\\\/11\\\/19\\\/cyber-attack-today-public-company-sec-disclosure-attack-outage\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/kohenavocats.fr\\\/wp-content\\\/uploads\\\/2024\\\/11\\\/allison-saeng-FimlRcXllbw-unsplash-scaled.webp\",\"articleSection\":[\"US &amp; UK Corporate Law\",\"US &amp; UK Law\"],\"inLanguage\":\"en-US\",\"citation\":\"Cyber Attack Today: When a U.S. Public Company Must Disclose an Attack or Outage\",\"about\":[{\"@type\":\"Thing\",\"name\":\"US &amp; UK Corporate Law\"},{\"@type\":\"Thing\",\"name\":\"US &amp; UK Law\"}],\"dateModified\":\"2026-11-19T02:21:57+00:00\",\"speakable\":{\"@type\":\"SpeakableSpecification\",\"cssSelector\":[\".article-content > p:first-of-type\"]}},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/2026\\\/11\\\/19\\\/cyber-attack-today-public-company-sec-disclosure-attack-outage\\\/\",\"url\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/2026\\\/11\\\/19\\\/cyber-attack-today-public-company-sec-disclosure-attack-outage\\\/\",\"name\":\"Cyber Attack Today: When a U.S. Public Company Must Disclose an Attack or Outage\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/2026\\\/11\\\/19\\\/cyber-attack-today-public-company-sec-disclosure-attack-outage\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/2026\\\/11\\\/19\\\/cyber-attack-today-public-company-sec-disclosure-attack-outage\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/kohenavocats.fr\\\/wp-content\\\/uploads\\\/2024\\\/11\\\/allison-saeng-FimlRcXllbw-unsplash-scaled.webp\",\"datePublished\":\"2026-11-19T02:21:57+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/2026\\\/11\\\/19\\\/cyber-attack-today-public-company-sec-disclosure-attack-outage\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/2026\\\/11\\\/19\\\/cyber-attack-today-public-company-sec-disclosure-attack-outage\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/2026\\\/11\\\/19\\\/cyber-attack-today-public-company-sec-disclosure-attack-outage\\\/#primaryimage\",\"url\":\"https:\\\/\\\/kohenavocats.fr\\\/wp-content\\\/uploads\\\/2024\\\/11\\\/allison-saeng-FimlRcXllbw-unsplash-scaled.webp\",\"contentUrl\":\"https:\\\/\\\/kohenavocats.fr\\\/wp-content\\\/uploads\\\/2024\\\/11\\\/allison-saeng-FimlRcXllbw-unsplash-scaled.webp\",\"width\":4000,\"height\":3000},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/2026\\\/11\\\/19\\\/cyber-attack-today-public-company-sec-disclosure-attack-outage\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Cyber Attack Today: When a U.S. Public Company Must Disclose an Attack or Outage\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/#website\",\"url\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/\",\"name\":\"Reda KOHEN\",\"description\":\"Ma\u00eetre Reda Kohen, attorney specialized in real estate and business law in Paris, advises and assists companies and individuals in their real estate, commercial and contractual transactions. He also handles real estate litigation and the resolution of complex commercial disputes.\",\"publisher\":{\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/#organization\",\"name\":\"Reda KOHEN\",\"url\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/kohenavocats.fr\\\/wp-content\\\/uploads\\\/2024\\\/05\\\/Logo-2-1.webp\",\"contentUrl\":\"https:\\\/\\\/kohenavocats.fr\\\/wp-content\\\/uploads\\\/2024\\\/05\\\/Logo-2-1.webp\",\"width\":2114,\"height\":1253,\"caption\":\"Reda KOHEN\"},\"image\":{\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/#\\\/schema\\\/logo\\\/image\\\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/#\\\/schema\\\/person\\\/6254a643e6239d803134a01c800381bd\",\"name\":\"Kohen\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/1c5e76ef76bbbfdd2b4da984e2bf2fa4056fd51a27d25ce2c332047f1dfd6e00?s=96&d=identicon&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/1c5e76ef76bbbfdd2b4da984e2bf2fa4056fd51a27d25ce2c332047f1dfd6e00?s=96&d=identicon&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/1c5e76ef76bbbfdd2b4da984e2bf2fa4056fd51a27d25ce2c332047f1dfd6e00?s=96&d=identicon&r=g\",\"caption\":\"Kohen\"},\"url\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/author\\\/kohenmlk\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Cyber Attack Today: When a U.S. Public Company Must Disclose an Attack or Outage","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/kohenavocats.fr\/en\/2026\/11\/19\/cyber-attack-today-public-company-sec-disclosure-attack-outage\/","og_locale":"en_US","og_type":"article","og_title":"Cyber Attack Today: When a U.S. Public Company Must Disclose an Attack or Outage","og_description":"Cyber attack today: under SEC rules, a U.S. public company must report a material cybersecurity incident on Form 8-K within four business days of deciding it is material, and accidental or vendor-side events can count.","og_url":"https:\/\/kohenavocats.fr\/en\/2026\/11\/19\/cyber-attack-today-public-company-sec-disclosure-attack-outage\/","og_site_name":"Reda KOHEN","article_published_time":"2026-11-19T02:21:57+00:00","og_image":[{"width":4000,"height":3000,"url":"https:\/\/kohenavocats.fr\/wp-content\/uploads\/2024\/11\/allison-saeng-FimlRcXllbw-unsplash-scaled.webp","type":"image\/webp"}],"author":"Kohen","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Kohen","Est. reading time":"20 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/kohenavocats.fr\/en\/2026\/11\/19\/cyber-attack-today-public-company-sec-disclosure-attack-outage\/#article","isPartOf":{"@id":"https:\/\/kohenavocats.fr\/en\/2026\/11\/19\/cyber-attack-today-public-company-sec-disclosure-attack-outage\/"},"author":{"name":"Kohen","@id":"https:\/\/kohenavocats.fr\/en\/#\/schema\/person\/6254a643e6239d803134a01c800381bd"},"headline":"Cyber Attack Today: When a U.S. Public Company Must Disclose an Attack or Outage","datePublished":"2026-11-19T02:21:57+00:00","mainEntityOfPage":{"@id":"https:\/\/kohenavocats.fr\/en\/2026\/11\/19\/cyber-attack-today-public-company-sec-disclosure-attack-outage\/"},"wordCount":4074,"publisher":{"@id":"https:\/\/kohenavocats.fr\/en\/#organization"},"image":{"@id":"https:\/\/kohenavocats.fr\/en\/2026\/11\/19\/cyber-attack-today-public-company-sec-disclosure-attack-outage\/#primaryimage"},"thumbnailUrl":"https:\/\/kohenavocats.fr\/wp-content\/uploads\/2024\/11\/allison-saeng-FimlRcXllbw-unsplash-scaled.webp","articleSection":["US &amp; UK Corporate Law","US &amp; UK Law"],"inLanguage":"en-US","citation":"Cyber Attack Today: When a U.S. Public Company Must Disclose an Attack or Outage","about":[{"@type":"Thing","name":"US &amp; UK Corporate Law"},{"@type":"Thing","name":"US &amp; UK Law"}],"dateModified":"2026-11-19T02:21:57+00:00","speakable":{"@type":"SpeakableSpecification","cssSelector":[".article-content > p:first-of-type"]}},{"@type":"WebPage","@id":"https:\/\/kohenavocats.fr\/en\/2026\/11\/19\/cyber-attack-today-public-company-sec-disclosure-attack-outage\/","url":"https:\/\/kohenavocats.fr\/en\/2026\/11\/19\/cyber-attack-today-public-company-sec-disclosure-attack-outage\/","name":"Cyber Attack Today: When a U.S. Public Company Must Disclose an Attack or Outage","isPartOf":{"@id":"https:\/\/kohenavocats.fr\/en\/#website"},"primaryImageOfPage":{"@id":"https:\/\/kohenavocats.fr\/en\/2026\/11\/19\/cyber-attack-today-public-company-sec-disclosure-attack-outage\/#primaryimage"},"image":{"@id":"https:\/\/kohenavocats.fr\/en\/2026\/11\/19\/cyber-attack-today-public-company-sec-disclosure-attack-outage\/#primaryimage"},"thumbnailUrl":"https:\/\/kohenavocats.fr\/wp-content\/uploads\/2024\/11\/allison-saeng-FimlRcXllbw-unsplash-scaled.webp","datePublished":"2026-11-19T02:21:57+00:00","breadcrumb":{"@id":"https:\/\/kohenavocats.fr\/en\/2026\/11\/19\/cyber-attack-today-public-company-sec-disclosure-attack-outage\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/kohenavocats.fr\/en\/2026\/11\/19\/cyber-attack-today-public-company-sec-disclosure-attack-outage\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/kohenavocats.fr\/en\/2026\/11\/19\/cyber-attack-today-public-company-sec-disclosure-attack-outage\/#primaryimage","url":"https:\/\/kohenavocats.fr\/wp-content\/uploads\/2024\/11\/allison-saeng-FimlRcXllbw-unsplash-scaled.webp","contentUrl":"https:\/\/kohenavocats.fr\/wp-content\/uploads\/2024\/11\/allison-saeng-FimlRcXllbw-unsplash-scaled.webp","width":4000,"height":3000},{"@type":"BreadcrumbList","@id":"https:\/\/kohenavocats.fr\/en\/2026\/11\/19\/cyber-attack-today-public-company-sec-disclosure-attack-outage\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/kohenavocats.fr\/en\/"},{"@type":"ListItem","position":2,"name":"Cyber Attack Today: When a U.S. Public Company Must Disclose an Attack or Outage"}]},{"@type":"WebSite","@id":"https:\/\/kohenavocats.fr\/en\/#website","url":"https:\/\/kohenavocats.fr\/en\/","name":"Reda KOHEN","description":"Ma\u00eetre Reda Kohen, attorney specialized in real estate and business law in Paris, advises and assists companies and individuals in their real estate, commercial and contractual transactions. He also handles real estate litigation and the resolution of complex commercial disputes.","publisher":{"@id":"https:\/\/kohenavocats.fr\/en\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/kohenavocats.fr\/en\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/kohenavocats.fr\/en\/#organization","name":"Reda KOHEN","url":"https:\/\/kohenavocats.fr\/en\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/kohenavocats.fr\/en\/#\/schema\/logo\/image\/","url":"https:\/\/kohenavocats.fr\/wp-content\/uploads\/2024\/05\/Logo-2-1.webp","contentUrl":"https:\/\/kohenavocats.fr\/wp-content\/uploads\/2024\/05\/Logo-2-1.webp","width":2114,"height":1253,"caption":"Reda KOHEN"},"image":{"@id":"https:\/\/kohenavocats.fr\/en\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/kohenavocats.fr\/en\/#\/schema\/person\/6254a643e6239d803134a01c800381bd","name":"Kohen","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/1c5e76ef76bbbfdd2b4da984e2bf2fa4056fd51a27d25ce2c332047f1dfd6e00?s=96&d=identicon&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/1c5e76ef76bbbfdd2b4da984e2bf2fa4056fd51a27d25ce2c332047f1dfd6e00?s=96&d=identicon&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/1c5e76ef76bbbfdd2b4da984e2bf2fa4056fd51a27d25ce2c332047f1dfd6e00?s=96&d=identicon&r=g","caption":"Kohen"},"url":"https:\/\/kohenavocats.fr\/en\/author\/kohenmlk\/"}]}},"_links":{"self":[{"href":"https:\/\/kohenavocats.fr\/en\/wp-json\/wp\/v2\/posts\/2168946","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/kohenavocats.fr\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kohenavocats.fr\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kohenavocats.fr\/en\/wp-json\/wp\/v2\/users\/251031309"}],"replies":[{"embeddable":true,"href":"https:\/\/kohenavocats.fr\/en\/wp-json\/wp\/v2\/comments?post=2168946"}],"version-history":[{"count":1,"href":"https:\/\/kohenavocats.fr\/en\/wp-json\/wp\/v2\/posts\/2168946\/revisions"}],"predecessor-version":[{"id":2168947,"href":"https:\/\/kohenavocats.fr\/en\/wp-json\/wp\/v2\/posts\/2168946\/revisions\/2168947"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/kohenavocats.fr\/en\/wp-json\/wp\/v2\/media\/16508"}],"wp:attachment":[{"href":"https:\/\/kohenavocats.fr\/en\/wp-json\/wp\/v2\/media?parent=2168946"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kohenavocats.fr\/en\/wp-json\/wp\/v2\/categories?post=2168946"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kohenavocats.fr\/en\/wp-json\/wp\/v2\/tags?post=2168946"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}