All incidents View linkage analytics →Get the evidence package — $79 what’s inside →

Confirmed3 filings · 3 statesUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 3 filings

Censis Technologies, Inc. — January 2023 breach

Clustered 3 filings across 3 jurisdictions · filing window Oct 1, 2024 → Oct 4, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

3 filings

States

Affected · reported

296

First → last filing

Oct 1, 2024 → Oct 4, 2024

Merge confidence

100%

incident inc_cafd4ecb4a214b44 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings. The filing describes unauthorized access. Intrusion Jan 25, 2023, discovered Sep 3, 2024 — the first regulatory filing landed 28 days later. 296 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 1 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

28days

Discovered → first regulatory filing

Filing span

3days

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.

Regulatory clocksMaine✓ ME AG ≤30d · 28dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 25, 2023breach begins

Sep 3, 2024discovered

notification delay · 28 days

Oct 1, 2024first filing

Oct 4, 2024most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

OCT 1ME AGME AG noticefirst filing · states nationwide total 296day 0
OCT 2MA AGMA AG notice2 MA residentsauto-linked+1d
OCT 4VT AGVT AG noticemost recent · no count statedauto-linked+3d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Jan 25, 2023
Discovered: Sep 3, 2024· 587d undetected
Data types: Financial account · Identity (basic) · Government ID · PCI
Attack vector: Unauthorized Access

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

296

Sum of filed state slices

3· 1.0% of stated

99% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing3 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method: deterministic
Confidence: 1.00 · above the 0.85 auto-merge floor
Audit: Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

3 days

Cadence

~1 / 1.5d

vs. multi-state median

2.7× faster

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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.