Why everything is breaking: outages, AI, and the new cyber math
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 joins Rapid Response to explain what’s actually going on. Kurtz describes how AI agents can turn a patch into a working exploit within an hour, why the old pyramid of hacktivists, criminals, and nation states has collapsed, and how CEOs are now taking services offline rather than risk being hacked. He also discusses CrowdStrike’s new AI Kill Switch, why slowing down the frontier labs won’t slow down the attackers, and what endurance racing has taught him about risk and speed.
About George
- Founded & leads CrowdStrike, top next-gen endpoint security provider
- Founded Foundstone; acquired by McAfee in 2004
- Former McAfee Worldwide CTO, GM & EVP at a $2.5B security company
- Author of Hacking Exposed, bestselling security book of all time
- 30+ years in cybersecurity; internationally recognized expert & speaker
Table of Contents:
- Why patching speed is now breaking systems
- Why outages are hard to trace in real time
- How AI is accelerating cyberattacks everywhere
- Why safety is replacing old security models
- Why smaller companies are now prime targets
- How AI agents are reshaping supply chain risk
- Why deepfakes and open models raise the stakes
- What leaders should do as cyber risk surges
- Episode Takeaways
Transcript:
Why everything is breaking: outages, AI, and the new cyber math
Note: Transcripts are automatically generated from episode audio, and are not fully corrected for spelling, grammar, and formatting.
GEORGE KURTZ: Are the agents doing something they shouldn’t be doing? Are they multiplying and attacking other systems, or bringing down systems internally? If you’re looking at everything it’s doing, you may want to hit the kill switch. But at the end of the day, the genie is out of the bottle. You can slow whatever you want down on the frontier. They should have great safety. They should have great controls. They should have guardrails. They should have great sandboxes. They need to do all that. But just slowing them down is not going to slow the rest of the world down.
BOB SAFIAN: That’s George Kurtz, CEO of cybersecurity firm CrowdStrike. I wanted to talk to George this week amid a wave of cyber outages and rising fears of AI run amok. George has an insider’s perspective, from hacker capabilities to the big AI labs. In this episode, he talks about what’s generating the recent troubles, what’s likely ahead, and what we can all do about it. So let’s get to it. I’m Bob Safian, and this is Rapid Response.
[THEME MUSIC]
I’m here with George Kurtz, co-founder and CEO of CrowdStrike. George, thanks for being here.
KURTZ: Good to see you, Bob.
Copy LinkWhy patching speed is now breaking systems
SAFIAN: So what is going on? Over the past week, we’ve seen Microsoft systems go down, air traffic systems go down, and companies like JPMorgan Chase and Apple have system problems. No one seems to know exactly what’s to blame, which gets, of course, the AI conspiracy theories going everywhere. Is all this just a coincidence?
KURTZ: Bob, my phone has blown up over the last week with people asking what’s happening. Is the world coming to an end? I think a few of my friends and colleagues might have their tinfoil hats on as well. People think the world is ending here because of everything that’s happening and are asking, “Is this really a coincidence?” And the question you pose is, is it AI? What is it? 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? Not just with Mythos, and obviously you’ve got sort of Daybreak models, but frontier models that are capable of finding all these vulnerabilities. And the whole industry has been racing to find as many vulnerabilities as it can and create as many patches as it can. That has taken place over the last number of months. 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.
SAFIAN: This is like the PHP code, and now Java, that people are scrambling to find and plug these gaps in.
KURTZ: Yeah, exactly. I think the Java one is actually going to be worse. There’s 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, 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. As I said, they hit the sound barrier patching, and we’ve got to find our way and get our sea legs a bit in terms of how we actually create these patches and get them rolled out without breaking things. As an industry, we’ve never had to move this quickly. So in summary, what you’re seeing, I think, is the culmination of all these vulnerabilities that have been found and all of these rushed patches that now have to take place.
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.
SAFIAN: We’re creating these bugs because we’re introducing things in some ways, I don’t want to say too fast, but at a speed where we’re not able to test everything before it’s out.
KURTZ: The number one thing that actually creates outages is change.
Things work, and then somebody makes a change somewhere, or it’s an unintended change, or it’s one small item on the router, and then all of a sudden things stop working. So that is by far the number one issue in why you have an outage. And unfortunately, when you look at how complicated these large cloud infrastructures are, one little change can have a cascading effect. So when you look at the companies that are impacted, everyone’s trying to do the right thing, but because of technology, how complicated it is, and how fast you have to move, all of the unintended consequences may not be known. If it’s just a cloud infrastructure, you’ve got these templates that you can update, and the next time the system comes up, it’s fixed, right? That is the easier part. 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. Again, as an industry, we’ll learn from this and get better.
Copy LinkWhy outages are hard to trace in real time
SAFIAN: You’ve talked about clarity in these sorts of outages. You were very upfront when there was a CrowdStrike update in 2024 that led to some Windows troubles and some grounded flights.
KURTZ: Yep.
SAFIAN: But it can take time to get that clarity, can’t it? Do you always know how and what created these outages? Sometimes you never know?
KURTZ: It’s difficult. We went through a big one, and we had our part fixed in about 72 minutes. But you had interactions with the Windows operating system that caused longer delays. When things stop working, everyone’s trying to figure out, well, what caused it? They can see the impact of it, but they’ve got to work back from what actually caused it. And then you really have to start looking at what changes were made. That’s really where you start to see the issues. You’ve got to go back and say, “OK, there was a router in Arkansas or something that somebody put in with the best intentions, and it should have been localized,” but all of a sudden it started broadcasting out and had other impacts. 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.
SAFIAN: As you describe it and go through these examples, the air traffic one seems like a particularly fragile one. Is the system fragile?
KURTZ: I think technology is just fragile, whether you’re in an Apple ecosystem, Android, or you use Microsoft or Google, whatever you’re using, right? 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?”
Copy LinkHow AI is accelerating cyberattacks everywhere
SAFIAN: These issues of the complications within the systems have been there for a long time. 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. You’ve been in the cyber game a long time.
KURTZ: Yeah.
SAFIAN: Are any of these episodes an aha moment for you, of us sort of crossing a threshold?
KURTZ: When you look at what we’re seeing today, it’s something I talked about probably two years ago: the automation now of the weaponization of vulnerabilities and patches. And what I mean by that is, you look at the latest Patch Tuesday from Microsoft. It was 1,000-plus vulnerabilities that were fixed, right? And again, this has spiked. Over the last year, I think we’ve had 25% of all the vulnerabilities ever created found in the last year, OK? 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.
SAFIAN: Yeah.
KURTZ: 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. This is how all the TVs got hacked. Did you follow the Android TVs?
When they pointed Claude at it and basically said, “Figure it out, how it all works,” then you get the exploitation, and then you have all the follow-on activity. So what I’m saying is, you don’t have to be an expert in any of these technologies now, like how the refrigeration systems work. You point an AI agent at it, and once you understand how to communicate with it, then you can build all the exploitation around it. And typically they’re underprotected because it’s a refrigerator. Nobody really thought about security when they were building it.
SAFIAN: I mean, there are some folks who say at this point, attackers aren’t doing fundamentally new things. They’re just doing the things they used to be able to do at greater scale and greater speed. But as you describe it, it sounds like new doors are already open.
KURTZ: They’re already open, but let me at least try to categorize the threat actors. The way I look at it, if you think about a pyramid in your head, at the base of the pyramid you have hacktivists. You have the greatest number of people with the lowest level of sophistication. The next part of the pyramid, the middle section, is e-crime. You’ve got more sophistication, but fewer of them. At the top, you’ve got nation-states, so the fewest number but the most sophisticated. We used to call that the apex predator. The new apex predator is the agent state. Now you’ve got agents that sit across all three of those layers, and what you see is the pyramid has now collapsed. What I mean by that is the hacktivist has the same capabilities as the nation-state. Using AI, you have the same capabilities. You can create a very sophisticated attack just by talking to the AI agent. So what that means now is you’ve got a higher number of attacks, greater volume, and a greater level of sophistication driven by automation. That is the scary part of where we are today: keeping up with the volume. But it’s democratized destruction. Anybody with an AI agent — some of the frontier models will refuse what you want to do — but if you take an obliterated model, which you can download from Hugging Face, and you plug it into your Mac or a Spark DGX or something, you can run the most sophisticated attacks without any refusals. That is the state of where we are today.
Copy LinkWhy safety is replacing old security models
SAFIAN: All these changes, these AI fears and vulnerabilities, they’re good for your business, aren’t they?
KURTZ: Technology change is good for our business and for security. What I mean by that is security has always paralleled the slope of the technology curve because it used to be simple, and now it’s super complicated, up and to the right. Every time there’s a change in technology, whether that is cloud, mobile, AI, or the move from mainframe to client server, you needed security to go with it. There’s a shift now from security, which I’ve done over the last 30 years — keep everyone out, right? Security business: keep everyone out — to safety: allow everyone to use technology. One was keep everybody out. The next one is, how do you safely allow the use of AI?
SAFIAN: In other words, how do you safely allow your own team to go out and come back and not bring things with them?
KURTZ: Exactly. This is security and safety. They sound similar, but they’re vastly different, and the safety element now opens up a much broader addressable market for us.
SAFIAN: How much of the game is becoming like my AI is better than their AI? You have to stay ahead of the attacks.
KURTZ: It’s the old Spy vs. Spy cartoon. It’s really what it is, right? Who’s going to stay ahead? What we’ve done is we’ve actually formed a superintelligence cybersecurity lab to create essentially frontier-caliber models for security, both on offense and defense. The offensive models continually make the defensive models better. Why is that important? Because right now, the offense, the bad guys, the bad threat actors, have an advantage over the defenders because the defenders didn’t have models capable of dealing with the attacks they were seeing. A good example of that — you may say, “How can that be?” — is Hugging Face.
People look at this and say, “Wow, the aha moment was you had autonomous agents breaking out of a sandbox, breaking into another company. They did it to pass a test, but it was done end to end.” Sure, that’s novel and unique, but the aha moment was the fact that the defenders didn’t have the same frontier capabilities in their models as the offense. What they had to do was go out to a Chinese model, and they had to figure out all these attacks, what was behind them, to make sense of the fact that it was actually coming from these AI agents. So the defense didn’t have the same capabilities as the offense because the models refused. They went to frontier, and it just said no. That’s why, in today’s world, the only way to solve this problem is to have defensive models that are better than the offense.
Copy LinkWhy smaller companies are now prime targets
SAFIAN: I could imagine that in the old world, if I were a hacker at any stage of the pyramid, I would probably target my efforts at bigger places because the return was bigger. It was worth the effort. But now it seems like it’s easier to spread those attacks anywhere, and I guess that probably means that smaller enterprises and smaller outfits are vulnerable. Maybe they were always vulnerable, but they’re targeted now in a different way?
KURTZ: Most things in life come down to time and money, just to simplify it, right?
How much time does it take? How much money can be gained? In this world, you can go to bed, let your agents run, and for $50 in tokens, you come back the next morning and you’ve got a new bounty of riches from companies that the agents have broken into. So you’re exactly right. When we think about ransomware or companies being extorted, the big multimillion-dollar payoffs are certainly going to be in the large enterprises. But what we’re seeing now is that because of the automation, there’s a lot of money to be made in the SMB.
Small dollars add up to big dollars. I talk to people all the time, and they say, “We’re not sure we need something like CrowdStrike because we don’t think we’re going to be attacked, or we’re small-time.”
SAFIAN: Right. Why would we be a target?
KURTZ: That is just not the case. You can make 5 million from one company, or you can have 100 companies at 500,000. Do the math. They’re going to be underprotected compared to a large enterprise. Generally, what happens is they get knocked offline, and it’s not as easy for the smaller companies to recover. It’s a big mess.
Copy LinkHow AI agents are reshaping supply chain risk
SAFIAN: Most companies run on tech they don’t control — cloud platforms and AI models and vendor software. How much can you trust a partner to provide the security for you?
KURTZ: I think you’ve got to look at the vendors you’re dealing with, how much they’re spending on security, what sort of certifications they have, and then you have to look at the supply chain attacks, which are very prevalent now. What I mean by that is, over the last 30-plus years, we said, “Keep everyone out. Don’t run untrusted software. If you’re going to download it, it has to be checked and secured,” and those sorts of things before you run it. We’ve turned that entire model on its head. So if you’re running a Claude or a Codex or whatever, pick something, generally these tools will go, “I need something open source. I’m going to go out, download it, and just run it,” and these packages get infected.
We took everything that we were doing defensively over the last 30 years, and we threw it out the window. We said, “We’re just going to let our agents, which we’re going to give our identity to — or worse, if it steals an identity that’s even greater than our own — then it can go out to the internet, download these packages, and just run whatever it’s going to run.” That’s the scary part of what we’re seeing now.
SAFIAN: I always thought of supply chain in a physical sense, but what George is talking about is the digital supply chain, where information is brought in by AI agents. So does that mean every business needs an AI agent kill switch? We’ll talk about that and more after the break. Stay with us.
[AD BREAK]
Before the break, CrowdStrike’s George Kurtz explained how a wave of efforts to patch cybersecurity vulnerabilities has ironically precipitated a flood of outages. Now he talks about a new product called the AI kill switch, why everyone should hug their IT people, and more. Let’s jump back in. You recently launched a product called the AI Kill Switch.
KURTZ: Yeah.
SAFIAN: Which is designed to stop rogue agents. How do you know which scenarios would prompt hitting the kill switch?
KURTZ: If you think about industry, if there was a manufacturing problem with a big machine, there’s always the red button. If you walk around any plant, you’ll see the big red button, right?
SAFIAN: Yes.
KURTZ: 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. When you look at the Hugging Face example, if you’re looking at everything it’s doing, even in an automated way, you can see that it broke out and what it’s doing, and you may want to hit the kill switch. The challenge with the kill switch is there’s blunt force. It’s almost like pulling the plug.
SAFIAN: Right. It’s pulling the plug on everything, right?
KURTZ: On everything. Or do you go, “Hey, this agent and its sub-agents need to be basically killed”? Those are the things that we continue to refine so you can get granular and not just pull the plug for an entire company.
SAFIAN: Over time, your switch will be able to be more targeted than it is right now.
KURTZ: We can do it en masse, and we’ve got more granular controls, but over time it gets more and more granular, down to the exact command, the exact agent, the exact sub-agent. Those are the things that we continue to add into the product.
Copy LinkWhy deepfakes and open models raise the stakes
SAFIAN: I wanted to ask you about the proliferation of deepfake tech. How widespread should we expect that sort of deepfake capability to grow? And if you can’t trust a voice or a face, do we have to rethink verification in some ways?
KURTZ: It’s a real problem. I can change my appearance to be anyone I want. The tools are there. There are AI overlays, so Bob, you can be talking to me, and the AI is listening to you and then immediately providing responses back. A good example of this is the North Koreans when they essentially are getting jobs as tech workers, and they’re passing with flying colors on all these technical tests. That’s the way they’re doing it. They’re in an interview, and they pass with flying colors because it’s listening and telling you how to respond.
Then they’re infiltrating companies and creating a laptop farm, and ultimately they have access to your company. They don’t have to break in. They’re already logged in.
SAFIAN: They’re working there. Yeah.
KURTZ: They’re already working there. So deepfake is a massive problem today, and authentication and identity are very, very important. You just can’t take somebody’s word for it or the fact that I’m going to get on Zoom with you and it looks like Bob is in your place there.
SAFIAN: So this week, Anthropic is going public. 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? Do you worry about developing AI too fast?
KURTZ: Yeah. Look, I’m not sure whose advice they listen to. We worked with Anthropic to be able to take our technology and run it in the Claude cohort container. So all of that is very positive. We have a very good relationship with them. But 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.
I mean, they’re good enough, and you can run them without any restrictions because they take all of the guardrails out, which is called an obliterated model, right? It comes from the term ablate, or remove. So you can go to Hugging Face, and you can say, “Just get rid of the refusals,” and you can have it do whatever you want. So they can slow down all they want, and by the way, they should have great safety. They should have great controls. They should have guardrails. They should have a great sandbox. They need to do all that. But just slowing them down is not going to slow the rest of the world down.
SAFIAN: In the spy-versus-spy world that you live in, you need those frontier models to continue to be at least three months ahead or more because you’re using those models to stay ahead of the folks who are attacking.
KURTZ: We do work with them and use them, but there’s a reason why we created our own labs, because we’re not going to just depend on the frontier models.
SAFIAN: Mm.
KURTZ: The thing is, they don’t have all the data that we’ve accumulated over the last 15 years. So we’ve taken open-weight models and post-trained them with our own data. So we’re getting frontier-level or better offensive models and defensive models at a fraction of the cost, and then we’ve built our own harness. We certainly will leverage any of the frontier models. They’re doing great work, but we’re not going to just depend on what they’re doing. We built our own, and that’s why we now have a massive lab ourselves that, in the cyber world, is operating at frontier-level capabilities. Our models are not going to cure cancer, but we want the best cyber models out there, and that’s what we’re working on.
SAFIAN: What perspective do you have about what role government plays in the evolution of these AI labs?
KURTZ: Yeah.
SAFIAN: Policing themselves, you guys policing yourselves with your own lab?
KURTZ: Well, I think standards and guidelines are important, and there are other areas for policing. I can’t wait for OpenAI and Anthropic to go public because you’re held to a much different standard. There are so many compliance requirements. There are so many disclosure requirements. With that comes more liability. So I think there’s a natural forcing function there. But the government role is, how do we maintain our lead in AI, SI, pick your acronym. I think if you just clamp down and say we’re going to have the FAA certifying models, that’s not going to work.
Because the rest of the world is moving very quickly. So what are customers saying? They’re saying, “We want to work with the most secure and safe providers out there.” If you’re reckless and your agents are doing bad things and you can’t control them, and you don’t give visibility and provide safety from a model lab perspective, then I think the market is going to see that and go in a different direction. But keep in mind, and I just want to make this distinction, Bob, they are called labs. OK, 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.
SAFIAN: And you, or anyone as a lab operator, have a choice as to what and when you release things that you’ve tested in the lab into the real world.
KURTZ: That’s it. 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.
SAFIAN: Right.
KURTZ: You go back and do another run.
SAFIAN: Right.
KURTZ: Until you get it right. And then, obviously, these things are non-deterministic. They’re still going to have to fill in the blanks when they get to the real world. This is part of the problem, and just to simplify it a bit, the models get trained on what they know, OK? And then it’s almost like a kid that you raise. You give it morals and values and a framework for making a decision, but when it gets in the real world, there’s a scenario that’s never been seen before, and it has to use that framework to reason and make a decision. This is how a model works. So they can do the best training, they can put guardrails around it, but at some point it’s going to get in the real world and have to fill in the blanks on what decision it’s going to make.
SAFIAN: And how that judgment is determined, I mean, we struggle with that with our children. It’s hard to pin down that, too. That’s what that strange term interpretability, I guess, is about in the AI world: trying to figure out how it’s making that judgment.
KURTZ: Exactly. Unfortunately, it’s a bit of a black box. Part of what needs to be done is to understand the reasoning chains of how the model is actually deciding what it’s doing. That generally isn’t exposed, and I think it should be.
Copy LinkWhat leaders should do as cyber risk surges
SAFIAN: Beyond CrowdStrike, you’re an endurance race car driver, and a good one. You won your class at Daytona and Le Mans, among other places, this year. Both car racing and cybersecurity involve accepting a certain amount of risk. Are there lessons that apply from one to the other?
KURTZ: I think there are two critical concepts that apply. One is managing risk, and two is speed. Because when you’re driving a car and you’re racing, it’s all about how much risk you take. Do you risk passing the guy in the corner? Do you risk stuffing it in under braking and having an issue? Is it a clean pass? You’re in traffic. How much risk do you take? Is it at the beginning of the race? Is it at the end of the race? That’s security. How fast do we go patch something? Are we OK with breaking something versus having a breach? There’s a risk. There’s a trade-off. And then there’s speed. At the end of the day, there’s speed and the stopwatch. In security, speed has become paramount. It’s always been important, but it used to be weeks before people patched. “We’ll have it patched in 30 days.” That is long gone, right? So the speed and the cadence that you have to deal with this is the same thing in racing. In racing, the saying is, “If you’re not moving forward, you’re moving backward.”
It’s the same in security.
SAFIAN: So what should any business leader do right now, immediately, with speed, to improve their cyber footing? And I guess, what should we be preparing ourselves to endure as we go through this period of tech change?
KURTZ: Well, I think maybe first is go find your security and IT people and give them a hug, because they are at 110 percent of capacity now. We talk to teams over and over, and it’s not sustainable. So I think it’s focusing on how you manage risk. What’s most important? How do you prioritize? They’re not going to be able to patch everything as quickly as they’d like, so understanding critical assets and understanding exploitability lets you prioritize what happens. I’ve never seen this before, but it’s happening across industry: company CISOs and 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.”
SAFIAN: Because the risk of being hacked is so much higher.
KURTZ: Exactly. So think about these big services that we depend on. We work with the largest enterprise companies, and they’re like, “Hey, we’ll take down this part of the service because we would rather just take it down than have a security issue.” And that would never have entered the equation a year ago, but now 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.”
SAFIAN: And a year ago, what did they do?
KURTZ: A year ago it was like, “Hey, just do your best, patch it, mitigate it, put some rules in place, keep everything running.” And now, with AI agents, how fast they move, and this concept of a swarm, they’re basically saying, “Hey, we may just take it down,” because if the AI agents get in, A, you have a breach, but you also might be down 30 days rather than a few hours of taking it down, because you’ve got to figure out all the breaches and where it all is. You have defensive AI, which is to keep the offensive AI agents out. That’s one. And two is, how do you use security to provide safety so that you can actually exploit the power of AI? That was one of the number one things I’ve heard from CEOs, CIOs, and chief information security officers, who have said, “We need to go faster and deploy AI for the benefits, but we can’t unless it’s safe and secure.” If you’re racing an Audi or a Miata, you’ve got a lot of time to make a decision on whether you should pass or not. It’s slow motion compared to a Formula 1 car. So you may have to make decisions faster and accept some level of breakage until the industry gets better at understanding how to patch and keep things running in the wake of these AI attacks.
SAFIAN: Well, George, I really appreciate this. I’m not sure if I feel calmer and more relaxed, but I feel more informed.
KURTZ: Well, it was great to spend some time with you. On a positive note, I am an AI optimist, and I think there’s enough technology and security that can keep us safe as a society. But with any great power comes great responsibility, and we’ve just got to harness it and make sure we use it in a secure way.
SAFIAN: Amen to that. I wanna double-click on a stat George shared. Twenty-five percent of all cyber vulnerabilities ever created were identified in the last year. Companies used to try patching trouble spots, but now they’re preemptively shutting down to forestall any potential invasion of rogue AI agents. What George is telling us is if you feel like the cybersecurity environment is in flux, you’re dead right. Still, that doesn’t mean everything is about to collapse. I’m mindful of George’s car racing specialty as an endurance racer. That means he keeps the long term in mind with each move he makes, regardless of how fast he’s moving. In today’s world, that seems like a process we all need to get comfortable with. I’m Bob Safian. Thanks for listening.
Episode Takeaways
- CrowdStrike CEO George Kurtz says the recent wave of outages is less an AI conspiracy than the cost of patching at AI speed, as companies race to fix newly exposed flaws and sometimes break systems in the process.
- Kurtz argues cyberattacks have entered a new era because AI can weaponize fresh patches almost instantly, giving even low-level attackers capabilities that once belonged only to elite nation-state operators.
- That shift, he says, is forcing security to evolve into safety, with companies needing tools like AI kill switches and stronger controls to let agents operate without letting them run wild.
- He warns that smaller businesses and digital supply chains are especially exposed now, since autonomous agents can cheaply target underprotected firms and pull risky open-source code straight into company systems.
- For leaders, Kurtz’s advice is blunt: prioritize the most critical assets, support overstretched IT teams, and accept that in some cases taking services offline may be smarter than risking an AI-driven breach.