DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed12 filings · 11 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcritical sensitivity
Merged incident · 12 filings

JOHNSON CONTROLS, INC. — February 2023 breach

Clustered 12 filings across 11 jurisdictions · filing window Jun 1, 2025 → Jul 7, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

12 filings

States

11

Affected · reported

64,178

First → last filing

Jun 1, 2025 → Jul 7, 2025

Merge confidence

100%

incident inc_8ff64b50720047bb · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings. The filings describe unauthorized access. Intrusion Feb 1, 2023–Sep 30, 2023, discovered Sep 24, 2023 — the first regulatory filing landed 616 days later (flagged late). 64,178 individuals reported across the linked filings. Data reported: Government ID, Biometric, PII, and 7 more. Notifications rolled out on a 36-day schedule across 12 filings beginning Jun 1, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
616days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
36days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksVermont✗ VT AG >45 bdayWashington✗ WA AG >90dCalifornia✗ CA 60-day late · 645dOregon✗ OR AG >45dTexas✗ TX AG >30dIowa✓ IA AG ≤5 bdayFull clock table in Litigation Timeline

Sensitive data

authenticationbiometricidentity_government

Incident timeline

Feb 1, 2023breach begins
Sep 24, 2023discovered
notification delay · 616 days
Jun 1, 2025first filing
Jul 7, 2025most 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. JUN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. JUN 30IA AGIA AG notice2,259 IA residents+29d
  3. JUN 30VT AGVT AG noticeno count stated+29d
  4. JUN 30DE AGDE AG noticeno count stated+29d
  5. JUN 30WA AGWA AG notice4,903 WA residents+29d
  6. JUN 30MT AGMT AG notice639 MT residents+29d
  7. JUN 30IN AGIN AG notice16,729 IN residents+29d
  8. JUN 30CA AGCA AG noticeno count stated+29d
  9. JUL 1OR AGOR AG noticestates nationwide total 3,829+30d
  10. JUL 1TX AGTX AG notice38,037 affected+30d
  11. JUL 1IL AGIL AG noticeno count stated+30d
  12. JUL 7NH AGNH AG noticemost recent · 1,611 NH residents+36d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 1, 2023 – Sep 30, 2023
IA AG
Discovered
Sep 24, 2023· 235d undetected
IL AG + IA AG + VT AG +7
Data types
Authentication · Biometric · Credentials · Employment · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
IL AG + WA AG + IA AG +5
Attack vector
Unauthorized Access
IA AG

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

Affected residents by state

per-state reported counts

US3,829
TX38,037
IN16,729
WA4,903
IA2,259
NH1,611
MT639

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 claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing12 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
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

36 days

Cadence

~1 / 3.3d

vs. multi-state median

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