Summary
- The incident-disclosure rule says an Item 1.05 Form 8-K must be filed within four business days of determining an incident was material. The clock starts at a judgement, not at the intrusion, the discovery or the containment.
- The annual report is held to a different standard. Item 106 asks for the company's processes, board oversight and management's role, described in enough detail for a reasonable investor to understand them. Process gets a comprehension test; the incident gets a determination test.
There is no company in this story, and that is the point. The instrument is the subject.
On 4 August 2023 the Federal Register page for the adopting release put the obligation in one sentence: "An Item 1.05 Form 8-K must be filed within four business days of determining an incident was material" (release page as published). Read it the way a general counsel reads it. The clock does not start when the intruder arrives. It does not start when the security team notices. It does not start when containment ends. It starts at an act of judgement, and the thing judged is materiality.
The sentence names no test for materiality, no actor performing the determination, and no interval between discovery and decision. It is a filing duty, so the determination in practice belongs to the registrant whose signature is on the form. What the release does not print is any standard an outsider could apply to check the judgement against the facts, or any record of when the judgement was reached.
Then there is the unit. Four business days is not four calendar days, and count the difference on a Friday decision: four calendar days land on Tuesday, four business days with a weekend in between land on Thursday. That is my arithmetic on the word the release uses, not a gloss the release supplies. Neither document reviewed for this piece defines "business day," so whether the count runs over weekends, federal holidays or a filing-system outage is not established. The number in the headline is the least interesting thing about the clock; the unit, and who sets it, is everything.
What must be inside the filing is stated plainly enough. Registrants must describe the material aspects of the incident's "Nature, scope, and timing; and —Impact or reasonably likely impact" (same release page). Four elements, two pairs, and one deliberate hole. "Timing" is required; the reviewed text never says whether timing means when the intrusion occurred, when it was discovered, or when the company decided it was material. Every one of those readings is available. Only one of them would let a reader reconstruct whether the four-day count was met, and nothing in the excerpt chooses it.
The brake is where the drafting gets interesting. "A registrant may delay filing as described below, if the United States Attorney General ("Attorney General") determines immediate disclosure would pose a substantial risk to national security or public safety." That is the whole of what the page prints. The words "as described below" point at mechanics, and the excerpt then breaks off.
How long a delay may run, what the registrant must send to whom, whether a further postponement exists, whether the filing must even say a delay was granted — all of it sits in text this run did not obtain, so none of it is asserted here. The gate is real and the gate is narrow, resting on one office and two stated grounds. The passage through it is, on the evidence in hand, undocumented.
The annual report keeps an entirely different register. Regulation S-K Item 106 requires a registrant to "Describe the registrant's processes, if any, for assessing, identifying, and managing material risks from cybersecurity threats in sufficient detail for a reasonable investor to understand those processes" (17 CFR 229.106). Two words carry more weight than the rest. "If any" means a company without such processes may satisfy the item by saying so — the rule licenses an honest description of nothing. And "sufficient detail for a reasonable investor to understand" is a comprehension standard: not effectiveness, not maturity, not certification, just enough clarity that a reader grasps what the machinery is.
Beside it, governance: "Describe the board of directors' oversight of risks from cybersecurity threats," and "Describe management's role in assessing and managing the registrant's material risks from cybersecurity threats" (same section). Describing an oversight role is not attesting that oversight happened. Nothing in the fragments held imposes a frequency, names a committee, or demands evidence that the board did anything at all beyond the description.
Put the registers next to each other and the architecture shows. Process disclosure is judged by whether a reasonable investor can understand it. Incident disclosure is judged by whether the company determined the incident was material. One standard is calibrated to the reader. The other is calibrated to the discloser.
So what can a third party actually check? That a filing exists. What it says about nature, scope, timing and impact. Whether it names the date the materiality determination was made — the one date that would let anyone outside reconstruct the arithmetic of the four days, and the one date the reviewed text never requires. Across the two documents read for this article on 17 November 2026 — the eCFR section carrying Item 106 and the Federal Register page carrying the release text — I found no provision requiring publication of an Attorney General notification, of a delay determination, or of an aggregate count of incidents determined material.
That is a finding about those two documents as retrieved, not about the rule, the Commission's practice or any other agency's records.
Two limits belong here rather than in a footnote. The operative Form 8-K Item 1.05 text and its numbered instructions were not obtained; two attempts on two different renditions failed, so nothing in this article describes the delay's duration, the notification a registrant gives, any route to a further delay, any duty to state in the filing that a delay was obtained, or any interval between discovery and determination. And only three fragments of Item 106 are held — (b)(1), (c)(1) and (c)(2). Subsection (a) and the remainder of subsection (b) were not in the excerpt, so nothing here describes what they require or permit.
No Form 8-K Item 1.05 filing, no delay notification and no enforcement action was obtained or examined, and no company's compliance, timeliness or conduct is asserted or implied.
For the record of coverage: two searches of this archive on 17 November 2026, at limit 25, for "SEC cybersecurity incident disclosure" and "material cybersecurity incident," returned no rows on the disclosure instrument. The directory entry for the U.S. Securities & Exchange Commission counts nine articles. That is a count, nothing more.
The filing is not a lie detector and it was never meant to be. It is a notice that a judgement has been made, published within a stated number of an undefined unit of time, and kept honest by the ordinary machinery of securities fraud rather than by any clock a reader can verify. For a board, that is the actionable finding: the audit trail the rule requires is the description of the process, and the process is the only place the determination can be made checkable. If the determination date is not written down somewhere a third party can eventually see, then four business days is a promise about diligence with no observable start.
Member Briefing
Read the full trend briefing
Members read the full briefing with the source notes behind every finding.
Strategic Circle
A daily briefing in your language, built from changes we have verified.
Join for USD 20/monthCancel anytime.
Members also get the full research library, a daily briefing on the networks they follow and the private forum.






