All incidents View linkage analytics →Get the evidence package — $7.99 what’s inside →

Confirmed2 filingsUnverified claimConfirmedEnforcedmidnight_blizzardlow sensitivity

Merged incident · 2 filings

MICROSOFT CORPORATION — November 2023 breach

Clustered 2 filings across 1 jurisdiction · filing window Jan 19, 2024 → Mar 8, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge63%

Determination

Confirmed

Members

2 filings

States

—

Affected · reported

—

First → last filing

Jan 19, 2024 → Mar 8, 2024

Merge confidence

63%

incident inc_be1747af8c9340a9 · merged by llm · confidence 63%

Confirmed breach. Merged as one breach: 2 regulatory filings. The filings describe unauthorized access. Intrusion Nov 1, 2023, discovered Jan 12, 2024 — the first regulatory filing landed 7 days later; 1 later filing was flagged late. Data reported: IP / system, Credentials, and Metadata. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

7days

Discovered → first regulatory filing

Materiality delta

5days

Discovery to SEC materiality determination

SEC filing delay

2days

Materiality determination to SEC 8-K filing

Filing span

49days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Leak precedence — no leak-site claim in this cluster; needs two dated filings.

Regulatory clocksSEC✗ SEC 4-day late · 51dFull clock table in Litigation Timeline

No cross-filing comparison data available for this incident.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.