47 minSeason 4, episode 8

The Mythos Problem: When AI Finds Every Vulnerability

With Chris Romeo, Izar Tarandach, and Matt Coles

Security testing & vulnerability management

In this episode, we break down the “AI Vulnerability Storm” and what happens when AI can find—and exploit—vulnerabilities faster than humans can fix them.

Part of: AI security incidents, explained

Part of: AI in security testing and bug bounty

Episode title image: The Mythos Problem: When AI Finds Every Vulnerability

Listen to the conversation

About this episode

In this episode, we break down the “AI Vulnerability Storm” and what happens when AI can find—and exploit—vulnerabilities faster than humans can fix them.

We explore how compressed OODA loops are shifting the balance toward attackers, why traditional scoring like CVSS may start to break down, and whether “just patch faster” is even realistic anymore. The team also questions the push toward AI agents everywhere—and whether fighting AI with more AI actually solves the problem.

At the end of the day, it comes back to fundamentals: reduce your attack surface, simplify your systems, and focus on what actually matters.


🚀 Join the Conversation
Is this a real shift in security—or just faster chaos?


Follow AI Security Table:

➜ Home: https://securitytable.ai/

➜ X: https://x.com/AISecurityTable

➜ LinkedIn: https://www.linkedin.com/company/ai-security-table/

➜ YouTube: https://www.youtube.com/@AISecurityTable

Transcript · 47 min conversation

0:10Izar Tarandach Just had to look at the microphone.

0:12Matt Coles Just look at it and go, ah!

0:15Chris Romeo Hey folks, welcome to the Security Table where Isar is looking at his microphone, which I don't think makes it work any better, but it's a place to start. It's a new day. A new day.

0:27Matt Coles My, my girlfriend is here. I have, I should be looking here. That's called a, that's called a monocle.

0:34Chris Romeo And you could, you could totally rock the monocle if you went for it.

0:38Matt Coles I can't take my glasses off cuz otherwise I poke myself in the eye with my monocle.

0:42Chris Romeo Well, we, we are a safety-first organization here, so please do not take out an eye with a monocle. All right. Well, the topic of the day, the day is a paper that's just been released that is encapsulating a pretty big issue that's going to impact cybersecurity for pretty much ever from this point forward. And the name of the paper is The AI Vulnerability Storm: Building a Mythos-Ready Security Program. And so between Mythos and Glass— Project Glasswing— Mythos being this new Anthropic model, which is good at finding vulnerabilities, it's a little bit too good at finding vulnerabilities in systems and creating exploits. And then Project Glasswing is the collaborative collective of various organizations coming together to share information under this heading of AI-generated exploits. So that's kind of the setup, I guess, of what I understand about Mythos and Glasswing. What's, uh, what, what is this paper trying to do? Like, what's their goal? Anybody able to figure that out?

2:06Izar Tarandach I think that the first big goal here is that they are setting up the next war between G for GIF. Is it mitos, mitos? What, what, what, how did, what?

2:19Matt Coles It's mythical.

2:20Izar Tarandach It's mythical.

2:21Matt Coles Remember the mythical man month?

2:24Izar Tarandach Yep.

2:24Matt Coles Now this is the mythical LLM day.

2:27Izar Tarandach So is it mitos, mitos?

2:33Chris Romeo Somebody answer that.

2:33Matt Coles Are you Greek or are you?

2:36Izar Tarandach Oh, that's a very good point.

2:41Matt Coles Uh, you could ask, uh, you could ask, um, Gemini or something to, uh, to pronounce it for you.

2:46Izar Tarandach It's just going to laugh at my accent.

2:49Matt Coles I know it.

2:49Chris Romeo I know it.

2:50Izar Tarandach That, that, that they're getting too smart, but actually the, the, the mythos here. Okay. I'm going to go with mythos. So the mythos here, just to keep on the Greek, uh, theme, is setting up the next, uh, Sisyphus effort. If, uh, people are not familiar with my accent or with Sisyphus, it's that guy that is condemned to roll the big rock up the mountain just to see it fall on the other side, and then he has to start again and again and again.

3:20Matt Coles Is it better to be Sisyphus or Daedalus?

3:24Chris Romeo Oh, wow.

3:26Izar Tarandach Or Prometheus, the guy with the eagle pecking on the liver. Yeah, that's—

3:31Matt Coles Lots of doom and gloom in the Greek mythology.

3:32Izar Tarandach It's like, man, the Greek had a lot of time in their hands. Whoa.

3:38Matt Coles All they did was sit around and like philosophize, right?

3:41Izar Tarandach Right.

3:41Matt Coles Philosophize. I can't say that.

3:43Chris Romeo Wow.

3:44Matt Coles I'm sure they had linguists too, but.

3:46Chris Romeo You got it right the first time.

3:48Matt Coles I did?

3:48Izar Tarandach Philosophize? Yeah. Yeah.

3:50Chris Romeo Philosophize on something.

3:51Matt Coles Wow.

3:52Izar Tarandach Actually, I could sign up for that job.

3:55Matt Coles You'd have to wear a toga.

3:57Izar Tarandach Just sit down. Oh, I can rock a toga. But just sit down and philosophize. Sounds good. Okay, let's philosophize a bit here. So, uh, full disclaimer, is our critique. Yeah. I, I, I, I have read up just to the, uh, executive summary and that they were very nice to, to give us a, a point by point, blow by blow.

4:23Matt Coles Playing. Well, we should say this is a, this is a paper in draft form.

4:26Izar Tarandach Oh yeah.

4:27Matt Coles Provided under common something, uh, Non-commercial, common, CC, whatever.

4:33Izar Tarandach Uh, oh, come on.

4:35Matt Coles By CISA, or by, sorry, by, by, not by CISA, by the former director of CISA.

4:41Chris Romeo Cloud Security Alliance. Cloud Security Alliance.

4:43Izar Tarandach CSA, CSA.

4:44Chris Romeo Collective plus genaisecondurityproject.osp.

4:47Izar Tarandach Yeah, I always got this confusion between CSA and CISA. And what a community it is! Because we got names like, uh, Jan Esterly, our beloved Bruce Schneier, Phil Venables. Who else I recognize here?

5:04Matt Coles Katie Maceris.

5:07Izar Tarandach Katie.

5:07Matt Coles Katie. Thank you.

5:11Izar Tarandach Who else? Rob Joyce, of course. And Gadi Evron, who's been doing a huge job with AI lately, AI security lately. And Yeah, I'm sorry, but I'm bad at names.

5:26Matt Coles Rob Van Den Veer is on here.

5:28Izar Tarandach Oh yeah, yeah, yeah, yeah, definitely. But, um, and the whole, the whole team over there in SANS, right?

5:34Matt Coles Ed Skoudis and others.

5:37Izar Tarandach Yeah, but just, I was telling you, you guys before, just like starting to scroll through the pages, I get to the authors and contributing authors one, and I'm like, whoa, okay, I can't say a single word against this thing because Nope. Like this, this huge brain trust right here on page 2 probably didn't leave anything to be, uh, to be, uh, questioned. So let's close shop and go home. Yeah.

6:07Chris Romeo There's always a time to question. Uh, yeah. I mean, I kind of read it, I, I guess I interpret it a little bit differently in that this is likely the existential problem of the intersection of cybersecurity and AI for the next 5 years. So it is getting a lot of attention. It's getting a, a lot of people are thinking about it because we've reached the point where AI can break stuff at a 100x time faster speed than humans can, maybe even more than 100x.

6:44Izar Tarandach Mm-hmm. So I'm going to agree with that, but with a slight aside. In the past few years, which as we know in AI technology terms are decades, we have seen many times something hyped up, something declared. And then when we got to look under the hood, it was all of a sudden, ah, it was in these conditions, but not those conditions. And the wind was going in the right direction. The moon was in the right place. Apart from a very select number of people, nobody has actually seen these results and measured and tried and reproduced results and, and things like that.

7:28Matt Coles Well, and, and just, and just to highlight it on page 10, it does actually talk about the Mythos experience. Internal testing at Anthropic showed Mythos generated 181 working exploits on against Firefox. Whereas Claude Opus 4.6 only had 2 under the same, same conditions.

7:52Izar Tarandach So, what was the opening? What was the opening of that sentence?

7:56Matt Coles 100, uh, Mythos generated 181 working exploits.

8:00Izar Tarandach No, no, no, the opening, the opening before that.

8:02Matt Coles Internal testing at Anthropic.

8:03Izar Tarandach Uh-huh, by whom? At Anthropic. Who produces both models?

8:08Matt Coles Anthropic.

8:09Izar Tarandach Who are we paying when we use both models?

8:13Matt Coles What are you getting at here, sir?

8:15Izar Tarandach I'm going to need something a bit more independent before I run away with this.

8:19Matt Coles Sure. I'll keep looking, but so far, 181 working exploits against a web browser. So you're talking about JavaScript engine and an HTML processor.

8:36Izar Tarandach Oh yeah, sure.

8:37Chris Romeo And if you go to the timeline, Isar, I mean, there is more data to back up, uh, page 12, uh, um, February 5th, 2026, Anthropic using Claude Opus 4.6 reported 500+ high severity vulnerabilities in open source software.

8:54Izar Tarandach Look, I'm not saying that this is bullshit. I'm just saying that there have been instances in the past.

8:59Chris Romeo Sure.

9:00Izar Tarandach Things got propped up to a certain level only then to fall down from a cliff when people look—

9:06Chris Romeo Yeah, but I mean, I think we can all, we can all admit the fact that even if this isn't it, it is coming. It is coming though. It's like, it's, it's, even if this isn't all that they're saying it is, the technology is moving in this direction and within 1 to 2 years, this will be a reality. Where this model will no longer be in preview only? People, company, you know, nation states, other organizations are going to have access to this, and this is going to change the game on the— it's going to drive software security to be resolved, or people are going to go out of business?

9:44Izar Tarandach As it is well known by now, I am not a fighter pilot, but I play one on the internet. So The thing is, for years and years and years and forever, people have been looking at that thing called the OODA loop, the Observe, Orient, Decide, Act loop in cybersecurity. And the way that it connects to my joystick is that it came from like from the military, from, from fighter pilots in saying that in a, in a, in a dogfight, The, the pilot with the, the smallest OODA loop, the, the pilot that's capable to observe, orient, decide, and act in the shortest amount of time, is the one that wins the fight because they can react and predict and act much, much, uh, faster than, than their opponents. And we have been seeing the same argument applied to cybersecurity for many, many, many years. And to me, what, what this whole thing now with AI means is that the, the OODA loops are getting, sorry, extremely compressed. Where things get different, and, and I think that this paper brings that up, uh, very well, is the first three phases, the observe, orient, uh, decide, those three, they, they they scale together, both the attacker and the defender. Using AI, they can make those things go faster. Where things get bogged for me is the act. Because for the attacker, acting is releasing the attack, pointing it, firing it, and out it goes. For the defender, the act is patch those things before the attack comes in.

11:34Matt Coles And again— But you're assuming they patch, you're assuming the patch exists. Yes, that you're assuming the patch works. And you're assuming that there isn't a bypass.

11:43Izar Tarandach Exactly. Thank you. Which are all amplifiers of that timescale for the defender, right? So I was very surprised when I saw in the page.

11:55Matt Coles Oh, I know, by the way, you hope the patch doesn't break something else. Who? Because you have that too.

12:00Izar Tarandach And you hope that the IT people who are not the security people who actually say, yeah, okay, we're going to put patch in place. Don't have their own processes that take woodles of time on top of that.

12:11Matt Coles Woodles of time for the OODA?

12:12Izar Tarandach Woodles. Woodles for the OODA.

12:13Chris Romeo A lot of OODA this morning.

12:16Matt Coles A lot of OODA.

12:18Izar Tarandach Yeah. Turn it into fun. Okay. So the, the, the thing is, uh, so the paper says that what to do now to deal with the current risk spike, or that is what to do now to, to, to, to deal with the, attack a root loop being so compressed, adjust risk calculations and reorient security program resources for increasing volume of patches, decreasing time to patch, and more persistent complex attacks. Nobody thought of this before, I guess, right?

12:51Chris Romeo It's news.

12:51Izar Tarandach It's okay. What do I do now? It's Monday morning. What do I do now?

12:56Matt Coles You panic first, ask questions later.

13:00Chris Romeo Where's my towel?

13:02Izar Tarandach Where's my towel?

13:04Matt Coles Forget that keep calm and patch on thing. You gotta panic first.

13:11Izar Tarandach Focus on the basics and harden your environment further. Here I'm going to open a parenthesis. Lately I've been hearing this a lot from my boss, Uri Friedman, with the security brutalism thing that I already told you guys about. Going back to the basics is the only thing that you can do, right? I mean, reduce your attack surface and then you don't have to patch anything.

13:33Matt Coles So how far back? So let's be careful about— let's be cognizant of this. How far back? I'm thinking, are we back into the perimeter? There's a perimeter and network segmentation as opposed to everything is open all the time.

13:47Izar Tarandach Well, get the perimeter reduction, put it together, zero trust, and every single thing becomes its own perimeter.

13:54Matt Coles That's the theory, but that's why you have to patch everything because everything is its own premise. As opposed to network segmentation where you literally wall off parts of your network.

14:03Izar Tarandach Exactly. But that's the thing. Network segmentation also depends on the implementation of a TCP/IP stack, which could have its own bugs. So you could be trusting a segmentation that actually doesn't exist. But the moment you start looking at it as a simplification of everything, And instead of just patching everything, you start taking a more critical look at saying, do I really need this thing?

14:29Matt Coles Protection first.

14:29Chris Romeo Everything.

14:30Izar Tarandach Yeah. Is everything that's in my attack surface, is it just fluff or does it have a practical purpose? And that's something that we don't like to do.

14:41Matt Coles But that's what we do during threat modeling to some extent.

14:44Izar Tarandach That's what we do during threat modeling because threat modeling is the answer to everything. Right? So I could call threat modeling 4G too, and it would sound the same. That's 2 Hitchhiker's Guide to the Galaxy references in less than 5 minutes. I want a bonus.

15:03Matt Coles Sure, we'll give you that $0 bonus on top of the $0 we pay you.

15:06Izar Tarandach Thank you. So my point, and actually Uri's point. Is that before you do all the, the acting panic runaround, just reduce the frigging, the frigging attack surface. Chances are you don't need everything that you need. Look at the plumbing, make the plumbing simpler before, before you go make it shinier.

15:30Chris Romeo Right.

15:31Matt Coles And before you think of, before, and, and just to extend that, I guess a little bit, if you think that that thing is, that thing, that one of those targets is useless, it's always useful to an attacker. 'Cause exactly because pivoting and, and, and, uh, you know, APTs exist.

15:46Chris Romeo And that's one of the things this paper is highlighting is that, uh, Mythos is, is chaining together vulnerabilities, right? So it's not just finding critical zero-day style exploits. It's doing a lot of vulnerability chaining to get these results. Right.

16:03Matt Coles And so those relatively low severity, relatively low severity vulnerabilities that had very little You know, impact as a result, you know, malware authors aren't using them to necessarily, you know, do ransomware attacks. Mythos is able to chain those together to gain a foothold or to gain little bits of information about memory or whatever. Right.

16:26Izar Tarandach So basically what you guys are pointing at right now in my head is that we used to, to use things like CVSS to say that something was a medium problem. Because the complexity was high. And MITRE can just be able to reduce that complexity so that what was medium yesterday becomes high and critical today.

16:46Matt Coles There's a, there's a metric in CPSS4 though, which is not just the complexity of the exploit, which would be something that Mythos can reduce, but, but conditions on the attack, which Mythos can't control.

17:01Izar Tarandach True, but Those are mostly fixed because a given piece of software has a given way of being installed.

17:09Matt Coles Agreed. And it, but it's variable by install. In other words, it's, it's fixed based on, uh, there's, there's a, there's a cap to that because of the way the software or, or system, not just software, right? May be utilized or, or may have been, you know, developed and recommended to be installed. But then as each sys, as each company and their organization, then they create the specific deployment that may be variable across deployments.

17:34Chris Romeo So does CVSS even matter in this new world of mythos-generated vulnerabilities?

17:41Matt Coles That's an interesting question.

17:42Izar Tarandach I think it matters. That's an interesting question. In my opinion, it just means that the scale now is going to slide, but I'm very curious to see where Matt was going.

17:54Matt Coles So, uh, I guess on the one hand, it's still, I think, valuable in terms of understanding how bad a vulnerability could be. Um, because there's more metric, there's more, more than just simply exploitability in that metric. Uh, so there is, there is that, I guess, but if everything is, if everything's critical, nothing is critical.

18:18Izar Tarandach Yes.

18:19Matt Coles But Mythos doesn't make a vulnerability critical. Mythos makes a vulnerability easy. Uh, and so it doesn't rate, it doesn't change its severity. It reduces some of the factors and it reduces some of the factors involved in determining that severity, at least under CVSS. Um, but it does, it doesn't change, it doesn't change everything about the, about the vulnerability. So I think the vulnerability calculation is still useful. I might ask an alternative question. What's the value of EPSS? Exploitability Prediction Score.

18:54Chris Romeo Hmm.

18:55Izar Tarandach True.

18:56Matt Coles If everything is exploitable, it's always 1.

18:59Chris Romeo Yeah. So it's not, so it just doesn't matter anymore if AI can determine. Go ahead.

19:07Izar Tarandach One, one observation on top of that is that we are assuming that everybody has access to something like Mitos, right? Which is probably not going to be true.

19:18Matt Coles Well, it's interesting. I'm looking at the table on page, uh, starting on page 17, a Mythos-Ready Security Program Risk Register. And number 1 is accelerated threat exploitation. AI models have discovered, have been discovering vulnerabilities for over a year. Mythos accelerates it, but the capability predates it.

19:36Izar Tarandach Yes.

19:36Matt Coles So that means if it's not Mythos, it's something else.

19:40Chris Romeo Yes, but, and it's going to get rolled into the, it's going to get rolled into the core models. It's just a matter of time.

19:47Izar Tarandach I, I don't know. The, the moment that this amount of, uh, red lights start showing up, people go up and say, okay, this is a nuclear weapon level thing. We need to control it. And sure, there will be escapes. There will be other people reproducing parts of it and this and that and the other one. And there'll be some kid buying plutonium on eBay and building their own reactor and whatever. But at the end of the day, if somebody decides that, uh, they need a very good reason to regulate access to something like this, this is it. This is basically a bunch of people very, very, very high in the industry saying, uh, we need controls over this because otherwise it's going to be hell.

20:26Matt Coles Yeah.

20:26Chris Romeo But we have, they never actually said that in the paper though. We have governments putting words in their mouth.

20:30Matt Coles We have governments which are actively funding this type of research, right? So it's, it's not gonna, it's, this is a commercial enterprise, right? Mythos is a commercial company. They have profit and loss margins to worry about.

20:40Chris Romeo Well, Anthropic is a commercial company.

20:42Matt Coles They just got blacklisted by the government, by the US government, right?

20:45Izar Tarandach But to, to, to Chris's point, yes, I'm putting, uh, uh, words in their mouths. That's true. But what I'm interpreting here is a lot of, uh, uh, people that we have learned to really listen to because they have had repeated successes in the things that they have predicted are now predicting something that we as an industry have always put forward as one of the big blockers, which is the time to patch. And they're saying, hey, the only way that you can solve this thing is by raising this, this other thing that you always said that it's very difficult.

21:20Chris Romeo Yeah.

21:20Matt Coles Now it does say—

21:21Izar Tarandach in other words, there's no— in other words, there is no solution.

21:24Matt Coles Yeah. It does say non-frontier open weight models can already achieve much of this at an accessible cost. Right. Frontier models are acceleration, not the starting gun.

21:38Izar Tarandach Exactly.

21:38Matt Coles And each patch also becomes an exploit blueprint. So this is something we've known for a long time, that when patches come out, they get reverse engineered and the attackers know what's being patched. Because you can't hide it, right? I mean, you really can't, you can't really obfuscate a patch well enough unless, unless you encrypt every patch. And it's perfect encryption. And only the systems that can apply the patch can decrypt it. If, a bunch of ifs, right? So patches contain exploits. Patches contain information that exploit writers can use. And we know that LLMs are great at decompiling.

22:24Izar Tarandach Now, another interesting thing in here for me, it's, I just got to the table with the priority actions. The priority actions, the defensive ones themselves, are extremely dependent on LLMs, right? They're saying, turn agents and LLM capabilities inward on your own code and dependencies. That there is a big assumption in here that the solutions that we have had up to now, for example, reading code, are just not enough anymore. You need to have an LLM-based one.

22:55Matt Coles Well, that's number 2, require AI agent adoption.

22:59Izar Tarandach But, but, but that's on the writing. That's on the writing new code. The first one that they say is take an LLM-based scanner, turn it into your code right now. Basically, in, in, in my head, what it means is you can only fight fire with fire. So if the problem is an attack, you have to have a defense, defensive LLM.

23:21Chris Romeo If, if, if, why, why is AI generating 500, uh, let's just assume that it is in, in fact able to generate 500 critical, proven, remotely exploitable vulnerabilities against your product. How, I mean, it would take humans a year to fix that, to patch that.

23:41Izar Tarandach So their solution is turn your LLM scanners now into your code. A, as if people haven't been doing this already. B, as if we don't have the non-LLM scanners working already. And C, as if magically right now these scanners that didn't find something before are going to start finding things just because Mythos. They are still the same models. They are still the same things.

24:05Matt Coles It's calling out non-Mythos, uh, uh, LLMs here, agents, right?

24:09Chris Romeo Right.

24:10Matt Coles So, and including some open source ones, which is, which is good actually to see.

24:13Izar Tarandach Correct. It, it, it's awesome. It's awesome. Right. But to say that this is a critical thing to do this week, because otherwise, huh? I, I, I, I, I'm, I'm, I'm failing to see here how the, the proposed solution is any better than just keep doing what you should already be doing anyway.

24:35Chris Romeo Okay. So you're saying your argument is that people should be, are, have already been doing this before this paper was ever written, or they already are doing it in reality.

24:43Izar Tarandach No, my argument is, I think, two-headed. A, that this is not something that people should start doing because they should already be doing it. But B, more important, just because a more capable model came up with a bunch of findings doesn't mean that less capable models that existed before all of a sudden have more weight to what they could find or not. So if you, in other words, if you were doing this thing before, using the same models, you're not going to start automagically finding things this week because Mithras found things last week. In other words, this is just something that sounds good, but it's not immediately going to give you any, any added value.

25:34Matt Coles If you weren't, if you weren't already doing it, it gives you a ton of value. If you were already doing it, you're not gaining anything by doing it. You're not going to gain anything by doing it more.

25:44Izar Tarandach Right.

25:44Matt Coles By continuing to do it, I should say. Right.

25:46Izar Tarandach And if you were not doing it before with either an LLM-based or non-LLM-based scanner, then seriously, what are you doing?

25:54Matt Coles I mean, the theory, I mean, the theory goes here that the LLM scanner is better than the commercial SaaS tool.

26:03Izar Tarandach Have we seen numbers saying that they are?

26:05Matt Coles I don't know.

26:06Izar Tarandach I'm genuinely asking.

26:09Matt Coles I don't know. It's a good question.

26:10Chris Romeo Yeah. I don't know either.

26:12Matt Coles I mean, if you had a, if you had a, like if you had a Coverity or Fortify from ages back, right? I mean, that those were, those were high performance, you know, uh, very noisy, but high performance static analysis tools, right? They looked at call stacks and, you know, variable flow and the whole works, right? Is LLMs better? They're reading the code directly, whereas those SAS tools were looking at compiler output. Now, granted, we're talking about compiled languages versus interpreted languages. Maybe the language pipelines are better or worse. I think the SAS tool capabilities have changed over time. And of course, now we also have, you know, a plethora of supply chain attacks or, you know, dependency problems, which maybe LLMs are better at making those connections than the tools themselves.

27:15Izar Tarandach That's the thing, the making the connections. You touched exactly at it. I would say that nowadays, if you're not using both approaches at the same time, And the specific reason why I say both is that, first of all, before the whole LLM thing came true, we already knew that we were having very, very good non-LLM scanners in terms of building all the AST, understanding the language, understanding how things are written and not, understanding the artifacts that even interpreters and compilers could put into the final code that gets deployed. But the most important thing that they give us is determinism. They do go through all the paths. They do go all the good ones, at least.

27:58Matt Coles Yeah.

27:58Izar Tarandach They visit all the, the branches in the tree.

28:01Matt Coles When given enough resources, they do.

28:03Chris Romeo Exactly.

28:03Izar Tarandach Yeah, exactly. It's resources and time. But, well, time's a resource. But, uh, uh, once you have that shopping list, giving it to an LLM to check one by one, that's a different use case than just typing on your agent. "Find some vulnerabilities in my code." Is it that simple?

28:22Matt Coles Really? Can I do that right now?

28:24Izar Tarandach A, you can. B, yes, some people do that. C, no, that's not the right way of doing it. But the important thing here is that once those things come together and become one pipeline, they are much stronger than working apart, right? So again, we go back to the AI-infused thing. Not AI-powered thing. You have to have AI helping your other tools, helping your other methodologies, and not always, in some cases, yes, but not always substituting them altogether. So Captain Obvious, la la la la la here, but things evolve. They don't always, uh, uh, surpass each other and, and don't always take one input, take one output, one in, is the best move here.

29:18Matt Coles Okay, so I'm looking at this list of priority actions. And something, something is troubling. Point your agents at your code. Number one, require AI agent use across your, your, across your organization. Establish governance and defend your agents. So go ahead and deploy this technology that has, that which they say specifically has poor defenses in effect, right? Without agents, most tasks will be untenable, but they must be defended. Agents are not covered by existing controls and introduce both cyber defense and agentic supply risk. So make these things ubiquitous in your organization. Prepare to be attacked.

30:17Chris Romeo Yeah.

30:18Matt Coles Not, listen, not build your infrastructure and defenses first, then deploy.

30:23Chris Romeo Well, this is the AI age, Matt. Nobody has time for that.

30:28Matt Coles Boy, it's like, it's not like we have to patch or anything.

30:35Izar Tarandach Yeah. At the end of the day, I, I think that nobody is going to go into a, uh, what's the name of those processes? The, um, digitalization, uh, uh, jump or whatever. Whenever, whenever everybody goes to the cloud and those massive lifts and all that.

30:51Matt Coles Oh, digital transformation.

30:52Izar Tarandach Nobody's going to, yeah, no, nobody's going to go like the other way around and say, um, oh no.

30:57Chris Romeo I'm still holding off on the cloud. Don't trust it.

31:01Matt Coles I heard rumors you might be better secured than everyone else.

31:06Chris Romeo Uh, so just to close the loop on this list, like, I mean, I think this list of priority actions is fine. I mean, nobody ever takes a document like this and says, well, I better get to work. Team, you'd be surprised. Point agents at your code and pipelines.

31:22Matt Coles Nope.

31:22Chris Romeo And then we have to require AI. Like, people don't—

31:24Matt Coles this is an action list for CISOs. That this is, that's what, because it's because of the names and because of Mythos and people are just gonna do this blindly. I, I have, I'm, I will predict that many companies will implement these almost verbatim.

31:45Izar Tarandach And I'm going to predict on top of Matt's prediction, two things. First of all, next week we're going to see some kind of standard that verbatim goes through the steps and says, this is the new reality.

31:57Matt Coles A, NIST 800-53 Rev 6, the LLM version.

32:02Chris Romeo No, it would take them at least 5 years to write that. Come on.

32:06Izar Tarandach And, and, and B, I want to say, I, I wanted to, to, to go back to something that Matt said before the microphone went on. If anybody wants to try to implement this as is in this table, Cybersecurity industry as a whole is saved, right? Because they will need so much, so much, so many, so many people. Thanks. Cause it's countable now. Yeah. So many people to implement this thing that everybody, anybody that's sitting down in front of a computer nowadays and saying AI is going to take my job, those people are going to have new jobs real, real, real fast.

32:49Chris Romeo Framework installers.

32:51Izar Tarandach Yeah, you're going to need so much work.

32:56Matt Coles You need humans to make the decision. So number 7 is our earlier point about inventory and inventory and reduce attack surface.

33:06Izar Tarandach Yep.

33:06Matt Coles In order to do reduction, you have to make a decision. And unless you, well, I guess until the agents are good at automatic targeting of systems, then, and understanding value of those targets, then you need a human in the loop. And you need a human, you need a human or humans in the loop who can understand the environments and what the attack surface represents and the value of those systems as well as the value to the attacker. The AI can assist, but the human, I think, will probably be necessary.

33:42Chris Romeo At least in the short term.

33:43Izar Tarandach Because if your AI can do all this stuff by itself, you have different problems.

33:48Matt Coles But, well, yeah, I mean, a big, a big, uh, power bill, probably, and token bill.

33:54Izar Tarandach That too. But it's fun that Matt pointed at the, at the item 7, and I went to the big text in there and immediately something like jumped up.

34:04Matt Coles As fun.

34:04Izar Tarandach Right in the middle of the page.

34:06Chris Romeo As fun.

34:06Matt Coles As fun jump. That's where my eyes went to.

34:09Izar Tarandach And I was going, wait, wait, wait, S-bombs. And I read the whole sentence, generate real S-bomb.

34:15Matt Coles This is on real S-bombs.

34:17Izar Tarandach No, no, no, no, no. And then I went to next sentence because I was hoping that it was going to tell me what to do with the real S-bomb that I just generated. It doesn't.

34:26Matt Coles No. In fact, it's back, fast backwards. You should be aggressively shutting down things, then generate your S-bomb.

34:31Izar Tarandach And then do the S-bomb.

34:33Matt Coles But, you know, it is, it is open for public comment. We should. Submit that comment.

34:37Chris Romeo Just put it out there. Okay, so here's the ultimate scary question.

34:43Matt Coles Oh, isolate. Sorry, isolate or air gap at risk systems. It is talking about network defense.

34:49Chris Romeo We're going to air gap. We're going to air gap. In the modern internet, we're going to air gap.

34:52Matt Coles We're going to go for enclaves again. Enclaves are coming back, baby.

34:55Izar Tarandach Oh, remember the enclave?

34:57Matt Coles Remember the enclaves?

34:58Izar Tarandach Remember how the enclave got popped?

35:00Matt Coles Remember all the Tempest research and how you could break enclaves? Yeah.

35:05Chris Romeo True. That's getting really nerdy though.

35:07Matt Coles Yes, it is.

35:08Chris Romeo When you, we start getting into that level. So here's the question for you, philosophical, so that you can philosophize, to use a word that we shared earlier.

35:17Matt Coles If you can spell it, that'd be awesome. But I can't, I can't, I can't say, but I can't say mythos.

35:23Chris Romeo It's mythos. Mythos.

35:24Matt Coles Mythos.

35:26Chris Romeo Mythos. Mythos. Can't, do we reach a world where all the critical vulnerabilities are found for a product and mitigated. So there are no longer— so you have a product and it no longer has critical vulns.

35:43Matt Coles No. It depends why some vulnerabilities are unpatchable.

35:52Izar Tarandach Yes.

35:53Matt Coles At some point you will run out of the technical vulnerabilities, right? You'll run out of the buffer overflows.

35:59Izar Tarandach Okay.

35:59Matt Coles And you'll still be left with business logic flaws that you probably cannot patch.

36:06Chris Romeo Why wouldn't you be able to patch a business logic flaw?

36:08Matt Coles Because it's human-generated, human-informed, uh, in other words, in order to make the system useful for a target audience, there are almost certainly going to be flaws that you cannot patch.

36:22Izar Tarandach True.

36:23Matt Coles Authentication issues, authorization issues. Privacy problems. You're not going to necessarily be able to patch all of these.

36:31Izar Tarandach On top of that, you're assuming that every patch works 100% and doesn't bring problems with itself. And we have seen again and again and again that the patches work.

36:39Chris Romeo That's why you have AI quality assurance.

36:44Matt Coles If that patch breaks major functionality, like, hey, here's how I patch this. I turn off this API. You're not gonna do that.

36:55Izar Tarandach No, but, but that's saying that the only way to patch is to remove functionality, right? So it's taking the worst case that you, you pointed out, right? Yeah.

37:03Matt Coles At some point you'll run into patches that require significant modification to the, you know, of the system.

37:10Chris Romeo At the end, there's the way AI writes code. It, it operates a whole lot faster than human beings do, so it can just rewrite Uh-huh.

37:19Matt Coles And if one system— And open new attack surfaces as a result.

37:23Izar Tarandach But you're assuming that every system lives in a vacuum. Systems talk to systems. If both systems don't go up at the same time, then one system could hold up the patch of the first one and say, well, if I want this functionality, I can't patch because otherwise I can't talk to the other system.

37:42Matt Coles This is the problem of containers, right? When you spin up and down containers, If one comes up on a different rev, you've broken your infrastructure.

37:51Izar Tarandach It's the whole dependencies, not dependability, dependencies thing, right? Things have to move forward at the same pace that they maintain compatibility with each other.

38:03Matt Coles And the big trend right now is pinning your dependencies. So even if you apply a patch, you're still not going to get the patch because, I mean—

38:11Chris Romeo That was famous 10 years ago. Dependency padding.

38:15Matt Coles Okay. It still continues today.

38:18Izar Tarandach Yeah. Yes.

38:21Matt Coles Uh, so number 9 on this list, I think, is, uh, will require some discussion and we, I don't think we have time for it today, but at some point we probably should talk about it.

38:31Izar Tarandach Wait, which one? 9?

38:32Matt Coles 9.

38:33Chris Romeo Build us a deception capability.

38:35Izar Tarandach Yeah. So bring on the Decepticons.

38:42Matt Coles So deploy canaries, honey tokens. I don't even— and actually, if you guys know what honey tokens are, let me know.

38:51Chris Romeo I do. I do.

38:53Matt Coles What's a honey token?

38:54Chris Romeo Unfortunately, it's like a fake password. Oh, or, or token that gets left somewhere so that somebody can find it and then use it, and then the use of it triggers the detection.

39:06Izar Tarandach So it basically becomes a canary. So I don't see why the distinction between both things, but the truth is canaries, especially at the, the secret and credential level are really useful. My question again comes to time. Do I deploy these things before I do the other, the other 10, 11?

39:26Matt Coles No, it says, yeah, the other two things, it's high. So do it in the next 90 days and 6 months out.

39:32Izar Tarandach Yeah, but 9/11 is critical in the next 6 months. So how does it work? It's critical, but do it in the next 6 months.

39:40Chris Romeo They should have sorted this by start.

39:42Matt Coles But also, what's— what is VulnOps?

39:47Izar Tarandach It's a new ops that's going to generate a completely new industry.

39:51Chris Romeo Watch this space. I've heard that term thrown around for a year or two at this point. VulnOps.

39:56Matt Coles Autonomous Vulnerability Research and Remediation. Isn't that Pen testing?

40:02Chris Romeo No, because it's not— pen testing is not autonomous at this point.

40:05Matt Coles Not yet.

40:08Chris Romeo That's the, that's the car crash that we're heading towards.

40:11Izar Tarandach Staffed and automated like DevOps, but for autonomous vulnerability research and remediation.

40:16Matt Coles So this is a team within your development staff that just finds vulnerabilities?

40:21Chris Romeo That used to be QA, you know, but it's using Mythos to find all those vulnerabilities before external attackers can find them.

40:30Matt Coles Well, I thought your agents were doing that before when you started the program.

40:34Chris Romeo Someone's got to run the agents. Agents aren't completely independent yet.

40:38Izar Tarandach So you Google for VulnOps. The first thing that comes up is a project on GitHub. Then the second one is a domain saying VulnOps coming soon.

40:49Chris Romeo Then we have standby for VulnOps.

40:53Matt Coles Uh, go for VulnOps.

40:55Izar Tarandach Oh, the third one is actually a LinkedIn post that says what it is. Let's see what it is.

40:59Chris Romeo We could rename our, our podcast, the VulnOps Podcast.

41:03Matt Coles Well, then there'd be no conflict and we'd be the original VulnOps Podcast.

41:06Chris Romeo Well, then somebody would just copy us. Somebody would just make another podcast called the VulnOps Podcast. You know how it goes.

41:14Izar Tarandach Much like how MDR brings together a plethora, plethora of technologies to help defensive teams detect and respond to threats, VulnOps does a similar job for vulnerabilities.

41:29Matt Coles Okay.

41:30Chris Romeo I'm liking it so far. I'm gonna get a t-shirt.

41:32Izar Tarandach Yeah, but that's the thing. I don't care about being corrected. I'm used to it.

41:37Chris Romeo No, no, no. I'm just saying, I'm talking about this whole idea of Olmops. I think I might be in.

41:41Izar Tarandach Oh, yeah, yeah, yeah. No, it's just that the thing promised to tell me what it was and it didn't. So I'm still looking.

41:48Chris Romeo Typical AI.

41:49Izar Tarandach No, no, this was normal Google.

41:52Chris Romeo Typical humans. Humans. Vulnerability.

41:57Matt Coles So, so at the end of this, is this something to watch or something to take action on?

42:03Izar Tarandach Which one?

42:04Matt Coles This paper thing, the whole thing.

42:06Chris Romeo No, no, no, no.

42:07Izar Tarandach Definitely something to watch.

42:08Chris Romeo I think, I think you gotta take action, but I think you gotta start rocking and rolling right now if you're, if you want to get left behind.

42:17Matt Coles Yeah.

42:17Chris Romeo I mean, you can't, you can't roll this type of stuff out in a weekend. This is not a weekend project.

42:22Matt Coles Wait, you can't firecode your security programs?

42:25Chris Romeo I mean, you should. Somebody should try it so we could laugh at them.

42:27Izar Tarandach Not again. But, uh, no, no, no, no. I think that, I think that first of all, in my opinion and following Security Brutalism, you have to go and ask yourself, why haven't I been doing half of this already? Right? Then it's the reduce, reduce, reduce, reduce. Seriously, just reduce. I look around my room in here and the amount of old digital junk that I have at some point I should throw away, but sentimentality hits in and I can't, but, uh, don't be sentimental to your system.

43:00Chris Romeo Certainly the attack surface reduction is not a bad thing, but it doesn't solve this problem.

43:05Izar Tarandach It doesn't solve, but in the amount of things that you need to actually fix and keep an eye on, it brings you back to fundamentals.

43:12Chris Romeo Right. I mean, I've been preaching attack surface reduction for at least a decade at this point. And the funny thing is nobody ever does it.

43:18Matt Coles No, because the more computing resources you find, you get, the more you use.

43:24Izar Tarandach Because budget, the more you get to buy the next shiny thing, you're going to get more budget next year. Right? So it, it, it's apparently it's better to say I need $100 million to get the next shiny thing than I saved $100 million by dropping that shiny thing from last year. Mm-hmm.

43:43Chris Romeo Yeah.

43:44Izar Tarandach Right.

43:44Matt Coles Which means, which means on this list should have been budgets should change. Budget planning should change.

43:50Izar Tarandach Yep, definitely.

43:51Chris Romeo They never talked about budget, did they?

43:54Matt Coles Nope. They didn't say how much this is gonna cost. Right. We don't know what the token cost for Mythos is and how, what the myth, what the token budget is.

44:04Izar Tarandach And how many nuclear sites we're going to have to build to power this whole thing.

44:08Chris Romeo Hopefully a couple.

44:10Matt Coles I'd rather build a nuclear site at this point than go back to coal mining.

44:18Izar Tarandach True. So what do we close with this thing? Talking point: an aggressive plan is needed.

44:25Chris Romeo Um, I could say that about anything though.

44:28Izar Tarandach No, wait, wait, wait.

44:29Chris Romeo They say aggressive plan is needed about mowing my lawn. I need an aggressive plan.

44:34Izar Tarandach Wow. The funded foundation is why our program can adapt rather than react in a crisis. What has changed is—

44:45Chris Romeo yep, I was making up my own OODA on the fly.

44:51Matt Coles Defender agents, do not wait for industry governance frameworks. Defend— define your own now, because that always worked.

45:04Chris Romeo Well, so I guess we leave this as a wait and see.

45:07Izar Tarandach Actually, they have a closing paragraph here that I really like. Building a MITRE-ready security program is not about reacting to one model or announcement. It is about permanently closing the gap between how fast vulnerabilities are found and how fast your organization can respond. In other words, reduce your OODA.

45:25Chris Romeo Does that actually say reduce your OODA, or are you just adding that in?

45:28Izar Tarandach No, no, no, that's me. That's me.

45:30Chris Romeo Okay. I thought that was what I was going to hear, but I was just checking.

45:33Matt Coles That's me.

45:33Izar Tarandach Yep. That's me. That's me.

45:36Chris Romeo And so, I mean, it's not, they're not, they're not saying anything we really disagree with at the end of the day. Nope.

45:41Izar Tarandach Nope.

45:41Matt Coles This is double down and make it happen.

45:43Izar Tarandach I mean, yep. Bordering on duh stuff.

45:47Matt Coles And, and, and this is also, I guess, I guess I've come around on this paper. It, I was a little skeptical reading it to start, but it's really, if you are resistant to any of this, figure out a way to not be resistant to this.

46:03Izar Tarandach Yes.

46:03Chris Romeo Because as the Borg are famous for saying, resistance is futile.

46:10Izar Tarandach Futile.

46:11Matt Coles You will be assimilated.

46:13Chris Romeo You will be assimilated. I think that's where we leave it.

46:16Matt Coles I think that's Star Trek is much better at for these than Star Wars in my opinion.

46:24Chris Romeo But live long and prosper. That's right. That's— ISAR is the OG Spock threat modeling supermodel.

46:33Izar Tarandach Oh yeah.

46:36Matt Coles Wait, wait. You did.

46:39Izar Tarandach Hey, it comes from the same place, right?

46:43Chris Romeo Right from the heart. It's from the heart.

46:45Izar Tarandach I got membership. I got membership on the tribe. Yeah.

46:48Chris Romeo All right. Well, folks, we'll leave this with you here. Go basically build the whole ALI Vaultnops program over the weekend, and we But reduce your, reduce your attack surface before. Reduce the attack surface before. And we expect a TPS report diagramming the whole thing.

Transcript supplied by AssemblyAI. It may contain transcription errors.

Originally published as The Security Table. Part of the AI Security Table archive.