DataBreaches.Net

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

Ignoring leak reports and inquiries is just asking for trouble

Posted on October 9, 2014 by Dissent

This is an example of how NOT to secure patient information and how NOT to respond when you’re contacted about a vulnerability.

Kevin Wetzel of SLC Security Services LLC posted a vulnerability report on Cape Fear Valley Health System in Fayetteville, NC.  The vulnerability, first noted by SLC on August 26, was described as the entity leaking PII and PHI via unencrypted email.  Over 1,000 patient records were noted, although SLC did not continue to monitor the leak as SLC is not one of their clients.  They describe the leak this way:

This entity is leaking information containing PII and confidential patient information to include name, date of birth and location as well as diagnostic and treatment information. There are multiple issues with this entity to include email issues as well as unencrypted radio communications and potential wireless issues at their location

If that’s true, then Ouch!

Wetzel reports that he spoke with the privacy officer at Cape Fear Medical:

That office stated that their IT Security Personnel would be in touch with our office to obtain the information as of 9/9/2014. No follow up has been acknowledged.

So what happened then? Has Cape Fear  investigated? Has it notified patients of any leak? Has it notified HHS?

Cape Fear Valley did not respond to an email inquiry sent to them on September 18 by PHIprivacy.net.

Category: Uncategorized

Post navigation

← TX: 4,000 veterans personal information compromised
Macomb County, Michigan notifies employees and dependents of business associate breach →

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

  • Washington Post investigating cyberattack on journalists, WSJ reports
  • Resource: State Data Breach Notification Laws – June 2025
  • WestJet investigates cyberattack disrupting internal systems
  • Plastic surgeons often store nude photos of patients with their identity information. When would we call that “negligent?”
  • India: Servers of two city hospitals hacked; police register FIR
  • Ph: Coop Hospital confirms probe into reported cyberattack
  • Slapped wrists for Financial Conduct Authority staff who emailed work data home
  • School Districts Unaware BoardDocs Software Published Their Private Files
  • A guilty plea in the PowerSchool case still leaves unanswered questions
  • Brussels Parliament hit by cyber-attack

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

  • 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
  • States sue to block the sale of genetic data collected by DNA testing company 23andMe

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.