DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

Pacific Specialty Insurance Company notifies plan members of breach that occurred in March, 2019

Posted on February 25, 2020 by Dissent

Once again, we see a timeline where it took a loooong time before an entity actually discloses a breach, but the entity’s explanation involves how long it took to determine who was impacted. In this case, it tood from June 14, when they first became suspicious of activity that had occurred in March until November 7 to figure out who was impacted. After that, it reportedly took another two months to get contact information for those impacted.

Here’s part of their breach notification of February 24:

What Happened? On June 14, 2019 Pacific Specialty became aware of suspicious activity in employee email accounts.  It immediately began an investigation to determine what happened and what information may have been affected.  With the assistance of third-party forensic investigators, it was determined that certain employee email accounts were subject to unauthorized access between March 20, 2019 and March 30, 2019.  Every potentially accessible file within the impacted accounts was reviewed to determine what files may have been accessible to the unauthorized actor. On November 7, 2019 Pacific Specialty became aware of the identities of the individuals whose information was included in the impacted accounts. It continued working to obtain contact information for impacted individuals through January 14, 2020.

What Information Was Involved?The types of information contained within the potentially impacted emails varied by individual but include:  an individual’s name, Social Security number, driver’s license and/or government issued identification, financial information, payment card information, medical information, and health insurance information.

What is Pacific Specialty Doing in Response to this Incident?Pacific Specialty is committed to, and takes very seriously, its responsibility to protect all data in its possession.  Pacific Specialty is continuously taking steps to enhance data security protections.  As part of its incident response, it changed the log-in credentials for all employee email accounts to prevent further unauthorized access.  Since then, it has continued ongoing efforts to enhance security controls, such as enabling multifactor authentication, and implemented additional controls to help protect employee email accounts from unauthorized access.

In an abundance of caution, Pacific Specialty is offering 12 months of complimentary credit monitoring to potentially affected individuals so that they may take further steps to best protect their personal information, should they feel it is appropriate to do so.  On January 24, 2020, Pacific Specialty also began mailing notice letters to individuals whose information was contained within the impacted accounts and for whom it had a postal address.

You can read the full press release here.


Related:

  • PowerSchool commits to strengthened breach measures following engagement with the Privacy Commissioner of Canada
  • Two more entities have folded after ransomware attacks
  • Data breach feared after cyberattack on AMEOS hospitals in Germany
  • Global hack on Microsoft product hits U.S., state agencies, researchers say
  • Michigan ‘ATM jackpotting’: Florida men allegedly forced machines to dispense $107K
  • Premier Health Partners issues a press release about a breach two years ago. Why was this needed now?
Category: HackHealth DataU.S.

Post navigation

← How the Grand Est region fights against the ransomware attack that paralyzed its computer network
DoppelPaymer Ransomware Launches Site to Post Victim’s Data →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • Scattered Spider Hijacks VMware ESXi to Deploy Ransomware on Critical U.S. Infrastructure
  • Hacker group “Silent Crow” claims responsibility for cyberattack on Russia’s Aeroflot
  • AIIMS ORBO Portal Vulnerability Exposing Sensitive Organ Donor Data Discovered by Researcher
  • Two Data Breaches in Three Years: McKenzie Health
  • Scattered Spider is running a VMware ESXi hacking spree
  • BreachForums — the one that went offline in April — reappears with a new founder/owner
  • Fans React After NASCAR Confirms Ransomware Breach
  • Allianz Life says ‘majority’ of customers’ personal data stolen in cyberattack (1)
  • Infinite Services notifying employees and patients of limited ransomware attack
  • The safe place for women to talk wasn’t so safe: hackers leak 13,000 user photos and IDs from the Tea app

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • Congress tries to outlaw AI that jacks up prices based on what it knows about you
  • Microsoft’s controversial Recall feature is now blocked by Brave and AdGuard
  • Trump Administration Issues AI Action Plan and Series of AI Executive Orders
  • Indonesia asked to reassess data privacy terms in new U.S. trade deal
  • Meta Denies Tracking Menstrual Data in Flo Health Privacy Trial
  • Wikipedia seeks to shield contributors from UK law targeting online anonymity
  • British government reportedlu set to back down on secret iCloud backdoor after US pressure

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net

Mastodon: Infosec.Exchange/@PogoWasRight

Signal: +1 516-776-7756

DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.