DataBreaches.Net

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

Paging regulators to Aisle 4 to look at Pacific Union College’s data security and breach disclosure

Posted on November 9, 2023 by Dissent

On November 8, Pacific Union College in California notified the Maine Attorney General’s Office of a breach in March 2023 that impacted 56,041 people. Their notification, submitted by external counsel at McDonald Hopkins,  indicates that the breach occurred between March 5 and March 19, 2023 and was discovered on October 9, 2023.

That discovery date is utter rubbish. Let’s dig into this one a bit deeper by consulting the redacted copy of the notification to those affected. It appears below this post.

The notification letter of November 8 states, “We recently discovered unauthorized access to our network occurred between March 5 and March 19, 2023.”

“Recently discovered?” Hardly. On June 6, 2023, DataBreaches reported:

That Pacific Union College (PUC) experienced a cyberattack is not a secret. The college even posted a notice on their website on April 7 stating that they were experiencing “Additional complications relating to the ongoing cybersecurity issue, which has recently affected some of our internal networks, phone systems, and web services. The remainder of the notice provided the status of various types of systems and services and assured the community of updates “as new information becomes available.”

But the next update on the website wasn’t until May 3, when they wrote) emphasis added by DataBreaches):

Several weeks ago, Pacific Union College experienced what we now know was a targeted ransomware attack. Federal authorities were contacted, and other cybersecurity teams were recruited to work with our IT department.

Pacific Union College had discovered the incident before April 7 and knew it was a ransomware incident by May 3.

So why are they claiming it was discovered on October 9? Because that’s when they discovered personally identifiable information was involved? If so, that, too, appears to be utter rubbish.

Once again, DataBreaches calls your attention to reporting on June 6 that, according to the threat actors, the college had negotiated with them for a month and seen samples of data. Even if the college had not seen samples of student data during the alleged negotiations, on June 6, DataBreaches published redacted examples of personal information of employees and students.  On June 6, then, Pacific Union College could have and should have known personal information was involved. Not October 9. On or about June 6 at the latest.

Read the full article of June 6 to see what Pacific Union College knew or could have known.

Yet they told Maine the breach was discovered on October 9, and they told those being notified on November 8 that they had “recently discovered” a breach?

Why are entities permitted to get away with such deceptive notifications?

DataBreaches does not know whether the college will be hit with a class action lawsuit over this breach. If they are, plaintiffs’ counsel will likely find the June 6 report noteworthy.

And regardless of whether there is any class-action lawsuit, maybe the California Attorney General and the Federal Trade Commission should take a look both at the college’s risk assessment and security for personal information — including student federal financial aid forms and data that colleges are required to secure under GLBA.

Pacific_Union_College

Related:

  • Cyber-Attack On Bectu’s Parent Union Sparks UK National Security Concerns
  • Attorney General James Announces Settlement with Wojeski & Company Accounting Firm
  • JFL Lost Up to $800,000 Weekly After Cyberattack, CEO Says No Patient or Staff Data Was Compromised
  • John Bolton Indictment Provides Interesting Details About Hack of His AOL Account and Extortion Attempt
  • A business's cyber insurance policy included ransom coverage, but when they needed it, the insurer refused to pay. Why?
  • Before Their Telegram Channel Was Banned Again, ScatteredLAPSUS$Hunters Dropped Files Doxing Government Employees (2)
Category: Commentaries and AnalysesEducation SectorU.S.

Post navigation

← Bitter Pill: Third-Party Pharmaceutical Vendor Linked to Pharmacy and Health Clinic Cyberattack
Leader of $70M Cryptocurrency and Binary Options Fraud Schemes Extradited to the U.S. →

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

  • Doctor Alliance Data Breach: 353GB of Patient Files Allegedly Compromised, Ransom Demanded
  • St. Thomas Brushed Off Red Flags Before Dark-Web Data Dump Rocks Houston
  • A Wiltshire police breach posed possible safety concerns for violent crime victims as well as prison officers
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Almost two years later, Alpha Omega Winery notifies those affected by a data breach.
  • Court of Appeal reaffirms MFSA liability in data leak case, orders regulator to shoulder costs
  • A jailed hacking kingpin reveals all about the gang that left a trail of destruction
  • Army gynecologist took secret videos of patients during intimate exams, lawsuit says
  • The Case for Making EdTech Companies Liable Under FERPA
  • NHS providers reviewing stolen Synnovis data published by cyber criminals

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

  • Data broker Kochava agrees to change business practices to settle lawsuit
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Changes in the Rules for Disclosure for Substance Use Disorder Treatment Records: 42 CFR Part 2: What Changed, Why It Matters, and How It Aligns with HIPAAs
  • Always watching: How ICE’s plan to monitor social media 24/7 threatens privacy and civic participation
  • Who’s watching the watchers? This Mozilla fellow, and her Surveillance Watch map

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net
Security Issue: security[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.