Skip to content
ContentLora

    Tip: press / anywhere to search.

    Explainer

    Cyber-incident reporting rules: SEC 8-K, CIRCIA, NIS2 and DORA

    US public companies must file a Form 8-K within four business days of deciding a cyber incident is material, and the EU's NIS2 Directive gives essential and important entities 24 hours for an early warning and 72 hours for a fuller notification.[1][2] A broader US rule for critical infrastructure under CIRCIA, with 72-hour incident and 24-hour ransom-payment reports, was still unfinished in November 2026, and CISA says reporting is not required until its final rule takes effect.[3][4]

    Editor reviewedUpdated Explainer16 claims · 100% primaryCybersecurity, Tech policy

    This explainer summarises reporting rules as written in the official texts. It is not legal advice. Which rules apply depends on the organisation’s sector, size and country; check with the relevant regulator or a lawyer.

    Several overlapping regimes

    Organisations can face more than one duty to report a cyberattack, each with its own trigger, recipient and deadline: four business days after a materiality decision for the SEC, 24 hours for a NIS2 early warning.[1][2] This page compares the main US and EU regimes for security incidents. Personal-data breach rules sit alongside them; see how data breaches happen.

    United States: the SEC’s four-day rule

    In July 2023 the Securities and Exchange Commission adopted rules requiring public companies to disclose any cybersecurity incident they determine to be material under a new Item 1.05 of Form 8-K, describing its nature, scope, timing and likely impact.[5] The filing is generally due four business days after the materiality determination. It can be delayed if the US Attorney General finds that immediate disclosure would pose a substantial risk to national security or public safety.[1]

    The clock starts at the materiality decision, not at discovery, but the company must make that decision without unreasonable delay after discovering the incident.[6] If details are still unknown when the 8-K is due, the company must say so and file an amendment later.[7] Larger companies had to comply from 18 December 2023 and smaller reporting companies from 15 June 2024.[8] Recent filings under the rule are listed in the 2026 cyber incidents tracker.

    United States: CIRCIA, still pending

    The Cyber Incident Reporting for Critical Infrastructure Act of 2022 (CIRCIA) requires covered entities to report covered cyber incidents to CISA within 72 hours of reasonably believing one has occurred, and ransom payments within 24 hours of paying.[3] Those duties start only once CISA’s implementing rule takes effect.[4]

    CISA published its proposed rule on 4 April 2024. It estimated that about 316,244 entities would be covered and that the rule would cost $2.6 billion over its analysis period.[9] As of November 2026, CISA says it held four town hall meetings in June 2026, that multiple funding lapses affected its rulemaking, and that it is still working on the final rule.[4] Until that rule takes effect, CIRCIA reporting is not required, though CISA encourages voluntary reports.[4] Ransomware victims can already report through federal channels; see how ransomware works.[10]

    European Union: NIS2

    The NIS2 Directive applies to “essential” and “important” entities. It sets a three-stage clock for significant incidents:[2]

    1. Early warning within 24 hours of becoming aware of the incident.
    2. Incident notification within 72 hours, with an initial assessment.
    3. Final report no later than one month after the notification.

    Member states had to adopt national laws by 17 October 2024 and apply them from 18 October 2024.[11] For breaches of the risk-management or reporting duties, national law must allow maximum fines of at least €10 million or 2% of worldwide annual turnover, whichever is higher, for essential entities, and at least €7 million or 1.4% for important entities.[12]

    European Union: DORA and GDPR

    Financial firms have their own regime. The Digital Operational Resilience Act (DORA), which applies from 17 January 2025, requires financial entities to report major ICT-related incidents to their competent authority.[13]

    Separately, when personal data is involved, GDPR requires the organisation to notify its data protection authority without undue delay and, where feasible, within 72 hours. It must tell affected people without undue delay when the breach is likely to pose a high risk to them.[14][15] In the US, every state, plus the District of Columbia, Puerto Rico and the Virgin Islands, has its own breach-notification law for personal information.[16]

    Comparing the clocks

    RegimeWhoFirst deadline
    SEC Item 1.05 (US)Public companies4 business days after a materiality decision[1]
    CIRCIA (US, pending)Covered critical-infrastructure entities72 hours (incidents), 24 hours (ransom payments)[3]
    NIS2 (EU)Essential and important entities24-hour early warning[2]
    GDPR (EU)Controllers of personal data72 hours where feasible[14]

    For the US agency that would receive CIRCIA reports, see cisa; for the securities regulator, see sec.

    Developing in AI & Computing

    Go deeper

    Questions readers ask

    How fast must a US public company disclose a cyberattack?

    Under SEC rules adopted in 2023, an Item 1.05 Form 8-K is generally due four business days after the company determines an incident is material, and that determination must be made without unreasonable delay after discovery.[1][6]

    What is CIRCIA?

    The Cyber Incident Reporting for Critical Infrastructure Act of 2022. It requires covered entities to report covered cyber incidents to CISA within 72 hours and ransom payments within 24 hours, but only once CISA's final rule takes effect, which had not happened as of November 2026.[3][4]

    What are the NIS2 reporting deadlines?

    An early warning within 24 hours of becoming aware of a significant incident, an incident notification within 72 hours, and a final report within one month of the notification.[2]

    Is a data breach report under GDPR the same thing?

    It is a separate duty. GDPR requires notifying the data protection authority of a personal data breach within 72 hours where feasible, and telling affected people without undue delay when the risk to them is high.[14][15]

    What happens if an EU company does not report?

    NIS2 requires member states to set maximum fines for breaches of its risk-management and reporting rules of at least €10 million or 2% of worldwide turnover for essential entities, and €7 million or 1.4% for important entities.[12]

    Sources

    · 16 claims from 7 publishers

    Each numbered claim is a statement we checked against the sources listed with it. Tap a number in the text to see its sources in place.

    1. [1]

      An Item 1.05 Form 8-K is generally due four business days after a company determines an incident is material, and may be delayed if the US Attorney General finds immediate disclosure would pose a substantial risk to national security or public safety. confirmedas of 2023-07-26

    2. [2]

      The EU's NIS2 Directive requires essential and important entities to send an early warning within 24 hours of becoming aware of a significant incident, an incident notification with an initial assessment within 72 hours, and a final report within one month of the notification. confirmedas of 2026-11-08

    3. [3]

      The Cyber Incident Reporting for Critical Infrastructure Act of 2022 requires covered entities to report covered cyber incidents to CISA within 72 hours of reasonably believing one occurred, and ransom payments within 24 hours of payment. confirmedas of 2026-11-08

    4. [4]

      As of November 2026 CISA says it held four CIRCIA town hall meetings from 15 to 18 June 2026, that multiple funding lapses affected its rulemaking, and that it continues to work on the final rule; reporting will not be required until the final rule takes effect, though CISA encourages entities to share incident information voluntarily before then. confirmedas of 2026-11-08

    5. [5]

      SEC rules adopted in July 2023 require public companies to disclose any cybersecurity incident they determine to be material under Item 1.05 of Form 8-K, describing its nature, scope, timing and material or reasonably likely material impact. confirmedas of 2023-07-26

    6. [6]

      Under the SEC's 2023 rules, a company must determine whether a cybersecurity incident is material without unreasonable delay after discovering it. confirmedas of 2026-11-08

    7. [7]

      If required information is not yet known when an Item 1.05 8-K is due, the company must say so in the filing and later file an amendment. confirmedas of 2026-11-08

    8. [8]

      Companies other than smaller reporting companies had to start complying with Item 1.05 on 18 December 2023, and smaller reporting companies on 15 June 2024. confirmedas of 2026-11-08

    9. [9]

      CISA published its CIRCIA proposed rule on 4 April 2024, estimating that about 316,244 entities would be covered and that the rule would cost $2.6 billion over the analysis period. confirmedas of 2026-11-08

    10. [10]

      StopRansomware.gov says victims should report to federal law enforcement through IC3 or a Secret Service field office, and can contact CISA for technical help or to share information. confirmedas of 2026-11-07

      • Stop Ransomware · CISA (StopRansomware.gov) · Primary source (retrieved 2026-11-07)
    11. [11]

      NIS2 required EU member states to adopt and publish national measures by 17 October 2024 and apply them from 18 October 2024. confirmedas of 2026-11-08

    12. [12]

      Under NIS2, member states must make essential entities that breach the risk-management or reporting rules liable to maximum fines of at least €10 million or 2% of worldwide annual turnover, whichever is higher, and important entities at least €7 million or 1.4%. confirmedas of 2026-11-08

    13. [13]

      The EU's Digital Operational Resilience Act, which applies from 17 January 2025, requires financial entities to report major ICT-related incidents to their competent authority. confirmedas of 2026-11-08

    14. [14]

      Under Article 33 of the EU GDPR, a controller must notify the competent supervisory authority of a personal data breach without undue delay and, where feasible, within 72 hours of becoming aware of it, unless the breach is unlikely to result in a risk to people's rights and freedoms. confirmedas of 2026-11-07

    15. [15]

      Under Article 34 of the GDPR, when a breach is likely to result in a high risk to people's rights and freedoms, the controller must tell the affected people without undue delay. confirmedas of 2026-11-07

    16. [16]

      According to the FTC, all US states, the District of Columbia, Puerto Rico and the Virgin Islands have laws requiring notification of security breaches involving personal information. confirmedas of 2026-11-07

    Revision history (1)
    1. Page created.

    Created Nov 8, 2026. Last reviewed by an editor on Nov 8, 2026. Next scheduled review: Feb 8, 2027.

    Cite this page

    "Cyber-incident reporting rules: SEC 8-K, CIRCIA, NIS2 and DORA." ContentLora, updated Nov 8, 2026. https://contentlora.com/explain/cyber-incident-reporting-rules-explained

    Spotted an error? Suggest a correction or emailcorrections@contentlora.com.