social.coop

LavX NewsHarnessing Near Misses: A New Frontier in Incident ManagementIn the complex landscape of software development and systems reliability, near misses often go unnoticed, yet they hold the key to preventing future incidents. By treating these operational surprises ...<a href="https://news.lavx.hu/article/harnessing-near-misses-a-new-frontier-in-incident-management" rel="nofollow noopener noreferrer" target="_blank">https://news.lavx.hu/article/harnessing-near-misses-a-new-frontier-in-incident-management</a><a href="https://mastodon.cloud/tags/news" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#news</a> <a href="https://mastodon.cloud/tags/tech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tech</a> <a href="https://mastodon.cloud/tags/DevOps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DevOps</a> <a href="https://mastodon.cloud/tags/ReliabilityEngineering" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ReliabilityEngineering</a> <a href="https://mastodon.cloud/tags/IncidentManagement" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IncidentManagement</a>

craque sprung 🏳️‍🌈I am very happy because my DevEx team at work is becoming a lot more official and getting a lot of attention. Which means we may be able to officially make it a real team and the three of us can be 100% on it. So we're creating a new wiki space and top-level jira project and all that.But sad, too, because I am moving resilience and incident documentation out of SRE and into our space. Because I am more concerned about seeing the work get done than I am about what team should own it.So I'm satisfied that incident program management fell into DevEx. There are also no other SREs but me (out of like 12) that like dealing with incident management anyway.My boss said that after what I did with the retro, he is completely comfortable having me oversee the improvement of our incident management.Seems like I am becoming adept at fixing fucked on-call rotations!<a href="https://c.im/tags/SRE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SRE</a> <a href="https://c.im/tags/IncidentManagement" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IncidentManagement</a>

dan slimmonBlog! <a href="https://blog.danslimmon.com/2025/01/29/incident-sev-scales-are-a-waste-of-time/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://blog.danslimmon.com/2025/01/29/incident-sev-scales-are-a-waste-of-time/</a> <a href="https://hachyderm.io/tags/incidentresponse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#incidentresponse</a> <a href="https://hachyderm.io/tags/sre" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sre</a> <a href="https://hachyderm.io/tags/devops" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#devops</a> <a href="https://hachyderm.io/tags/webops" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#webops</a> <a href="https://hachyderm.io/tags/itil" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#itil</a> <a href="https://hachyderm.io/tags/sysadmin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sysadmin</a> <a href="https://hachyderm.io/tags/incidentmanagement" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#incidentmanagement</a>

Dissent Doe :cupofcoffee: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. 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 noreferrer" translate="no" target="_blank">https://www.consumer.sc.gov/sites/consumer/files/Documents/Security%20Breach%20Notices/2025/LexingtonSchoolDistrictFour.pdf</a>It appears to be a copy of what they have sent out to residents as a preliminary notification.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 noreferrer" target="_blank">#PowerSchool</a> gave districts to use? <a href="https://infosec.exchange/@douglevin" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@douglevin</a> <a href="https://infosec.exchange/@brett" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@brett</a> <a href="https://freeradical.zone/@funnymonkey" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@funnymonkey</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/incidentmanagement" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#incidentmanagement</a> <a href="https://infosec.exchange/tags/EduSec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EduSec</a>

AndiMann'The <a href="https://masto.ai/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> tools that could disrupt the entire <a href="https://masto.ai/tags/IT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IT</a> <a href="https://masto.ai/tags/IncidentManagement" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IncidentManagement</a> market"LOL no! Grafana is great for what it is, but 💯 no to this headline LOL!😂<a href="https://masto.ai/tags/Grafana" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Grafana</a> <a href="https://masto.ai/tags/PagerDuty" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PagerDuty</a> <a href="https://masto.ai/tags/AIOps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AIOps</a> <a href="https://masto.ai/tags/Observability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Observability</a> <a href="https://masto.ai/tags/O11Y" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#O11Y</a> <a href="https://masto.ai/tags/FOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FOSS</a> <a href="https://masto.ai/tags/OSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OSS</a> <a href="https://masto.ai/tags/VictorOps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VictorOps</a> # Splunk <a href="https://masto.ai/tags/OnCall" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OnCall</a> <a href="https://masto.ai/tags/XMatters" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#XMatters</a> <a href="https://masto.ai/tags/SRE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SRE</a> <a href="https://masto.ai/tags/DevOps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DevOps</a><a href="https://www.zdnet.com/article/the-open-source-tools-that-could-disrupt-the-entire-it-incident-management-market/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.zdnet.com/article/the-open-source-tools-that-could-disrupt-the-entire-it-incident-management-market/</a>

Dissent Doe :cupofcoffee:From the Better-Late-Than-Never Department:"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.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."As a reminder, they paid $350k ransom to ransomware gang to get decryptor key. <a href="https://www.observer-reporter.com/news/local-news/2024/dec/18/washington-county-considering-ransomware-policy-after-january-cyberattack/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.observer-reporter.com/news/local-news/2024/dec/18/washington-county-considering-ransomware-policy-after-january-cyberattack/</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/govsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#govsec</a> <a href="https://infosec.exchange/tags/riskassessment" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#riskassessment</a> <a href="https://infosec.exchange/tags/disasterplan" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#disasterplan</a> <a href="https://infosec.exchange/tags/IncidentManagement" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IncidentManagement</a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cybersecurity</a>

Noble ShiftMost holiday movies that involve Santa in some way exist due to poor SOP, Opsec, and Incident & Response Management.<a href="https://mastodon.social/tags/opsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opsec</a> <a href="https://mastodon.social/tags/incidentmanagement" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#incidentmanagement</a> <a href="https://mastodon.social/tags/responce" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#responce</a> <a href="https://mastodon.social/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#security</a> <a href="https://mastodon.social/tags/infosec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#infosec</a> <a href="https://mastodon.social/tags/santa" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#santa</a> <a href="https://mastodon.social/tags/holiday" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#holiday</a> <a href="https://mastodon.social/tags/movies" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#movies</a> <a href="https://mastodon.social/tags/northpole" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#northpole</a> <a href="https://mastodon.social/tags/sop" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sop</a> <a href="https://mastodon.social/tags/hohoho" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#hohoho</a>

Dissent Doe :cupofcoffee: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. <a href="https://databreaches.net/2024/12/17/a-positive-example-of-forthright-breach-disclosure/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://databreaches.net/2024/12/17/a-positive-example-of-forthright-breach-disclosure/</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/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> <a href="https://infosec.exchange/tags/IncidentManagement" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IncidentManagement</a> <a href="https://infosec.exchange/tags/IncidentReporting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IncidentReporting</a> <a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#infosec</a>

craque sprung 🏳️‍🌈I *cringe* when I see the phrase "stand down" in regard to incident response in software.It brings up images of police and military actions and I hate it.<a href="https://c.im/tags/SRE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SRE</a> <a href="https://c.im/tags/IncidentManagement" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IncidentManagement</a>

Kevin RiggleDiscover how Akamai's innovative approach to <a href="https://ioc.exchange/tags/IncidentManagement" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IncidentManagement</a>, born out of necessity, influenced the industry standard, in this <a href="https://ioc.exchange/tags/CriticalPointWarStories" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CriticalPointWarStories</a> bonus episode with Abhijit Mehta!<a href="https://youtu.be/NVUY4fvY89A" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://youtu.be/NVUY4fvY89A</a>

PhilWe had a string of <a href="https://mstdn.io/tags/incidents" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#incidents</a> at work last week. The app would suddenly start slowing to a crawl before tipping over entirely. We were pretty sure there was a problem at a vendor's end but we weren't sure what else was at play. Our key engineer spent a lot time digging into what was going on and by the third day had told our other two engineers and brought them into the conversation too. Our customer support reps were freaking out. What should they tell the customers?? <a href="https://mstdn.io/tags/IncidentManagement" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IncidentManagement</a>

Kevin Riggle"I basically took out production and our production monitoring in one fell swoop." Julia Lunetta shares a cautionary tale about shared filesystems and single points of failure. <a href="https://ioc.exchange/tags/DevOps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DevOps</a> <a href="https://ioc.exchange/tags/IncidentManagement" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IncidentManagement</a> <a href="https://ioc.exchange/tags/CriticalPOintWarStories" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CriticalPOintWarStories</a><a href="https://youtu.be/2f9ifyVxg1s" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://youtu.be/2f9ifyVxg1s</a>

Jason Yip"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 noreferrer" target="_blank">#IncidentManagement</a>, therefore, prioritizes preventive and proactive work over reactive work."<a href="https://mastodon.online/tags/AnatomyOfAnIncident" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AnatomyOfAnIncident</a>

Dissent Doe :cupofcoffee:"Italy, exposed database puts dental clinic patients’ data at risk: " <a href="https://www.suspectfile.com/italy-exposed-database-puts-dental-clinic-patients-data-at-risk/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.suspectfile.com/italy-exposed-database-puts-dental-clinic-patients-data-at-risk/</a><a href="https://infosec.exchange/@amvinfe" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@amvinfe</a> followed up on some findings by <a href="https://infosec.exchange/@chum1ng0" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@chum1ng0</a> and they tried to get two entities to lock down exposed data that includes personal information. Despite repeated notifications, the data are still not locked down, it seems. <a href="https://infosec.exchange/tags/responsibledisclosure" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#responsibledisclosure</a> <a href="https://infosec.exchange/tags/incidentresponse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#incidentresponse</a> <a href="https://infosec.exchange/tags/incidentmanagement" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#incidentmanagement</a> <a href="https://infosec.exchange/tags/GDPR" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GDPR</a>

AndiMann"@PagerDuty Expands <a href="https://masto.ai/tags/GenerativeAI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GenerativeAI</a> Solutions with PagerDuty Advance to Mitigate <a href="https://masto.ai/tags/Risk" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Risk</a> of Operational <a href="https://masto.ai/tags/Outages" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Outages</a>"Love this! In <a href="https://masto.ai/tags/Observability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Observability</a> & <a href="https://masto.ai/tags/IncidentManagement" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IncidentManagement</a> <a href="https://masto.ai/tags/AI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AI</a> should do more for <a href="https://masto.ai/tags/CloudOps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CloudOps</a> <a href="https://masto.ai/tags/SRE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SRE</a> <a href="https://masto.ai/tags/DevOps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DevOps</a> <a href="https://masto.ai/tags/ITOps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ITOps</a> than read docs. It should do the work!<a href="https://investor.pagerduty.com/news/news-details/2024/PagerDuty-Expands-GenerativeAI-Solutions-with-PagerDuty-Advance-to-Mitigate-Risk-of-Operational-Outages/default.aspx" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://investor.pagerduty.com/news/news-details/2024/PagerDuty-Expands-GenerativeAI-Solutions-with-PagerDuty-Advance-to-Mitigate-Risk-of-Operational-Outages/default.aspx</a>

AndiMann"@PagerDuty Expands <a href="https://masto.ai/tags/GenerativeAI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GenerativeAI</a> Solutions with PagerDuty Advance to Mitigate <a href="https://masto.ai/tags/Risk" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Risk</a> of Operational <a href="https://masto.ai/tags/Outages" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Outages</a>"Love this! In <a href="https://masto.ai/tags/Observability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Observability</a> & <a href="https://masto.ai/tags/IncidentManagement" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IncidentManagement</a> <a href="https://masto.ai/tags/AI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AI</a> should do more for <a href="https://masto.ai/tags/CloudOps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CloudOps</a> <a href="https://masto.ai/tags/SRE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SRE</a> <a href="https://masto.ai/tags/DevOps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DevOps</a> <a href="https://masto.ai/tags/ITOps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ITOps</a> than read docs. It should do the work!!<a href="https://investor.pagerduty.com/news/news-details/2024/PagerDuty-Expands-GenerativeAI-Solutions-with-PagerDuty-Advance-to-Mitigate-Risk-of-Operational-Outages/default.aspx" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://investor.pagerduty.com/news/news-details/2024/PagerDuty-Expands-GenerativeAI-Solutions-with-PagerDuty-Advance-to-Mitigate-Risk-of-Operational-Outages/default.aspx</a>

Dissent Doe :cupofcoffee:Change Healthcare submitted a breach notification to <a href="https://infosec.exchange/tags/HHS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HHS</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."). 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. <a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#databreach</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/HITECH" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HITECH</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/ALPHV" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ALPHV</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/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cybersecurity</a> <a href="https://infosec.exchange/tags/incidentmanagement" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#incidentmanagement</a>

Dissent Doe :cupofcoffee:Northeast Rehabilitation Hospital Network's "incident" was a <a href="https://infosec.exchange/tags/ransomware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ransomware</a> attack with data leaked, but they haven't said that. And this wasn't their first cyberattack in recent years. <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 noreferrer" translate="no" target="_blank">https://databreaches.net/2024/07/29/northeast-rehabilitation-hospital-networks-incident-was-a-ransomware-attack-with-data-leaked-but-they-havent-said-that/</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/transparency" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#transparency</a> <a href="https://infosec.exchange/tags/IncidentManagement" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IncidentManagement</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/@brett" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@brett</a> <a href="https://infosec.exchange/@amvinfe" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@amvinfe</a>

Dissent Doe :cupofcoffee:Almost 3 months afterDataBreaches[.]net reported on the <a href="https://infosec.exchange/tags/BlackSuit" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BlackSuit</a> attack on <a href="https://infosec.exchange/tags/Post" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Post</a>&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. 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 noreferrer" translate="no" target="_blank">https://databreaches.net/2024/04/17/the-post-and-courier-hacked-black-suit-claims-to-have-500-gb-of-data/</a>Post & Courier's notice in July: <a href="https://www.postandcourier.com/site/evening-post-publishing-provides-notice-of-data-event.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.postandcourier.com/site/evening-post-publishing-provides-notice-of-data-event.html</a>FITSNews blasted P&C for its lack of timely <a href="https://infosec.exchange/tags/notification" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#notification</a> and <a href="https://infosec.exchange/tags/transparency" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#transparency</a>: <a href="https://www.fitsnews.com/2024/07/23/the-post-and-courier-got-hacked/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.fitsnews.com/2024/07/23/the-post-and-courier-got-hacked/</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/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cybersecurity</a> <a href="https://infosec.exchange/tags/journalism" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#journalism</a> <a href="https://infosec.exchange/tags/incidentmanagement" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#incidentmanagement</a> <a href="https://infosec.exchange/@brett" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@brett</a>

Dissent Doe :cupofcoffee: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 noreferrer" target="_blank">#Medusa</a> in 2023, and I read something that struck me as unusual: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.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? Portal: <a href="https://philhealthleak.privacy.gov.ph/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://philhealthleak.privacy.gov.ph/</a><a href="https://mastodon.social/@campuscodi" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@campuscodi</a> <a href="https://mastodon.social/@zackwhittaker" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@zackwhittaker</a> <a href="https://infosec.exchange/@brett" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@brett</a> <a href="https://infosec.exchange/@troyhunt" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@troyhunt</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/IncidentManagement" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IncidentManagement</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/incidentresponse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#incidentresponse</a> <a href="https://infosec.exchange/tags/notification" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#notification</a>

Recent searches

Search options

Administered by:

Server stats:

#incidentmanagement