CoPilot Provider Support Services
ent_431b18cf742154cb35d19056
Disclosures
4
State AG · 4 jurisdictions
Incidents
1
filings grouped by incident
Max affected reported
220,000
as filed · State AG OR
Leak-site claims
0
none in sample
Identity resolution
- Canonical name
- CoPilot Provider Support Services
- Normalized
- copilot provider support— dedupe via name-norm; Microsoft / MSFT collapse to one row
- GLEIF LEI
- No match
- SEC EDGAR CIK
- None — not an SEC registrant
- Domain
- None on record
Disclosure history (4)newest first
- 🐻California State AGas victim2017-01-19
CoPilot Provider Support Services, Inc. experienced unauthorized access to its database via a website used by physicians to check insurance coverage for ORTHOVISC and MONOVISC injections. The incident occurred in October 2015 and was discovered on December 23, 2015. An individual accessed the database through unauthorized means and downloaded health information, including names, dates of birth, addresses, phone numbers, and medical insurance card information. One version of the notice indicated Social Security numbers were not involved, while another indicated they were. CoPilot engaged a cybersecurity firm, referred the matter to law enforcement, and offered one year of identity monitoring through Kroll.
- 🦫Oregon State AGas victim2017-01-19
CoPilot Provider Support Services, Inc. reported a data breach to the Oregon Attorney General. The breach was reported on 2017-01-19. The breach was discovered on 12/23/2015. 220,000 individuals were affected. Notice was sent on 1/18/2017.
- 🦬Montana State AGas victim2017-01-18
CoPilot Provider Support Services reported a data breach to the Montana Attorney General. The breach was reported on 2017-01-18. The breach occurred on 12/23/2015. 2 Montana residents were affected.
- 🌲Washington State AGas victim2017-01-18
CoPilot Provider Support Services, Inc., a health sector entity reported a other incident to the Washington Attorney General. The organization became aware of the incident on 2015-12-23 and filed notice on 2017-01-18. 1,522 Washington residents were affected. 392 days elapsed between awareness and notification.