urbanists.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
We're a server for people who like bikes, transit, and walkable cities. Let's get to know each other!

Server stats:

529
active users

#healthsec

1 post1 participant0 posts today
Dissent Doe :cupofcoffee:<p>It sounds like Esse Health suffered a seriously impactful ransomware attack that affected their ability to access patient records and provide some patient care. </p><p>I have not seen any group claim responsibility for this attack (yet), but here is a media link and link to Esse Health's undated update notice:</p><p><a href="https://www.firstalert4.com/2025/05/07/cyberattack-puts-healthcare-hold-hundreds-st-louis-metro/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">firstalert4.com/2025/05/07/cyb</span><span class="invisible">erattack-puts-healthcare-hold-hundreds-st-louis-metro/</span></a><br><a href="https://www.essehealth.com/network-updates/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">essehealth.com/network-updates/</span><span class="invisible"></span></a></p><p><a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>databreach</span></a> <a href="https://infosec.exchange/tags/ransomware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ransomware</span></a> <a href="https://infosec.exchange/tags/HealthSec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HealthSec</span></a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cybersecurity</span></a></p>
Dissent Doe :cupofcoffee:<p>Correcting one of my posts: It was not Atrium Health that owned the data Jeremiah Fowler reported on to Website Planet. I heard from Atrium Health today and it was Carolina Anesthesiology, P.A., who owned the data that were exposed. </p><p>My corrected post is at:<br><a href="https://databreaches.net/2025/04/24/no-need-to-hack-when-its-leaking/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">databreaches.net/2025/04/24/no</span><span class="invisible">-need-to-hack-when-its-leaking/</span></a></p><p><a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>healthsec</span></a> <a href="https://infosec.exchange/tags/dataleak" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dataleak</span></a></p><p>(I can't believe it but I just had to correct my correction on the name of the actual owners. Please make this week be over.)</p>
Dissent Doe :cupofcoffee:<p>Updating an incident: </p><p>The InterLock ransomware gang has claimed responsibility for the DaVita attack. They claim to have exfiltrated &nbsp;1,510 GB of data,&nbsp; 683,104 files, and&nbsp; 75,836 folders, and have leaked the file tree and some folder information.</p><p><a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>healthsec</span></a> <a href="https://infosec.exchange/tags/ransomware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ransomware</span></a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cybersecurity</span></a> <a href="https://infosec.exchange/tags/DaVita" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DaVita</span></a> <a href="https://infosec.exchange/tags/InterLock" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>InterLock</span></a> <a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>databreach</span></a></p>
Dissent Doe :cupofcoffee:<p>No need to hack when it’s leaking: Atrium Health edition:<br><a href="https://databreaches.net/2025/04/24/no-need-to-hack-when-its-leaking-atrium-health-edition/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">databreaches.net/2025/04/24/no</span><span class="invisible">-need-to-hack-when-its-leaking-atrium-health-edition/</span></a></p><p><a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>healthsec</span></a> <a href="https://infosec.exchange/tags/leak" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>leak</span></a> <a href="https://infosec.exchange/tags/HIPAA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HIPAA</span></a> <a href="https://infosec.exchange/tags/SecurityRule" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SecurityRule</span></a> <a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>databreach</span></a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cybersecurity</span></a></p>
Dissent Doe :cupofcoffee:<p><span class="h-card" translate="no"><a href="https://infosec.exchange/@JayeLTee" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>JayeLTee</span></a></span> SavantCare never responded to my inquiries, either. Prior to sending them questions, I simply queried them as to whether they are covered by HIPAA. They responded to that email by affirming that they are regulated by HIPAA. But then they ignored all the questions that followed about the leak, their data security, any business associate agreement with GRMTech, and whether they are notifying HHS and affected patients. </p><p><a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>databreach</span></a> <a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>healthsec</span></a> <a href="https://infosec.exchange/tags/HIPAA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HIPAA</span></a> <a href="https://infosec.exchange/tags/HHS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HHS</span></a> <a href="https://infosec.exchange/tags/incident_response" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>incident_response</span></a> <a href="https://infosec.exchange/tags/leak" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>leak</span></a></p>
Dissent Doe :cupofcoffee:<p>UnitedHealth's Change Healthcare got a ton of what some might consider well-deserved bad press last year after a ransomware attack by AlphV/BlackCat. </p><p>Now they're getting more bad press. </p><p>UnitedHealth is demanding that some struggling doctors immediately repay loans issued after last year’s cyberattack. That wasn't the way the providers were told repayment would work in terms of when and how. </p><p><a href="https://infosec.exchange/tags/CNBC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CNBC</span></a> has the story:</p><p><a href="https://www.cnbc.com/2025/04/11/unitedhealth-makes-doctors-repay-loans-issued-after-change-cyberattack.html" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">cnbc.com/2025/04/11/unitedheal</span><span class="invisible">th-makes-doctors-repay-loans-issued-after-change-cyberattack.html</span></a></p><p><a href="https://infosec.exchange/tags/IncidentResponse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IncidentResponse</span></a> <a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>databreach</span></a> <a href="https://infosec.exchange/tags/ransomware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ransomware</span></a> <a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>healthsec</span></a></p>
Dissent Doe :cupofcoffee:<p>From the We-Wish-This-Was-An-April-Fools-Joke-But-It’s-Not department:</p><p>Vitenas Cosmetic Surgery patient data hacked and leaked</p><p><a href="https://databreaches.net/2025/04/01/vitenas-cosmetic-surgery-patient-data-hacked-and-leaked/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">databreaches.net/2025/04/01/vi</span><span class="invisible">tenas-cosmetic-surgery-patient-data-hacked-and-leaked/</span></a></p><p><a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>databreach</span></a> <a href="https://infosec.exchange/tags/extortion" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>extortion</span></a> <a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>healthsec</span></a></p>
Dissent Doe :cupofcoffee:<p>Oracle Health is becoming the poster child for how NOT to respond to a breach:</p><p><a href="https://www.bleepingcomputer.com/news/security/oracle-health-breach-compromises-patient-data-at-us-hospitals/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">bleepingcomputer.com/news/secu</span><span class="invisible">rity/oracle-health-breach-compromises-patient-data-at-us-hospitals/</span></a></p><p><a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>healthsec</span></a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cybersecurity</span></a> <a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>databreach</span></a> <a href="https://infosec.exchange/tags/incidentresponse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>incidentresponse</span></a> <a href="https://infosec.exchange/tags/HIPAA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HIPAA</span></a> <a href="https://infosec.exchange/tags/transparency" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>transparency</span></a></p>
Dissent Doe :cupofcoffee:<p>Four months after learning of a vendor's breach, Concord Orthopaedics in NH notifies almost 68,000 patients. </p><p>At the same time that they were mailing notifications, <a href="https://infosec.exchange/tags/EverestTeam" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>EverestTeam</span></a> was leaking 2.9 GB of files with patient info from 2018-2024. </p><p><a href="https://databreaches.net/2025/03/27/four-months-after-learning-of-a-vendors-breach-concord-orthopaedics-notifies-almost-68000-patients/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">databreaches.net/2025/03/27/fo</span><span class="invisible">ur-months-after-learning-of-a-vendors-breach-concord-orthopaedics-notifies-almost-68000-patients/</span></a></p><p><a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>databreach</span></a> <a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>healthsec</span></a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cybersecurity</span></a> <a href="https://infosec.exchange/tags/ThirdParty" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ThirdParty</span></a> <a href="https://infosec.exchange/tags/vendor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>vendor</span></a> <a href="https://infosec.exchange/tags/HIPAA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HIPAA</span></a></p>
Dissent Doe :cupofcoffee:<p>Health-care billing company Medical Billing Specialists Inc. (MBS Select) has been hit with a potential class action lawsuit over their 2024 breach.</p><p>Notifications first went out a year after the attack by Akira ransomware group. </p><p><a href="https://databreaches.net/2025/02/26/medical-billing-vendor-sued-over-health-data-leak-gold-mine/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">databreaches.net/2025/02/26/me</span><span class="invisible">dical-billing-vendor-sued-over-health-data-leak-gold-mine/</span></a></p><p>h/t, Bloomberg Law.</p><p>Direct link to complaint: <a href="https://www.bloomberglaw.com/public/desktop/document/MarianoGuerravMedicalBillingSpecialistsIncDocketNo125cv10453DMass?doc_id=X7V6GF8O0QV9EOAVLKEKKSJCO87" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">bloomberglaw.com/public/deskto</span><span class="invisible">p/document/MarianoGuerravMedicalBillingSpecialistsIncDocketNo125cv10453DMass?doc_id=X7V6GF8O0QV9EOAVLKEKKSJCO87</span></a></p><p><a href="https://infosec.exchange/tags/BAA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BAA</span></a> <a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>databreach</span></a> <a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>healthsec</span></a> <a href="https://infosec.exchange/tags/ransomware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ransomware</span></a> <a href="https://infosec.exchange/tags/notification" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>notification</span></a></p>
Dissent Doe :cupofcoffee:<p>From Bluesight's press release for the 2025 Breach Barometer, some of the key findings:</p><ul><li><p>More than 300 million patient records breached in 2024, a 26% increase over 2023. This included the largest healthcare breach ever recorded, affecting 1 in 2 Americans.</p></li><li><p>Insider threats, hackers and third-party relationships drove breach impact in 2024, with business associates accounting for the majority of breached records (77%) in the 2025 Breach Barometer dataset.</p></li><li><p>Breach notifications took an average of 205 days&nbsp;after an incident in 2024, compared to 177 days in the previous year.</p></li></ul><p>I'll have more details on some of these issues on my blog in the near future, but encourage you to download the full report now: </p><p><a href="https://bluesight.com/wp-content/uploads/2025/02/2025-Breach-Barometer-Annual-Report.pdf" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">bluesight.com/wp-content/uploa</span><span class="invisible">ds/2025/02/2025-Breach-Barometer-Annual-Report.pdf</span></a></p><p>For those of you that read the Protenus Breach Barometer report I produced with Protenus every year beginning in 2016, Bluesight recently acquired Protenus and is continuing to produce the report in collaboration with my work. </p><p><a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>databreach</span></a> <a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>healthsec</span></a> <a href="https://infosec.exchange/tags/statistics" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>statistics</span></a> <a href="https://infosec.exchange/tags/analysis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>analysis</span></a> <a href="https://infosec.exchange/tags/BAA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BAA</span></a></p>
Dissent Doe :cupofcoffee:<p>Update: On February 24, 2025, the Termite ransomware group claimed responsibility for the attack on Genea, a network of fertility (IVF) clinics in Australia.</p><p>On their dark web leak site, Termite claims to have ~700 GB of data from Genea's servers,, including patient data. They posted a number of screenshots with patient records as proof of claims.&nbsp;</p><p><a href="https://infosec.exchange/tags/Genea" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Genea</span></a> <a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>databreach</span></a> <a href="https://infosec.exchange/tags/IVF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IVF</span></a> <a href="https://infosec.exchange/tags/ransomware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ransomware</span></a> <a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>healthsec</span></a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cybersecurity</span></a> <a href="https://infosec.exchange/tags/Termite" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Termite</span></a></p><p><span class="h-card" translate="no"><a href="https://mastodon.social/@David_Hollingworth" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>David_Hollingworth</span></a></span></p>
Dissent Doe :cupofcoffee:<p>Beverly Hills Plastic Surgeon Jaime Schwartz M.D. Sued for Not Timely Notifying Patients of Two Hacks: <a href="https://databreaches.net/2025/02/22/beverly-hills-plastic-surgeon-jaime-schwartz-m-d-sued-for-not-timely-notifying-patients-of-two-hacks/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">databreaches.net/2025/02/22/be</span><span class="invisible">verly-hills-plastic-surgeon-jaime-schwartz-m-d-sued-for-not-timely-notifying-patients-of-two-hacks/</span></a></p><p>h/t, <a href="https://infosec.exchange/tags/404media" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>404media</span></a> <a href="https://infosec.exchange/tags/Courtwatch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Courtwatch</span></a> </p><p><a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>databreach</span></a> <a href="https://infosec.exchange/tags/extortion" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>extortion</span></a> <a href="https://infosec.exchange/tags/incident_response" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>incident_response</span></a> <a href="https://infosec.exchange/tags/notification" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>notification</span></a> <a href="https://infosec.exchange/tags/transparency" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>transparency</span></a> <a href="https://infosec.exchange/tags/hack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>hack</span></a> <a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>healthsec</span></a></p>