What Next-Generation Protection Should Do: Lessons from the CrowdStrike Incident

In the evolving landscape of cybersecurity, the quest for next-generation protection has never been more critical. A recent incident involving CrowdStrike has underscored the limitations of current security systems that rely heavily on frequent updates and patches. As cybersecurity experts have argued for years, the ideal protection system should not require constant updates to stay effective. Instead, it should incorporate embedded AI and evolving algorithms that can adapt to new threats without the need for frequent intervention.

The Challenges of Static Systems and Limitations of Frequent Updates

One of the key issues with current systems is their static nature. Traditional security measures often rely on fixed rules and signatures, which can become outdated as attackers develop new techniques. This static approach contrasts with the dynamic capabilities of machine learning and AI, which can continuously evolve to address new threats.

The CrowdStrike incident underscores a broader cybersecurity challenge: the inherent risks of relying on continuous updates. Systems dependent on regular patches often operate reactively, struggling to keep pace with rapidly evolving threats. This approach can introduce delays and vulnerabilities, as updates may not always be timely or perfect. Microsoft's Patch Tuesday model exemplifies this issue, where scheduled updates aim to maintain security but also create potential risks. Systems reliant on periodic patches can be exposed to threats emerging between update cycles, while the patching process itself can sometimes introduce new vulnerabilities or compatibility problems.

The Case for Embedded AI , Evolving Algorithms and How It Could Have Prevented the CrowdStrike Incident

The optimal solution for next-generation security incorporates advanced technologies such as embedded AI and evolving algorithms directly into the security system. These technologies offer several advantages:

• Proactive Defense: Systems with embedded AI can anticipate and counteract threats in real-time, without waiting for updates. This proactive approach helps to prevent attacks before they can exploit vulnerabilities.

•   Adaptive Learning: AI-driven security systems can learn from new threats and adjust their defenses accordingly. This continuous learning process reduces the need for frequent updates and ensures that the system remains effective against emerging threats.

• Reduced Risk: By eliminating the reliance on periodic updates, AI-integrated systems lower the risk associated with update delays and potential vulnerabilities introduced during the patching process.

• In the context of the CrowdStrike incident, a system with embedded AI could have provided several benefits:

• Early Detection: AI algorithms could have detected the problematic update before it was widely deployed, identifying potential issues and preventing the update from causing widespread disruption.

• Real-Time Adaptation: Instead of relying on a delayed response, an AI-driven system could have adapted its defenses in real-time, mitigating the impact of the update and addressing vulnerabilities as they emerged.

• Continuous Protection: With embedded AI, the system would continuously monitor for new threats and adjust its defenses accordingly, reducing the need for reactive updates and improving overall security.

The Future of Cybersecurity Protection

The next generation of cybersecurity protection should focus on embedding AI and evolving algorithms into security systems. By doing so, organizations can achieve: Enhanced Resilience: Continuous adaptation to new threats without the need for frequent updates.

Improved Efficiency: Reduced reliance on periodic patches and updates, minimizing the risk of vulnerabilities introduced during the update process.

Greater Security: Proactive defense mechanisms that anticipate and counteract threats before they can cause harm.

CyberSecOp: Your Partner in Finding the Right Solutions

At CyberSecOp, we understand the complexities of modern cybersecurity and the challenges posed by current systems. Our team, along with our trusted partners, is dedicated to helping your organization find the right solutions for your unique needs. We specialize in identifying and integrating advanced technologies that offer proactive and adaptive protection, ensuring that you are equipped with the best defense mechanisms available.

CrowdStrike and Microsoft Outage

On July 19th CrowdStrike deployed a faulty patch/configuration update for its Falcon sensor software. The effected devices were those PC’s and servers running Windows operating systems. The outage, which affected systems worldwide, including Windows virtual machines and the MS Azure platform, began rebooting and/or crashing at approximately 10:48 AM Eastern. (The affected systems also included those running Windows 10 and 11 that were running CrowdStrike Falcon). Machines running macOS and Linux were NOT affected. It was noted in a number of sources that there was a similar issue for devices running Linux in April 2024.

 At 9:27 AM Eastern, CrowdStrike deployed updated content. Devices that booted with this later content were not affected. 

NATURE OF THE ISSUE:

CrowdStrike’s CEO, George Kurtz, confirmed the issue was due to a faulty kernel configuration level file and NOT the result of a Cyber Attack. Given the AT&T data breach just 10 days ago on July 12th, and the fact that there have been 10 major Cyber Attacks or Data Breaches so far in 2024, it was not surprising for the general public, as well as all of the affected all types and sizes of businesses ranging from airlines to hospitals to federal agencies and retail stores to immediately think that another Cyber Incident was the cause of the ensuing outages caused by the configuration issue. Thankfully this was not a cyber-attack, however, this issue does point out just how vulnerable the organizations we critically reliant on are. 

THE FIX:

Should any organizations still be unable to fix their issues, there are a number of organizations, including CyberSecOp, that are able to help you with the relatively direct but painstaking task fix for the ‘outage’.

• Affected Machines can be restored by booting into safe-mode or the Windows Recovery Environment and deleting any .sys files beginning with C-00000291- and with timestamp 0409 UTC in the %windir%\System32\drivers\CrowdStrike\ directory. 

• This process must be done locally on each individual device.

• Someone will have to reboot the affected computers individually with manual intervention on each system.

• NOTE: Some Azure customers have had success by rebooting the affected virtual machines numerous times (10,12,15 times was not unheard of) while connected to Ethernet.
  NOTE: Microsoft has also recommended restoring from back-up from before July 18th. 

HOW AND WHY THIS HAPPENED

Though at this time we cannot be 100% certain as to what caused this issue, we can expect that one of the primary culprits was the lack of testing and validation of the configuration update prior to its release. As noted in last week’s posting from CyberSecOp, it is absolutely critical for organizations of all sizes, across all market segments to properly plan and establish policies for their use, deployment and on-going updating of their technology ecosystem. In this case, whether or not CrowdStrike has the proper plans and controls in place to ensure they have screened and tested their upgrades, patches and releases is not in question – what is being questioned, and far more importantly is - have they been followed. Further, are those organizations and their managed services providers; effected by this latest outage properly testing and validating ANY changes to their environments before deploying them in to production environments? Is the CMDB in place? 

THE MORAL OF THE STORY  …

Organizations must develop, iterate on, and adhere to robust policies and procedures to enhance their change management processes. From a risk management standpoint, organizations should reconsider their operational strategies to ensure that dependency on a single vendor does not impact all of their operations. Diversifying vendors and creating competitive hedges can be crucial in times of disaster. Questions organizations should consider asking their managed services providers include:

• Was this a planned update?

• What testing was conducted in non-production environments, and what were the results?

• What CMDB policies and procedures were overlooked?