DataBreaches.Net

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

The Global State of Internet of Healthcare Things (IoHT) Exposures on Public-Facing Networks

Posted on October 22, 2024 by Dissent

Censys recently published a new research report that looks at exposed data on the internet involving healthcare devices and systems connected to PHI. Here’s their Executive Summary:

  • Censys discovered 14,004 unique IP addresses exposing healthcare devices and data systems connected to potentially sensitive medical information on the public internet. These exposures greatly raise the risk of unauthorized access and exploitation. This figure likely reflects the lower bound of the total risk, as many more devices may be exposed but not publicly visible..
  • Nearly 50% of the exposed hosts (6,884) are located in the United States, followed by 10.5% (1,476) in India. This is likely due to both countries having large, complex healthcare infrastructure that serves large populations, where organizations must handle vast amounts of sensitive data. Comparatively, we detected only 200 publicly available hosts in the United Kingdom, possibly a reflection of its more centralized healthcare infrastructure.
  • Open DICOM ports and DICOM-enabled web interfaces intended for exchanging and viewing medical images account for 36% of the exposures, with 5,100 hosts publicly exposing these systems. This is concerning because DICOM is a legacy protocol with several known security weaknesses.
  • EMR/EHR systems, which store and manage electronic health records, represent the second-largest exposure type at 28% with 4,031 interfaces publicly available. The exposure of the login interfaces to these systems potentially puts vast amounts of sensitive personal health data, including medical histories and social security numbers at risk.
  • Healthcare organizations must prioritize securing their internet-exposed assets that handle sensitive patient data, particularly DICOM and EMR/EHR systems. This includes strengthening access controls, enforcing multi-factor authentication, and ensuring proper configurations in both cloud and on-premise environments to protect sensitive medical data.

Read more at Censys.

 


Related:

  • Little Rock Psychologist Indicted by Federal Grand Jury for Defrauding Medicare and Arkansas Blue Cross Blue Shield
  • Software companies must be held liable for British economic security, say MPs
  • UK privacy regulator has seen ‘collapse in enforcement activity,’ rights coalition says
  • SEC Voluntarily Dismisses SolarWinds Litigation
  • Cyberattack disables Onsolve Code Red emergency alert system across St. Louis region (1)
  • CrowdStrike catches insider feeding information to ScatteredLapsus$Hunters
Category: Commentaries and AnalysesHealth DataOf Note

Post navigation

← Hong Kong watchdog slams sports club for sloppy cybersecurity ahead of ransomware attack
Pro-Palestinian hacktivists attack infrastructure in Cyprus →

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

  • Defense Bill Would Require New Cyber Requirements for Some DoD Telecom Contracts
  • Tell the truth, or someone will tell it for you — Trumbull County, Ohio edition
  • US Posts $10 Million Bounty for Iranian Hackers
  • South Korea police raid e-commerce giant Coupang over data leak; govt schedules hearing
  • FinCEN Report: Reported Ransomware Incidents and Payments Reached All-Time High in 2023
  • Leavenworth, Kansas cyberattack disrupts city services
  • They’ve escaped a lot of media attention, but Anubis RaaS is a threat to the medical sector (1)
  • “In the most expedient time possible…”
  • Portugal updates cybercrime law to exempt security researchers
  • LockBit 5’s “new secure blog domain” infra leaked already

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

  • FTC Denies Petition from SpyFone App CEO to Vacate 2021 Order
  • Privacy concerns raised as Grok AI found to be a stalker’s best friend
  • PRIVACY—S.D. Cal.: Employee did not waive privacy right in personal email data on company provided laptop, (Dec 5, 2025)
  • EU justice chief draws red line on privacy reforms
  • Kaiser Permanente to Pay Up to $47.5M in Web Tracker Lawsuit

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: Dissent.73
DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.