2026California SB 446: 30-day consumer notice cap in force Jan 1, 2026 · New York § 899-aa: 30 days + mandatory NY DFS noticeintake@breachconnect.com
Home/Notification Laws/Federal & Sectoral Breach Reporting Deadlines
Federal & sectoral

Federal & Sectoral Breach Reporting Deadlines: HIPAA, FTC Safeguards, SEC, NYDFS, CIRCIA and GDPR

Federal and sectoral clocks overlap with state law and with each other — and they start from different events. Knowing which date starts which clock is the difference between compliant and late.

45 CFR §§ 164.400–414 · 16 CFR Part 314 · Form 8-K Item 1.05 · 23 NYCRR § 500.17 · 6 U.S.C. § 681b · GDPR Arts. 33–34

The six clocks at a glance

FrameworkAuthorityClock startsDeadlineScope
HIPAA Breach Notification Rule45 CFR §§ 164.400–414Date of discovery60 calendar daysCovered entities and business associates handling unsecured PHI
FTC Safeguards Rule16 CFR Part 314Date of discovery30 calendar daysNon-bank financial institutions when ≥500 consumers’ unencrypted customer information is acquired
SEC Cybersecurity DisclosureForm 8-K, Item 1.05Date of materiality determination4 business daysU.S. public companies and foreign private issuers once an incident is determined material
NYDFS Part 50023 NYCRR § 500.17Determination of cybersecurity event / ransom payment72 hours (24 hours for an extortion payment, plus 30-day written justification)NY-licensed banks, insurers, mortgage and financial entities
CIRCIA (CISA) Pending final rule6 U.S.C. § 681bReasonable belief of covered incident / ransom payment72 hours (24 hours for a ransom payment)Covered critical infrastructure entities (pending CISA final rule effective date)
EU GDPRArticles 33 & 34Becoming aware of the breach72 hours to the supervisory authority; data subjects without undue delay if high riskPersonal data of EU residents

Four different trigger events

The most common federal reporting error is not missing a deadline — it is starting the clock on the wrong date. Each framework counts from a different event:

  • Discovery — HIPAA and the FTC Safeguards Rule. A breach is treated as discovered on the first day it is known, or by exercising reasonable diligence would have been known, to the organization.
  • Materiality determination — SEC Form 8-K Item 1.05. The four-business-day clock starts when the registrant determines the incident is material, which must occur without unreasonable delay after discovery.
  • Determination of a cybersecurity event / reasonable belief — NYDFS Part 500 (72 hours) and CIRCIA (72 hours).
  • Ransom payment — NYDFS and CIRCIA both impose a separate 24-hour clock that starts when an extortion payment is made.
Document every date

Record the date and time of first detection, of the determination that a breach or cybersecurity event occurred, of any materiality determination, and of any payment. Regulators and plaintiffs will test each one.

HIPAA Breach Notification Rule — 60 calendar days

45 CFR §§ 164.400–414. Covered entities and business associates handling unsecured protected health information must notify affected individuals within 60 calendar days of discovery. When a breach affects 500 or more residents of a state or jurisdiction, HHS and prominent media outlets must also be notified within the same window. Breaches affecting fewer than 500 individuals are logged and reported to HHS annually, within 60 days after the end of the calendar year.

PHI encrypted consistent with HHS guidance is "secured" and falls outside the notification requirement — the federal analogue of the state encryption safe harbor. Business associates notify the covered entity, which typically owns the individual notices.

FTC Safeguards Rule — 30 calendar days

16 CFR Part 314. Non-bank financial institutions — mortgage brokers, auto dealers, non-SEC-registered advisers and similar businesses — must notify the Federal Trade Commission within 30 calendar days of discovery when unencrypted customer information of 500 or more consumers is acquired without authorization. The FTC notice is separate from, and in addition to, state consumer notices.

SEC Form 8-K Item 1.05 — 4 business days

U.S. public companies and foreign private issuers must disclose a material cybersecurity incident within 4 business days of determining it is material. The clock counts business days, so a Thursday determination produces a following-Wednesday deadline. The disclosure describes the nature, scope and timing of the incident and its material or reasonably likely material impact. Materiality is a legal judgment made with counsel and disclosure committees, which is why the determination date itself must be documented carefully.

NYDFS Part 500 — 72 hours and 24 hours

23 NYCRR § 500.17. NY-licensed banks, insurers, mortgage and other financial entities report a qualifying cybersecurity event to the Department of Financial Services within 72 hours of determination. If an extortion or ransom payment is made, DFS must be notified within 24 hours of the payment, followed by a written explanation of why payment was necessary — alternatives considered and sanctions diligence performed — within 30 days.

Separately, New York's general breach statute now sends consumer-breach notices to DFS even for non-licensed businesses (see the 30-day rules guide).

CIRCIA (CISA) — 72 hours and 24 hours, pending final rule

6 U.S.C. § 681b. The Cyber Incident Reporting for Critical Infrastructure Act will require covered critical infrastructure entities to report covered cyber incidents to CISA within 72 hours of reasonable belief, and ransom payments within 24 hours. Reporting obligations take effect with CISA's final rule; until its effective date, the clocks are a planning assumption rather than a live obligation. BreachConnect shows CIRCIA as pending final rule in the tracker.

EU GDPR — 72 hours

Articles 33 and 34. Where personal data of EU residents is involved, the controller notifies the competent supervisory authority within 72 hours of becoming aware of a breach, unless it is unlikely to result in a risk to individuals. Data subjects are notified without undue delay when the breach is likely to result in a high risk. U.S. companies with EU customers or employees frequently overlook this clock until day three.

Stacking federal and state clocks

Federal frameworks rarely preempt state breach statutes; they stack. A healthcare organization that is also publicly traded, with patients in California and New York, can face simultaneous SEC (4 business days from materiality), HIPAA (60 days), California (30 days) and New York (30 days plus four agencies) obligations. A sensible order of operations:

  1. Hours 0–24: engage breach counsel, preserve evidence, identify any ransom-payment decisions that start 24-hour NYDFS or CIRCIA clocks.
  2. Hours 24–72: NYDFS and GDPR 72-hour filings; CIRCIA if in scope once effective.
  3. Days 1–10: materiality analysis and potential 8-K within 4 business days of the determination.
  4. Day 30: FTC Safeguards notice and 30-day state consumer letters (CA, NY, FL, WA, CO, ME).
  5. Days 45–60: remaining state clocks and HIPAA individual, HHS and media notices.

The Deadline & Regulator Tracker merges federal and state clocks into one chronological schedule you can print as a brief for counsel. Read the full state matrix for every jurisdiction BreachConnect covers.

Coordinate response

Scoping an incident or a readiness program?

Send a non-sensitive scope summary. BreachConnect matches you with notification vendors, DFIR firms and IR retainer providers that fit your states, record count and coverage — alongside the breach counsel you choose.