Concorde Investment Services reported a data breach to the Indiana Attorney General. The breach occurred on 2024-06-23 and was reported on 2025-02-25. 13 Indiana residents were affected. 684 individuals affected in total.
Affected (this filing): 684
Clustered 2 filings across 2 jurisdictions · filed Feb 25, 2025. View entity profile → Other incidents for this victim →
incident inc_87006e8a5fa34ced · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Identity (basic) · Government ID
IN MD
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jun 23, 2024
When the intrusion reportedly occurred, per the linked filings
Aug 12, 2024
Reported by MARYLAND AG filing
Concorde Investment Services reported a data breach to the Indiana Attorney General. The breach occurred on 2024-06-23 and was reported on 2025-02-25. 13 Indiana residents were affected. 684 individuals affected in total.
Affected (this filing): 684
Concorde Investment Services notified the Maryland AG of a data event affecting 2 residents. Unauthorized access to employee email accounts occurred between June 13 and August 19, 2024, likely via phishing. Impacted data included names and Social Security numbers. Concorde provided credit monitoring and guidance to affected individuals.
Affected (this filing): 2
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.