Clustered 3 filings across 3 jurisdictions · filing window Nov 28, 2023 → Mar 20, 2024. View entity profile → Other incidents for this victim →
incident inc_1a4462799bfe4769 · 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 WA
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 30, 2023
When the intrusion reportedly occurred, per the linked filings
Oct 30, 2023
Reported by WASHINGTON AG filing
Axiom Construction and Consulting is a full-envelope architectural sheet-metal contractor and professional manager of construction services. We deliver a wide range of retail and commercial projects throughout Washington. To date, Axiom has completed over 130 projects that have consisted of over two million square feet of metal siding and roofing.
Axiom Construction and Consulting, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2024-03-20. The breach occurred on 10/30/2023. 3 Montana residents were affected.
Affected (this filing):
Axiom Construction and Consulting, a business sector entity reported a ransomware incident to the Washington Attorney General. The organization became aware of the incident on 2023-10-30 and filed notice on 2024-03-20. 1,127 Washington residents were affected. 142 days elapsed between awareness and notification. 5 days to identify the breach. 0 days to contain the breach.
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,127