JOHNSON CONTROLS, INC. — February 2023 breach
Clustered 3 filings across 2 jurisdictions · filing window Sep 24, 2023 → Nov 13, 2023. View entity profile → Other incidents for this victim →
incident inc_026eb5580cd44807 · merged by deterministic · confidence 100%
Litigation Timing
Discovered → first regulatory filing
Range of discovered_at dates across filings
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.
Incident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.
Member cascade — every filing about this breach
- SEP 24SC AGSC AG noticefirst filing · 12,134 SC residentsday 0
- SEP 27SEC 8-KSEC 8-K noticeno count stated+3d
- NOV 13SEC 8-KSEC 8-K noticemost recent · no count statedauto-linked+50d
- 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 SC AG
- Discovered
- Sep 23, 2023SEC 8-KSep 24, 2023SC AGfilings disagree on discovery
- Data types
- Credentials · Identity (basic) SC AG
- Attack vector
- Unauthorized Access SC AG
Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.
Evidence ladder — rungs this incident occupies
No leak-site claim on record for this incident.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
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
50 days
Cadence
~1 / 25d
vs. multi-state median
6.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.