HackingHealthcareHealthcareSupply Chain (3P Vendor)Customer Data InvolvedEmployee Data InvolvedIdentity (basic)Government IDFinancial accountPHIHealth (basic)MediumContained

Providence WA Anesthesia Services PC

bd_324c3d5636571582 · schema v1 · pii pii-v1

Severity

Medium

Discovered

Sep 22, 2022

Filed

Oct 24, 2022

To disclose

5 weeks

Affected

72state residents only

Linked

4 filings

Confidence

66%

Full breach record for Providence WA Anesthesia Services PC →

Providence WA Anesthesia Services PC notified Montana residents of a data breach involving its third-party management company. Suspicious activity was detected on July 11, 2022, and the company was notified on September 22, 2022. Compromised data included PHI, SSNs, DOBs, driver's licenses, and financial account info. The company engaged forensic experts, reset passwords, and offered IDX identity protection services.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 73 days

discovery → filing · 5 weeks / 32 days

Jul 11, 2022

Begins

Sep 22, 2022

Discovered

Oct 24, 2022

Filed

vs. sector median

8 wks faster

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

Linked disclosures

Why this link?

Regulatory filings (3) · sorted by filing gap

Maine State AGbd_da9b8e9c19ba82922022-10-25 · +1dVerified
Washington State AGbd_e30373c6d1c0c24c2022-10-25 · +1dVerified
HHS OCRbd_e9e6c369255001df2022-09-23 · +31dCandidate

Name: Providence WA Anesthesia Services PC
norm: providence wa anesthesia

Name: Providence WA Anesthesia Services PC
norm: providence wa anesthesia
Industry: Healthcarellm

Discovered: Sep 22, 2022
Breach occurred: Jul 11, 2022
Undetected for: 73 daysoccurrence → discovery
Materiality determined: —
Notification sent: Oct 24, 2022
Affected individuals: 72state-resident count only
Data types: Identity (basic)Government IDFinancial accountPHIHealth (basic)
Attack vector: Third-Party / Supply Chain
MITRE ATT&CK: T1078 Valid AccountsT1119 Automated Collection
Threat actor: External
Third party: via Management Company
Initial access: external_remote_services

During the incident: Management company immediately implemented its incident response protocols
Disconnected all systems
Engaged external cybersecurity experts to conduct a forensic investigation
Conducted a global password reset
Tightening firewall restrictions
Implementing endpoint threat detection and response monitoring software on workstations and servers
Offering identity theft protection services through IDX
Changes made: Conducted a global password reset
Tightening firewall restrictions
Implementing endpoint threat detection and response monitoring software on workstations and servers
Source: Quoted from the filing itself, not independently verified.

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

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 4 filings · 4 states

View merged incident ↗

HHS OCRSep 23 · first

Montana State AG+31d · this page

Maine State AG+32d

Washington State AG+32d

Pattern: first filing Sep 23 (NY), last Oct 25 (WA) — a 32-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/OCP/Consumer-Notification-Letter-647.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Oct 24, 2022
Raw hash: 8f3b1049c77579f2737dbfd64d54b79742d52439119b05324bdc08e84bf20c04

Linked disclosures

Regulatory filings (3) · sorted by filing gap

Reporting entityProvidence WA Anesthesia Services PC

Victim entityProvidence WA Anesthesia Services PC

Incidentdiscovered Sep 22, 2022

Stated responseManagement company immediately implemented its incident response protocols

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov