Microsoft outage: CrowdStrike explains what exactly went wrong
In a technical blog, the company said the sensor configuration update that caused the system crash was remediated at around 10.57 a.m.
IANS
Representative Image (IANS)
NEW DELHI: As millions of Windows computers were left crippled for hours, disrupting the services of airlines, banks, hospitals and stock exchanges worldwide, cyber-security platform CrowdStrike on Saturday tried to explain what actually went wrong at their end.
According to the company which provides third-party security updates to the Satya Nadella-run tech giant, on July 19, at 9.30 a.m. (India time), it released a sensor configuration update to Windows systems.
Sensor configuration updates are an ongoing part of the protection mechanisms of the Falcon platform.
“This configuration update triggered a logic error resulting in a system crash and blue screen (BSOD) on impacted systems,” said CrowdStrike.
In a technical blog, the company said the sensor configuration update that caused the system crash was remediated at around 10.57 a.m.
“This issue is not the result of or related to a cyberattack,” it said.
Millions of customers running Falcon sensor for Windows version 7.11 and above that were online were impacted.
“Systems running Falcon sensor for Windows 7.11 and above that downloaded the updated configuration from 9.30 a.m. to 10.57 a.m. -- were susceptible to a system crash,” the company said.
According to it, this is not a new process and the architecture has been in place since Falcon’s inception.
The update that occurred at 9.30 a.m. was designed to target newly observed, malicious named pipes being used by common C2 frameworks in cyberattacks.
The configuration update triggered a logic error that resulted in an operating system crash.
“CrowdStrike has corrected the logic error by updating the content in Channel File 291. No additional changes to Channel File 291 beyond the updated logic will be deployed. Falcon is still evaluating and protecting against the abuse of named pipes,” the company explained.
Systems that are not currently impacted will continue to operate as expected, continue to provide protection, and have no risk of experiencing this event in the future.
“We understand how this issue occurred and we are doing a thorough root cause analysis to determine how this logic flaw occurred. This effort will be ongoing,” said CrowdStrike.
