home.social

#incidentmanagement — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #incidentmanagement, aggregated by home.social.

  1. Mean time to repair directly impacts revenue and trust. When automation cuts MTTR by over 50%, the business case becomes clear: fewer escalations, less downtime, and calmer teams.

    #IncidentManagement #AIOps #Automation #SRE #ITOps

  2. The 2024 CrowdStrike outage caused a worldwide Windows Blue Screen crash, impacting airlines, banks, and enterprises.
    This deep dive explains how DevOps & SRE teams mitigated impact, recovered systems, and prevented total failure.
    🔗 shorturl.at/VLqxz

    #CrowdStrikeOutage #DevOps #SRE #IncidentManagement #CyberResilience #CloudOps #PostMortem #ReliabilityEngineering #aws

  3. The 2024 CrowdStrike outage caused a worldwide Windows Blue Screen crash, impacting airlines, banks, and enterprises.
    This deep dive explains how DevOps & SRE teams mitigated impact, recovered systems, and prevented total failure.
    🔗 shorturl.at/VLqxz

    #CrowdStrikeOutage #DevOps #SRE #IncidentManagement #CyberResilience #CloudOps #PostMortem #ReliabilityEngineering #aws

  4. Auch 2026 findet wieder ein #GI-SPRING-Graduiertenworkshop der Fachgruppe Security - Intrusion Detection and Response (SIDAR) statt. Diesmal am 21. und 22.04.2026 in #Heidelberg.

    Zu den Themen gehören #VulnerabilityAssessment, #ThreatIntelligence, #IntrusionDetection, #Malware, #IncidentManagement, #WirelessSecurity, #DigitalForensics usw.

    Einreichungen werden bis zum 15.03.2026 angenommen.

    spring.fg-sidar.gi.de

    #CyberSecurity #Conference

  5. Auch 2026 findet wieder ein #GI-SPRING-Graduiertenworkshop der Fachgruppe Security - Intrusion Detection and Response (SIDAR) statt. Diesmal am 21. und 22.04.2026 in #Heidelberg.

    Zu den Themen gehören #VulnerabilityAssessment, #ThreatIntelligence, #IntrusionDetection, #Malware, #IncidentManagement, #WirelessSecurity, #DigitalForensics usw.

    Einreichungen werden bis zum 15.03.2026 angenommen.

    spring.fg-sidar.gi.de

    #CyberSecurity #Conference

  6. Auch 2026 findet wieder ein #GI-SPRING-Graduiertenworkshop der Fachgruppe Security - Intrusion Detection and Response (SIDAR) statt. Diesmal am 21. und 22.04.2026 in #Heidelberg.

    Zu den Themen gehören #VulnerabilityAssessment, #ThreatIntelligence, #IntrusionDetection, #Malware, #IncidentManagement, #WirelessSecurity, #DigitalForensics usw.

    Einreichungen werden bis zum 15.03.2026 angenommen.

    spring.fg-sidar.gi.de

    #CyberSecurity #Conference

  7. Auch 2026 findet wieder ein #GI-SPRING-Graduiertenworkshop der Fachgruppe Security - Intrusion Detection and Response (SIDAR) statt. Diesmal am 21. und 22.04.2026 in #Heidelberg.

    Zu den Themen gehören #VulnerabilityAssessment, #ThreatIntelligence, #IntrusionDetection, #Malware, #IncidentManagement, #WirelessSecurity, #DigitalForensics usw.

    Einreichungen werden bis zum 15.03.2026 angenommen.

    spring.fg-sidar.gi.de

    #CyberSecurity #Conference

  8. Today's AWS outage was a stark reminder: what happens when the tools you rely on to manage incidents... are part of the incident?

    When Slack, Zoom, PagerDuty, and even Statuspage are impacted, how do you get your response team re-connected to solve the underlying problem? Once they're talking to each other, they can improvise a response, but that first step of re-establishing contact is critical.

    This isn't just a hypothetical. It's a real-world scenario that can paralyze even the most prepared organizations. Relying on a plan that's tucked away in a long-forgotten document is a recipe for disaster.

    Here's what I recommend to the leaders I advise:

    🔹 Have a "Rally Point" Plan: Don't just have a backup concept; have a pre-defined, communicated, and accessible fallback plan. Every second counts in an incident, and you can't waste time figuring out where to communicate. If you normally use Slack and Zoom, then think Google Meet or Microsoft Teams for your backup, and vice versa. Maybe even an old-fashioned conference call bridge. The key is that everyone knows where to go, when the normal places aren't working.

    🔹 Make it Accessible: Your plan is useless if it's on a server that nobody can get to at the moment. Laminated wallet cards, a shared password vault with offline access, or a regularly updated file on every employee's laptop are all viable options.

    🔹 Practice, Practice, Practice: Fire drills aren't just for fires. Run drills for your fallback communication plan. This ensures everyone remembers it exists and that the mechanisms still work.

    🔹 Don't Forget Security: Assume that your fallback channel is compromised, and that outsiders are listening in. Use it just as a rendezvous point to direct responders to more secure, authenticated channels, where you can validate every participant. Don't discuss sensitive information in the open.

    Incidents are costly, not just in revenue, but in reputation and team morale. Proactive preparation isn't a luxury; it's a necessity.

    What's your team's communication fallback plan? Share your thoughts in the comments below. 👇

    #IncidentManagement #BusinessContinuity #SiteReliability #DevOps #AWSOutage

  9. Release It! by Michael T. Nygard

    "Manage perceptions after a major #incident It’s as important as managing the incident itself."

    #IncidentManagement #readwise

  10. In August 2020, @SchizoDuckie 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."

    In today's installment, I bring you "No Need to Hack When It's Leaking: Brandt Kettwick Defense Edition." It chronicles efforts by @JayeLTee, @masek, and I to alert a Minnesota law firm to lock down their exposed files, some of which were quite sensitive.

    Read the post and see how even the state's Bureau of Criminal Apprehension had trouble getting this law firm to respond appropriately.

    databreaches.net/2025/07/04/no

    Great thanks to the Minnesota Bureau of Criminal Apprehension for their help on this one, and to @TonyYarusso and @bkoehn for their efforts.

    #dataleak #misconfiguration #incidentresponse #incidentmanagement #responsibledisclosure #securityalert #infosec

  11. 🚨 Cyber threats are evolving fast! 74% of CISOs are increasing their crisis simulation budgets in 2025 to stay ahead. With high-profile breaches on the rise, organizations must test and refine their response strategies.

    At RELIANOID, we provide the tools to enhance cyber resilience and ensure businesses are always prepared. 🛡️


    relianoid.com/blog/cisos-are-i

  12. At RELIANOID, we help teams move from:
    🚨 Chaos (fragmented tools & manual processes)
    ➡️ Proactive resilience (collaborative, data-driven systems).

    Break the "doom loop" of incident management. Let's build a culture where incidents = opportunities. 💡


    relianoid.com/blog/transformin

  13. 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.

    observer-reporter.com/news/loc

    #databreach #ransomware #govsec #riskassessment #disasterplan #IncidentManagement #cybersecurity

  14. Most holiday movies that involve Santa in some way exist due to poor SOP, Opsec, and Incident & Response Management.

    #opsec #incidentmanagement #responce #security #infosec #santa #holiday #movies #northpole #sop #hohoho

  15. Change Healthcare submitted a breach notification to #HHS 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.

    #databreach #HIPAA #HITECH #HealthSec #ALPHV #ransomware #cybersecurity #incidentmanagement

  16. Julia Thoreson at Bloomberg sharing “Incident Management: Lessons from Emergency Services” breaking down how the lessons learned in emergency services can apply to incident management in technical systems #monitorama #monitorama24 #incidentmanagement

  17. If you've ever been on-call, you know that it can be stressful AF! Next week's guest on @geekingout_pod, Ashley Sawatsky of Rootly, talks about the importance of on-call health, and what you can do to prevent trauma and burnout. Episode drops on Feb 20th.

    Catch the YouTube premiere 👉 buff.ly/3SXSyah, or subscribe through your fave podcasting app!

    #oncall #siteReliabilityEngineering #incidentResponse #incidentManagement

  18. CW: Incident management / birdsite

    This thread and the nested thread could be the basis of a lot of good writing about incident management.

    It would be super wrong to think the question is, "How many engineers do they need to maintain Twitter?" A better question might be, "How clear an understanding do they have of how to maintain Twitter, now that so many people have left?" #IncidentManagement #Clausewitz

    twitter.com/amdev/status/15941