Walker<p><span class="h-card" translate="no"><a href="https://cyberplace.social/@GossiTheDog" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>GossiTheDog</span></a></span> its not like DFIR relies on audit logs.</p><p>For fucks sake, Microsoft.</p><p><a href="https://infosec.exchange/tags/incidentresponse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>incidentresponse</span></a> <a href="https://infosec.exchange/tags/dfir" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dfir</span></a></p>
101010.pl is one of the many independent Mastodon servers you can use to participate in the fediverse.
101010.pl czyli najstarszy polski serwer Mastodon. Posiadamy wpisy do 2048 znaków.
Administered by:
Server stats:
483active users
101010.pl: About · Status · Profiles directory · Privacy policy
Mastodon: About · Get the app · Keyboard shortcuts · View source code · v4.5.0-alpha.2
#incidentresponse
4 posts · 4 participants · 0 posts today
Dissent Doe :cupofcoffee:<p>First it looked like Clinical Diagnostics (Eurofins) had paid Nova ransomware gang not to leak the Dutch patient data for 485k women in cancer screening program. Nova even confirmed they got paid to a news outlet (which in and of itself is weird, as most gangs will not acknowledge payment). </p><p>But then yesterday, Nova changed the listing and seems to now be demanding more payment because the police got involved? </p><p>It's very hard to figure out what Nova is saying in their broken English and translations of where they now write in Russian. See what you think:</p><p><a href="https://databreaches.net/2025/08/19/when-a-deal-is-not-a-done-deal-nova-demands-higher-payment-from-clinical-diagnostics/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">databreaches.net/2025/08/19/wh</span><span class="invisible">en-a-deal-is-not-a-done-deal-nova-demands-higher-payment-from-clinical-diagnostics/</span></a></p><p><a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>databreach</span></a> <a href="https://infosec.exchange/tags/ransomware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ransomware</span></a> <a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>healthsec</span></a> <a href="https://infosec.exchange/tags/incidentresponse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>incidentresponse</span></a></p>
Chum1ng0 - Security Research :verified:<p><a href="https://infosec.exchange/tags/Brazil" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Brazil</span></a>: 121,981 files were exposed without security on a server containing health documents.</p><p>*I contacted the Acqua Institute via email reporting their server being compromised, attaching this email with CERT BR; none of these entities responded to my email*</p><p>-The server was blocked on July 16th-</p><p>-I tried to contact the ANPD (National Data Protection Authority) but never received a response.</p><p>-I contacted a data protection expert who answered my questions that the ANPD couldn't answer via email.</p><p>-The data controller may have informed the ANPD, we don't know...</p><p>Read more: </p><p><a href="https://medium.com/@newschu.substack.com/brazil-121-981-files-were-exposed-without-security-on-a-server-containing-health-documents-50dee9f31bb1" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">medium.com/@newschu.substack.c</span><span class="invisible">om/brazil-121-981-files-were-exposed-without-security-on-a-server-containing-health-documents-50dee9f31bb1</span></a></p><p><a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cybersecurity</span></a> <a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>databreach</span></a> <a href="https://infosec.exchange/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dataleak</span></a> <a href="https://infosec.exchange/tags/incidentresponse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>incidentresponse</span></a> </p><p><span class="h-card" translate="no"><a href="https://infosec.exchange/@PogoWasRight" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>PogoWasRight</span></a></span></p>
Dissent Doe :cupofcoffee:<p>Well, I've had it. The firm responsible for exposed court and prosecution files from at least two states has not responded to phone calls, emails, LinkedIn messages, or contacts by their host. </p><p>On Saturday, I called the FBI tip line and let them know what's going on. Maybe the FBI will call me and ask me for the IP addresses so they can call the firm and tell them to lock down the damned shares. </p><p>Then today, I filed a formal <a href="https://infosec.exchange/tags/FTC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FTC</span></a> complaint against the firm for violation of Section 5 of the FTC Act for its inadequate security, its failure to have any procedure to receive, evaluate, and escalate third -party alerts of security issues, and for using the same password in all client installations for a Msql SQL database.</p><p>And oh, last night I learned that a court system in a third state was not only exposed, too, but was hit by ransomware in March. Lovely. </p><p><a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cybersecurity</span></a> <a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>infosec</span></a> <a href="https://infosec.exchange/tags/incidentresponse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>incidentresponse</span></a> <a href="https://infosec.exchange/tags/FTC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FTC</span></a> <a href="https://infosec.exchange/tags/govsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>govsec</span></a> <a href="https://infosec.exchange/tags/judiciary" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>judiciary</span></a> <a href="https://infosec.exchange/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dataleak</span></a> <a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>databreach</span></a></p>
al3x<p>hey friends, still me, still sharing roles even in the full of summer. someone i know is the SOC lead for a MSSP and is looking for a DFIR person for a weekend 4/10 shift. anyone interested? hmu with your linkedin and i’ll pass along 😊</p><p><a href="https://infosec.exchange/tags/getfedihired" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>getfedihired</span></a> <a href="https://infosec.exchange/tags/dfir" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dfir</span></a> <a href="https://infosec.exchange/tags/soc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>soc</span></a> <a href="https://infosec.exchange/tags/incidentresponse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>incidentresponse</span></a></p>
Dissent Doe :cupofcoffee:<p>So as a quick update on the issue of two state courts that we know of exposing sealed records: </p><p>Last night, those of us still trying to figure out who was responsible figured it out -- it is a vendor (third-party) who is responsible for the exposed shares. </p><p>With the researcher's cooperation and input, I sent a detailed email last night to the only email address that vendor has on their website. </p><p>No reply was received, of course. </p><p>So I just called their main number... and started to tell them why I was calling, and they hung up on me.</p><p>😡 </p><p>I just called back. They didn't answer the phone, so I left a VM on their administrative offices' extension. </p><p>If the firm doesn't call me back or lock down those shares today, expect me to say more here tomorrow. </p><p>It is now 1 month since people started trying to get these shares secured. None of us are paid to do this. And getting hung up on should get the company a <a href="https://infosec.exchange/tags/CID" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CID</span></a> from the <a href="https://infosec.exchange/tags/FTC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FTC</span></a> in a more perfect world -- to ask what their procedures and policies are for receiving a security alert from an external (third) party.</p><p><a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>infosec</span></a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cybersecurity</span></a> <a href="https://infosec.exchange/tags/incidentresponse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>incidentresponse</span></a> <a href="https://infosec.exchange/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dataleak</span></a> <a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>databreach</span></a></p>
Dissent Doe :cupofcoffee:<p>Promises, promises. </p><p>Exclusive: Brosix and Chatox promised to keep your chats secured. They didn’t.</p><p>A researcher found a misconfigured backup with -- yes, you guessed it -- everything in plaintext instead of encrypted. </p><p>Some entities that used the service are medical entities that were actually mentioning protected health information or attaching files with <a href="https://infosec.exchange/tags/PHI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PHI</span></a> in the chat. </p><p>There were almost 5k Allstate employees using the service and sharing customer <a href="https://infosec.exchange/tags/PII" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PII</span></a> in files. </p><p>And oh yeah, I found one company gossiping about me and plotting against me after I notified them they were leaking tons of <a href="https://infosec.exchange/tags/PHI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PHI</span></a>. I've done them a favor by not publishing all their chat logs about me. :) </p><p>There also appeared to be some "dodgy" stuff on the backup, too. </p><p>Read the details about the exposed backup in my post at <a href="https://databreaches.net/2025/08/05/exclusive-brosix-and-chatox-promised-to-keep-your-chats-secured-they-didnt/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">databreaches.net/2025/08/05/ex</span><span class="invisible">clusive-brosix-and-chatox-promised-to-keep-your-chats-secured-they-didnt/</span></a></p><p><a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>infosec</span></a> <a href="https://infosec.exchange/tags/encryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>encryption</span></a> <a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>databreach</span></a> <a href="https://infosec.exchange/tags/incidentresponse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>incidentresponse</span></a> <a href="https://infosec.exchange/tags/chatox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>chatox</span></a> <a href="https://infosec.exchange/tags/brosix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>brosix</span></a> <a href="https://infosec.exchange/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dataleak</span></a></p><p><span class="h-card" translate="no"><a href="https://mastodon.social/@zackwhittaker" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>zackwhittaker</span></a></span></p>
Dissent Doe :cupofcoffee:<p>A number of sites are misreporting a Premier Health Partners breach as affecting 154,731 patients. That number was actually a partial number from an <em>earlier</em> incident and not from the 2023 one they have just issued a press release about. </p><p>More background and details at:</p><p><a href="https://databreaches.net/2025/07/20/premier-health-partners-issues-a-press-release-about-a-breach-two-years-ago-why-was-this-needed-now/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">databreaches.net/2025/07/20/pr</span><span class="invisible">emier-health-partners-issues-a-press-release-about-a-breach-two-years-ago-why-was-this-needed-now/</span></a></p><p><a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>databreach</span></a> <a href="https://infosec.exchange/tags/HIPAA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HIPAA</span></a> <a href="https://infosec.exchange/tags/incidentresponse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>incidentresponse</span></a></p>
Pen Test Partners<p>A critical vulnerability in old Telerik software gave an attacker remote code execution on an SFTP-only Windows server. That meant they didn’t need credentials, antivirus didn’t trigger, and default log sizes meant almost nothing useful was captured.</p><p>From there? PowerShell exclusions, admin account created, RDP tunnelled in via Ngrok, ransomware deployed. </p><p>They even opened Pornhub either to cover traffic or celebrate the moment. Who knows?</p><p>This attack wasn’t subtle. But it worked because basic controls were missing. </p><p>We’ve broken down the incident. Plus, recommendations you can act on now to prevent the same thing.</p><p>📌<a href="https://www.pentestpartners.com/security-blog/sil3ncer-deployed-rce-porn-diversion-and-ransomware-on-an-sftp-only-server/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">pentestpartners.com/security-b</span><span class="invisible">log/sil3ncer-deployed-rce-porn-diversion-and-ransomware-on-an-sftp-only-server/</span></a></p><p><a href="https://infosec.exchange/tags/CyberSecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CyberSecurity</span></a> <a href="https://infosec.exchange/tags/IncidentResponse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IncidentResponse</span></a> <a href="https://infosec.exchange/tags/Ransomware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Ransomware</span></a> <a href="https://infosec.exchange/tags/ThreatDetection" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ThreatDetection</span></a> <a href="https://infosec.exchange/tags/DigitalForensics" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DigitalForensics</span></a> <a href="https://infosec.exchange/tags/InfoSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>InfoSec</span></a></p>
Brian Greenberg :verified:<p>A major cybersecurity legal case is moving forward. ✈️ Delta Air Lines proceeding with its $550M+ lawsuit against CrowdStrike over the July 2024 outage that canceled 7,000 flights and impacted 1.3M passengers.</p><p>⚖️ The court allowed claims of:<br>🧠 Gross negligence<br>💻 Computer trespass<br>🕵️♂️ Limited fraud</p><p>📉 Delta claims the update could have been caught with a simple test. CrowdStrike is pushing back, saying damages should be limited under Georgia law. This case may redefine how courts view software vendor liability, especially for updates in critical infrastructure.</p><p>💬 Should companies expect higher legal accountability for third-party software failures?</p><p><a href="https://infosec.exchange/tags/CyberSecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CyberSecurity</span></a> <a href="https://infosec.exchange/tags/Delta" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Delta</span></a> <a href="https://infosec.exchange/tags/CrowdStrike" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CrowdStrike</span></a> <a href="https://infosec.exchange/tags/LegalTech" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LegalTech</span></a> <a href="https://infosec.exchange/tags/IncidentResponse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IncidentResponse</span></a></p><p><a href="https://www.reuters.com/sustainability/boards-policy-regulation/delta-can-sue-crowdstrike-over-computer-outage-that-caused-7000-canceled-flights-2025-05-19/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">reuters.com/sustainability/boa</span><span class="invisible">rds-policy-regulation/delta-can-sue-crowdstrike-over-computer-outage-that-caused-7000-canceled-flights-2025-05-19/</span></a></p>
Dissent Doe :cupofcoffee:<p>In August 2020, <span class="h-card" translate="no"><a href="https://infosec.exchange/@SchizoDuckie" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>SchizoDuckie</span></a></span> and I published what was to become the first of a series of articles or posts called "No Need to Hack When It's Leaking."</p><p>In today's installment, I bring you "No Need to Hack When It's Leaking: Brandt Kettwick Defense Edition." It chronicles efforts by <span class="h-card" translate="no"><a href="https://infosec.exchange/@JayeLTee" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>JayeLTee</span></a></span>, <span class="h-card" translate="no"><a href="https://infosec.exchange/@masek" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>masek</span></a></span>, and I to alert a Minnesota law firm to lock down their exposed files, some of which were quite sensitive.</p><p>Read the post and see how even the state's Bureau of Criminal Apprehension had trouble getting this law firm to respond appropriately. </p><p><a href="https://databreaches.net/2025/07/04/no-need-to-hack-when-its-leaking-brandt-kettwick-defense-edition/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">databreaches.net/2025/07/04/no</span><span class="invisible">-need-to-hack-when-its-leaking-brandt-kettwick-defense-edition/</span></a></p><p>Great thanks to the Minnesota Bureau of Criminal Apprehension for their help on this one, and to <span class="h-card" translate="no"><a href="https://infosec.exchange/@TonyYarusso" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>TonyYarusso</span></a></span> and <span class="h-card" translate="no"><a href="https://hachyderm.io/@bkoehn" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>bkoehn</span></a></span> for their efforts. </p><p><a href="https://infosec.exchange/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dataleak</span></a> <a href="https://infosec.exchange/tags/misconfiguration" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>misconfiguration</span></a> <a href="https://infosec.exchange/tags/incidentresponse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>incidentresponse</span></a> <a href="https://infosec.exchange/tags/incidentmanagement" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>incidentmanagement</span></a> <a href="https://infosec.exchange/tags/responsibledisclosure" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>responsibledisclosure</span></a> <a href="https://infosec.exchange/tags/securityalert" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>securityalert</span></a> <a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>infosec</span></a></p>
Walker<p><span class="h-card" translate="no"><a href="https://cyberplace.social/@GossiTheDog" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>GossiTheDog</span></a></span> </p><p>See, this is why I like this field, when people are involved you always see something new. </p><p>The third party ransomware negotiator, negotiated kickbacks from the ransomware actor when negotiating the ransom payment for their client. </p><p>Amazing.</p><p><a href="https://infosec.exchange/tags/incidentresponse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>incidentresponse</span></a> <a href="https://infosec.exchange/tags/ransomware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ransomware</span></a></p>
Dissent Doe :cupofcoffee:<p>With great thanks to <span class="h-card" translate="no"><a href="https://infosec.exchange/@masek" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>masek</span></a></span> and <span class="h-card" translate="no"><a href="https://infosec.exchange/@JayeLTee" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>JayeLTee</span></a></span> and others who assisted or tried to, including Rogers ISP and law enforcement in Canada, we can finally say:</p><p>Bolton Walk-In Clinic patient data leak locked down! </p><p>Read about this very frustrating effort to get exposed patient data locked down:</p><p><a href="https://databreaches.net/2025/06/30/bolton-walk-in-clinic-patient-data-leak-locked-down-finally/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">databreaches.net/2025/06/30/bo</span><span class="invisible">lton-walk-in-clinic-patient-data-leak-locked-down-finally/</span></a></p><p><a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>healthsec</span></a> <a href="https://infosec.exchange/tags/PHIPA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PHIPA</span></a> <a href="https://infosec.exchange/tags/HIPA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HIPA</span></a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cybersecurity</span></a> <a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>infosec</span></a> <a href="https://infosec.exchange/tags/incidentresponse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>incidentresponse</span></a> <a href="https://infosec.exchange/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dataleak</span></a></p>
Dissent Doe :cupofcoffee:<p><span class="h-card" translate="no"><a href="https://infosec.exchange/@masek" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>masek</span></a></span> <span class="h-card" translate="no"><a href="https://infosec.exchange/@JayeLTee" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>JayeLTee</span></a></span> For the life of me, I cannot understand why this got kicked over to the anti-rackets branch, but thank you for what you managed to accomplish. </p><p>I will post an update to this leak on my blog sometime this week, but in the interim:</p><p>Any patients of the Bolton Walk-In Clinic should consider filing a complaint with the provincial Privacy Commission and requesting an investigation into the clinic's failure to comply with medical privacy laws such as PHIPA. IMO, the IPC should also be asked to require the clinic to notify every patient whose unencrypted information was exposed. </p><p>Additional details about earlier efforts by <span class="h-card" translate="no"><a href="https://infosec.exchange/@JayeLTee" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>JayeLTee</span></a></span> and I to get this leak secured can be found in my post at <a href="https://databreaches.net/2024/12/03/bolton-walk-in-clinic-in-ontario-lock-down-your-backup-already/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">databreaches.net/2024/12/03/bo</span><span class="invisible">lton-walk-in-clinic-in-ontario-lock-down-your-backup-already/</span></a></p><p><a href="https://infosec.exchange/tags/dataleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dataleak</span></a> <a href="https://infosec.exchange/tags/incidentresponse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>incidentresponse</span></a> <a href="https://infosec.exchange/tags/PHIPA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PHIPA</span></a> <a href="https://infosec.exchange/tags/Ontario" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Ontario</span></a> <a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>healthsec</span></a></p>
The DFIR Report<p>Announcing the DFIR Labs Digital Forensics Challenge - Enterprise Edition! This isn't another textbook simulation. We're giving your team exclusive access to a brand-new, unreleased case from a real incident.</p><p>🗓️ When: August 30, 2025 (14:00 – 18:00 UTC)<br>🛠️ Choose your SIEM: Azure Log Analytics, Elastic, or Splunk.<br>🕵️ Your Squad: Form a team of 2-3 analysts.<br>🏆 The Glory: Solve the case, claim bragging rights, and win prizes for the top team!</p><p>Spaces are limited. Assemble your elite team and register now to secure your spot!</p><p>Register Here: <a href="https://dfirlabs.thedfirreport.com/dfirchallenge-enterprise-edition" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">dfirlabs.thedfirreport.com/dfi</span><span class="invisible">rchallenge-enterprise-edition</span></a></p><p><a href="https://infosec.exchange/tags/DFIR" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DFIR</span></a> <a href="https://infosec.exchange/tags/DigitalForensics" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DigitalForensics</span></a> <a href="https://infosec.exchange/tags/IncidentResponse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IncidentResponse</span></a> <a href="https://infosec.exchange/tags/CyberSecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CyberSecurity</span></a> <a href="https://infosec.exchange/tags/InfoSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>InfoSec</span></a></p>
Dissent Doe :cupofcoffee:<p>McLaren provides written notice to 743,131 patients after ransomware attack in July 2024:</p><p><a href="https://databreaches.net/2025/06/22/mclaren-provides-written-notice-to-743131-patients-after-ransomware-attack-in-july-2024/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">databreaches.net/2025/06/22/mc</span><span class="invisible">laren-provides-written-notice-to-743131-patients-after-ransomware-attack-in-july-2024/</span></a></p><p><a href="https://infosec.exchange/tags/HealthSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HealthSec</span></a> <a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>databreach</span></a> <a href="https://infosec.exchange/tags/encryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>encryption</span></a> <a href="https://infosec.exchange/tags/extortion" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>extortion</span></a> <a href="https://infosec.exchange/tags/transparency" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>transparency</span></a> <a href="https://infosec.exchange/tags/incidentresponse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>incidentresponse</span></a> </p><p>This was their second ransomware attack in a year. Personal injury lawyers are already recruiting plaintiffs. </p><p><span class="h-card" translate="no"><a href="https://mastodon.social/@campuscodi" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>campuscodi</span></a></span> <span class="h-card" translate="no"><a href="https://infosec.exchange/@amvinfe" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>amvinfe</span></a></span> <span class="h-card" translate="no"><a href="https://infosec.exchange/@brett" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>brett</span></a></span></p>
Frontend Dogma<p>Want to Be a Better Frontend Engineer? Try a Week On-Call, by (not on Mastodon or Bluesky):</p><p><a href="https://denodell.com/blog/try-a-week-on-call" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">denodell.com/blog/try-a-week-o</span><span class="invisible">n-call</span></a></p><p><a href="https://mas.to/tags/career" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>career</span></a> <a href="https://mas.to/tags/training" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>training</span></a> <a href="https://mas.to/tags/incidentresponse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>incidentresponse</span></a></p>
Dissent Doe :cupofcoffee:<p>Attribution is hard, Thursday edition...</p><p>NEW by me: A guilty plea in the PowerSchool case still leaves unanswered questions</p><p><a href="https://databreaches.net/2025/06/12/a-guilty-plea-in-the-powerschool-case-still-leaves-unanswered-questions/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">databreaches.net/2025/06/12/a-</span><span class="invisible">guilty-plea-in-the-powerschool-case-still-leaves-unanswered-questions/</span></a></p><p><a href="https://infosec.exchange/tags/PowerSchool" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PowerSchool</span></a> <a href="https://infosec.exchange/tags/hack" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hack</span></a> <a href="https://infosec.exchange/tags/extortion" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>extortion</span></a> <a href="https://infosec.exchange/tags/attribution" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>attribution</span></a> <a href="https://infosec.exchange/tags/transparency" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>transparency</span></a> <a href="https://infosec.exchange/tags/incidentresponse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>incidentresponse</span></a> </p><p><span class="h-card" translate="no"><a href="https://infosec.exchange/@douglevin" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>douglevin</span></a></span> <span class="h-card" translate="no"><a href="https://freeradical.zone/@funnymonkey" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>funnymonkey</span></a></span> <span class="h-card" translate="no"><a href="https://journa.host/@mkeierleber" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>mkeierleber</span></a></span> <span class="h-card" translate="no"><a href="https://infosec.exchange/@brett" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>brett</span></a></span></p>
Healthcare IT Security Robot<p>DATE: June 05, 2025 at 08:37AM<br>SOURCE: HEALTHCARE INFO SECURITY</p><p>Direct article link at end of text block below.</p><p>What are the most commonly overlooked details of <a href="https://mastodon.clinicians-exchange.org/tags/ransomware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ransomware</span></a> <a href="https://mastodon.clinicians-exchange.org/tags/incidentresponse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>incidentresponse</span></a> plans? <a href="https://t.co/cL89jDVfGq" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">t.co/cL89jDVfGq</span><span class="invisible"></span></a></p><p>Here are any URLs found in the article text: </p><p><a href="https://t.co/cL89jDVfGq" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">t.co/cL89jDVfGq</span><span class="invisible"></span></a></p><p>Articles can be found by scrolling down the page at <a href="https://www.healthcareinfosecurity.com/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">healthcareinfosecurity.com/</span><span class="invisible"></span></a> under the title "Latest"</p><p>-------------------------------------------------</p><p>Private, vetted email list for mental health professionals: <a href="https://www.clinicians-exchange.org" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">clinicians-exchange.org</span><span class="invisible"></span></a></p><p>Healthcare security & privacy posts not related to IT or infosec are at <span class="h-card" translate="no"><a href="https://mastodon.clinicians-exchange.org/@HIPAABot" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>HIPAABot</span></a></span> . Even so, they mix in some infosec with the legal & regulatory information.</p><p>-------------------------------------------------</p><p><a href="https://mastodon.clinicians-exchange.org/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>security</span></a> <a href="https://mastodon.clinicians-exchange.org/tags/healthcare" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>healthcare</span></a> <a href="https://mastodon.clinicians-exchange.org/tags/doctors" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>doctors</span></a> <a href="https://mastodon.clinicians-exchange.org/tags/itsecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>itsecurity</span></a> <a href="https://mastodon.clinicians-exchange.org/tags/hacking" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hacking</span></a> <a href="https://mastodon.clinicians-exchange.org/tags/doxxing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>doxxing</span></a> <a href="https://mastodon.clinicians-exchange.org/tags/psychotherapy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>psychotherapy</span></a> <a href="https://mastodon.clinicians-exchange.org/tags/securitynews" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>securitynews</span></a> <a href="https://mastodon.clinicians-exchange.org/tags/psychotherapist" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>psychotherapist</span></a> <a href="https://mastodon.clinicians-exchange.org/tags/mentalhealth" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mentalhealth</span></a> <a href="https://mastodon.clinicians-exchange.org/tags/psychiatry" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>psychiatry</span></a> <a href="https://mastodon.clinicians-exchange.org/tags/hospital" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hospital</span></a> <a href="https://mastodon.clinicians-exchange.org/tags/socialwork" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>socialwork</span></a> <a href="https://mastodon.clinicians-exchange.org/tags/datasecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>datasecurity</span></a> <a href="https://mastodon.clinicians-exchange.org/tags/webbeacons" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webbeacons</span></a> <a href="https://mastodon.clinicians-exchange.org/tags/cookies" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cookies</span></a> <a href="https://mastodon.clinicians-exchange.org/tags/HIPAA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HIPAA</span></a> <a href="https://mastodon.clinicians-exchange.org/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>privacy</span></a> <a href="https://mastodon.clinicians-exchange.org/tags/datanalytics" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>datanalytics</span></a> <a href="https://mastodon.clinicians-exchange.org/tags/healthcaresecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>healthcaresecurity</span></a> <a href="https://mastodon.clinicians-exchange.org/tags/healthitsecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>healthitsecurity</span></a> <a href="https://mastodon.clinicians-exchange.org/tags/patientrecords" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>patientrecords</span></a> <span class="h-card" translate="no"><a href="https://a.gup.pe/u/infosec" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>infosec</span></a></span> <a href="https://mastodon.clinicians-exchange.org/tags/telehealth" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>telehealth</span></a> <a href="https://mastodon.clinicians-exchange.org/tags/netneutrality" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>netneutrality</span></a> <a href="https://mastodon.clinicians-exchange.org/tags/socialengineering" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>socialengineering</span></a></p>
Dissent Doe :cupofcoffee:<p>It looks like the Gunra ransomware gang is escalating its leak of data from American Hospital Dubai ("AHD"). Their spokesperson informs me that they are planning to leak the data on the clearnet so more people will have access to downloading it. </p><p>AHD did not respond to my email inquiries yesterday. A second request was emailed to them this morning. </p><p>Background on this attack and AHD's internal communications about the breach:</p><p><a href="https://databreaches.net/2025/06/04/ransomware-group-gunra-claims-to-have-exfiltrated-450-million-patient-records-from-american-hospital-dubai/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">databreaches.net/2025/06/04/ra</span><span class="invisible">nsomware-group-gunra-claims-to-have-exfiltrated-450-million-patient-records-from-american-hospital-dubai/</span></a></p><p><a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>databreach</span></a> <a href="https://infosec.exchange/tags/ransomware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ransomware</span></a> <a href="https://infosec.exchange/tags/incidentresponse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>incidentresponse</span></a> <a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>healthsec</span></a> <a href="https://infosec.exchange/tags/UAE" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UAE</span></a> <a href="https://infosec.exchange/tags/Gunra" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Gunra</span></a></p>
TrendingLive feeds
Mastodon is the best way to keep up with what's happening.
Follow anyone across the fediverse and see it all in chronological order. No algorithms, ads, or clickbait in sight.
Create accountLoginDrag & drop to upload