DisclosureLens
UnknownTechnologyInformationGovernment IDHealth (basic)Financial accountMedium

LenelS2

bd_aaa137d117733bc7 · schema v1 · pii pii-v1

Severity

Medium

Discovered

—

Filed

Dec 23, 2024

To disclose

—

Affected

386state residents only

Linked

5 filings

Confidence

95%
Full breach record for LenelS2 →

LenelS2 reported a data breach to the Massachusetts Office of Consumer Affairs and Business Regulation. The breach was reported on 2024-12-23. 386 Massachusetts residents were affected.

Leak gap clock⏱ Leak >30d
⚠ no discovery dateNo discovery date was extracted, so no notification clock can be evaluated.

Incident timeline — partial

? — ?

Breach window unknown

Dec 23, 2024

Filed

—

Corroborated · see linked filings

Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.

This filing is one of 5 about the same incident.View merged incident
A leak claim by play about this victim predates this filing by 60 days.View originating leak claim

Linked disclosures

Why this link?

Ransomware claims (1)

Regulatory filings (3) · sorted by filing gap

Filing propagation · 4 filings · 4 states

View merged incident ↗
New Hampshire State AGDec 18 · first
Indiana State AGDec 18 · first
Maine State AG+4d
Massachusetts State AG+5d · this page

Pattern: first filing Dec 18 (NH), last Dec 23 (MA) — a 5-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

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

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.