UTAHHackingHealthcareHealthcareVulnerability ExploitData ExfiltratedCustomer Data InvolvedPHIHealth (basic)Government IDIdentity (basic)HighContained

Central Utah Clinic

bd_9c7b577b2e2ffa91 · schema v1 · pii pii-v1

Severity

High

Discovered

Jun 9, 2014

Filed

Aug 7, 2014

To disclose

8 weeks

Affected

31,677

Confidence

67%

Full breach record for Central Utah Clinic →2 incidents on file

Central Utah Clinic reported to HHS on 2014-08-07 a Hacking/IT Incident affecting 31677 individuals. Breached information located on Network Server. Cybercriminals compromised an Internet-facing server containing ePHI (images, radiology reports, patient names, DOB, SSN, addresses, phone numbers). Corrective actions included blocking the server, penetration tests, policy updates, and security training.

J jump to incidentP pin to compareR raw source

HIPAA clock✓ HHS report on time8 weeks discovery → filing

⚠ unattributedNo provenance was recorded for this discovery date and it matches no other date on the record. It may be correct, but it is not independently grounded.

Incident timeline

discovery → filing · 8 weeks / 59 days

Jun 9, 2014

Discovered

Aug 7, 2014

Filed

vs. sector median

4 wks faster

Tracked as a single-filing incident — the only disclosure on record for this event so far.Confirmed31,677 affectedView incident

Name: Central Utah Clinic
norm: central utah clinic
Industry: Health Care Services

Name: Central Utah Clinic
norm: central utah clinic
Industry: Healthcaresource default

Discovered: Jun 9, 2014
Materiality determined: —
Notification sent: —
Affected individuals: 31,677nationwide
Data types: PHIHealth (basic)Government IDIdentity (basic)
HHS breach type: Hacking / IT incident
Where the data lived: Network server
Covered-entity type: Healthcare provider
Attack vector: Unauthorized Access
MITRE ATT&CK: T1190 Exploit Public-Facing Application
Threat actor: External
Regulator citations: Notified HHSOCR provided technical assistance regarding necessary changes to its policies and procedures, and its security management process
Initial access: exploit_public_facing

During the incident: Updating its inventory of ePHI, servers, databases, users, and applications
Reducing vulnerabilities and blocking the affected server from the Internet
Conducting penetration tests
Drafting new security policies
Implementing new response procedures
Updating patch management procedures
Upgrading the functionality in its firewalls, antivirus, and antimalware software
Expanding its security team
Providing security and awareness training to its workforce
Changes made: Updating its inventory of ePHI, servers, databases, users, and applications
Reducing vulnerabilities and blocking the affected server from the Internet
Conducting penetration tests
Drafting new security policies
Implementing new response procedures
Updating patch management procedures
Upgrading the functionality in its firewalls, antivirus, and antimalware software
Expanding its security team
Providing security and awareness training to its workforce
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 8 weeks(59 days from discovery to filing)
Compliance flags: HHS report on timeHHS notified
Discovery-date grounding: unattributedNo provenance was recorded for this discovery date and it matches no other date on the record. It may be correct, but it is not independently grounded.
Clock breakdown: Statute Window Elapsed Threshold Status
HIPAA
Discovered: Jun 9, 2014
→ Notified: not extracted
— 60 days HHS report on time
HIPAA
Discovered: Jun 9, 2014
→ Notified: not extracted
— regulatory submission HHS notified

Statute	Window	Elapsed	Threshold	Status
HIPAA	Discovered: Jun 9, 2014 → Notified: not extracted	—	60 days	HHS report on time
HIPAA	Discovered: Jun 9, 2014 → Notified: not extracted	—	regulatory submission	HHS notified

Status: No extraction artifact recorded for this disclosure.

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.

Source URL: https://ocrportal.hhs.gov/ocr/breach/breach_report.jsf
DisclosureLens renders the full SEC/HHS filing inline below from the originating regulator’s public record (§4.5 fair report privilege).
Filed at: Aug 7, 2014
Raw hash: c24eb95af45cf6dbaf2c33c43fb3bf34ad926448e26b4b457ceadd61d9485b06

AI-assisted summary above. The structured extract on this page was generated from the document below. Inspect the source to verify or correct any field.

text/html2.2 KB

Download View at source

Reporting entityCentral Utah Clinic

Victim entityCentral Utah Clinic

Incidentdiscovered Jun 9, 2014

Stated responseUpdating its inventory of ePHI, servers, databases, users, and applications

ComplianceHHS report on time

Extraction provenanceno artifact recorded

Source provenanceocrportal.hhs.gov

Source filing