DataBreaches.Net

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

Vulnerabilities in a Third-Party Healthcare Payment Processor

Posted on March 29, 2016 by Dissent

Randy Westergren looked into Christiana Care’s online payment portal, which involves  a third party payment processor developed by BYL Companies, LLC.  What Randy found was very concerning, and he promptly notified BYL of his findings.

You can read his write-up of it all on his site.

So here’s the thing: how many people may have actually exploited the vulnerability he found before he reported it and they patched it?  We don’t know.

This is not the first time a healthcare payment processor screwed up. Years ago, I reported how Verus, Inc. forgot to restore a firewall following an upgrade and left a number of its client hospitals’ payment portals unsecured. Over 60,000 patients had to be notified and the firm folded.

How secure do you feel using online patient portals? I’ve never used them because I’m so distrustful of security – or lack thereof – by now.

 

Category: Breach IncidentsExposureHealth DataSubcontractor

Post navigation

← NY: Nurse who took pics of patients’ private parts at Syracuse hospital turns in license
NZ: Case note 269784: Employee repeatedly accessed health records without proper reason →

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

  • Major trial underway for data leak that left 72,000 victims in France
  • Anubis: A Closer Look at an Emerging Ransomware with Built-in Wiper
  • HealthEC Agrees to $5.48 Million Settlement to End Data Breach Lawsuit
  • US offering $10 million for info on Iranian hackers behind IOControl malware
  • Sompo Japan Insurance submits improvement plan after info leakage
  • Moreno Valley, Calif., Schools Report Data Breach
  • The Growing Cyber Risks from AI — and How Organizations Can Fight Back
  • Credit Control Corporation data allegedly from 9.1 million consumers listed for sale on forum
  • Copilot AI Bug Could Leak Sensitive Data via Email Prompts
  • FTC Provides Guidance on Updated Safeguards Rule

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

  • Your household smart products must respect your privacy – including your air fryer
  • Vermont signs Kids Code into law, faces legal challenges
  • Data Categories and Surveillance Pricing: Ferguson’s Nuanced Approach to Privacy Innovation
  • Anne Wojcicki Wins Bidding for 23andMe
  • Would you — or wouldn’t you?
  • New York passes a bill to prevent AI-fueled disasters
  • Synthetic Data and the Illusion of Privacy: Legal Risks of Using De-Identified AI Training Sets

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.