Crowdstrike has been the talk of the town for the past month for causing a massive global IT outage that left work disruptions worldwide, leading to companies losing billions due to the shutdown. Initially, it was revealed that faulty cybersecurity led to a massive mess, but after facing a tsunami of lawsuits from various companies, the cybersecurity firm has decided to explain in detail the root cause and the steps it is taking to ensure a similar mishap does not happen in the future.
Crowdstrike is facing a barrage of legal actions over $5B in financial losses, but a small print in its contract might save the company
Last month was rough for Crowdstrike, given how a mistake on their end led to a massive global IT outage. The impact of this outage still looms for some industries. It caused major disruptions for health care, banks, and airlines and even halted some emergencies.
Since all the major corporations use and are associated with the company's security services, the crashed windows led to significant financial losses incurred by these companies. The troubles for the security service provider seem to be never-ending, as the company is now facing numerous lawsuits for causing an estimated $5 billion in financial losses.
Amidst growing concerns and legal pursuits, Crowdstrike has now explained the root cause of the faulty update in a detailed report and how the issue was not spotted in testing before it was rolled out globally. The company was working on making it easier to update security threats on client computers, and for this, it tried a new method that would allow for threats to be detected in real time. The crash happened when Crowdstrike sent an update with 20 pieces of data instead of the 21 data points required, leading to the system crashing due to the error.
The second question was how the testing did not detect the issue before reaching the masses. This was due to the tests being unable to detect the missing piece, as they were designed to handle 21 data set templates even if they were not all used. Crowdstrike explains:
The selection of data in the channel file was done manually and included a regex wildcard matching criterion in the 21st field for all Template Instances, meaning that execution of these tests during development and release builds did not expose the latent out-of-bounds read in the Content Interpreter when provided with 20 rather than 21 inputs.
To ensure this issue does not relapse, the company has now added run-time bounds to see if there is a mismatch. The cybersecurity provider would gradually introduce updates by releasing them to a limited group initially to minimize the risk.
Crowdstrike now has to deal with the slew of lawsuits filed against it by companies from various sectors. Wired has shared Delta Airlines' intent to sue the security service provider for the $500 million lost due to the outage. However, Crowdstrike might be saved due to its terms and conditions, which limit its liability and make the small print hard to nullify.
Follow Wccftech on Google to get more of our news coverage in your feeds.
