Incident and breach reporting deadlines compared
| Rule | Trigger | Clock starts | Deadline | Who to notify | What to include | Who it applies to | Citation |
|---|---|---|---|---|---|---|---|
| SEC Form 8-K, Item 1.051 | TriggerA cybersecurity incident that the company determines to be material1 | Clock startsWhen the company determines the incident is material. That determination must be made without unreasonable delay after discovery.1 | DeadlineWithin four business days. If the U.S. Attorney General determines that disclosure poses a substantial risk to national security or public safety and notifies the SEC, disclosure may be delayed up to 30 days, a further 30 days and, in extraordinary circumstances, a final 60 days.1 | Who to notifyThe SEC, by filing Form 8-K1 | What to includeThe material aspects of the nature, scope and timing of the incident, and its material impact or reasonably likely material impact on the company. Information not yet determined or available goes in an amended 8-K within four business days after it is determined or becomes available.1 | Who it applies toCompanies that file current reports on Form 8-K under Section 13 or 15(d) of the Securities Exchange Act of 19341 | CitationForm 8-K, General Instruction B.1 and Item 1.051 |
| Federal banking agencies' computer-security incident notification rule2 | TriggerA notification incident: a computer-security incident that has materially disrupted or degraded, or is reasonably likely to, the organization's ability to carry out banking operations or deliver banking products and services to a material portion of its customers; business lines whose failure would cause a material loss of revenue, profit or franchise value; or operations whose failure would threaten U.S. financial stability2 | Clock startsWhen the banking organization determines that a notification incident has occurred2 | DeadlineAs soon as possible and no later than 36 hours3 | Who to notifyThe appropriate OCC supervisory office or OCC-designated point of contact, by email, telephone or other similar methods the OCC may prescribe (the Federal Reserve and FDIC rules name their own points of contact)2 | What to includeThe rule does not list required contents; it sets the method (email, telephone or similar) and the deadline2 | Who it applies toNational banks, federal savings associations and federal branches and agencies of foreign banks under the OCC rule; the Federal Reserve and FDIC versions cover the banking organizations those agencies supervise2 | Citation12 CFR 53.3; 12 CFR 225.302; 12 CFR 304.232 |
| Bank service provider duty under the same rule4 | TriggerA computer-security incident that has materially disrupted or degraded, or is reasonably likely to, covered services to a banking organization for four or more hours. Scheduled maintenance, testing or updates already communicated do not count.4 | Clock startsWhen the bank service provider determines it has experienced such an incident4 | DeadlineAs soon as possible (no fixed number of hours)4 | Who to notifyAt least one bank-designated point of contact at each affected banking organization customer; if none was given, the CEO and CIO or two people of comparable responsibility4 | What to includeThe rule does not list required contents4 | Who it applies toBank service companies and other persons that perform services subject to the Bank Service Company Act for banking organizations4 | Citation12 CFR 53.4; 12 CFR 225.303; 12 CFR 304.244 |
| NYDFS Cybersecurity Regulation, 23 NYCRR 500.175 | TriggerA cybersecurity incident at the covered entity, its affiliates or a third-party service provider that impacts the covered entity and requires it to notify a government, self-regulatory or other supervisory body, is reasonably likely to materially harm a material part of normal operations, or deploys ransomware in a material part of its systems. Separately, any extortion payment made in connection with a cybersecurity event.5 | Clock startsWhen the covered entity determines that a cybersecurity incident has occurred; for extortion, when the payment is made5 | DeadlineAs promptly as possible and no later than 72 hours. Extortion payment: notice within 24 hours and a written explanation within 30 days.5 | Who to notifyThe New York Superintendent of Financial Services, electronically on the DFS form5 | What to includeThe DFS form, then any information DFS requests, with a continuing duty to update on material changes. For extortion: why payment was needed, alternatives considered and sanctions-compliance diligence.5 | Who it applies toPersons operating under a license, registration, charter or similar authorization under New York's Banking, Insurance or Financial Services Law5 | Citation23 NYCRR 500.1(e), 500.1(g), 500.17(a) and (c)5 |
| HIPAA Breach Notification Rule6 | TriggerA breach of unsecured protected health information6 | Clock startsDiscovery: the first day the breach is known, or would have been known with reasonable diligence, to anyone in the workforce or an agent (other than the person who committed it)6 | DeadlineIndividuals: without unreasonable delay and no later than 60 calendar days. HHS: at the same time as individuals if 500 or more are affected; otherwise within 60 days after the end of the calendar year. Media: no later than 60 calendar days. Law enforcement can require a delay.6 | Who to notifyAffected individuals; the Secretary of HHS; prominent media outlets when more than 500 residents of a state or jurisdiction are affected. A business associate notifies the covered entity within 60 days.6 | What to includeWhat happened with dates, the types of information involved, steps individuals should take, what the entity is doing, and contact details including a toll-free number, email, website or postal address. Plain language.6 | Who it applies toHIPAA covered entities and their business associates6 | Citation45 CFR 164.404, 164.406, 164.408, 164.410, 164.4126 |
| FTC Health Breach Notification Rule7 | TriggerA breach of security of unsecured PHR identifiable health information: acquisition without the individual's authorization7 | Clock startsDiscovery: the first day the breach is known or reasonably should have been known7 | DeadlineIndividuals and media: without unreasonable delay and no later than 60 calendar days. FTC: at the same time as individuals if 500 or more are affected; otherwise in an annual log within 60 days after year end.7 | Who to notifyAffected U.S. individuals; the FTC; prominent media when 500 or more residents of a state or jurisdiction are affected. A third party service provider notifies the vendor or PHR related entity.7 | What to includeWhat happened with dates and, where known, who acquired the data; the types of information; steps individuals should take; what the entity is doing; at least two contact methods. Plain language.7 | Who it applies toVendors of personal health records, PHR related entities and their third party service providers. Not HIPAA covered entities or business associates acting as such.7 | Citation16 CFR 318.1-318.67 |
| FTC Safeguards Rule notification (in effect since May 13, 2024)9 | TriggerA notification event involving the information of at least 500 consumers: acquisition of unencrypted customer information without authorization (information counts as unencrypted if the encryption key was accessed by an unauthorized person)8 | Clock startsDiscovery: the first day the event is known to the institution, including to any employee, officer or other agent other than the person who committed it8 | DeadlineAs soon as possible and no later than 30 days after discovery8 | Who to notifyThe Federal Trade Commission, electronically on the form on ftc.gov8 | What to includeName and contact details; types of information involved; date or date range if possible to determine; number of consumers affected or potentially affected; a general description; and whether a law enforcement official has given a written determination that notifying the public would impede a criminal investigation or damage national security8 | Who it applies toFinancial institutions under FTC jurisdiction, such as mortgage lenders and brokers, payday lenders, finance companies, tax preparation firms and investment advisers not required to register with the SEC12 | Citation16 CFR 314.1, 314.2(m), 314.4(j), 314.58 |
| NCUA cyber incident report10 | TriggerA reportable cyber incident: a substantial cyber incident causing substantial loss of confidentiality, integrity or availability, disruption from a cyberattack, or disruption or unauthorized access through a compromised third party or supply chain10 | Clock startsWhen the credit union reasonably believes it has experienced a reportable cyber incident. For an incident caused through a compromised third party or supply chain, within 72 hours of being notified by the third party, whichever is sooner.10 | DeadlineAs soon as possible and no later than 72 hours10 | Who to notifyThe NCUA-designated point of contact, by email, telephone or similar method10 | What to includeThe rule does not list required contents10 | Who it applies toFederally insured credit unions10 | Citation12 CFR 748.1(c)10 |
| CIRCIA (Cyber Incident Reporting for Critical Infrastructure Act of 2022)11 | TriggerUnder the statute: covered cyber incidents and ransom payments by covered entities. The details are set by CISA's rule, which is not final.11 | Clock startsUnder the statute: when the entity reasonably believes a covered cyber incident occurred, or when it makes a ransom payment11 | DeadlineNot yet required as of 2026-11-14. The statute directs CISA's rule to require reports within 72 hours (incidents) and 24 hours (ransom payments). CISA proposed the rule on April 4, 2024 (89 FR 23644), held town halls on June 15-18, 2026 and says it continues to work on the final rule. Reporting is not required until the final rule takes effect.11 | Who to notifyCISA11 | What to includeSet by the final rule; not yet issued as of 2026-11-1411 | Who it applies toCovered entities, as the final rule will define them11 | CitationCIRCIA; CISA NPRM, 89 FR 2364411 |
| Federal agency incident notification to CISA (FISMA)13 | TriggerAn information security incident where the confidentiality, integrity or availability of a federal information system of a civilian Executive Branch agency is potentially compromised13 | Clock startsWhen the agency's top-level incident response team, security operations center or IT department identifies the incident13 | DeadlineWithin one hour. Major incidents (as defined by OMB) are also reported to Congress within 7 days of identification. As of 2026-11-14 CISA says these 2017 guidelines are being updated for a new reporting form published November 9, 2026.13 | Who to notifyCISA; Congress for major incidents13 | What to includeFunctional impact, information impact, recoverability, when first detected, number of systems, records and users affected, network location, and a point of contact13 | Who it applies toFederal civilian Executive Branch agencies13 | CitationFISMA; CISA Federal Incident Notification Guidelines13 |
License: CC BY 4.0. Underlying government texts are public domain or under their own terms. Attribute "Moraph Insights" with a link to the page.
Method
We compared the reporting duty in each rule's own text: the eCFR for federal regulations, the SEC's Form 8-K instructions, the NYDFS copy of Part 500, and CISA's own pages for CIRCIA status and federal agency reporting. Each cell was checked against its source on 2026-11-13 and re-checked on 2026-11-14. Cells say only what the source says; where a rule lists no required contents, the cell says so. State breach notification laws were left out (see Omitted). This table explains the rules; it is not legal advice.
Omitted
What was left out, and why.
- A row left out: No single primary source summarizes the 50 state breach notification laws; a summary row would rest on secondary compilations.
Notes
- The OCC, Federal Reserve and FDIC rules use the same wording; the banking row cites the OCC text, and the citation column lists all three.
- NYDFS publishes the amended Part 500 on its website with a note that its copy is not an official version.
- CIRCIA report contents will be set by the final rule; the contents in CISA's 2024 proposal are not summarized, so a proposal is not shown as a requirement.
Sources
- U.S. Securities and Exchange Commission. Form 8-K, General Instructions and Item 1.05 (Material Cybersecurity Incidents). Checked .
- Office of the Comptroller of the Currency. 12 CFR part 53, Computer-Security Incident Notification (OCC). Checked .
- Board of Governors of the Federal Reserve System. 12 CFR part 225, subpart N, Computer-Security Incident Notification (Federal Reserve). Checked .
- Federal Deposit Insurance Corporation. 12 CFR part 304, subpart C, Computer-Security Incident Notification (FDIC). Checked .
- New York State Department of Financial Services. 23 NYCRR Part 500, Cybersecurity Requirements for Financial Services Companies, Second Amendment text (DFS copy; DFS notes it is not an official version). Checked .
- U.S. Department of Health and Human Services. 45 CFR part 164, subpart D, Notification in the Case of Breach of Unsecured Protected Health Information (164.400-164.414). Checked .
- Federal Trade Commission. 16 CFR part 318, Health Breach Notification Rule. Checked .
- Federal Trade Commission. 16 CFR 314.4(j), Standards for Safeguarding Customer Information: notification to the FTC. Checked .
- Federal Trade Commission. 16 CFR 314.5, Effective date. Checked .
- National Credit Union Administration. 12 CFR 748.1(c), Cyber incident report. Checked .
- Cybersecurity and Infrastructure Security Agency. Cyber Incident Reporting for Critical Infrastructure Act of 2022 (CIRCIA). Checked .
- Federal Trade Commission. 16 CFR 314.1, Purpose and scope. Checked .
- Cybersecurity and Infrastructure Security Agency. Federal Incident Notification Guidelines. Checked .
How we source and check every fact: Editorial standards · Corrections
Last reviewed .
Spotted an error? Tell us and we will check it and correct the table where needed.