Clustered 3 filings across 3 jurisdictions · filing window Nov 24, 2022 → Feb 14, 2023. View entity profile → Other incidents for this victim →
incident inc_f51fd3d3e996423b · merge_method human · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
MT NH
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 12, 2022
When the intrusion reportedly occurred, per the linked filings
Nov 18, 2022
Reported by NEW HAMPSHIRE AG filing
https://www.janusresearch.com JANUS is a technology innovator and engineering and technical services large business. Founded in 1997 as a virtual training and mission support services company, we have grown over time by forging a reputation for technical excellence, innovation, cost-schedule performance, and customer service. Today, JANUS’ centers of...
Janus Research Group reported a data breach to the Montana Attorney General. The breach was reported on 2023-02-10. The breach occurred from 11/12/2022 to 11/17/2022. 1 Montana residents were affected.
Affected (this filing): 1
Janus Research Group notified the New Hampshire Attorney General of a data event affecting one NH resident. Unauthorized access occurred Nov 12-17, 2022, via stolen employee credentials. Name and SSN were potentially exposed. Incident discovered Nov 18, 2022. Response included forensic investigation, law enforcement notification, and 24 months of credit monitoring via Experian.
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.
Affected (this filing): 1