AccidentalGovernmentGovernmentMisconfigurationDelayed DiscoveryPIIIdentity (basic)Government IDHealth (basic)MediumContained

Salt Lake County, Utah

bd_774deb24ec0b2628 · schema v1 · pii pii-v1

Severity

Medium

Discovered

Sep 9, 2015

Filed

Oct 9, 2015

To disclose

4 weeks

Affected

11state residents only

Linked

3 filings

Confidence

66%

Full breach record for Salt Lake County, Utah →

Salt Lake County, Utah, notified individuals of a security incident discovered on September 9, 2015, involving improper security settings set by a software services vendor on June 18, 2015. The misconfiguration potentially exposed names, addresses, SSNs, and limited medical information from workers' compensation claims. The county restored settings, engaged credit monitoring, and cooperated with law enforcement.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 83 days

discovery → filing · 4 weeks / 30 days

Jun 18, 2015

Begins

Sep 9, 2015

Discovered

Oct 9, 2015

Filed

This filing is one of 3 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (2) · sorted by filing gap

New Hampshire State AGbd_3a75c1fcda4875082015-10-09Verified
Massachusetts State AGbd_ebb443350266c6762015-10-14 · +5dVerified

Name: Salt Lake County, Utah
norm: salt lake county utah

Name: Salt Lake County, Utah
norm: salt lake county utah
Industry: Governmentllm

Discovered: Sep 9, 2015
Breach occurred: Jun 18, 2015
Undetected for: 83 daysoccurrence → discovery
Materiality determined: —
Notification sent: —
Affected individuals: 11state-resident count only
Data types: PIIIdentity (basic)Government IDHealth (basic)
Data elements: Social Security numberMedical information
Attack vector: Misconfiguration
MITRE ATT&CK: T1078 Valid Accounts
Regulator citations: cooperating with law enforcement’s investigation

During the incident: Secured the services of IDT911 to provide triple bureau credit monitoring services at no cost to you for one year
Restored all proper security settings
Ensuring that vendors hired by Salt Lake County have adequate security oversight procedures
Cooperating with law enforcement’s investigation
Changes made: Ensuring that vendors hired by Salt Lake County have adequate security oversight procedures
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 4 weeks(30 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 3 filings · 3 states

View merged incident ↗

New Hampshire State AGOct 9 · first

Montana State AGOct 9 · first · this page

Massachusetts State AG+5d

Pattern: first filing Oct 9 (NH), last Oct 14 (MA) — a 5-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

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://dojmt.gov/wp-content/uploads/Salt-Lake-County-Utah.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Oct 9, 2015
Raw hash: 933c689918523e9edd62b7afbee97951071124313c9e6caefe109f95a7b6275a

Linked disclosures

Regulatory filings (2) · sorted by filing gap

Reporting entitySalt Lake County, Utah

Victim entitySalt Lake County, Utah

Incidentdiscovered Sep 9, 2015

Stated responseSecured the services of IDT911 to provide triple bureau credit monitoring services at no cost to you for one year

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov