mastodon.ie

0 posts0 participants0 posts today

Dissent Doe :cupofcoffee:<a href="https://infosec.exchange/@JayeLTee" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@JayeLTee</a> 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. <a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#databreach</a> <a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#healthsec</a> <a href="https://infosec.exchange/tags/HIPAA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HIPAA</a> <a href="https://infosec.exchange/tags/HHS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HHS</a> <a href="https://infosec.exchange/tags/incident_response" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#incident_response</a> <a href="https://infosec.exchange/tags/leak" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#leak</a>

Dissent Doe :cupofcoffee:Thanks to everyone in the fediverse who has favorited, boosted, and reached out to me supportively over the injunction and takedown order that I wouldn't comply with (overview: <a href="https://infosec.exchange/@PogoWasRight/114110520940142405" translate="no" rel="nofollow noopener noreferrer" target="_blank">https://infosec.exchange/@PogoWasRight/114110520940142405</a>) Special thanks to <a href="https://mastodon.social/@zackwhittaker" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@zackwhittaker</a> for reporting about it all on <a href="https://infosec.exchange/tags/TechCrunch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechCrunch</a>:<a href="https://techcrunch.com/2025/03/06/hacked-health-firm-hcrg-demanded-journalist-take-down-data-breach-reporting-citing-uk-court-order/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://techcrunch.com/2025/03/06/hacked-health-firm-hcrg-demanded-journalist-take-down-data-breach-reporting-citing-uk-court-order/</a><a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#databreach</a> <a href="https://infosec.exchange/tags/HCRG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HCRG</a> <a href="https://infosec.exchange/tags/ransomware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ransomware</a> <a href="https://infosec.exchange/tags/incident_response" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#incident_response</a> <a href="https://infosec.exchange/tags/injunction" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#injunction</a>

Dissent Doe :cupofcoffee:Another day, another leak, another inaccurate claim by an entity, and another inappropriate attack on a researcher. Buckle up. <a href="https://infosec.exchange/@JayeLTee" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@JayeLTee</a> had alerted me to his nasty encounter with TeammateApp's CEO. See his post <a href="https://infosec.exchange/@JayeLTee/114057470165488882" translate="no" rel="nofollow noopener noreferrer" target="_blank">https://infosec.exchange/@JayeLTee/114057470165488882</a> and his substack at <a href="https://jltee.substack.com/p/new-zealand-companys-impossible-to-hack-security" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://jltee.substack.com/p/new-zealand-companys-impossible-to-hack-security</a>My report/commentary is at :No need to hack when it’s leaking, Monday edition: TeammateApp: <a href="https://databreaches.net/2025/02/24/no-need-to-hack-when-its-leaking-monday-edition-teammateapp/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://databreaches.net/2025/02/24/no-need-to-hack-when-its-leaking-monday-edition-teammateapp/</a><a href="https://mastodon.social/@zackwhittaker" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@zackwhittaker</a> <a href="https://infosec.exchange/@SchizoDuckie" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@SchizoDuckie</a> <a href="https://infosec.exchange/tags/incident_response" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#incident_response</a> <a href="https://infosec.exchange/tags/disclosure" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#disclosure</a> <a href="https://infosec.exchange/tags/notification" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#notification</a> <a href="https://infosec.exchange/tags/dataleak" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dataleak</a>

Dissent Doe :cupofcoffee: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">https://databreaches.net/2025/02/22/beverly-hills-plastic-surgeon-jaime-schwartz-m-d-sued-for-not-timely-notifying-patients-of-two-hacks/</a>h/t, <a href="https://infosec.exchange/tags/404media" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#404media</a> <a href="https://infosec.exchange/tags/Courtwatch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Courtwatch</a> <a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#databreach</a> <a href="https://infosec.exchange/tags/extortion" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#extortion</a> <a href="https://infosec.exchange/tags/incident_response" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#incident_response</a> <a href="https://infosec.exchange/tags/notification" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#notification</a> <a href="https://infosec.exchange/tags/transparency" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#transparency</a> <a href="https://infosec.exchange/tags/hack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#hack</a> <a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#healthsec</a>

Dissent Doe :cupofcoffee:Some former employees of Granite School District are frustrated with the district's lack of accurate and timely information in the wake of a September attack by Rhysida -- especially since the data were leaked on Rhysida's leak site more than a month ago.A former employee tells me it only took him 3 hours to figure out that there were a lot more data types and affected people than the district has revealed so far. My post about it all: <a href="https://databreaches.net/2024/12/17/granite-school-district-breach-worse-than-the-district-has-revealed-former-employee/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://databreaches.net/2024/12/17/granite-school-district-breach-worse-than-the-district-has-revealed-former-employee/</a><a href="https://infosec.exchange/@douglevin" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@douglevin</a> <a href="https://freeradical.zone/@funnymonkey" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@funnymonkey</a> <a href="https://infosec.exchange/@brett" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@brett</a> <a href="https://journa.host/@mkeierleber" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@mkeierleber</a> <a href="https://infosec.exchange/tags/EduSec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EduSec</a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cybersecurity</a> <a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#databreach</a> <a href="https://infosec.exchange/tags/ransomware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ransomware</a> <a href="https://infosec.exchange/tags/incident_response" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#incident_response</a> <a href="https://infosec.exchange/tags/transparency" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#transparency</a> <a href="https://infosec.exchange/tags/disclosure" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#disclosure</a>

Dissent Doe :cupofcoffee:Cardiology of Virginia patient data appears to be up for sale. Has the entity issued any statement at all? <a href="https://databreaches.net/?p=118189" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://databreaches.net/?p=118189</a><a href="https://infosec.exchange/tags/HIPAA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HIPAA</a> <a href="https://infosec.exchange/tags/ransomware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ransomware</a> <a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#healthsec</a> <a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#databreach</a> <a href="https://infosec.exchange/tags/incident_response" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#incident_response</a>

The Nimble NerdDigital Sherlock: Decoding Threat Actor Behavior Through Forensics <a href="https://thenimblenerd.com/?p=16074&utm_content=bufferb270e&utm_medium=social&utm_source=bufferapp.com&utm_campaign=buffer" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://thenimblenerd.com/?p=16074&utm_content=bufferb270e&utm_medium=social&utm_source=bufferapp.com&utm_campaign=buffer</a> <a href="https://infosec.exchange/tags/incident_response" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#incident_response</a>

The Nimble NerdThe Confluence Confusion: CVE-2023-22518’s Digital Jaws Attack <a href="https://thenimblenerd.com/article/the-confluence-confusion-cve-2023-22518s-digital-jaws-attack" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://thenimblenerd.com/article/the-confluence-confusion-cve-2023-22518s-digital-jaws-attack</a> <a href="https://infosec.exchange/tags/incident_response" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#incident_response</a>

The Nimble NerdApple’s Buffet of Bugs: A Carnival of Vulnerabilities <a href="https://thenimblenerd.com/article/apples-buffet-of-bugs-a-carnival-of-vulnerabilities" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://thenimblenerd.com/article/apples-buffet-of-bugs-a-carnival-of-vulnerabilities</a> <a href="https://infosec.exchange/tags/incident_response" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#incident_response</a>

The Nimble NerdPinata of Vulnerabilities: Linux Kernel’s Latest Security Advisory Unwrapped <a href="https://thenimblenerd.com/article/pinata-of-vulnerabilities-linux-kernels-latest-security-advisory-unwrapped" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://thenimblenerd.com/article/pinata-of-vulnerabilities-linux-kernels-latest-security-advisory-unwrapped</a> <a href="https://infosec.exchange/tags/incident_response" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#incident_response</a>

The Nimble NerdBaking a Financial Disaster: The French ATM Company Serving Vulnerability Croissants <a href="https://thenimblenerd.com/article/baking-a-financial-disaster-the-french-atm-company-serving-vulnerability-croissants" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://thenimblenerd.com/article/baking-a-financial-disaster-the-french-atm-company-serving-vulnerability-croissants</a> <a href="https://infosec.exchange/tags/incident_response" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#incident_response</a>

Recent searches

Search options

Administered by:

Server stats:

#incident_response