Clustered 7 filings across 7 jurisdictions · filed Mar 12, 2024. View entity profile → Other incidents for this victim →
incident inc_5664f6128d3d4a3f · merge_method human · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
CA ME MT NH OR VT WA
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.
all State AG
per-filing reported counts
State AGs report only their own residents; bars show per-filing counts.
Earliest sighting first · deep chronology in Litigation Timeline
Nov 12, 2023 → Nov 13, 2023
When the intrusion reportedly occurred, per the linked filings
Nov 12, 2023
Reported by VERMONT AG, NEW HAMPSHIRE AG, WASHINGTON AG filings
Feb 5, 2024
Reported by OREGON AG, MAINE AG filings
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.
Gerson Lehrman Group, Inc. reported a data breach to the Oregon Attorney General. The breach was reported on 2024-03-12. The breach occurred during 11/12/2023 - 11/13/2023. The breach was discovered on 2/5/2024. Notice was sent on 3/12/2024.
Gerson Lehrman Group, Inc. reported an external system breach that occurred on November 12, 2023, and was discovered on February 5, 2024. The breach affected 152,621 individuals, compromising their names and Social Security numbers. Gerson Lehrman Group began notifying the impacted individuals on March 12, 2024, and offered 12 months of identity monitoring services.
Affected (this filing): 152,621
On November 12, 2023, Gerson Lehrman Group (GLG) experienced a ransomware incident in which an unauthorized third party accessed data from GLG's computer systems. Affected personal information may include name and other personal elements. GLG activated its incident response plan, engaged cybersecurity firms, and is offering complimentary CyEx Identity Defense Total credit monitoring to affected individuals.
Gerson Lehrman Group, Inc reported a data breach to the Montana Attorney General. The breach was reported on 2024-03-12. The breach occurred from 5/29/2023 to 5/30/2023. 1,808 Montana residents were affected.
Affected (this filing): 1,808
Gerson Lehrman Group (GLG) disclosed a ransomware incident on November 12, 2023, where an unauthorized third party accessed its computer systems. GLG activated its incident response plan, engaged cybersecurity firms, and hardened systems. The breach potentially impacted names and government identifiers (e.g., SSN) for individuals in multiple states, including Vermont and Rhode Island. GLG offered complimentary credit monitoring via CyEx Identity Defense Total.
Gerson Lehrman Group, Inc. reported a ransomware incident on November 12, 2023, affecting personal information of 710 New Hampshire residents. GLG activated its incident response plan, engaged forensic experts, and notified federal law enforcement. Affected data included names and other PII. Remediation included enhanced access controls and employee retraining. Credit monitoring was offered to affected individuals.
Affected (this filing): 710
Gerson Lehrman Group, Inc., a business sector entity reported a ransomware incident to the Washington Attorney General. The organization became aware of the incident on 2023-11-12 and filed notice on 2024-03-12. 3,734 Washington residents were affected. 121 days elapsed between awareness and notification. 0 days to identify the breach. 1 days to contain the breach.
Affected (this filing): 3,734