University of Massachusetts Amherst
bd_2dd1bf2b944367ee · schema v1 · pii pii-v1
Full breach record for University of Massachusetts Amherst →17 incidents on fileRegulator's decision — not a breach notification
This record is a regulator's decision, not the organisation's own breach notice. Breach-notification fields (discovery date, notification clock) are structurally absent — what this source establishes is the outcome and the provisions the decision cites.
UMass Amherst settled potential HIPAA Privacy and Security Rules violations involving a malware infection. The settlement includes a corrective action plan and a monetary payment of $650,000.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Nov 22, 2016
Filed
—
Corroborated · see linked filings
This record is the regulator's action, not a breach notice; its own dates cannot anchor compliance clocks. See the linked filings.
Linked disclosures
Why this link?Regulatory filings (2) · sorted by filing gap
- Massachusetts State AGbd_f96d7b84c59a404c2013-06-10 · +1261dVerified
- HHS OCRbd_f5329cc0d2a7121d2013-06-05 · +1266dCandidate
Filing propagation · 2 filings
View merged incident ↗Pattern: first filing Jun 5 (MA), last Jun 10 (MA) — a 5-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
- instrument + outcome
- amount as filed (USD)
- CFR provisions
- the breach it recites
- discovery date
- notification clock
The dates the agreement recites belong to the underlying breach, years earlier, and are kept as evidence of WHICH breach rather than as this record’s timeline.