Sierra Pacific Industries
bd_1416d6826022edaf · schema v1 · pii pii-v1
Full breach record for Sierra Pacific Industries →2 incidents on fileThreat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Black Basta on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jul 6, 2022
Claim posted
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (4) · sorted by filing gap
- Oregon State AGbd_6e34008b1f781b2e2022-08-09 · +34dVerified
- Oregon State AGbd_2ede0a3fdb3056562023-01-11 · +189dVerified
- Maine State AGbd_bb46c0a8265452b22023-01-11 · +189dVerified
- Montana State AGbd_bf8002671afa71e82023-01-11 · +189dVerified
Filing propagation · 5 filings · 3 states
View merged incident ↗Pattern: first filing Jul 6, last Jan 11 (MT) — a 189-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.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.