One hash-anchored incident determination timestamp starts three parallel regulatory notification clocks: the 36-hour interagency banking-regulator rule, the 4-business-day SEC Form 8-K Item 1.05 notification, and the 72-hour NYDFS notice. Emits a hash-anchored OpenChainGraph v0.4 artifact with a decision-tree attestation slot per obligation.
Deadline clock, not a filing system
Not legal advice
🔒 All inputs are processed locally in your browser. No data is transmitted. Use synthetic or anonymised inputs only, do not enter real personal or confidential data.
Scope limits, read before use: the SEC 8-K leg's "4 business days" is computed weekends-only, no U.S. federal or SEC-closure holiday calendar is applied. A real SEC-closed weekday that is not a weekend makes this clock's deadline one business day earlier than the true deadline, a conservative direction, not a permissive one. A pending Item 1.05 rescission petition (flagged as of April 2026) is carried as an annotation only, it does not change the computed deadline under the rule as currently in force. This tool computes deadlines only, it does not transmit, file, or submit any notification on your behalf.
When the incident was determined to be a reportable cyber incident. Clocks start here.
Hash of the underlying incident-evidence bundle (e.g. an art-379/art-418 incident record), anchored into this artifact's inputs.
Leave blank to skip overdue detection.
Obligation
Applicable
Deadline (UTC)
Status
OpenChainGraph v0.4 artifact · execution_hash:
Related
Complementary to the Incident Response Runbook Builder: that tool shapes the surrounding incident-response process; this clock starts once a determination is made. See also ART-418 and ART-379 for adjacent incident-record composers.