1. Podcasts
  2. Software Engineering Daily
  3. Security in the Age of Instant Exploits
Software Engineering Daily

6 Oct 2026 · 50m · 21 chapters

Episode artwork

Security in the Age of Instant Exploits

In short

How AI changes software security by compressing the time from vulnerability disclosure to working exploits, enabling large-scale secret scanning and faster vulnerability discovery, while also giving defenders stronger tools if they apply context, continuous scanning, and automated remediation.

Guests

Alon Shindel, VP of AI and threat research at Wiz (acquired by Google in 2026), with a background in security since childhood; Gregor Vann, CTO/founder in Singapore, building Wintik.ai (AI-era email).

Key claims

The “disclosure-to-exploit” window has shrunk from months/years to days and even hours (citing zero-day clock.com). Attackers and defenders both get AI, but defenders can win by using internal context. Wiz uses “red agent” AI scanning and “green agent” remediation planning, including cloud-to-code tracing and prioritizing fixes by sensitivity/criticality.

Notable examples

MongoBlade (MongoDB) exploit derivable from public reports using Claude; GitHub tokens embedded in exposed web pages leading to account compromise and supply-chain risk; open-source maintainers overwhelmed by many AI-generated reports (example: one project receiving ~15 reports from different companies).

Written by AI. May contain mistakes.

Chapters

0:32

AI's Impact on Software Security

Discover how AI is transforming the landscape of software security and exploitation.

“In the world of software security, there was historically a comfortable lag between the moment a vulnerability became public and the moment attackers could exploit it.”
1:26

Guest Introduction: Alon Shindel

Meet Alon Shindel, VP of AI and threat research at Wiz, and learn about his background.

“the growing strain on open-source maintainers, and more.”
2:08

Alon's Journey into Cybersecurity

Hear Alon share his path into cybersecurity and his role at Wiz.

“hi it's great to be here thank you for having me yeah absolutely you are at whiz and this is i I think the second time we've now had someone from Wazon, which is exciting.”
4:51

The Evolution of Cyber Threats

Explore how cybersecurity challenges have evolved, especially with AI.

“You know, it's been a very fast journey.”
5:44

AI and Vulnerability Research

Learn about the role of AI in discovering software vulnerabilities and its implications.

“affected the security landscape and then sort of how should people be then thinking about their security sort of setup now that AI can be a part of that.”
7:19

Democratization of Hacking

Discuss how AI is making hacking more accessible and the implications for security.

“and how AI changes the threat landscape just by opening maybe new attack surfaces for the attackers.”
10:51

The Zero-Day Clock and Response Time

Understand the decreasing time to exploit vulnerabilities and its impact on security.

“Now, even, you know, a single person just from home can run these large operations, scan the internet, find these exposures.”
12:34

Rethinking Security Frameworks

Explore the need for new frameworks to respond to AI-driven threats in cybersecurity.

“And so we see more vulnerabilities and we see that, yeah, we need to respond to them faster because you see the exploits faster.”
14:00

AI's Role in Attack Surface Management

Explore how AI is used to identify and prioritize vulnerabilities in systems.

“And the reason that this part, I mean, it was always important not to have exposed resources out there.”
20:51

Navigating Responsible Disclosure in Cybersecurity

Discuss the principles of responsible disclosure and the challenges faced by developers.

“We also try to reach out either through the security email or, I mean, just to contact the company the same way that the other reports are being submitted.”
Show all 21 chapters
28:00

Understanding AI in Security Remediation

Learn how AI is utilized in identifying and remediating security issues in code repositories.

“connecting it to the file, to your code file that it is coming from is also difficult.”
29:15

The Trade-offs in Secure Development Practices

Explore the challenges and trade-offs developers face when adopting secure coding practices and tools.

“And part of this, I think the next step there will be how do you automatically test the new code?”
30:28

Risks of Unmaintained Libraries and Packages

Discuss the risks associated with using poorly maintained libraries and how to mitigate these risks.

“So if you see, and it's, I mean, something that was discussed in the past as well, where some libraries and some packages are not maintained well.”
32:19

AI's Role in Modern Code Analysis

Examine how AI models enhance the ability to find complex vulnerabilities in code.

“So since, I mean, if you write your code with a coding agent, in many cases, you don't even know what's inside it.”
35:04

Unique Challenges in Vulnerability Detection

Learn about the challenges in detecting vulnerabilities across diverse codebases and systems.

“Now, AI models, LLMs, they understand text well, and code is also text with structure, with rules, and all that.”
36:35

The Importance of Robust AI Systems in Security

Discover the significance of creating reliable AI systems for effective vulnerability management.

“I think I can share some of the challenges that we have from Billnard.”
39:42

Accepting Probabilistic Outcomes in Cybersecurity

Understand how the cybersecurity field is adapting to the probabilistic nature of AI outputs.

“Yeah, and one thing just briefly on that as well is just like the reproducibility of things that have been found.”
42:00

Understanding Probabilistic Vulnerabilities

Learn about the probabilistic nature of certain vulnerabilities and the challenges they present.

“But in the end, cybersecurity, yeah, you can have this like different results for different runs.”
43:32

The Evolving Landscape of Exploits

Explore how the exploit rate has decreased and what it means for cybersecurity.

“So that's just the fact we're not at one yet.”
45:50

Future of Vulnerability Management

Discuss the future expectations for vulnerability discovery and the role of the community in enhancing security.

“I mean, if we talk about this, there will be a curve at some point where I think that most of the open source software will be scanned.”
47:23

Sharing Knowledge in Cybersecurity

Understand the importance of sharing insights and knowledge within the cybersecurity community.

A man walking through an airport, asking his phone a question

Ask about this episode

Get the gist, explore an idea or ask about something said.

Claude

On Software Engineering Daily, what are the key points of this episode?

Searching your listening

Transcript

Automatic transcript. May contain errors.

0:00Are you passionate about software development and the tech industry? Software engineering daily is looking for a new podcast host host to grow its hosting team. In this role, you'll help shape the show's editorial direction and interview engineers, founders, hackers, and tech leaders. Podcasting experience is a plus, but not required. Curiosity, great communication skills, and a genuine interest in the craft of building software are what matter most. If this sounds like you, reach out at editor at softwareengineeringdaily.com. In the world of software security, there was historically a comfortable lag between the moment a vulnerability became public and the moment attackers could exploit it.

0:42This lag was often measured in months, but AI models can now read a vulnerability report and generate a working exploit almost instantly. They can scan the entire internet for exposed secrets at a scale no human team could match, and surface complex flaws that traditional tools missed for years. However, the same capabilities are just as available to defenders, and there is a case to be made that defenders hold the stronger hand. Alon Shindel is the VP of AI and threat research at Wiz, which is a cloud security platform acquired by Google in 2026. In this episode, Alon joins Gregor Vann to discuss how AI has compressed the time from disclosure to exploit, the prospects for defenders to stay ahead, how Wiz approaches scanning and remediation, the growing strain on open-source maintainers, and more.

1:36Gregor Vand is a CTO and founder, currently working at the intersection of communication, security, and AI, and is based in Singapore. His latest venture, Wintik.ai, reimagines what email can be in the AI era. For more on Gregor, find him at van.hk or on LinkedIn.

2:07hello and welcome to software engineering daily my guest today is alan schindel welcome alan hi it's great to be here thank you for having me yeah absolutely you are at whiz and this is i I think the second time we've now had someone from Wazon, which is exciting. I spoke to one of your colleagues, Rami McCarthy, probably two years ago at this point, which is crazy to think it was that long ago. But yeah, great to have you here today, Alan. And we're going to be talking all things AI, AI threats in general. So both the threats themselves that come from AI being possible now and detection that's also then possible and all these kind of things, which is super exciting.

2:48as we like to do. Just curious, how did you get into security generally? And how did you find your way to whiz the company? So for me, I think I was always curious about security. I started building websites when I was on, I think, third or fourth grade, just enjoy the creating. And I think that, I mean, ever since that, I was always fascinated by hackers and how can my website be hacked? So I think I kind of naturally was attracted to this domain. And whenever I had when it was in school or after that in the professional career, whenever I had the opportunity to choose a cybersecurity position, I went there or class.

3:30I went there. And yeah, so it's a journey that started a long time ago, more than 20 years ago. and I was really lucky to walk and meet other people in this domain and some of them are industry leaders who guided me and mentored me helped me to get to this point and one of them is actually one of the first engineers at Weez who is one of my childhood friends and we went to the same kindergarten we know each other since we were five and he joined Weez he knew the founders joined WEEZ on the first day, one of the first employees. And a few months after they started and they wanted to expand, he texted me, asked me, what am I doing now?

4:14And if I'm available to talk about a new opportunity, I said, yeah, it sounds interesting. And that's the story of how I got to WEEZ around five and a half years ago. So I'm always grateful for this opportunity. And maybe the lesson is that it's good to keep these relationships close, even when they start so early. Yeah, cybersecurity in kindergarten, that's definitely one. That's a new one. I guess that means because Wiz, I can't quite remember how old Wiz is a company, but that means you've been there like since very early on at Wiz. Yeah, Wiz now is six. Yeah, started six years ago. So it feels shorter.

4:56You know, it's been a very fast journey. And I think we saw, yeah, I mean, we feel like we saw almost everything since Log4j in 2021, when, I mean, it was one of the largest vulnerabilities that we saw. Now we are seeing the supply chain attacks, this wave of Shai Chulud and other similar GitHub worms that we are seeing. But of course, everything with AI and how AI impacts security, it kind of feels like we're starting all over again since the challenge is real there are new challenges the pace is is faster than ever so even though we are six i think it feels like we started just last year because we everything changes so fast yeah absolutely and i think yeah on that on that things change fast point that's kind of where we want to talk about things today all things ai and like how has that affected the security landscape and then sort of how should people be then thinking about their security sort of setup now that AI can be a part of that.

6:00It's something that we've touched on, especially we have an SED monthly episode. Me and one of the other hosts talk about things and we're often like kind of noodling on this idea like, okay, how has AI really changed the security landscape? But it's great to have you to actually be able to answer some of those questions properly today so yeah i mean i think just kind of opening with more of a like a stat i guess which was that in theory the the firefox team had said that they had fixed more security bugs in april 2026 than in the entire previous year and that was because of mythos the anthropic model that had been released back then it went offline for a little while but it has to our understanding come back online about six days before we recorded so if it's offline again by the time this comes out sorry to the audience but it is online as we're talking today so yeah this model mythos and there's a co-model fable which which we can always get onto as well but yeah just talk to us about that like how has like that kind of affected how we should be i guess looking at just let's just start with like landscape total like what does that mean so i think we'll get into into mythos and vulnerability research with AI, but I think it's always important to remember that there are two different perspectives, how you can use AI for security and also securing AI and how AI changes the threat landscape just by opening maybe new attack surfaces for the attackers.

7:31So whenever we talk about the impact of AI on security, we have to talk about both of these different aspects. And I think we see today, I mean, I started with that, we see that there is a new reality. And I'm saying that it's like having new rules of physics today, because everything that we knew before is changing. So for example, we see how faster you can find vulnerabilities. That's one example. We'll deep dive into that later. But mythos is only one point and it was maybe a loud wake up call for the industry. But the trend of AI models that are becoming good in vulnerability research is something that we have started seeing even last year.

8:25In December, we had in Wizz, we launched an AI vulnerability competition. We invited hackers to find vulnerabilities in software, in cloud software, AI software. Now, most of the teams that finished in the highest positions in this competition used AI to find the vulnerabilities. And we are talking about around four months, five months before Mythos was announced. and we keep seeing that the other models like opus 46 gemini open ai the gpt 55 they all show great capabilities in finding vulnerabilities and in addition to other great capabilities in just software engineering and building software so i think this is one of the things that is changing now and we're talking about the reality that hacking is democratized and it is becoming easy for everyone to find vulnerabilities.

9:22And it's even easier to do web hacking. I started by talking about how I used to build a website, how it inspired me to get into cybersecurity. I think today, if I had, when I was 10, if I had access to a model, like even, again, Opus, not even Mythos, I think it was a great tool to start scanning the internet and find just exposed data out there or lambda functions that whenever you trigger them, they just get you secrets back. And the barrier to get into cybersecurity is becoming lower and lower. You still have, I mean, I think that you still need basic skills, understanding what you are seeing, but we see that these models can help us.

10:05And in Wizz, we saw it was one of the early uses of AI for us was for what we call the red agent. It was kind of the AI automated attacker. And it was amazing to see how fast we were able to build this feature and how fast we were able to enable it to thousands of customers. I think probably one of the features that we saw the fastest adoption speed for just because they are so effective. I mean, you scan the web page, you scan the HTML file, JavaScript file, and AI is doing an amazing walk in analyzing it, thinking like a hacker and finding the exposures there. So when I say that hacking has been democratized, that's what I mean, that it's becoming easier to hack a website.

10:51And it's also becoming, I mean, the job, this walk is now scalable because you don't need, even if you had amazing, I mean, we saw hackers before, we saw APTs, NationState, they are doing great work, but it required time, effort, skills. Now, even, you know, a single person just from home can run these large operations, scan the internet, find these exposures. And I think that for us as an industry, the cybersecurity industry on the blue side, there are also great opportunities there. So everything is changing. It doesn't necessarily mean that things will be worse in the long term. Yeah, there is a great article you put out, which talks about a framework, you know, around looking for vulnerabilities and then defending against.

11:40So I'm going to sort of reference that throughout our chat today. There is something you mentioned there, zero day clock.com, which is for those that don't know, yeah, if you sort of pull that up, it's a very interesting, downward trending chart through the years of, you know, how fast it has been to basically exploit, you know, from a sort of found exploitation. and if i just look at this like 2021 was when that was seen as like wow it took one year to go from you know something has been discovered to the time it was breached and then we fast forward to 2025 and it's already dropped to one month and now in 2026 it's one week or rather sorry and it's actually we also reached in 2026 one day and they at least are projecting one hour by 2027 and even maybe one minute by 2027 like i think that really frames it super interestingly like we've just in what the space of five years gone from oh we've got a year to potentially patch this to you're lucky if you've got a day now does that kind of sound sound right to you yeah definitely i mean we see it as part of my work here i'm also i also own the response to vulnerabilities so it's not only finding them it's So responding to them and we see how in the last year, we were just busy with back to back response to new vulnerabilities.

13:01And so we see more vulnerabilities and we see that, yeah, we need to respond to them faster because you see the exploits faster. And I remember days, even if I look back, I think one of the after I joined WIS, one of the first vulnerabilities that was released, there was a critical Apache HTTP server vulnerability. And I think it took, like the vulnerability was published, I think it took like around two or three days until we saw the exploit. Now, maybe one of the recent examples is MongoBlade, the vulnerability in MongoDB. And you're able, so just from the report of the vulnerability that was public, you could have just sent it to Claude and get the full exploit back.

13:41So that's what we see. And in the AI threat readiness framework that you mentioned, we are trying to help organizations and security teams and also software engineering teams to rethink their response framework. And I think that part of that is really how do you reduce exposure? And the reason that this part, I mean, it was always important not to have exposed resources out there. But now if you have resources that are just out there and everyone can find them and hack them very fast. This is a really interesting piece because it sort of crosses into ASM, which is attack surface management, which is actually something a few moons ago, I kind of worked on products in that area.

14:31I'm really curious, what's kind of your then definition of what has changed because you can apply AI to that now? The way we apply AI in this space is by creating the AI attacker. And today we see how these capabilities of attackers and defenders converge. And we can, I mean, in Wizz, we scan your environment from the inside. So we know which resources are the important ones, where do we have sensitive data, where are the crown jewels of your organization. and we use this data to create more like smarter scans and prioritize the resources according to their sensitivity, according to their criticality to your system.

15:18And when we have these hints about what actually is on this resource, we can trigger this AI scan. We scan the page from the outside like an attacker, but we can give it some hints about what's in it. And in this way, we create a very effective scanning mechanism. We actually found thousands of vulnerabilities and critical exposures just out there. And if it wasn't us that found it, it would have been an attacker. And all this data was just out there. So we scan it, we analyze the HTML file, the JavaScript file, try to find what is exposed, whether we can find, we see that we sometimes find tokens that are maybe GitHub tokens, other tokens that are just, you know, accidentally embedded in these web pages.

16:06Everyone can read them, use them to log in to the organization system, and then just, you know, start their hacking campaign there. I mean, we see different, of course, hackers, they can try to infiltrate data they can try to maybe start a supply chain if it's a github token you can maybe add some malicious script to the product or the package that this company creates and infect the downstream customers and you know of course there are many other opportunities for attacks there but the bottom line is that we are trying to use ai leverage ai the same way that attackers will do. But the reason that I'm optimistic is that as attackers, we have more context.

16:51Context is the key for AI. In cybersecurity, context has been the key and the king. Even, you know, five years ago, I think that was the significant part of how we built to use context to prioritize. Now with AI, it's becoming even more critical because you need to, the models, they can't walk without context. And if you have better context, the results will be better. So when we as defenders, we know what we have inside our system, in our environment, we know what's important. Attackers, they can, you know, brute force, they can just spray and try to find exposures, but they don't know what's really important until they actually get in and i think that's an an area where we as defenders have the advantage and this is part of the reason that in the long term i'm optimistic because attackers i mean everyone i think that will see that we as defenders i mean let's assume we have access to the same models we can talk about whether it's going to be true or not but but let's assume that we have access to the same models the defenders have better context and this is why i believe that we can defend and have the advantage on the attackers yeah that's super interesting i hadn't maybe thought of it like that where pre pre ai okay the context is the developer who can say well like i know how this was put together and i know kind of where the skeletons lie a little bit you know and why why for example oh we had to brush this bit out and that's the one i'm not super confident on having the same degree of our security engineer wasn't able to look at that for quite as long as the as this other bit over here which got way more stakeholders looking at it basically so i think that's super interesting where that can all then be fed into you know and even like i guess like github you know histories for example where like that conversation that happened around that pull request for example where someone says okay well i guess we're going to push this out but i'm not super happy about this like that that can be brought into the defend context right Yeah, exactly.

19:24generic contractor pools. These are pre-vetted, high-quality engineers with real on-call and SLA experience. They work directly in your Slack, JIRA, and daily stand-ups in your exact U.S. time zone with zero friction. If you're ready to stop losing sprints to open recs, head over to variacode.com slash S-E-D right now and get a custom shortlist of senior candidates in 48 hours. That's V-A-R-I-A-C-O-D-E dot com slash S-E-D. Your customer lives in the real world and it's messy. Intermittent connections, mid-onboarding drop-offs, edge cases on devices you've never tested. Mobile apps reflect reality in a way no other surface does.

20:05Yet, from an engineering perspective, they're the hardest to understand. It's common for mobile engineers to see green backend dashboards, normal error rates, no crashes. but inevitably, somewhere, there's a frustrated user watching your app spin. After a few seconds, they'll lose patience, close the app, and turn their attention somewhere else. They may never come back. The worst part? Most observability tools never see any of it. BitRift, on the other hand, captures 100 % of mobile data, unsampled and in real time, so it's immediately queryable by engineers and AI agents. It's mobile observability built for the real world.

20:39Try BitRift today. bitrift.io slash signup. sponsored by deepgram the leader in voice ai so you can use voices like mine so before we kind of move on to like how ai has has then helped more on like the actual patching of all these discoveries something that maybe it's a tricky topic sometimes which is just like responsible disclosure so like you know when things are found companies there are various sort of laws in different countries around like how long you in theory have to then declare these etc but if you're finding like 3 000 in a week how do you guys look at that for us it's an important principle to comply with the different disclosure rules by you know different platforms i mean when i talk about thousands of findings so it's it's part of what you see in in the whiz product so when there is something that is i mean we believe that is say even like super critical and we see that there There might be an exposure that, I mean, our system flags is super critical.

21:43We also try to reach out either through the security email or, I mean, just to contact the company the same way that the other reports are being submitted. In other cases, when it's a customer, we can just reach out to the security team directly. And I think that there's also maybe a new problem. And when we talk about the scale of findings that for maybe open source projects or some other small maintainers, that they have a problem, that they are getting maybe dozens, hundreds of reports from different companies every week. We just saw an example last week for an open source project that disclosed the vulnerability.

22:24And they had, I think, 15 different companies or researchers who reported this issue. And the reason is that everyone scans these open source projects with AI, but it creates a problem with like triage. How do you triage issues when you have so many? We saw some other maintainers that said that they just they won't respond to reports that were AI generated reports since you also see some AI slope over there. So it's not only that. I mean, that's another problem that AI creates that you have to review more and more data. So for us, we are lucky to have a great team and enough people to actually make sure that reports go to their right place.

23:05And we have, of course, the product where most of these issues are reported and security teams, they have the processes to respond to these issues. But it's indeed, I think that's another area where the industry is changing now. And how do you report issues to maintainers? How can maintainers? And I think it is a real problem because you have some people that, I mean, with their hobby on their free time, they do something great for everyone's good. And now they have to, you know, they are being sometimes even ashamed for not responding fast enough, but they don't have the resources. You know, it's just their life.

23:41And this is why it's good to see, like you mentioned before, the Mozilla, like the Firefox project. So I think one of the important initiatives now is how can the Frontier Labs walk with or scan these critical open source projects that are the backbone of everything, of the internet, of everything we know, and how can we help them find all these vulnerabilities before the attackers do? And I know that both Google, OpenAI and Tropic, they all invest efforts there. And I think it's something that we must do now before these capabilities propagate to the red side. Yeah, definitely. And yeah, as you call out in open source, it's just a whole other role game as well.

24:29i think you know looking at how if we sort of go into a bit more of the framework keyword you mentioned in that in your article and then like actually then how to accelerate the actual patching and like the zero day response which again going back to zero day clock.com that's no more than one day now in 20 like if we hit one day in 2026 means we we might be already down to like 20 hours because the next the next marker is one hour so we're probably down below 24 hours at this point as it probably sounds you know this needs to start involving a lot more continuous automated remediation which i think was always like the holy grail right like no human in the loop and like something's just declared and and suddenly you've got like kind of an agent to go and like deal with it i think wiz does have you know you talked about the red agent which is like like AI powered sort of attacking, if you like.

25:26And then we've got the green agent, which is on the response side. So like, could you kind of describe like how does that all work, I guess? I think it's part, I mean, in order to get to full automation, it's kind of a circle where you find an exposure and you need to analyze it and remediate it automatically. Honestly, I mean, it's not easy. I don't think that anyone has, you know, the perfect solution today, And of course, I'm sure that the listeners, they're working on some systems that have been there for maybe years and they have their legacy code. It's not easy. It's important to say there's no, I don't want to make anyone feel bad because they think that there's a perfect solution and they don't apply it.

26:11So the way that we see it is first, yeah, you have to continuously scan. And maybe the first layer of scans is kind of very wider and shallow scans, like the one that I mentioned with the red agent. that you keep scanning your attack surface, trying to understand what's exposed. And when I talk about attack surface, so it's not only your web assets, you also have to scan your GitHub repos. We saw all these recent supply chain attacks, your CI-CD pipelines, scanning every resource that you have that can be potentially hacked, scan it continuously with AI, try to find these exposures before the attackers do.

26:51The next step after that is trying to understand the potential risk. And in order to solve that, you can either reduce exposure. And I think that's, again, I mentioned it before. I think that's a very important part. Reducing exposure is becoming critical today because you have, and that's what we usually see. I think in many cases, the problem is not only the vulnerability. The problem is a resource that shouldn't have been exposed or shouldn't have been public. So just trying to reduce your walk by reducing exposure, that's the first step. But if you have a resource that indeed has a vulnerability in it, a vulnerability that can be exploited, maybe you have a misconfiguration on this resource.

27:32Maybe you have a code vulnerability on your side, more on the upsec side. So, yeah, you have to start planning your remediation. This is where the green agent walk is starting, trying to understand first where this issue is coming from, finding the root cause. And that's another part that is usually overlooked because finding where is the source? I mean, just finding an exposure vulnerability out there and connecting it to the owner in your organization, connecting it to the file, to your code file that it is coming from is also difficult. It used to be something that was difficult. cloud, it's still not easy, but AI can also help with that if AI has both access to your exposure data and to your code repo.

28:17So you can do this, what we call cloud to code and find where is the source of this issue. And then you have to start and plan your remediation steps. And again, AI is not only good in hacking. It's great, of course, in building software, understanding software. And this is where we are building this agent that finds the issue and then plans the remediation or also sometimes offers different remediation plans. And another interesting progress there was that we can add some memory. So you can just add instructions to this agent. So if you prefer always patching, that's one thing. I mean, you can ask it to always prioritize patching or you can ask it to prioritize reducing exposure by changing to your telephone files.

29:03So maybe focus on everything that is not the code itself. Still very, it's not an easy thing to do. And I think there's still a walk for the industry to understand how you can do automated patching. Because after you patch, you have to test it. And part of this, I think the next step there will be how do you automatically test the new code? How do you make sure that this change doesn't have impact on other parts of your system? And this automatic workflow, you can see that there are some cases where it can work well, but there's still work to do. And part of it is sometimes even changing the architecture, your architecture, that it will be easier.

29:40So using, for example, secure images is one solution where you can help organizations kind of close this end-to-end loop faster with better architecture yeah the um as you you just touched on there these like hardened images or like hardened containers depending on what people call them but yeah we've we've had a couple of episodes on that either the drawback there i think or like the perceived drawback is just like having to as a developer having to accept some constraints on on your tool chain or like make sort of special changes to these containers like I guess that's just something that developer teams just have to accept a trade-off on if they're willing, if they're wanting to actually make their whole supply chain more secure for this purpose.

30:26Yeah, I think this changing in supply chain, I mean, another change that we are seeing now is even assessing the potential risk from different libraries and packages that are there. So if you see, and it's, I mean, something that was discussed in the past as well, where some libraries and some packages are not maintained well. And again, we don't judge the maintainers. And I think that they have a great challenger. And that's another thing that we see in our research here. So we also find we try to scan this public repo, try to scan CI, CD pipelines, and GitHub actions. And we see that there are, and we're working with these maintainers, as I mentioned, like we do it responsibly, but there are many projects that have exposures.

31:19And if this project is very popular, it is used by many organizations, it has an exposure and there is no, it doesn't have good security hygiene. It is something that is a ticking bomb. You can see this package as a ticking bomb. And I think that another part of the exposure reduction processes that we see, we're not only talking about just public resources, it's also about vetting your open source code in using more secure SBOM. And I think that's another part that when I talk about shifting left and changes in the architecture, so it's not only security images, it's also the securing the SBOM from the beginning and making better or the more secure choices.

32:04And again, it's not going to be easy. I don't think that any software developer would like to stop using a popular library, but it's another change that we're seeing. And by the way, one of the reasons that we are seeing maybe more insecure use of packages is also AI. So since, I mean, if you write your code with a coding agent, in many cases, you don't even know what's inside it. And like, you just use all these dependencies. that were added by the coding agent and you don't really know what you have inside your code. So still like this disability is important and also making the right choices.

32:41And I hope that coding agents will also understand and that will be part of what we see from them, prioritizing and the more secure architecture and more secure S-Bomb for your environment. Yeah. And like getting into, I guess, actual code analysis, you know, we haven't touched on that in detail yet but i think i think this is where things do get super interesting because there have been tools around for a long time you know effectively static analysis tools like you know are known as like sast in the industry you know that basically yeah i would like look at the code and say oh like this is a known pattern for why this is going to be a problem but my understanding is that you know now if we look at sort of what like frontier ai models can find like We're talking things like complex logic flaws.

33:28I think what's going to be described as IDOR, so insecure direct object reference, chain vulnerabilities, and then just a sort of general insecure application flows. I think especially those first two are interesting, like complex logic flaws and then IDOR, which I have no idea what it is. So I think we should get into that. Could you just talk us, what are these things that AI models are finding that was quite hard to find before? That's an area where we actually see this, great deep in capabilities of understanding code and understanding what are these, yeah, I mean, some issues that I really think that we didn't have any technology that could have, yeah, that could have found these issues before.

34:09We had, so SaaS, yeah, it's not a new acronym. It's like these products have been around for years. We also, we've built one internally in Wiz, and the goal over there is finding the vulnerabilities in code more on the upsec level, on the application level. So sometimes it can be even maybe a simple example that people know is a SQL injection, just to see if you have insecure processing of input from your users, if it can maybe lead to issue like SQL injection. And I think that the reason that it was a real scientific academic problem is how do you understand languages? And you saw that most of the companies that led the efforts there, the work was based on language crossing, even trying to understand code flows, building kind of a graph flow, you know, CFG, understanding the flow of your code.

35:03And it was just, I mean, from a technical perspective, it was something that was extremely difficult to do. Now, AI models, LLMs, they understand text well, and code is also text with structure, with rules, and all that. And we see, I think, yeah, since December, great deep in capabilities of AI models in understanding code. Well, and this is why we see that they can be easily used for coding now and also to find these type of vulnerabilities. So when we talk about finding like vulnerabilities, vulnerabilities, I mean, they are not the same. There are different classes of vulnerabilities. So you have memory vulnerabilities and that's one type of them trying to find where you have memory leaks or memory issues that you can exploit and kind of inject your code into the memory of the process.

35:54Some issues are more on the AppSec side. And even for us here in Wiz, we see them as kind of different efforts. So we have one team working on creating a great, more like, call it a very deep vulnerability engine that focuses on the memory vulnerabilities. And another engine that is more like the AI SAST that will be part of the product. And over there, it's really trying to find these vulnerabilities that are in code. SQL injection like iDore, the ones that were mentioned before, that are more about whether you can actually understand the code and kind of doing the code review that we know, but more from a security perspective.

36:35And the reason that we have a great opportunity now is that AI can actually understand the code. Still, it's not easy. I mean, you can think about systems. I think I can share some of the challenges that we have from Billnard. So you have organizations that work with many different repositories and you have to start and find, you know, all the references from these different repositories. That's one challenge because you need like AI. In the end, the LLM, it has to get the context, like the full context, understand the whole system. So if you have now and we see it, we see that we have, I mean, we see organizations with hundreds of different repos and that their projects are kind of scattered across these different environments.

37:16So you have to kind of find all the, like, find this trail and understand it. We also see other products that are just, like, very large. So you have to start kind of writing it down. And the way that we are doing it is kind of separating different tasks to different agents. So we are trying to model the process that we are doing internally to find vulnerabilities, processes that we use as humans to find vulnerabilities, the old classic manual way, and try to, for example, first find all these different things, then collect data about where we see references to this issue, then really try to hack it, then test it, validate it, having kind of a judge.

37:56Sometimes we even use different models. It's actually a nice technique that we see that different models, they have, so Claude has different advantages, Gemini has different advantages, GPT has different advantages. So we're trying to use actually different models. And when we see that a model is maybe stuck, like that doesn't find a solution, call the other model and try to do that for help. Like we have different researchers who excel in different domains. So we are trying to build all that and in the end to build a system that will be able to find these vulnerabilities. Also to make sure I think the problem is that also to reduce false positive and understand the real criticality of the issue.

38:38One of the problems that we saw with LLMs were that whenever they find something, they usually flag it as super critical. And it's not always when they say that something is critical, it's not always critical. That's part of the training issue. But we also need to assess the criticality of the vulnerability and make sure that we don't create false alerts. And maybe just one last anecdote there. we see that that even models the other like frontier models that are not mythos or fable not from this class of very large mythos in the end it's a model i mean it's it's great but it's the largest or like it's it's a very large model from if we talk about the number of parameters like complete like different order of magnitude from all the others but we see that this process of like building a good harness with these different agents that can work with each other and work on different tasks as part of this flow, you can get to great, like almost similar results to what you see with Mythos.

39:39And it's also something that is important to remember that whenever we talk about finding vulnerabilities or how good the model is in this task, it's not only about the model, it's also the harness and good harnesses and capabilities of the frontier models today that are not from the same class of mythos and fable are also great in these tasks. Yeah, and one thing just briefly on that as well is just like the reproducibility of things that have been found. Like how, you know, if, so I guess if I think more of the SaaS model, it's like, well, this thing has been found, it's very clear, like here's the steps, like recreate it, for example.

40:22i get the impression that the ai found vulnerabilities it sort of can tell you what was found and what the impact might be but actually then for someone to reproduce that i think isn't that a little bit more challenging yeah it is just i was on a call before before we started recording the podcast that was one of the issues that we discussed that part of building a good AI system today, like every AI system, is how do you create your evals, your valuations, and benchmarks to understand what you're doing well and sometimes what happens when you make a change to your system, whether you can actually reproduce the same processes that you saw before.

41:03First, I think that we have to remember that LLMs, there's, of course, some random factor there, since they are based on probabilistic processes. But our goal is to try and make them as deterministic as possible. And I think the honest answer is that we're not there yet. And we see that what we're trying to build when I talked about harnesses before is really to make sure that regardless of the probabilistic nature of the LLM, we want to make sure that it actually reproduces the, you can run it deterministically. Of course, when you are a vendor that creates products, it's hard to sell something that might give different answers.

41:42Honestly, I see more tolerance, I guess, to this randomality that is out there. I think that if you look back four years, it was something that no one accepted. And I think now people are getting used to AI systems that give you different answers. So there is maybe slightly more tolerance than what we used to see before in cybersecurity. But in the end, cybersecurity, yeah, you can have this like different results for different runs. And part of what we're doing with like our engines are trying to reproduce the issue multiple times. We have to remember that some vulnerabilities also have this probabilistic nature of memory vulnerabilities, the vulnerabilities that just, yeah, I mean, vulnerability can, you can run the exploit or just one out of 10, on average, just one out of 10 runs will succeed.

42:29So you have two different mechanisms here that are probabilistic and that makes it even harder to run. But yeah, it's part of the challenges that we have today. it's part of the walk i think also like the frontier labs they uh invest uh great efforts in in making the models more deterministic yeah and i think this is it i mean it goes outside security but just sort of keeping it within security i think the the unlock here is people are still they're more willing to accept the the less deterministic aspect on the basis that they'll still get quite a lot of things that would just never have been found if this had to be a completely deterministic system so that's what you get you get the yes it's a larger pool of things to kind of sift through but equally some of those literally have been found to be some like crazily problematic things that sass haven't picked up for many years for example so that makes sense why why sort of tolerance is is a little bit higher at especially at the moment which is super interesting as we sort of like cruise to the i guess sort of to the end of the episode i mean i really like the framing again from from your article which is like it's a very positive framing which is you know that ai is available to attackers as much as it is on the defense side but the defense side is looking better basically and yeah i mean if again if i look at the zero day clock i really encourage anyone listening to go check it out first of all just to go back on what i said around we are in 2026 apparently we are actually down to two hours on the time to exploit.

44:08So that's just the fact we're not at one yet. So that's why it hadn't been ticked off. But I look at the chart again, it's like, oh, wow, we're down to two hours. So it's not only a day, but it's down to two hours. But the other thing which is interesting is that the exploit rate, so this is like percentage of all published CVEs that are confirmed exploited in the wild versus CVE volume has actually dropped, which like kind of backs up, I think your sort of positive thesis there, right? where like actually now in 2026, it's down to like the exploit rate is down to 0.25%. And that's like, just to give some relative terms, that's down from 2.2 % in 2021.

44:48So yeah, that's really interesting. That does kind of suggest that AI being available is actually improving things. Yeah, maybe by the time the episode is over, or, you know, it will be, the export time will be shorter. But I think that we see, I mean, And maybe another fact to remember about vulnerabilities, finding a vulnerability doesn't necessarily mean that it's easy to exploit it or find the exploit. And we see that it's easy. And I think most, by the way, most of the vulnerabilities that we find with AI, we can't really exploit. And I think maybe it's something that we'll see that models can do.

45:25I mean, when we see better models, they will be able to do it better. but it doesn't necessarily mean, I mean, finding vulnerability doesn't necessarily mean that you can actually do something, like attackers can do something bad about it. So like overall, I mean, I think that my expectation is to see, yeah, like in the short term, more and more vulnerabilities that are being discovered, but most of them won't be exploitable. And I think that we'll get to a point. I mean, if we talk about this, there will be a curve at some point where I think that most of the open source software will be scanned.

45:59And as long as we don't see another huge leap of advancement on the LLM side and on the mobile side, most of the issues will be just fixed. So it means that, and by the way, same for us, like, no, I'm not just generally speaking of speaking, also for how next year will look like for security teams. I think they will have, we will have hard work, patching our systems, fixing the vulnerabilities. There will be many CVEs that we'll need to patch. But at some point, I think that we'll start seeing the number of vulnerabilities that are being partially decreasing just because, I mean, because we will find most of these issues.

46:41And we'll also make the changes to our architecture in order to reduce the likelihood of exploitation. So it's a part of the changes that we're seeing now. The, I think some people call the vulnerability apocalypse. There are other names they give this year, but in my opinion, if you're looking a year or two from now, after we are past that, and I think that it's also something that is in our hands. I mean, if we do great work now as a community and we work together to fix these issues and try to find them before the attackers do we can make our life easier and in the long term create a more secure world where you have fast attackers but also faster defenders yeah absolutely well yeah i think you you definitely sort of opened my eyes a bit just to like the the why's here of like why actually having ai and being on the defense side why we're actually in a good position which is great because i think a lot of the news out there like it's very doomsday you know oh this is going to be yeah as you say like volun apocalypse so yeah no i think it's that's been super helpful and all this kind of tips that you've given listeners today in terms of how to use ai to like secure your applications and super helpful so i would obviously recommend people go to as wiz.io slash blog there's articles there anywhere else that people can find you or anything like that yeah so on on linkedin just search my name on twitter just again with the same same name i'm there and yeah we're trying i think as part maybe something more uh like on personal load is that i'm i'm trying i think that we have great responsibility i think that there's something very unique about cyber security where creating content is is something or sharing your your thoughts, something that can have great influence on others.

48:37And that was one of my missions in WEEZ on like for my group to encourage, you know, everyone in my team and to support them in creating, writing blog posts or writing and sometimes even just infographics, trying to share what we are saying. We have the privilege to work with great security teams from all over the world, learn and I shared some of our insights today and yeah like this this distribution channel whether it's LinkedIn x and of course podcast is the way for us to share our thoughts and we're trying to keep so we are going to publish another blog post soon on AI and finding vulnerabilities with AI and we keep sharing our thoughts there amazing well again thank you Alan for coming on today great to great to hear all these things learned a lot yeah and we'll be following along picking up these new discoveries on all the places you just you just mentioned so thank you so much for coming on thank you so much for having me

49:55Thank you.

From the publisher

In the world of software security, there was historically a comfortable lag between the moment a vulnerability became public and the moment attackers could exploit it. This lag was often measured in months, but AI models can now read a vulnerability report and generate a working exploit almost instantly. They can scan the entire internet for exposed secrets at a scale no human team could match, and surface complex flaws that traditional tools missed for years. However, the same capabilities are just as available to defenders, and there is a case to be made that defenders hold the stronger hand.

Alon Schindel is the VP of AI and Threat Research at Wiz, which is a cloud security platform acquired by Google in 2026. In this episode, Alon joins Gregor Vand to discuss how AI has compressed the time from disclosure to exploit, the prospects for defenders to stay ahead, how Wiz approaches scanning and remediation, the growing strain on open source maintainers, and more.

Sponsorship inquiries:
[email protected]

The post Security in the Age of Instant Exploits appeared first on Software Engineering Daily.

More from Software Engineering Daily

All episodes