{
 "page": "https://insights.moraph.com/compare/incident-reporting-clocks",
 "csv": "https://insights.moraph.com/compare/incident-reporting-clocks.csv",
 "publisher": "Moraph",
 "license": "https://creativecommons.org/licenses/by/4.0/",
 "license_note": "License: CC BY 4.0. Underlying government texts are public domain or under their own terms.",
 "attribution": "Moraph Insights, https://insights.moraph.com/compare/incident-reporting-clocks",
 "slug": "incident-reporting-clocks",
 "title": "Incident and breach reporting deadlines compared",
 "sector": "Cross-sector",
 "lens": "Security & Resilience",
 "in_short": "The clocks run from one hour (federal civilian agencies to CISA) and 36 hours (banks to their federal regulator) to 72 hours (NYDFS and NCUA), four business days (SEC Form 8-K Item 1.05), 30 days (FTC Safeguards Rule) and 60 calendar days (HIPAA and the FTC Health Breach Notification Rule). Most clocks start when the organization determines or discovers the incident, not when it began. CIRCIA reporting to CISA is not yet required as of 2026-11-14, because the final rule has not been issued.",
 "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.",
 "published": "2026-11-13",
 "last_reviewed": "2026-11-14",
 "columns": [
  {
   "id": "regime",
   "label": "Rule"
  },
  {
   "id": "trigger",
   "label": "Trigger"
  },
  {
   "id": "clock_starts",
   "label": "Clock starts"
  },
  {
   "id": "deadline",
   "label": "Deadline"
  },
  {
   "id": "notify",
   "label": "Who to notify"
  },
  {
   "id": "content",
   "label": "What to include"
  },
  {
   "id": "applies_to",
   "label": "Who it applies to"
  },
  {
   "id": "citation",
   "label": "Citation"
  }
 ],
 "rows": [
  {
   "id": "sec-8k-105",
   "cells": {
    "regime": {
     "text": "SEC Form 8-K, Item 1.05",
     "source": "s1",
     "checked": "2026-11-14"
    },
    "trigger": {
     "text": "A cybersecurity incident that the company determines to be material",
     "source": "s1",
     "checked": "2026-11-14"
    },
    "clock_starts": {
     "text": "When the company determines the incident is material. That determination must be made without unreasonable delay after discovery.",
     "source": "s1",
     "checked": "2026-11-14"
    },
    "deadline": {
     "text": "Within 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.",
     "source": "s1",
     "checked": "2026-11-14"
    },
    "notify": {
     "text": "The SEC, by filing Form 8-K",
     "source": "s1",
     "checked": "2026-11-14"
    },
    "content": {
     "text": "The 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.",
     "source": "s1",
     "checked": "2026-11-14"
    },
    "applies_to": {
     "text": "Companies that file current reports on Form 8-K under Section 13 or 15(d) of the Securities Exchange Act of 1934",
     "source": "s1",
     "checked": "2026-11-14"
    },
    "citation": {
     "text": "Form 8-K, General Instruction B.1 and Item 1.05",
     "source": "s1",
     "checked": "2026-11-14"
    }
   }
  },
  {
   "id": "bank-agencies-36h",
   "cells": {
    "regime": {
     "text": "Federal banking agencies' computer-security incident notification rule",
     "source": "s2",
     "checked": "2026-11-14"
    },
    "trigger": {
     "text": "A 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 stability",
     "source": "s2",
     "checked": "2026-11-14"
    },
    "clock_starts": {
     "text": "When the banking organization determines that a notification incident has occurred",
     "source": "s2",
     "checked": "2026-11-14"
    },
    "deadline": {
     "text": "As soon as possible and no later than 36 hours",
     "source": "s3",
     "checked": "2026-11-14"
    },
    "notify": {
     "text": "The 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)",
     "source": "s2",
     "checked": "2026-11-14"
    },
    "content": {
     "text": "The rule does not list required contents; it sets the method (email, telephone or similar) and the deadline",
     "source": "s2",
     "checked": "2026-11-14"
    },
    "applies_to": {
     "text": "National 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 supervise",
     "source": "s2",
     "checked": "2026-11-14"
    },
    "citation": {
     "text": "12 CFR 53.3; 12 CFR 225.302; 12 CFR 304.23",
     "source": "s2",
     "checked": "2026-11-14"
    }
   }
  },
  {
   "id": "bank-service-provider",
   "cells": {
    "regime": {
     "text": "Bank service provider duty under the same rule",
     "source": "s4",
     "checked": "2026-11-14"
    },
    "trigger": {
     "text": "A 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.",
     "source": "s4",
     "checked": "2026-11-14"
    },
    "clock_starts": {
     "text": "When the bank service provider determines it has experienced such an incident",
     "source": "s4",
     "checked": "2026-11-14"
    },
    "deadline": {
     "text": "As soon as possible (no fixed number of hours)",
     "source": "s4",
     "checked": "2026-11-14"
    },
    "notify": {
     "text": "At 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 responsibility",
     "source": "s4",
     "checked": "2026-11-14"
    },
    "content": {
     "text": "The rule does not list required contents",
     "source": "s4",
     "checked": "2026-11-14"
    },
    "applies_to": {
     "text": "Bank service companies and other persons that perform services subject to the Bank Service Company Act for banking organizations",
     "source": "s4",
     "checked": "2026-11-14"
    },
    "citation": {
     "text": "12 CFR 53.4; 12 CFR 225.303; 12 CFR 304.24",
     "source": "s4",
     "checked": "2026-11-14"
    }
   }
  },
  {
   "id": "nydfs-500-17",
   "cells": {
    "regime": {
     "text": "NYDFS Cybersecurity Regulation, 23 NYCRR 500.17",
     "source": "s5",
     "checked": "2026-11-14"
    },
    "trigger": {
     "text": "A 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.",
     "source": "s5",
     "checked": "2026-11-14"
    },
    "clock_starts": {
     "text": "When the covered entity determines that a cybersecurity incident has occurred; for extortion, when the payment is made",
     "source": "s5",
     "checked": "2026-11-14"
    },
    "deadline": {
     "text": "As promptly as possible and no later than 72 hours. Extortion payment: notice within 24 hours and a written explanation within 30 days.",
     "source": "s5",
     "checked": "2026-11-14"
    },
    "notify": {
     "text": "The New York Superintendent of Financial Services, electronically on the DFS form",
     "source": "s5",
     "checked": "2026-11-14"
    },
    "content": {
     "text": "The 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.",
     "source": "s5",
     "checked": "2026-11-14"
    },
    "applies_to": {
     "text": "Persons operating under a license, registration, charter or similar authorization under New York's Banking, Insurance or Financial Services Law",
     "source": "s5",
     "checked": "2026-11-14"
    },
    "citation": {
     "text": "23 NYCRR 500.1(e), 500.1(g), 500.17(a) and (c)",
     "source": "s5",
     "checked": "2026-11-14"
    }
   }
  },
  {
   "id": "hipaa-breach",
   "cells": {
    "regime": {
     "text": "HIPAA Breach Notification Rule",
     "source": "s6",
     "checked": "2026-11-14"
    },
    "trigger": {
     "text": "A breach of unsecured protected health information",
     "source": "s6",
     "checked": "2026-11-14"
    },
    "clock_starts": {
     "text": "Discovery: 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)",
     "source": "s6",
     "checked": "2026-11-14"
    },
    "deadline": {
     "text": "Individuals: 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.",
     "source": "s6",
     "checked": "2026-11-14"
    },
    "notify": {
     "text": "Affected 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.",
     "source": "s6",
     "checked": "2026-11-14"
    },
    "content": {
     "text": "What 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.",
     "source": "s6",
     "checked": "2026-11-14"
    },
    "applies_to": {
     "text": "HIPAA covered entities and their business associates",
     "source": "s6",
     "checked": "2026-11-14"
    },
    "citation": {
     "text": "45 CFR 164.404, 164.406, 164.408, 164.410, 164.412",
     "source": "s6",
     "checked": "2026-11-14"
    }
   }
  },
  {
   "id": "ftc-hbnr",
   "cells": {
    "regime": {
     "text": "FTC Health Breach Notification Rule",
     "source": "s7",
     "checked": "2026-11-14"
    },
    "trigger": {
     "text": "A breach of security of unsecured PHR identifiable health information: acquisition without the individual's authorization",
     "source": "s7",
     "checked": "2026-11-14"
    },
    "clock_starts": {
     "text": "Discovery: the first day the breach is known or reasonably should have been known",
     "source": "s7",
     "checked": "2026-11-14"
    },
    "deadline": {
     "text": "Individuals 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.",
     "source": "s7",
     "checked": "2026-11-14"
    },
    "notify": {
     "text": "Affected 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.",
     "source": "s7",
     "checked": "2026-11-14"
    },
    "content": {
     "text": "What 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.",
     "source": "s7",
     "checked": "2026-11-14"
    },
    "applies_to": {
     "text": "Vendors of personal health records, PHR related entities and their third party service providers. Not HIPAA covered entities or business associates acting as such.",
     "source": "s7",
     "checked": "2026-11-14"
    },
    "citation": {
     "text": "16 CFR 318.1-318.6",
     "source": "s7",
     "checked": "2026-11-14"
    }
   }
  },
  {
   "id": "ftc-safeguards-314-4j",
   "cells": {
    "regime": {
     "text": "FTC Safeguards Rule notification (in effect since May 13, 2024)",
     "source": "s9",
     "checked": "2026-11-14"
    },
    "trigger": {
     "text": "A 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)",
     "source": "s8",
     "checked": "2026-11-14"
    },
    "clock_starts": {
     "text": "Discovery: the first day the event is known to the institution, including to any employee, officer or other agent other than the person who committed it",
     "source": "s8",
     "checked": "2026-11-14"
    },
    "deadline": {
     "text": "As soon as possible and no later than 30 days after discovery",
     "source": "s8",
     "checked": "2026-11-14"
    },
    "notify": {
     "text": "The Federal Trade Commission, electronically on the form on ftc.gov",
     "source": "s8",
     "checked": "2026-11-14"
    },
    "content": {
     "text": "Name 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 security",
     "source": "s8",
     "checked": "2026-11-14"
    },
    "applies_to": {
     "text": "Financial 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 SEC",
     "source": "s13",
     "checked": "2026-11-14"
    },
    "citation": {
     "text": "16 CFR 314.1, 314.2(m), 314.4(j), 314.5",
     "source": "s8",
     "checked": "2026-11-14"
    }
   }
  },
  {
   "id": "ncua-748",
   "cells": {
    "regime": {
     "text": "NCUA cyber incident report",
     "source": "s10",
     "checked": "2026-11-14"
    },
    "trigger": {
     "text": "A 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 chain",
     "source": "s10",
     "checked": "2026-11-14"
    },
    "clock_starts": {
     "text": "When 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.",
     "source": "s10",
     "checked": "2026-11-14"
    },
    "deadline": {
     "text": "As soon as possible and no later than 72 hours",
     "source": "s10",
     "checked": "2026-11-14"
    },
    "notify": {
     "text": "The NCUA-designated point of contact, by email, telephone or similar method",
     "source": "s10",
     "checked": "2026-11-14"
    },
    "content": {
     "text": "The rule does not list required contents",
     "source": "s10",
     "checked": "2026-11-14"
    },
    "applies_to": {
     "text": "Federally insured credit unions",
     "source": "s10",
     "checked": "2026-11-14"
    },
    "citation": {
     "text": "12 CFR 748.1(c)",
     "source": "s10",
     "checked": "2026-11-14"
    }
   }
  },
  {
   "id": "circia",
   "cells": {
    "regime": {
     "text": "CIRCIA (Cyber Incident Reporting for Critical Infrastructure Act of 2022)",
     "source": "s11",
     "checked": "2026-11-14"
    },
    "trigger": {
     "text": "Under the statute: covered cyber incidents and ransom payments by covered entities. The details are set by CISA's rule, which is not final.",
     "source": "s11",
     "checked": "2026-11-14"
    },
    "clock_starts": {
     "text": "Under the statute: when the entity reasonably believes a covered cyber incident occurred, or when it makes a ransom payment",
     "source": "s11",
     "checked": "2026-11-14"
    },
    "deadline": {
     "text": "Not 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.",
     "source": "s11",
     "checked": "2026-11-14"
    },
    "notify": {
     "text": "CISA",
     "source": "s11",
     "checked": "2026-11-14"
    },
    "content": {
     "text": "Set by the final rule; not yet issued as of 2026-11-14",
     "source": "s11",
     "checked": "2026-11-14"
    },
    "applies_to": {
     "text": "Covered entities, as the final rule will define them",
     "source": "s11",
     "checked": "2026-11-14"
    },
    "citation": {
     "text": "CIRCIA; CISA NPRM, 89 FR 23644",
     "source": "s11",
     "checked": "2026-11-14"
    }
   }
  },
  {
   "id": "federal-agencies-cisa",
   "cells": {
    "regime": {
     "text": "Federal agency incident notification to CISA (FISMA)",
     "source": "s12",
     "checked": "2026-11-14"
    },
    "trigger": {
     "text": "An information security incident where the confidentiality, integrity or availability of a federal information system of a civilian Executive Branch agency is potentially compromised",
     "source": "s12",
     "checked": "2026-11-14"
    },
    "clock_starts": {
     "text": "When the agency's top-level incident response team, security operations center or IT department identifies the incident",
     "source": "s12",
     "checked": "2026-11-14"
    },
    "deadline": {
     "text": "Within 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.",
     "source": "s12",
     "checked": "2026-11-14"
    },
    "notify": {
     "text": "CISA; Congress for major incidents",
     "source": "s12",
     "checked": "2026-11-14"
    },
    "content": {
     "text": "Functional impact, information impact, recoverability, when first detected, number of systems, records and users affected, network location, and a point of contact",
     "source": "s12",
     "checked": "2026-11-14"
    },
    "applies_to": {
     "text": "Federal civilian Executive Branch agencies",
     "source": "s12",
     "checked": "2026-11-14"
    },
    "citation": {
     "text": "FISMA; CISA Federal Incident Notification Guidelines",
     "source": "s12",
     "checked": "2026-11-14"
    }
   }
  }
 ],
 "sources": [
  {
   "id": "s1",
   "title": "Form 8-K, General Instructions and Item 1.05 (Material Cybersecurity Incidents)",
   "publisher": "U.S. Securities and Exchange Commission",
   "url": "https://www.sec.gov/files/form8-k.pdf",
   "checked": "2026-11-14"
  },
  {
   "id": "s2",
   "title": "12 CFR part 53, Computer-Security Incident Notification (OCC)",
   "publisher": "Office of the Comptroller of the Currency",
   "url": "https://www.ecfr.gov/current/title-12/chapter-I/part-53",
   "checked": "2026-11-14"
  },
  {
   "id": "s3",
   "title": "12 CFR part 225, subpart N, Computer-Security Incident Notification (Federal Reserve)",
   "publisher": "Board of Governors of the Federal Reserve System",
   "url": "https://www.ecfr.gov/current/title-12/chapter-II/subchapter-A/part-225/subpart-N",
   "checked": "2026-11-14"
  },
  {
   "id": "s4",
   "title": "12 CFR part 304, subpart C, Computer-Security Incident Notification (FDIC)",
   "publisher": "Federal Deposit Insurance Corporation",
   "url": "https://www.ecfr.gov/current/title-12/part-304/subpart-C",
   "checked": "2026-11-14"
  },
  {
   "id": "s5",
   "title": "23 NYCRR Part 500, Cybersecurity Requirements for Financial Services Companies, Second Amendment text (DFS copy; DFS notes it is not an official version)",
   "publisher": "New York State Department of Financial Services",
   "url": "https://www.dfs.ny.gov/system/files/documents/2026/10/NYCRR-part-500-Cybersecurity-Regulation_1.pdf",
   "checked": "2026-11-14"
  },
  {
   "id": "s6",
   "title": "45 CFR part 164, subpart D, Notification in the Case of Breach of Unsecured Protected Health Information (164.400-164.414)",
   "publisher": "U.S. Department of Health and Human Services",
   "url": "https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-D",
   "checked": "2026-11-14"
  },
  {
   "id": "s7",
   "title": "16 CFR part 318, Health Breach Notification Rule",
   "publisher": "Federal Trade Commission",
   "url": "https://www.ecfr.gov/current/title-16/chapter-I/subchapter-C/part-318",
   "checked": "2026-11-14"
  },
  {
   "id": "s8",
   "title": "16 CFR 314.4(j), Standards for Safeguarding Customer Information: notification to the FTC",
   "publisher": "Federal Trade Commission",
   "url": "https://www.ecfr.gov/current/title-16/chapter-I/subchapter-C/part-314/section-314.4",
   "checked": "2026-11-14"
  },
  {
   "id": "s9",
   "title": "16 CFR 314.5, Effective date",
   "publisher": "Federal Trade Commission",
   "url": "https://www.ecfr.gov/current/title-16/chapter-I/subchapter-C/part-314/section-314.5",
   "checked": "2026-11-14"
  },
  {
   "id": "s10",
   "title": "12 CFR 748.1(c), Cyber incident report",
   "publisher": "National Credit Union Administration",
   "url": "https://www.ecfr.gov/current/title-12/chapter-VII/subchapter-A/part-748/section-748.1",
   "checked": "2026-11-14"
  },
  {
   "id": "s11",
   "title": "Cyber Incident Reporting for Critical Infrastructure Act of 2022 (CIRCIA)",
   "publisher": "Cybersecurity and Infrastructure Security Agency",
   "url": "https://www.cisa.gov/topics/cyber-threats-and-advisories/information-sharing/cyber-incident-reporting-critical-infrastructure-act-2022-circia",
   "checked": "2026-11-14"
  },
  {
   "id": "s13",
   "title": "16 CFR 314.1, Purpose and scope",
   "publisher": "Federal Trade Commission",
   "url": "https://www.ecfr.gov/current/title-16/chapter-I/subchapter-C/part-314/section-314.1",
   "checked": "2026-11-14"
  },
  {
   "id": "s12",
   "title": "Federal Incident Notification Guidelines",
   "publisher": "Cybersecurity and Infrastructure Security Agency",
   "url": "https://www.cisa.gov/federal-incident-notification-guidelines",
   "checked": "2026-11-14"
  }
 ],
 "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."
 ],
 "omitted": [
  {
   "where": "state-breach-laws/all",
   "reason": "No single primary source summarizes the 50 state breach notification laws; a summary row would rest on secondary compilations."
  }
 ]
}
