Incident reporting clocks: from 60 days to hours, regulator by regulator

US cyber incident reporting deadlines for banks, credit unions, health organizations, listed companies, contractors and agencies, dated and compared as of November 16, 2026, and how they shortened.

The clocks, rule by rule

This report traces how long a US bank, credit union, health organization, listed company, defense contractor or federal agency has to tell a regulator about a cyber incident. Each row below was read from the rule text, the regulator's own page or the Federal Register, and every status is as checked on November 16, 2026. State breach notification laws are left out: we found no official compilation of all of them, and secondary summaries are not a source for this page. This is a description of the rules, not legal advice.

US cyber incident and breach reporting clocks, oldest first, as checked on November 16, 2026
RuleWho it coversClockClock starts atIn effectSources
HIPAA Breach Notification Rule, 45 CFR 164.404 and 164.408 [1] [2]HIPAA covered entities (business associates notify the covered entity on the same 60-day outer limit) [1] [2]60 calendar days to notify individuals; HHS at the same time if 500 or more people are affected, otherwise within 60 days after year end [1] [2]Discovery of a breach of unsecured protected health informationInterim final rule effective September 23, 2009 [1] [2]Sources [1] [2]
DFARS 252.204-7012, cyber incident reporting [3] [4]Defense contractors with covered contractor information systems72 hours [3] [4]Discovery of a cyber incident; report to DoD through DIBNetClause first issued, with the 72-hour clock, in a final rule effective November 18, 2013; rewritten by an interim rule effective August 26, 2015; current version dated May 2024 [23] [4] [3]Sources [3] [4] [23]
NYDFS 23 NYCRR 500.17(a), as adopted [5]Persons operating under a license, registration, charter, certificate, permit or similar authorization under New York's Banking Law, Insurance Law or Financial Services Law72 hours [5]Determination that a cybersecurity event has occurred that must be reported to a supervisory body or is reasonably likely to cause material harmEffective March 1, 2017 [5]Sources [5]
CISA Federal Incident Notification Guidelines (FISMA)Federal civilian executive branch agenciesOne hour to CISA; major incidents to Congress within 7 days of identification [7]Identification by the agency's top-level CSIRT, security operations center or IT departmentThe 2017 guidelines, being updated for a new reporting form published November 9, 2026 [7]Sources [7]
Computer-security incident notification rule, 12 CFR 53.3 (OCC), 12 CFR 225.302 (Federal Reserve), 12 CFR 304.23 (FDIC) [8] [9]Banking organizations supervised by the three agencies; bank service providers notify customers when services are disrupted for four or more hours36 hours to the primary federal regulator; service providers as soon as possible [8] [9]Determination that a notification incident has occurredEffective April 1, 2022; compliance May 1, 2022 [8] [9]Sources [8] [9]
NCUA cyber incident report, 12 CFR 748.1(c) [10] [11]Federally insured credit unions72 hours [10] [11]Reasonable belief that a reportable cyber incident occurred, or notice from a third party, whichever is soonerEffective September 1, 2023 [10] [11]Sources [10] [11]
SEC Form 8-K Item 1.05 [12] [13]Companies that file current reports under the Securities Exchange Act of 1934 [12] [13]Four business days; the Attorney General can authorize delaysDetermination that the incident is material, which must be made without unreasonable delay after discoveryAmendments effective September 5, 2023 [12] [13]Sources [12] [13]
NYDFS 23 NYCRR 500.17(a) and (c), second amendment [6]Same NYDFS covered entities72 hours for incidents; 24 hours for notice of an extortion payment and 30 days for a written explanation [6]Determination of a cybersecurity incident (now including one at an affiliate or third-party service provider); the payment itself for extortionSecond amendment effective November 1, 2023, with 30 days to comply with the new 500.17 duties [6]Sources [6]
SEC Regulation S-P, 17 CFR 248.30 [14] [15]Broker-dealers, investment companies, registered investment advisers, funding portals and transfer agents30 days to notify affected individuals; service providers notify the institution within 72 hours [14] [15]Becoming aware that unauthorized access to or use of customer information has occurred or is reasonably likely to have occurred (individuals); becoming aware of a breach in security (service providers)Amendments effective August 2, 2024 [14] [15]Sources [14] [15]
CIRCIA, 6 U.S.C. 681b [16] [17]Covered entities in critical infrastructure sectors, as the final rule will define them72 hours for covered cyber incidents; 24 hours for ransom payments [16] [17]Reasonable belief a covered incident occurred; making a ransom paymentNot in effect as of November 16, 2026: proposed April 4, 2024, final rule not issued [16] [17]Sources [16] [17]
FAR Case 2021-017, proposed clause 52.239-ZZ [18] [19]Federal contractors supplying products or services that contain information and communications technology8 hours to CISA, then updates every 72 hours [18] [19]Discovery that a security incident may have occurredProposed October 3, 2023; final rule targeted for September 2026, none in the Federal Register as checked on November 16, 2026 [18] [19]Sources [18] [19]
FAR Case 2017-016, proposed clause 52.204-XX [20]Federal contractors handling controlled unclassified information8 hours to the agency [20]Discovery of a suspected or confirmed CUI incidentProposed January 15, 2025 [20]; no final rule in the Federal Register as checked on November 16, 2026Sources [20]
HIPAA Security Rule proposal, 45 CFR 164.314 [21] [22]Business associates of HIPAA covered entities24 hours to report activation of a contingency plan to the covered entity [21] [22]Activation of the contingency planProposed January 6, 2025; listed as a long-term action with final action targeted for July 2027 [21] [22]Sources [21] [22]

From weeks to hours in under fifteen years

The oldest clock in the table is the HIPAA breach rule, which took effect on September 23, 2009 and gives a covered entity up to 60 calendar days after discovery to notify affected individuals [1] [2]. Sixty days is 1,440 hours [1]. The next generation of rules measured the outer limit in hours instead. The defense contract clause first issued in 2013 required reports within 72 hours of discovery [23], and its current version defines rapid reporting the same way [3]. New York's financial regulator set 72 hours from the determination that a reportable event occurred when Part 500 took effect on March 1, 2017 [5]. CISA's 2017 guidelines ask federal civilian executive branch agencies to report qualifying incidents within one hour of identification [7].

The federal banking agencies went below 72 hours in 2022: banking organizations must notify their primary federal regulator no later than 36 hours after determining that a notification incident has occurred, under a rule effective April 1, 2022 [8] [9]. That is half the 72-hour clocks that came before it, and 1,404 hours shorter than the HIPAA outer limit [1] [5] [8]. In 2023 three more clocks arrived. Federally insured credit unions must report within 72 hours from September 1, 2023 [10] [11]. Companies that file reports under the Securities Exchange Act of 1934 must file Form 8-K Item 1.05 within four business days of deciding an incident is material, under amendments effective September 5, 2023 [12] [13]. And New York's second amendment, effective November 1, 2023, added a 24-hour notice for any extortion payment, with a written explanation of why it was paid within 30 days [6].

The proposals in the pipeline go shorter again. A 2023 proposed FAR clause would have federal contractors report to CISA within 8 hours of discovering that a security incident may have occurred, then update every 72 hours [18]. A January 2025 FAR proposal on controlled unclassified information uses the same 8-hour window for reports to the agency [20]. The HIPAA Security Rule proposal of January 6, 2025 would require business associates to tell covered entities within 24 hours of activating a contingency plan [21]. All three were still proposals, with no final rule in the Federal Register, as checked on November 16, 2026 [19] [22].

Moraph's view

The trend is real but uneven. Health care is the outlier. The binding health clock is still the 60-day breach deadline from 2009, while banks, credit unions and New York licensees work to 36 or 72 hours. The direction of travel in health is visible only in a proposal, and its final action is listed for 2027 at the earliest. We expect health organizations to keep facing the longest regulatory clock in this table through 2027, and to feel the shorter clocks mainly through contracts with banks, payers and federal agencies.

What starts the clock matters as much as its length

Hour counts invite comparison, but the triggers differ, and the trigger decides how much time an organization really has. The HIPAA clock runs from discovery, which the rule ties to the first day a breach is known, or would have been known with reasonable diligence, to a workforce member or agent [1]. The defense clause also runs from discovery, so its 72 hours start early [3]. The bank rule runs for 36 hours from the organization's own determination that a notification incident has occurred, and the rule defines that kind of incident by material disruption to operations, business lines or financial stability [8].

The SEC clock is the clearest case of a short deadline behind a judgment call: four business days, starting only when the company determines the incident is material, a determination the form says must be made without unreasonable delay after discovery [12]. The NCUA rule starts from a reasonable belief that a reportable incident occurred, and for an incident at a third party, from notice by that third party if sooner [10]. New York's extortion clock runs 24 hours from the payment itself, with no determination step at all [6]. CISA's one-hour federal clock starts when the agency's top-level incident response team, security operations center or IT department identifies the incident [7].

Moraph's view

The practical clock is the time from the first alert to the decision the rule names. A team that takes three days to decide an incident is a notification incident has not met a 36-hour rule in any meaningful sense, even if it files within 36 hours of that decision. Supervisors are likely to look at how long the decision took, so the timestamp of each determination, and who made it, deserves the same care as the filing.

One incident, several clocks

The rules overlap, and one event can start several of them at once. A hypothetical case shows how. A publicly traded bank holding company with a New York-chartered bank suffers ransomware that disrupts customer services and pays a ransom. Its banking regulator expects notice within 36 hours of the notification incident determination [8] [9]. NYDFS expects notice within 72 hours of determining a cybersecurity incident occurred, and notice of the extortion payment within 24 hours of paying [6]. If the company decides the incident is material, it has four business days to file Form 8-K Item 1.05 [12]. If a broker-dealer affiliate's customer information was accessed, Regulation S-P adds a 30-day clock to notify affected individuals [14]. When CIRCIA's final rule takes effect, a covered entity in the group will add a 72-hour incident report and a 24-hour ransom payment report to CISA [16].

The statute behind CIRCIA anticipates this overlap. CISA says that, once the rule is in effect, federal agencies that receive incident reports will share them with CISA within 24 hours of receipt [16]. The NCUA's own rule also reaches incidents caused by a compromise of a credit union service organization, cloud provider or other third-party host [10], and the bank rule makes service providers tell their bank customers as soon as possible about disruptions lasting four or more hours [8]. Third parties now sit inside the regulated clock, not after it.

Where the pending rules stand on November 16, 2026

CIRCIA is the largest open item. CISA proposed its rule on April 4, 2024, and its page says CISA continues to work on the final rule, that multiple funding lapses affected the rulemaking, and that no organization is required to submit CIRCIA reports until the final rule takes effect [16]. The 2026 Unified Agenda listed the final rule for September 2026 and a statutory final rule deadline of October 4, 2025; both dates have passed with no final rule [17]. CISA held four town hall meetings between June 15 and June 18, 2026 [16].

The FAR incident reporting rule, FAR Case 2021-017, was also targeted for a final rule in September 2026 [19]; as checked on November 16, 2026, a Federal Register search found no final rule from that case. The HIPAA Security Rule proposal sits in the long-term section of the agenda with final action listed for July 2027 [22]. CISA says its 2017 federal guidelines are being updated to support a new incident reporting form published November 9, 2026, under the expected name Federal Incident Reporting Requirements [7].

Moraph's view

The shortening has paused at the rule level but not in practice. No rule in this table took effect in 2025 or 2026, yet the 2024 Regulation S-P amendments, the November 2026 federal reporting form and three pending proposals all point the same way. When CIRCIA's final rule does arrive, its statutory 72-hour limit will sit beside a 36-hour bank clock and a 24-hour ransom clock in New York, and the shortest applicable clock, not the federal default, will set the pace for any organization covered by more than one.

What this means for you

  • Banks and bank holding companies: Keep one dated decision record per incident that serves the 36-hour federal clock [8], the NYDFS 72-hour and 24-hour extortion clocks [6] and, for listed companies, the Form 8-K materiality decision [12], so each filing can show when its trigger was reached.
  • Credit unions: Build third-party notice into vendor contracts and runbooks, because the NCUA clock can start on notice from a third party [10].
  • Health systems and their business associates: Plan to the 60-day HIPAA outer limit as a ceiling, not a target, since notice is due without unreasonable delay [1], and follow the proposed 24-hour contingency plan notice [21] through to its final action, listed for July 2027 [22].
  • Federal contractors and agencies: Run to the 72-hour DFARS clock from discovery today [3], track the 8-hour FAR proposals [18] [20] and, for agencies, the update to CISA's one-hour guidelines and the new reporting form [7].
  • Incident response leads in any sector: Map which clocks one incident can start, keep the shortest at the top of the playbook, and add CIRCIA's 72-hour and 24-hour reports once CISA publishes a final rule [16].

Moraph predictions

Every prediction is Moraph's view, not a fact. Each has a date, a confidence level (70% means we expect to be wrong about three times in ten) and a test anyone can apply. We score them on this page when the date comes and never remove one. How we make and score predictions.

  1. P1 By Confidence 55% Open

    CISA will publish the CIRCIA final rule in the Federal Register by December 31, 2027.

    How we will check: Search the Federal Register for a document of type Rule from CISA under RIN 1670-AA04 published on or before December 31, 2027.

    Basis: CISA says it continues to work on the final rule and that funding lapses affected the rulemaking [16]; the Unified Agenda target of September 2026 and the statutory deadline of October 4, 2025 have both passed [17].

  2. P2 By Confidence 85% Open

    If a CIRCIA final rule is published by June 30, 2028, it will set the covered cyber incident report deadline at 72 hours and the ransom payment report deadline at 24 hours.

    How we will check: Read the reporting deadlines in the final rule's regulatory text (proposed as 6 CFR part 226). If no final rule is published by the date, the prediction is scored wrong.

    Basis: CISA describes the statutory deadlines as 72 hours from reasonable belief and 24 hours from a ransom payment [16]; the rule is listed at the final rule stage [17].

  3. P3 By Confidence 60% Open

    No final rule from FAR Case 2021-017 (the 8-hour contractor incident reporting proposal) will be published in the Federal Register by June 30, 2027.

    How we will check: Search the Federal Register for a final rule citing FAR Case 2021-017 or RIN 9000-AO34 published on or before June 30, 2027.

    Basis: The rule was proposed on October 3, 2023 [18] and its September 2026 final rule target [19] passed with no final rule in the Federal Register as checked on November 16, 2026.

  4. P4 By Confidence 70% Open

    HHS will not publish a final HIPAA Security Rule under RIN 0945-AA22 in the Federal Register by July 31, 2027.

    How we will check: Search the Federal Register for a final rule under RIN 0945-AA22 published on or before July 31, 2027.

    Basis: The proposal of January 6, 2025 [21] is listed as a long-term action with final action targeted for July 2027 [22].

  5. P5 By Confidence 85% Open

    The 36-hour outer limit in 12 CFR 53.3 will be unchanged on December 31, 2028.

    How we will check: Read 12 CFR 53.3 in the eCFR on December 31, 2028 and confirm it still says no later than 36 hours after the determination.

    Basis: The deadline has stood since the rule took effect on April 1, 2022 [8] [9].

Facts on this page link to their sources. Text marked "Moraph's view", and every prediction, is our own analysis, not a fact or advice. Methodology.

Spotted an error? Tell us and we will check it and correct the piece where needed.

  • incident reporting
  • breach notification
  • 36-hour rule
  • NYDFS Part 500
  • Form 8-K Item 1.05
  • NCUA
  • CIRCIA
  • DFARS 252.204-7012
  • HIPAA
  • FISMA