Breach filing
ArchivedUtah Department of Technology Services: 780,000 individuals, Apr 2012.
Utah Department of Technology Services reported a breach of unsecured protected health information to the HHS Office for Civil Rights on 11 April 2012. The filing records the organisation as a business associate in Utah and lists 780,000 individuals affected, which makes it the 2nd largest of the 68 Utah filings on the register and the 1st largest of the 218 filings submitted nationally in 2012. It was the only Utah filing in 2012.
Individuals affected
780,000
As reported to HHS
Modelled cost (IBM 2025)
$125M
Upper bound, method shown
Rank in UT
2nd
of 68 Utah filings
Rank in 2012
1st
of 218 filings nationally
Section F.1 / The filing
As posted by HHS OCR
Every value below is the portal's own field for this filing, plus its rank within the register.
- Covered entity type
- Business Associate
- Individuals affected
- 780,000
- Breach submission date
- 11 April 2012
- Submission year
- 2012
- Type of breach
- Hacking/IT Incident
- Location of breached information
- Network Server
- Business associate present
- Yes
- State
- Utah (UT)
- Portal status
- listed in the HHS OCR breach portal archive
- Rank in Utah by size
- 2nd of 68
- Rank in 2012 nationally
- 1st of 218
- Utah median filing
- 5,381 individuals
- Register id (derived)
- UT-20120411-utah-department-of-technology-services
Section F.2 / In context
Where this filing sits in Utah and in 2012
OCR classifies the incident as a hacking or IT incident, with the breached information held in a network server. Hacking/IT Incident is the type recorded on 51 of the 68 Utah filings (75%) and on 8% of all filings submitted in 2012. Network Server is the most common location in the state, appearing on 57% of Utah filings.
A business associate is recorded as present on the filing, as it is on 34% of Utah filings. At 780,000 individuals the breach is 145 times the Utah median filing of 5,381 and 195 times the national median of 4,000 across all 7,884 filings. It is one of 801 filings of 100,000 or more individuals.
As of 28 August 2026 the case is listed in the HHS OCR breach portal archive. OCR's closing summary of the case is reproduced in full below.
Utah's breach notification statute (Utah Code 13-44-202) requires notice to affected residents in the most expedient time possible, without unreasonable delay. Its attorney general threshold: 500 or more Utah residents (AG and Utah Cyber Center). The HIPAA Breach Notification Rule ran alongside it: notice to affected individuals and to HHS without unreasonable delay and no later than 60 days after discovery, which is the clock that put this filing on the portal.
Multiplying 780,000 individuals by IBM's $160 customer-PII cost per record (Cost of a Data Breach 2025, the figure the site's calculator uses) gives a modelled $125M; the 2026 edition's $192 gives $150M. Both are modelled estimates with the method shown, not costs disclosed by Utah Department of Technology Services. Because the filing is above the roughly 100,000-record range in which the per-record figure is reliable, the result is an upper bound, not an estimate: fixed costs are spread across far more records at this scale.
Section F.3 / OCR closing summary
The portal's archived description, in full
Written by the Office for Civil Rights when the case was closed and reproduced verbatim from the HHS export.
OCR opened an investigation of the covered entity (CE), Utah Department of Health, after it reported that a hacker had gained access to the network server of it business associate (BA), Utah Department of Technology Services (DTS). During the cyberattack, the hacker copied the unencrypted electronic protected health information (ePHI) of approximately 780,000 individuals to an internet protocol address in Romania. The ePHI involved in the breach included names, addresses, birth dates, social security numbers, physicians' names, and procedure codes designed for billing purposes. The CE provided breach notification to HHS, affected individuals, and the media, and provided free credit monitoring to affected individuals. Following the breach, the CE entered into a BA agreement with DTS. It also improved safeguards by developing an incident response plan, improving its password management process, strengthening its security practices to include encryption and improved firewalls, and completing a new risk analysis and risk management plan. OCR obtained assurances that the CE implemented the corrective actions noted above.
Section F.5 / Modelled cost
780,000 individuals through IBM's per-record figures
Modelled cost / method shown, not a disclosed cost
Upper boundIBM 2025 customer PII, $160 per record
$125M
780,000 x $160
IBM 2026 customer PII, $192 per record
$150M
780,000 x $192
Method: individuals affected, as reported by Utah Department of Technology Services to HHS, multiplied by IBM's customer-PII cost per record (Cost of a Data Breach 2025 Figure 6 and the 2026 edition). No cost has been disclosed by the entity for this filing; the figure is a planning estimate, not a fact about the breach. IBM's per-record figures come from mid-volume breaches and IBM cautions against applying them to breaches involving millions of records; the site's per-record page explains where the multiplication holds and where it breaks down.
Context: IBM's average cost of a healthcare breach is $6.64M in the 2026 report ($7.42M in 2025); the global average across all sectors was $4.44M in 2025.
Cost per record: method and limits / Healthcare breach cost, IBM 2026
Section F.6 / Notification clock
Utah statute and the HIPAA rule
State notification statute
Utah: Utah Code 13-44-202
Protection of Personal Information Act
- Notice to individuals
- In the most expedient time possible, without unreasonable delay
- Attorney general threshold
- 500 or more Utah residents (AG and Utah Cyber Center) (Without unreasonable delay)
- Private right of action
- No: No PROA; only the Attorney General can enforce
- Penalty
- Up to $2,500 per consumer, capped at $100,000 aggregate for related violations
The HIPAA Breach Notification Rule runs alongside the state statute: notice to affected individuals and to HHS without unreasonable delay and no later than 60 days after discovery.
Section F.7 / Peer filings
Utah filings closest in size
Neighbours by size rank among Utah filings in 2012, topped up from other years where 2012 has too few. Filings of 10,000 or more link to their own page.
| Covered entity | Type | Individuals | Submitted | Breach type | Location | BA |
|---|---|---|---|---|---|---|
| HealthEquity, Inc. | Business Associate | 4,300,000 | 9 Aug 2024 | |||
| Utah Imaging Associates, Inc. | Healthcare Provider | 582,170 | 3 Nov 2021 | |||
| Premier Family Medical | Healthcare Provider | 320,000 | 7 Sep 2019 | |||
| HealthEquity, Inc. | Business Associate | 165,800 | 17 Nov 2018 |
Index / Companion schedules
13 HHS breach register
→Hub: every filing, by state, year and entity.
04 Biggest breaches
→Mega-breaches with primary-source cost figures.
Industry / Healthcare
→IBM 2026: $6.64M average, 13 years at #1.
Regulation / HIPAA penalties
→OCR enforcement tiers and the 60-day rule.
11 50-state laws
→Deadline, AG threshold and penalties per state.
Cost / Per record
→Where the per-record model is reliable.
Provenance
Source: U.S. Department of Health and Human Services, Office for Civil Rights, Breach Portal (breaches affecting 500 or more individuals), retrieved 2026-08-28. Public domain. Individuals affected and dates as reported by the covered entity.
Portal: ocrportal.hhs.gov breach report. Statutory basis: HITECH Act section 13402(e)(4): the Secretary must post a list of breaches of unsecured protected health information affecting 500 or more individuals. Breaches affecting fewer than 500 individuals are reported to OCR annually and are not posted, so they are not on this register. Status wording follows the portal's two tabs ("Cases Currently Under Investigation" and "Archive") as of 28 August 2026; a filing moves to the archive when OCR closes the case. Modelled costs on this site are a method applied to the reported count, using IBM Cost of a Data Breach per-record figures, and are never a cost disclosed by the entity. This row: hhs-breach-archive__2026-08-28.csv, export row 6699.
Corrections: if you represent a listed entity and the portal row has been amended, email [email protected] with the portal entry and we will re-pull the export.