Structural Component Systems
bd_9e5ee5f35e56f8ac · schema v1 · pii pii-v1
Full breach record for Structural Component Systems →Structural Component Systems notified Massachusetts residents of a security incident where an unauthorized actor likely took files from the company's network. The investigation determined on January 16, 2026, that personal information, including first and last name, may have been accessed. The company secured its network, engaged outside cybersecurity professionals, and is offering complimentary credit monitoring. No specific discovery date or breach occurrence window was provided in the notice.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Mar 6, 2026
Filed
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Linked disclosures
Why this link?Ransomware claims (1)
- Leak Sitesecurotropbd_de61ecde4c8ab9362025-10-02 · +154dVerified by operator
Regulatory filings (5) · sorted by filing gap
- Indiana State AGbd_3e7689cadc13f60b2026-03-05 · +1dVerified
- Nebraska State AGbd_6c9e73f1727c019b2026-03-05 · +1dVerified by operator
- Indiana State AGbd_fb71123bee30254a2026-03-05 · +1dVerified
- New Hampshire State AGbd_c7379c5e91f9377e2026-03-10 · +4dVerified
Show 1 more filing ↓Show fewer ↑up to 10d gap
- New Hampshire State AGbd_11d1f5374b8a81422026-03-16 · +10dVerified
Filing propagation · 6 filings · 4 states
View merged incident ↗Pattern: first filing Mar 5 (IN), last Mar 16 (NH) — a 11-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.