DisclosureLens
Leak SiteState AGConfirmed6 filings · 3 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlockbit_3low sensitivity
Merged incident · 6 filings

Fauquier County Public Schools — September 2023 breach

Clustered 6 filings across 4 jurisdictions · filing window Sep 12, 2023 Oct 19, 2023. View entity profile → Other incidents for this victim →

affected count agreeMerge100%

Determination

Confirmed

Members

6 filings

States

3

Affected · reported

13,919

First → last filing

Sep 12, 2023 Oct 19, 2023

Merge confidence

100%

incident inc_d67d6c2f86404db3 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings and 3 unverified claims. The filing describes a ransomware attack. Intrusion Sep 9, 2023, discovered Sep 12, 2023 — the first regulatory filing landed 36 days later. 13,919 individuals reported across the linked filings. Data reported: PII and Identity (basic). Notifications rolled out on a 37-day schedule across 3 filings beginning Sep 12, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
36days

Discovered → first regulatory filing

Leak precedence
36days 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
37days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Materiality delta · SEC filing delayno SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksMaine ME AG >30d · 36dLeak gap Leak >30dFull clock table in Litigation Timeline

Incident timeline

Sep 9, 2023breach begins
Sep 12, 2023discovered
notification delay · 36 days
Oct 18, 2023first filing
Oct 19, 2023most 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 12Leak sitelockbit_3 postfirst filing · attacker claim · unverifiedday 0
  2. OCT 1Leak sitelockbit_3 postattacker claim · unverified+19d
  3. OCT 1Leak sitedispossessor postattacker claim · unverified+19d
  4. OCT 18ME AGME AG noticestates nationwide total 13,919+36d
  5. OCT 19IN AGIN AG noticestates nationwide total 13,919+37d
  6. OCT 19MA AGMA AG noticemost recent · 1 MA residents+37d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 9, 2023
ME AG
Discovered
Sep 12, 2023· 3d undetected
ME AG
Data types
PII · Identity (basic)
ME AG
Attack vector
Ransomware
ME 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)

13,919

Sum of filed state slices

5· 0.0% of stated

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

US13,919
ME2
IN2
MA1

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 claim3 members

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

Press / market report

No press coverage linked yet.

State AG / regulator filing3 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 22, 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

37 days

Cadence

~1 / 7.4d

vs. multi-state median

4.6× 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.