North American Signs reported a data breach to the Indiana Attorney General. The breach occurred on 2024-02-28 and was reported on 2024-04-24. 349 Indiana residents were affected. 557 individuals affected in total.
Affected (this filing): 557
Clustered 2 filings across 2 jurisdictions · filing window Apr 24, 2024 → May 20, 2024. View entity profile → Other incidents for this victim →
incident inc_c74df62f463c48dc · merge_method deterministic · confidence 95%
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.
IN NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Feb 28, 2024
When the intrusion reportedly occurred, per the linked filings
Feb 28, 2024
Reported by NEW HAMPSHIRE AG filing
North American Signs reported a data breach to the Indiana Attorney General. The breach occurred on 2024-02-28 and was reported on 2024-04-24. 349 Indiana residents were affected. 557 individuals affected in total.
Affected (this filing): 557
North American Signs reported a data security incident on May 20, 2024, to the New Hampshire Attorney General. On February 28, 2024, the company detected unusual network activity. An investigation by third-party cybersecurity experts determined that an unknown actor accessed and acquired certain data without authorization. The incident affected one New Hampshire resident, involving personal information such as name. NAS reported the incident to the FBI, engaged forensic investigators, and offered complimentary identity protection services to the affected individual.
Affected (this filing): 1
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.