Solera Holdings, LLC.’s Post

When an outage hits, that’s when an incident response plan truly gets tested. Regardless of whether a plan was in place or how effective it was, it’s disheartening to see the ongoing issues with the CrowdStrike and Microsoft outages. Here’s a workaround from CrowdStrike for affected systems: 1️⃣ Boot Windows into Safe Mode or the Windows Recovery Environment. 2️⃣ Navigate to C:\Windows\System32\drivers\CrowdStrike. 3️⃣ Find and delete the file named “C-00000291*.sys.” 4️⃣ Reboot the host normally. 🔗 CrowdStrike Blog: https://lnkd.in/gtZQ5TD4 Gartner also has some additional fixes. Want to strengthen your incident response? Check out our checklist here: 👉 https://lnkd.in/d8SakxUn

👉Microsoft users across the world faced system failure and the blue screen of death on 19th July 2024. It happened due to a faulty software update from CrowdStrike. Read the article to know everything about the outage. 👉Read the Article for more: https://rb.gy/leimqf #crowdstricke #bluescreen #microsoftuser #software #softwareupdate #systemfailure #CrowdStrikeOutage #wpeventmanager

🚨 Lessons from the CrowdStrike Outage: Building a Resilient Infrastructure - Part1🚨 The recent IT outage, occurring from late Thursday to early Friday, was deemed the largest in history. Triggered by a Microsoft software update, it affected 8.5 million Windows devices globally, leading to partial shutdowns in airports, banks, 911 services, and healthcare facilities. 💡 How can we prevent such a catastrophe in the future? CrowdStrike should implement thorough testing before deployment. Here are essential tests to adopt: 1. Unit Testing: Ensures individual components work correctly in isolation. Functional Testing: Validates software functions as per requirements, without worrying about internal code. 2. Performance Testing: Assesses system responsiveness, stability, and scalability under various loads to identify bottlenecks. 3. Security Testing: Detects vulnerabilities to ensure compliance with security standards and regulations. 4. Regression Testing: Confirms recent code changes haven’t disrupted existing functionalities, preventing new defects from slipping through. Let's prioritize these testing practices to safeguard against future disruptions! 💪🔧 #ITSecurity #SoftwareTesting #TechResilience

There's a lot that's already been said on this CrowdStrike outage, and there's a lot more to be said. But the underlying theme here is arrogance and complacency. CrowdStrike (vendor) and their clients have broken SEVERAL cardinal rules of software development and delivery. Here are the biggest two: 1. CrowdStrike got arrogant in that they just assumed they could push prod-software whenever they felt like it. NEVER deploy late in the week. Thursday and Friday's are ALWAYS off limits unless it's an absolute emergency, which this was not. 2. CrowdStrike clients got too complacent just blanketly accepting CrowdStrike updates to deploy to any and all systems all at once, without staging them on non-critical infrastructure first. Never, EVER trust a software vendor outright. This should be a cardinal rule in the private sector, and I know for A FACT it's a cardinal rule in the government. This should be an eye-opening event for C-levels to re-evaluate their technology "leaders" and start replacing them with more modern and effective personnel, personnel with experience in the field in the 21st century.

The recent global IT outage triggered by a CrowdStrike software update has had far-reaching effects, causing Microsoft Windows systems to crash and impacting operations worldwide. This unprecedented event has left businesses, governments, and end users searching for answers. Gain insights from a panel of Gartner experts leading the research on this matter. In this session, they will assess the impact of the CrowdStrike-triggered outage, determine immediate steps to address the issue in your organization, and identify longer-range implications and remedies: https://gtnr.it/4bL5Lti As the situation evolves, Gartner will provide updates and corrections to ensure you have the most accurate information. #CrowdStrike #InformationTechnology #Webinar

Join this complimentary Gartner webinar / Q&A session to get up to date information on the #CrowdStrike outage and recovery. As the situation evolves, Gartner will provide updates and corrections to ensure you have the most accurate information.

Today, we cover: 1 - Recap. 8.5M Windows machines impacted across industries 2 - Root cause. An update to naming rules for finding malicious processes somehow resulted in the CSAgent.sys process attempting to write to an invalid memory address, thus crashing the operating system 3 - A very slow, manual fix. Four days after the outage, recovery was ongoing, as every single impacted machine and host had to be fixed manually 4 - Who’s responsible? Obviously, CrowdStrike is and it’s tempting to think Microsoft should share blame. A regulation from 2009 could also have played a role 5 - Learnings for software engineers. Quantify potential impact, do canarying/staged rollouts, treat configuration like code, and more

A tough go this morning for organizations around the world running Crowdstrike Falcon software, experiencing massive outages across all industries. I suspect the support lines at Crowdstrike could be overloaded so I thought we would post a summary of events and actions. The root cause of the outage is reported to have originated from a defect in a content update for Windows hosts, deployed by Crowdstrike which led to widespread IT outages globally, including areas such as healthcare, banks, transportation and critical infrastructure. This issue causes Windows devices to “blue screen”, also known as “blue screen of death display” (BSOD), rendering those systems unable to start, perform any tasks or receive user input. Possible Workaround - Boot your system into Safe Mode by performing these steps: 1)    Restart your computer. 2)    Press the F8 key (or Shift + F8) repeatedly before the Windows logo appears. 3)    Select Safe Mode from the Advanced Boot Options menu. 4)    Navigate to the CrowdStrike Directory: a.    Open File Explorer. b.    Go to C:\Windows\System32\drivers\CrowdStrike. c.    Locate and Delete the Problematic File: Find the file matching "C-00000291.sys"*. 5)    Delete this file. 6)    Reboot Normally. 7)    Confirm the issue is resolved. Please perform these steps on a test system and validate functionality prior to deploying across the organization. 

CrowdStrike apologized today for a July - IT global outage caused by a flawed software update. The company pledged to implement a new process to prevent similar incidents. The outage resulted in significant disruptions, including flight cancellations and business losses. CrowdStrike’s senior vice president, Adam Meyers, testified before Congress. I personally believe that this incident emphasizes the critical need to have strict pre-deployment testing process and transparent series of communication during crises. For further information regarding the incident of 19 July, please refer to the event timeline provided in my earlier post https://lnkd.in/gWirNUTA Video Reference: https://lnkd.in/gps6CUqG #Crowdstrike #GlobalITOutage #Microsoft

Nearly everyone is aware of the CrowdStrike software outage that occurred on July 19th, 2024. Now that a few weeks have passed, we would like to share the key lessons we have learned from the incident. Click the link below to read our latest blog, “Lessons Learned from the CrowdStrike-Microsoft Misconfiguration Error” https://hubs.ly/Q02L6z7D0