# Form 8-K Item 1.05 requires a filing within four business days of deciding a cyber incident is material

Legal guide, read 16 November 2026

**The short answer.** Item 1.05 of Form 8-K requires a public company to report a cybersecurity incident it determines to be material within four business days of that determination. Two delays exist: the Attorney General's national security or public safety delay, and a seven-business-day delay for FCC CPNI registrants. Read on 16 November 2026.

## When does Form 8-K Item 1.05 apply to a ransomware attack?

It applies when a registrant determines that a cybersecurity incident it experienced is material. The item covers any incident determined to be material and is not limited to ransomware. The SEC's final rule, published in the Federal Register on 4 August 2023 and effective 5 September 2023, says the filing is due within four business days of determining the incident was material.

This page reads the rule as published in 2023. Later amendments, if any, were not checked.

## What must the filing say?

The registrant describes the material aspects of the nature, scope and timing of the incident, and its material impact or reasonably likely material impact. The SEC clarified that the item does not require specific technical information about the planned response or systems in such detail as would impede response or remediation. A registrant must amend a prior Item 1.05 Form 8-K to include information not determined or unavailable at the first filing.

## Can the filing be delayed?

Two delays exist. If the Attorney General determines that immediate reporting would pose a substantial risk to national security or public safety, the registrant may postpone the filing. A registrant subject to the FCC's CPNI breach rule (47 CFR 64.2011) may also delay up to seven business days after the notification required under that rule, and must notify the SEC through EDGAR. Outside those two cases, the release creates no general pause while an investigation is still running.

## What counts as unreasonable delay in deciding materiality?

The final rule requires the materiality determination "without unreasonable delay" after discovery. The SEC says a company that cannot yet determine the full extent of an incident may still know enough to decide whether it is material, and that deferring a board committee meeting past the normal time to convene would be unreasonable delay. Revising incident response policies to extend deadlines in order to delay a determination would also be unreasonable. The SEC found a safe harbor unnecessary, because normal internal practices and controls will suffice to show good faith.

Keep the time of each step in the [decision log](/plan/ransomware-decision-log/). Companies also report annually on the board's oversight of cybersecurity risk and management's role, as the [board briefing page](/readiness/ransomware-readiness-board-briefing/) notes.

## Related pages

- [Ransomware reporting duties: who to tell and when](/reporting/ransomware-reporting-duties/)
- [CIRCIA ransomware reporting: status on 16 November 2026](/reporting/circia-ransomware-reporting-status/)
- [HIPAA breach notification and healthcare ransomware](/reporting/hipaa-breach-notification-ransomware/)
- [State breach notification laws: citations by state](/reporting/state-breach-notification-laws/)
- [The ransomware readiness assessment](/assessment/)
- [The control mapping](/mapping/)

## Sources

- Federal Register: SEC final rule on cybersecurity risk management, strategy, governance and incident reporting (4 August 2023): https://www.federalregister.gov/documents/2023/08/04/2023-16194/cybersecurity-risk-management-strategy-governance-and-incident-disclosure (read 16 November 2026)

Last reviewed 16 November 2026. Canonical: https://ransomwarereadinessassessment.com/reporting/sec-form-8-k-item-1-05/
