CrowdStrike CEO: Companies are choosing between getting hacked and shutting down
Microsoft systems down. Air traffic systems down. Problems at Chase, United, and Apple. After a week of outages across big systems, the AI conspiracy theories are in full swing. CrowdStrike founder and CEO George Kurtz describes how AI agents can turn a patch into a working exploit within an hour, and how CEOs are now taking services offline rather than risk being hacked. He also discusses CrowdStrike’s new AI Kill Switch, and why slowing down the frontier labs won’t slow down the attackers.
This is an abridged transcript of an interview from Rapid Response, hosted by former Fast Company editor-in-chief Robert Safian. From the team behind the Masters of Scale podcast, Rapid Response features candid conversations with today’s top business leaders navigating real-time challenges. Subscribe to Rapid Response wherever you get your podcasts to ensure you never miss an episode.
So what is going on? Over the past week, we’ve seen Microsoft systems go down. Air traffic systems go down. . . . The AI conspiracy theories are everywhere. Is all this just a coincidence?
I think a few of my friends and colleagues might have their tinfoil hats on as well. The reality is it’s the bill for the Mythos moment. Nine months ago, when Mythos came out, it really set in motion everyone looking for these vulnerabilities, right? And the whole industry has been racing to find as many vulnerabilities as it can and create as many patches as it can. But what we’ve done now is hit the sound barrier of actually being able to roll out all these patches. So when you look at what’s really taking place, and you look at all the issues that were found in Black October, you’ve got Darker November.
This is like the PHP code, and now Java, that people are scrambling to find and plug these gaps in.
Yeah, exactly. I think the Java one is actually going to be worse. There are already working exploits for all of that. But what people are doing now is rushing to roll out all of these patches, and they’re making the decision: Breach or break. That is, are we going to get breached because we can’t patch fast enough, or are we just going to break something and hopefully fix it if we roll it out? That’s kind of a new norm now because the industry can’t keep up.
Technology is messy. Things happen, and we’re going to get better and better as an industry at dealing with this sort of AI speed that we’re facing. When you think about all the legacy systems that are out there, and you think about even banking-type systems, there’s a lot of legacy-type code out there, and it’s not as easy just to create a fix while everything is in midstream. So it’s not always clear, and when things are melting down, you get on these 24-hour bridges, and people are trying to figure out what actually happened. It’s a bit of fog of war.
As you describe it and go through these examples, the air traffic one seems like a particularly fragile one. Is the system fragile?
I think technology is just fragile, whether you’re in an Apple ecosystem, Android, or you use Microsoft or Google, whatever you’re using. Every day people use this, and they sort of just expect it to work, and they should. But behind the scenes, when you actually look at how complicated these systems are, how they operate, and the interaction with hardware and software, disks get full, memory gets overloaded. You would think that all this has been worked out, but there’s a lot of just making stuff work in the background. And the technology folks, the men and women who have to keep this running, literally wake up every day and are just like, “OK, what are we going to have to deal with today?”
We’ve had other kinds of cyber troubles recently: OpenAI’s agents breaking into Hugging Face, and French supermarkets hit by hackers shutting down refrigeration systems, which seem like a different order of things. Are any of these episodes an “aha” moment for you, of us sort of crossing a threshold?
When you look at the latest Patch Tuesday from Microsoft, it was 1,000-plus vulnerabilities that were fixed. And again, this has spiked. . . . I think we’ve had 25% of all the vulnerabilities ever created found in the last year. Just to give you an idea of the order of magnitude of what we have to deal with.
So all these patches come out, and now what we’re seeing is the automation by AI agents and threat actors, where they will take a patch and compare what was patched versus what wasn’t patched, and they immediately know where the flaw was. Then they automate the vulnerability exploitation of that. Within an hour, you can have all that done, where that would take a nation-state actor maybe weeks to do.
So the fact that we’re starting to see these issues come up as quickly as we are, I’m not surprised. But when you think about the refrigeration systems, this was a big one in Europe. What does AI allow you to do? There’s probably a handful of people, relatively speaking, on planet Earth who understand how to program these refrigeration systems. But when you actually take an AI agent and go, “Hey, I don’t know much about the refrigeration system. You figure out how to program it,” it will figure that out. You don’t have to be an expert in any of these technologies now. And typically they’re underprotected because it’s a refrigerator. Nobody really thought about security when they were building it.
How much of the game is becoming like “My AI is better than their AI?” You have to stay ahead of the attacks.
It’s the old Spy vs. Spy cartoon. It’s really what it is, right? Who’s going to stay ahead?
You recently launched a product called the AI Kill Switch. Which is designed to stop rogue agents. How do you know which scenarios would prompt hitting the kill switch?
If you think about industry, if there was a manufacturing problem with a big machine, there’s always the red button. It’s like, stop that thing because it could be causing bodily harm. And it’s the same scenario. Are the agents doing something they shouldn’t be doing? Are they multiplying, attacking other systems, or bringing down systems internally? You want to be able to hit the button. The challenge with the kill switch is there’s blunt force. It’s almost like pulling the plug.
You work closely with both OpenAI and Anthropic. Dario Amodei at Anthropic has called on the industry to slow down. There’s been quite a lot of noise about it, although development keeps steaming ahead. Do you give OpenAI and Anthropic advice about speeding versus slowing?
At the end of the day, the genie is out of the bottle. You can slow whatever you want down on the frontier. The open-weight models are three months behind. Just slowing them down is not going to slow the rest of the world down. But keep in mind, and I just want to make this distinction, Bob, they are called labs. Okay, labs. What happens in a lab? You develop something, it kind of works, it does great things, but when you put it in the real world, it may not actually work as intended in the lab, which is why the security industry has now moved into the safety industry and has become a great opportunity for folks like us.
Anyone can slow down. If the model is not right, if it’s not aligned, if it’s not getting the output you want, if the quality control is not there, you know what you do? You don’t release it. You go back and do another run until you get it right.
So what should any business leader do right now to improve their cyber footing?
Well, I think maybe first is go find your security and IT people and give them a hug, because they are at 110% of capacity now. I’ve never seen this before, but it’s happening across industry. Company CEOs are making a decision: Take something offline or be hacked. They’re saying, “Hey, we would rather take a massive service offline than be hacked.” They’re willing to make that decision if it’s so bad. When PHP came out, I had plenty of companies say, “Hey, we may just take everything down because it’s so bad.”
内容来自 Fast Company,版权归原作者所有。
阅读原文 ↗