National Center for Construction Education and Research reported a data breach to the Montana Attorney General. The breach was reported on 2023-03-24. The breach occurred on 1/26/2023. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filed Mar 24, 2023. View entity profile → Other incidents for this victim →
incident inc_5ae353c624d64c3f · merge_method llm · confidence 44%
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
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 26, 2023
When the intrusion reportedly occurred, per the linked filings
Mar 2, 2023
Reported by MAINE AG filing
National Center for Construction Education and Research reported a data breach to the Montana Attorney General. The breach was reported on 2023-03-24. The breach occurred on 1/26/2023. 1 Montana residents were affected.
Affected (this filing): 1
The National Center for Construction Education and Research reported an inadvertent disclosure of personal information. The breach, which occurred on January 26, 2023, and was discovered on March 2, 2023, affected one Maine resident. The compromised information included names and Social Security numbers. The organization offered 12 months of complimentary credit monitoring and identity restoration services through Equifax to those affected.
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.