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.

Server stats:

502
active users

#incidentmanagement

1 post1 participant0 posts today
Dissent Doe :cupofcoffee:<p>The Information and Privacy Commissioner of Ontario has completed a review into Daixin Team's massive cyberattack on five regional hospitals in 2023 and found hospital officials acted “adequately.”</p><p>Perhaps the most notable aspect of the report (from my perspective) was that the IPC said the hospitals were obligated to notify patients whose data had been encrypted (and not just those whose data had been exfiltrated). They saw no point in requiring that now, but wanted it noted that it should have happened.</p><p>So that seems to be making PHIPA's interpretation clearer for future victims of encryption incidents. </p><p>The full report makes an interesting read. </p><p>PHIPA Decision 284:<br><a href="https://decisions.ipc.on.ca/ipc-cipvp/phipa/en/item/521986/index.do" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">decisions.ipc.on.ca/ipc-cipvp/</span><span class="invisible">phipa/en/item/521986/index.do</span></a></p><p><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/notification" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>notification</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/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></p>
Dissent Doe :cupofcoffee:<p>Bradford Health Systems detected abnormal network activity in December 2023. They first sent out breach notices this week.</p><p><a href="https://databreaches.net/2025/05/30/bradford-health-systems-detected-abnormal-network-activity-in-december-2023-they-first-sent-out-breach-notices-this-week/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">databreaches.net/2025/05/30/br</span><span class="invisible">adford-health-systems-detected-abnormal-network-activity-in-december-2023-they-first-sent-out-breach-notices-this-week/</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/IncidentManagement" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IncidentManagement</span></a> <a href="https://infosec.exchange/tags/disclosure" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>disclosure</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/healthsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>healthsec</span></a> <a href="https://infosec.exchange/tags/HIPAA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HIPAA</span></a></p>
Dissent Doe :cupofcoffee:<p>B.C. health authority faces class-action lawsuit over 2009 data breach</p><p><a href="https://databreaches.net/2025/05/24/b-c-health-authority-faces-class-action-lawsuit-over-2009-data-breach/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">databreaches.net/2025/05/24/b-</span><span class="invisible">c-health-authority-faces-class-action-lawsuit-over-2009-data-breach/</span></a></p><p>Let's see... they didn't prevent breaches, they didn't detect breaches on their own, and they didn't notify 20,000 employees timely or provide any mitigation services timely or at all. </p><p>But can plaintiffs prevail? </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/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/incidentmanagement" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>incidentmanagement</span></a> <a href="https://infosec.exchange/tags/litigation" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>litigation</span></a> </p><p><span class="h-card" translate="no"><a href="https://twit.social/@privacylawyer" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>privacylawyer</span></a></span></p>
Dissent Doe :cupofcoffee:<p>Lexington School District Four in SC reported that 15,894 residents were affected by the PowerSchool breach. The state reached out to districts on Jan. 8 to tell them what was known at that time. </p><p>The district filed this with the state today: <a href="https://www.consumer.sc.gov/sites/consumer/files/Documents/Security%20Breach%20Notices/2025/LexingtonSchoolDistrictFour.pdf" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">consumer.sc.gov/sites/consumer</span><span class="invisible">/files/Documents/Security%20Breach%20Notices/2025/LexingtonSchoolDistrictFour.pdf</span></a></p><p>It appears to be a copy of what they have sent out to residents as a preliminary notification.</p><p>If memory serves, PowerSchool had told districts they would be giving them something for communications by the evening of the 8th. Did they ever do that? Or are the four bullets in the district's notification what <a href="https://infosec.exchange/tags/PowerSchool" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PowerSchool</span></a> gave districts to use? </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://infosec.exchange/@brett" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>brett</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> </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/incidentmanagement" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>incidentmanagement</span></a> <a href="https://infosec.exchange/tags/EduSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EduSec</span></a></p>
AndiMann<p>'The <a href="https://masto.ai/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSource</span></a> tools that could disrupt the entire <a href="https://masto.ai/tags/IT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IT</span></a> <a href="https://masto.ai/tags/IncidentManagement" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IncidentManagement</span></a> market"</p><p>LOL no! Grafana is great for what it is, but 💯 no to this headline LOL!😂</p><p><a href="https://masto.ai/tags/Grafana" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Grafana</span></a> <a href="https://masto.ai/tags/PagerDuty" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PagerDuty</span></a> <a href="https://masto.ai/tags/AIOps" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AIOps</span></a> <a href="https://masto.ai/tags/Observability" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Observability</span></a> <a href="https://masto.ai/tags/O11Y" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>O11Y</span></a> <a href="https://masto.ai/tags/FOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FOSS</span></a> <a href="https://masto.ai/tags/OSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OSS</span></a> <a href="https://masto.ai/tags/VictorOps" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VictorOps</span></a> # Splunk <a href="https://masto.ai/tags/OnCall" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OnCall</span></a> <a href="https://masto.ai/tags/XMatters" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XMatters</span></a> <a href="https://masto.ai/tags/SRE" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SRE</span></a> <a href="https://masto.ai/tags/DevOps" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DevOps</span></a></p><p><a href="https://www.zdnet.com/article/the-open-source-tools-that-could-disrupt-the-entire-it-incident-management-market/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">zdnet.com/article/the-open-sou</span><span class="invisible">rce-tools-that-could-disrupt-the-entire-it-incident-management-market/</span></a></p>
Dissent Doe :cupofcoffee:<p>From the Better-Late-Than-Never Department:</p><p>"Washington County is preparing to implement a new policy on how to respond to future cybersecurity attacks after a ransomware strike crippled the county government for more than two weeks earlier this year.</p><p>County solicitor Gary Sweat is asking the commissioners to consider approving a “business continuity and disaster contingency” plan that would have a protocol for county workers and its IT department to follow in the event of another cyber emergency."</p><p>As a reminder, they paid $350k ransom to ransomware gang to get decryptor key. </p><p><a href="https://www.observer-reporter.com/news/local-news/2024/dec/18/washington-county-considering-ransomware-policy-after-january-cyberattack/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">observer-reporter.com/news/loc</span><span class="invisible">al-news/2024/dec/18/washington-county-considering-ransomware-policy-after-january-cyberattack/</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/govsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>govsec</span></a> <a href="https://infosec.exchange/tags/riskassessment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>riskassessment</span></a> <a href="https://infosec.exchange/tags/disasterplan" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>disasterplan</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/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cybersecurity</span></a></p>
Dissent Doe :cupofcoffee:<p>OK, a huge thumbs up to Byte Federal for their breach notification letter. They frankly admit where they screwed up and what happened. I wish more notifications were as clear and straightforward as this one. </p><p><a href="https://databreaches.net/2024/12/17/a-positive-example-of-forthright-breach-disclosure/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">databreaches.net/2024/12/17/a-</span><span class="invisible">positive-example-of-forthright-breach-disclosure/</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/transparency" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>transparency</span></a> <a href="https://infosec.exchange/tags/disclosure" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>disclosure</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/IncidentReporting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IncidentReporting</span></a> <a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>infosec</span></a></p>
Jason Yip<p>"Incidents are expensive, not only in their impact on customers but also in the burden they place on human operators. Incidents are stressful, and they usually demand human intervention. Effective <a href="https://mastodon.online/tags/IncidentManagement" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IncidentManagement</span></a>, therefore, prioritizes preventive and proactive work over reactive work."</p><p><a href="https://mastodon.online/tags/AnatomyOfAnIncident" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AnatomyOfAnIncident</span></a></p>
Dissent Doe :cupofcoffee:<p>"Italy, exposed database puts dental clinic patients’ data at risk: "<br><a href="https://www.suspectfile.com/italy-exposed-database-puts-dental-clinic-patients-data-at-risk/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">suspectfile.com/italy-exposed-</span><span class="invisible">database-puts-dental-clinic-patients-data-at-risk/</span></a></p><p><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> followed up on some findings by <span class="h-card" translate="no"><a href="https://infosec.exchange/@chum1ng0" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>chum1ng0</span></a></span> and they tried to get two entities to lock down exposed data that includes personal information. </p><p>Despite repeated notifications, the data are still not locked down, it seems. </p><p><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/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/GDPR" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GDPR</span></a></p>
Dissent Doe :cupofcoffee:<p>Change Healthcare submitted a breach notification to <a href="https://infosec.exchange/tags/HHS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HHS</span></a> on July 19. They report the number of patients affected as "500" (a marker for "We have no friggin' idea how many and we'll get back to you at some date before the end of civilization maybe."). </p><p>They didn't comply with the "no later than 60 calendar days" requirement and I'm not sure what good a "500" report does anyone. </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/HITECH" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HITECH</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/ALPHV" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ALPHV</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/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cybersecurity</span></a> <a href="https://infosec.exchange/tags/incidentmanagement" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>incidentmanagement</span></a></p>
Dissent Doe :cupofcoffee:<p>Northeast Rehabilitation Hospital Network's "incident" was a <a href="https://infosec.exchange/tags/ransomware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ransomware</span></a> attack with data leaked, but they haven't said that. </p><p>And this wasn't their first cyberattack in recent years. </p><p><a href="https://databreaches.net/2024/07/29/northeast-rehabilitation-hospital-networks-incident-was-a-ransomware-attack-with-data-leaked-but-they-havent-said-that/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">databreaches.net/2024/07/29/no</span><span class="invisible">rtheast-rehabilitation-hospital-networks-incident-was-a-ransomware-attack-with-data-leaked-but-they-havent-said-that/</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/transparency" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>transparency</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/HealthSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HealthSec</span></a> <a href="https://infosec.exchange/tags/HIPAA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HIPAA</span></a> </p><p><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> <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></p>
Dissent Doe :cupofcoffee:<p>Almost 3 months afterDataBreaches[.]net reported on the <a href="https://infosec.exchange/tags/BlackSuit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BlackSuit</span></a> attack on <a href="https://infosec.exchange/tags/Post" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Post</span></a>&amp;Courier, the paper posted a notice on its site. The notice doesn't mention that all the data was leaked on the dark web months ago or that the paper had negotiated to try to get the data deleted. </p><p>My coverage in April: <a href="https://databreaches.net/2024/04/17/the-post-and-courier-hacked-black-suit-claims-to-have-500-gb-of-data/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">databreaches.net/2024/04/17/th</span><span class="invisible">e-post-and-courier-hacked-black-suit-claims-to-have-500-gb-of-data/</span></a></p><p>Post &amp; Courier's notice in July: <a href="https://www.postandcourier.com/site/evening-post-publishing-provides-notice-of-data-event.html" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">postandcourier.com/site/evenin</span><span class="invisible">g-post-publishing-provides-notice-of-data-event.html</span></a></p><p>FITSNews blasted P&amp;C for its lack of timely <a href="https://infosec.exchange/tags/notification" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>notification</span></a> and <a href="https://infosec.exchange/tags/transparency" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>transparency</span></a>: <a href="https://www.fitsnews.com/2024/07/23/the-post-and-courier-got-hacked/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">fitsnews.com/2024/07/23/the-po</span><span class="invisible">st-and-courier-got-hacked/</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/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cybersecurity</span></a> <a href="https://infosec.exchange/tags/journalism" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>journalism</span></a> <a href="https://infosec.exchange/tags/incidentmanagement" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>incidentmanagement</span></a> </p><p><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>
Dissent Doe :cupofcoffee:<p>I was just reading a follow-up on the Philippine Health Insurance (PhilHealth) breach by <a href="https://infosec.exchange/tags/Medusa" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Medusa</span></a> in 2023, and I read something that struck me as unusual:</p><p>The govt didn't pay the TA's demands but what they did do was set up a portal where citizens could check to determine if Medusa had leaked their personal identification number.</p><p>I can't recall any govt or private sector entity ever creating a portal like that before. Can you? I mean, telling people to check HaveIBeenPwnd is one thing, but to create a portal on a .gov domain to check what TAs leaked? </p><p>Portal: <a href="https://philhealthleak.privacy.gov.ph/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">philhealthleak.privacy.gov.ph/</span><span class="invisible"></span></a></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://mastodon.social/@zackwhittaker" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>zackwhittaker</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> <span class="h-card" translate="no"><a href="https://infosec.exchange/@troyhunt" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>troyhunt</span></a></span> </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/IncidentManagement" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IncidentManagement</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/notification" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>notification</span></a></p>
miry<p>Do you think your service needs to be available 24/7? Are you worried about downtime and potential social reactions?</p><p>Stay calm. Look at major companies like <a href="https://mastodon.social/tags/Nintendo" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Nintendo</span></a>. Their site is down (<a href="https://www.nintendo.com/de-de/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">nintendo.com/de-de/</span><span class="invisible"></span></a>), and they don't stress over it.</p><p>If your product is unique and cost-effective, customers will remain loyal, even during outages. </p><p><a href="https://mastodon.social/tags/Atlassian" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Atlassian</span></a> is a great example of this.</p><p>Keep calm and be happy!</p><p><a href="https://mastodon.social/tags/Reliability" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Reliability</span></a> <a href="https://mastodon.social/tags/IncidentManagement" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IncidentManagement</span></a></p>
Dissent Doe :cupofcoffee:<p>And then there were three -- 3 attacks in June 2023 where patients are first being notified now and where we do not know who was responsible for the attacks, at least two of which were ransomware attacks. </p><p>SouthCoast Medical Group and Privia Medical Group notify patients of June 2023 cyberattack</p><p><a href="https://databreaches.net/2024/07/06/southcoast-medical-group-and-privia-medical-group-notify-patients-of-june-2023-cyberattack/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">databreaches.net/2024/07/06/so</span><span class="invisible">uthcoast-medical-group-and-privia-medical-group-notify-patients-of-june-2023-cyberattack/</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/HIPAA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HIPAA</span></a> <a href="https://infosec.exchange/tags/HITECH" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HITECH</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/ransomware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ransomware</span></a> <a href="https://infosec.exchange/tags/IncidentManagement" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IncidentManagement</span></a> </p><p><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> <span class="h-card" translate="no"><a href="https://ioc.exchange/@allan" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>allan</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://mastodon.social/@campuscodi" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>campuscodi</span></a></span></p>
Dissent Doe :cupofcoffee:<p>Part 2 of 2:</p><p>SysInformation Healthcare Services, LLC, d/b/a EqualizeRCM also was the victim of a ransomware attack in June 2023, and we still don't know how many were affected. </p><p>Nor do I know which TA group is responsible for this one. Anyone know? </p><p><a href="https://databreaches.net/2024/07/02/how-many-clients-and-patients-were-affected-by-a-ransomware-attack-on-equalizercm-we-have-no-idea/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">databreaches.net/2024/07/02/ho</span><span class="invisible">w-many-clients-and-patients-were-affected-by-a-ransomware-attack-on-equalizercm-we-have-no-idea/</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/incidentmanagement" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>incidentmanagement</span></a></p>
Dissent Doe :cupofcoffee:<p>Part 1 of 2: </p><p>Florida Community Health Centers to notify almost 300,000 of ransomware attack that occurred in June 2023.</p><p><a href="https://databreaches.net/2024/07/03/florida-community-health-centers-to-notify-almost-300000-of-ransomware-attack/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">databreaches.net/2024/07/03/fl</span><span class="invisible">orida-community-health-centers-to-notify-almost-300000-of-ransomware-attack/</span></a></p><p>I don't know of any TA group that claimed responsibility for this one. Anyone know? </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/incidentmanagement" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>incidentmanagement</span></a></p>
Dissent Doe :cupofcoffee:<p>Daixin Team claims to have breached the Dubai Municipality:</p><p><a href="https://databreaches.net/2024/06/05/daixin-team-claims-to-have-breached-the-dubai-municipality/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">databreaches.net/2024/06/05/da</span><span class="invisible">ixin-team-claims-to-have-breached-the-dubai-municipality/</span></a></p><p><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/databreach" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>databreach</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/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cybersecurity</span></a> <a href="https://infosec.exchange/tags/IncidentManagement" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IncidentManagement</span></a></p>
Ben Cordero<p>There's still value in low-technical postmortems.</p><p>What made this incident low impact? has your team implemented various safety nets to reduce harmful effects?</p><p>How did you know that a rollback was the right thing to do?<br>Could you have implemented a fix-forward instead?</p><p>Who else did you need to involve? or were you able to fully execute the incident and any runbooks by yourself without disrupting anyone else?</p><p><a href="https://nfra.club/tags/Incidents" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Incidents</span></a> <a href="https://nfra.club/tags/IncidentResponse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IncidentResponse</span></a> <a href="https://nfra.club/tags/IncidentManagement" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IncidentManagement</span></a> <a href="https://nfra.club/tags/Postmortems" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Postmortems</span></a> <a href="https://nfra.club/tags/ICM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ICM</span></a> <a href="https://nfra.club/tags/IRM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IRM</span></a></p>
IT News<p>Rootly nabs $3.2M seed to build SRE incident management solution inside Slack - As companies look for ways to respond to incidents in their complex micro services... - <a href="http://feedproxy.google.com/~r/Techcrunch/~3/WvtSRHSU86g/" rel="nofollow noopener" target="_blank"><span class="invisible">http://</span><span class="ellipsis">feedproxy.google.com/~r/Techcr</span><span class="invisible">unch/~3/WvtSRHSU86g/</span></a> <a href="https://schleuss.online/tags/incidentmanagement" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>incidentmanagement</span></a> <a href="https://schleuss.online/tags/xyzventurecapital" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>xyzventurecapital</span></a> <a href="https://schleuss.online/tags/incidentresponse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>incidentresponse</span></a> <a href="https://schleuss.online/tags/recentfunding" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>recentfunding</span></a> <a href="https://schleuss.online/tags/enterprise" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>enterprise</span></a> <a href="https://schleuss.online/tags/startups" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>startups</span></a> <a href="https://schleuss.online/tags/funding" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>funding</span></a> <a href="https://schleuss.online/tags/rootly" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rootly</span></a> <a href="https://schleuss.online/tags/cloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cloud</span></a> <a href="https://schleuss.online/tags/tc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tc</span></a></p>