DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed8 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmazehigh sensitivity
Merged incident · 8 filings

Fairfax County Public Schools — August 2020 breach

Clustered 8 filings across 6 jurisdictions · filing window Sep 11, 2020 → Feb 28, 2021. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

8 filings

States

5

Affected · reported

172,128

First → last filing

Sep 11, 2020 → Feb 28, 2021

Merge confidence

100%

incident inc_53b99b12b5144fef · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 1 unverified claim. Intrusion Aug 21, 2020–Sep 7, 2020, discovered Sep 6, 2020 — the first regulatory filing landed 64 days later (flagged late). 172,128 individuals reported across the linked filings. Data reported: Government ID, Health (basic), Identity (basic), and 1 more. Notifications rolled out on a 170-day schedule across 7 filings beginning Sep 11, 2020. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
64days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
59days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
170days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksMaine✗ ME AG >90d · 175dLeak gap⏱ Leak >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 21, 2020breach begins
Sep 6, 2020discovered
notification delay · 64 days
Nov 9, 2020first filing
Feb 28, 2021most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. SEP 11Leak sitemaze postfirst filing · attacker claim · unverifiedday 0
  2. NOV 9MT AGMT AG notice14 MT residents+59d
  3. NOV 9IN AGIN AG noticestates nationwide total 19,653+59d
  4. NOV 16ME AGME AG noticestates nationwide total 19,653+66d
  5. NOV 16MA AGMA AG notice108 MA residents+66d
  6. NOV 19NH AGNH AG notice20 NH residents+69d
  7. JAN 21IN AGIN AG noticestates nationwide total 172,128+132d
  8. FEB 28ME AGME AG noticemost recent · states nationwide total 172,128+170d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 1, 2020 – Sep 7, 2020
MT AG
Discovered
Sep 6, 2020· 5d undetected
MT AG + ME AG + NH AG
Data types
Financial account · Health (basic) · Identity (basic) · Government ID
MT AG + ME AG + MA AG +1
Attack vector
Ransomware· Maze group
MT AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

172,128

Sum of filed state slices

369· 0.2% of stated

100% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US172,128
IN134
MA108
ME93
NH20
MT14

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing7 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 23, 2026 · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

170 days

Cadence

~1 / 24.3d

vs. multi-state median

21.3× slower

About this clustering

DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

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.