59 minSeason 4, episode 14

Don't Bury the Model T: Why STRIDE Still Drives in an AI World

With Chris Romeo, Izar Tarandach, and Matt Coles

Threat modeling & security architecture

Do AI systems require a new threat-modeling method, or are we abandoning useful tools before understanding their limits? Chris Romeo, Izar Tarandach, and Matt Coles first examine npm's move toward safer install defaults and the risk that agents trained on older behavior will simply re-enable dangerous options.

Episode title image: Don't Bury the Model T: Why STRIDE Still Drives in an AI World

Listen to the conversation

Episode chapters · 15 chapters
  1. Intro: deterministic fansAudio
  2. npm and secure install defaultsAudio
  3. Will AI agents re-enable risky behavior?Audio
  4. Other package managers and safe defaultsAudio
  5. Checking packages and internal repositoriesAudio
  6. Let's Encrypt and code-signing certificatesAudio
  7. Install scripts and compatibilityAudio
  8. The search for the wheat colorAudio
  9. Was STRIDE built for a vanished world?Audio
  10. Threat categories and modeling methodsAudio
  11. Non-deterministic AI and deterministic controlsAudio
  12. Hallucination and cross-context failuresAudio
  13. STRIDE and the Model T analogyAudio
  14. Tracing code versus explaining model behaviorAudio
  15. Closing assessmentAudio

About this episode

Do AI systems require a new threat-modeling method, or are we abandoning useful tools before understanding their limits? Chris Romeo, Izar Tarandach, and Matt Coles first examine npm's move toward safer install defaults and the risk that agents trained on older behavior will simply re-enable dangerous options. Then they debate the claim that STRIDE belongs to a world that no longer exists. The discussion separates threat categories from modeling techniques, non-deterministic model behavior from deterministic controls, and unfamiliar failures from familiar security responsibilities. The Model T analogy gives both sides something to argue with: an older framework may need adaptation, but declaring it obsolete does not explain how the replacement improves the analysis.

Mentioned in this Episode:
➜ npm install documentation
➜ Microsoft Threat Modeling Tool: STRIDE threats

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 · 59 min conversation

0:09Izar Tarandach We're on Jeannie.

0:10Chris Romeo It's true. We've gone from Jeannie to Dano, whatever that means.

0:14Matt Coles Book 'em down.

0:15Chris Romeo That'll be the name of my, my 7th book, From Jeannie to Dano.

0:21Izar Tarandach History of bookings.

0:24Chris Romeo History of bookings. Well, it appears once again on the Security Table, you have entered a conversation that was already happening, but we want to welcome you, our trusted deterministic fans from, from around the— or would they be non-deterministic?

0:43Matt Coles Uh, they're almost certainly non-deterministic.

0:45Izar Tarandach No, they're deterministic because we can trust them.

0:48Chris Romeo True. I like that. Put that on a t-shirt.

0:50Matt Coles Wait, wait, wait, wait. That Can you mathematically prove that?

0:55Izar Tarandach Uh, I could call on people who actually know math to do it.

0:58Chris Romeo Yeah. But I, I got the proof right here. 1+ 1= 2. Done.

1:03Izar Tarandach Uh, on which base?

1:04Chris Romeo Proven. Base 7.

1:08Izar Tarandach It, it, it could be 0 and carry the 1.

1:10Matt Coles True.

1:13Chris Romeo I forgot about that. It's always the one that gets— well, hey folks, I'm Chris Romeo joined by Izar Terrandash, Matt Coles. We are the knights of the security table. Actually, we're more like the knights that say knee than we are the knights of the round table. But okay, let's dive in here. Apparently NPM has made some changes to stuff and junk.

1:39Matt Coles About darn time.

1:42Izar Tarandach About darn time is right.

1:45Chris Romeo So, well, actually it's going to be this month apparently that these changes will be happening. Okay, about almost darn time. Basically, they're taking out some bad behavior. If I had to summarize this, they're taking out some bad behavior that npm could do. They're not removing it. They're just making it something that you have to enable.

2:06Matt Coles In other words, by defaulting it, enabling security by default.

2:10Chris Romeo Yes.

2:11Matt Coles Finally.

2:12Chris Romeo So just quickly to summarize what I see as the changes. Well, who am I kidding? What my AI says it sees as the changes. Npm install will not run pre-install, install, or post-install scripts from dependencies unless explicitly approved, which is that secure by default thing again. npm install will no longer fetch dependencies from Git repos, direct or transitive, unless explicitly permitted, removing code execution path where git dependencies— .npmrc file could alter which Git executable is used. And then third, dependencies installed from remote URLs such as HTTP. HTTPS tarballs would no longer be resolved unless explicitly permitted. So once again, does it sound like they're not, they're not taking anything out?

2:57Matt Coles Nope. Because they don't want to be adding, they don't want to be breaking massive backward compatibility problems, right?

3:02Chris Romeo Which I think is the right thing to do for something with the scale of npm.

3:06Izar Tarandach They are gating the bad behavior, right?

3:09Matt Coles Well, you have to make a decision. You as a developer, well, or you as a developer or you as the AI who is taking the place of the developer need to make a decision. Now, interesting, actually interesting. Sorry. Now that brings up an interesting thought. By leaving the behavior in, but enabled, but disabled by default. Does that mean almost certainly any AI that has been trained on npm prior to v12 will just re-enable it and we're going to be You're going to be broken again or potentially broken again.

3:43Izar Tarandach It will try to do it the wrong way. It will see that it doesn't work. It will try 30 other ways, including erasing your whole file system.

3:55Chris Romeo No, but it will work.

3:58Izar Tarandach And then you are going to say, but wait, this changed. And it's going to go back to you and say, you are absolutely right. I should have checked which version of npm I was running before I destroyed the file system.

4:13Matt Coles It's too late now.

4:16Chris Romeo I mean, so who needs a file system?

4:18Matt Coles Well, cause right. Cause V12, when V12 comes out, I mean, this won't be a, this will be a problem in the first like couple of weeks, but as soon as you get new models that are trained on V12, they'll know V12 has different behavior.

4:31Izar Tarandach But to me, the really interesting thing here. Is that npm has taken this high profile as a package distribution system, as a package manager, right? And it's not a very new thing. For a while, it was limited more to people who dealt in a certain part of the space, but now it's a—

5:01Matt Coles People who write JavaScript.

5:03Izar Tarandach See, I didn't want to go there, but then you went there. Yeah.

5:06Matt Coles So, uh, Ben, what else are you supposed to go there?

5:09Izar Tarandach It's npm.

5:09Matt Coles No, no, no.

5:09Izar Tarandach I mean, it's a bad—

5:11Matt Coles it's Node package manager. Node.js package manager.

5:14Izar Tarandach It's just that kind of person, people that go, oh, that's just for front ends. No, no, no, no. Let's write the backend because that's a great idea. Yeah.

5:20Matt Coles Cause somebody decided to write JavaScript to write backend servers.

5:25Izar Tarandach That's for a different episode. But the, the, the thing now is—

5:28Matt Coles I think we've had this episode before.

5:30Chris Romeo We did?

5:31Izar Tarandach Deja vu. So, uh, what I'm interested here is when will the other 30,000 different package, uh, package formats and package managers out there actually do the same thing, right? Because this is just the right thing to do. We should be making difficult for people to do bad things, even without knowing that it's a bad thing. Right. So if you really trust the package that you're pulling, then sure, by all means, allow dangerous, whatever the flag is. And if you don't, then at least stop and think before you do it and consider the consequences of the thing that you're asking your shell to do for you.

6:19Chris Romeo So I just made the connection here that these npm changes would have prevented, if they had been in existence, the Shai-Halud worm would have been not allowed, wouldn't have been able to operate. It was using a post-install script.

6:34Matt Coles It would have had to follow a different vector, right? It would have had to find a different package manager that had bad behavior. It wouldn't have been through npm. It would have been through something else.

6:43Izar Tarandach It would have been slowed down because a lot of people would just look at the output and say, oh, you just have to add a flag. Let's do it.

6:50Matt Coles Well, actually, that's an interesting question. Is there a bypass here? So if you disable but keep all the functionality. Could a package re-enable it? Like as a two-step process?

7:05Izar Tarandach Any, anything that can call another thing will be able to re-enable it, right? So if you have a bad script that calls a good script with bad flags, you're going to get a bad outcome. But the thing here is that at the end of the day, who is this going to actually serve? The people who already had a minimum of security awareness to know that this might be a problem. So unless it comes out with a big honking banner saying you're trying to do this thing and this thing may damage your— then I don't know if a lot of people are going to extract a lot of content from this.

7:47Matt Coles Well, I mean, honestly, right now with everybody doing, you know, or not everybody doing vibe coding, or spec-driven development, developers will never see it.

7:59Izar Tarandach Yeah, but this is going to break a lot of pipelines down there, right?

8:03Matt Coles Because they rely on pre and post-install functionality?

8:06Izar Tarandach They rely on installing a lot of these packages, and some of them do the post-install thing. I'm not saying all of them, but some of them I'm sure do. So there may be some breakage in the horizon if this becomes the default.

8:20Matt Coles Well, why wouldn't you just ask your AI to fix it? Which, as you said, may result in the deletion of your entire application, but at least initially.

8:35Izar Tarandach Which perhaps carries us into the next one.

8:40Matt Coles Well, before we get there, how did, how did RPM solve this?

8:43Izar Tarandach Right.

8:43Matt Coles So you, I think we were talking earlier, RPM.

8:46Izar Tarandach Well, on RPM, you can say explicitly which stages of the install you want to run, right? If you don't say anything, then it's going to run the whole thing, the pre, the install, and the post. Or you could say just run this one or just run that one. The thing is that RPMs, perhaps because of their age, I think, they do have a bit more of a security veneer around them. So you have they are signed. I'm not familiar with npm to the point of saying that those packages can be signed. I think that it's more of a provenance thing. Could be wrong. But RPM does have the whole signature verification ecosystem around.

9:31Matt Coles But signing doesn't eliminate bad behavior.

9:34Izar Tarandach No, it doesn't. But it gives you at least a Again, that's why I said the security veneer. It gives you the provenance. And if your sources are trusted, then by the transitive property, you're saying, okay, I trust them to run the pre-post and install scripts the same way that you run the, that you trust them to run their binaries. Right.

9:58Matt Coles Well, I guess that's today it's implicit trust, right? Because nobody's checking the packages. I mean, if they did, do you know anybody who— I mean, do you know of anybody who goes and looks at all of their JavaScript packages? Like explicitly, I want this one, I want this one, I want this one. Okay, besides Chris.

10:21Izar Tarandach No, I know people who will bring stuff in, scan stuff, put them in their own repository and direct all their developers to only use that. That repository, right? Because at the scale and speed that these things go, be honest with you, I'm not expecting anybody to do that verification by hand. It's like, oh, new shiny thing.

10:49Chris Romeo Yay. And there's tools to do that as well. You don't have to build that type of internal repository from scratch.

10:55Izar Tarandach Yeah, true. But hey, you know what? All in all, a good step forward.

11:04Matt Coles Well, yeah, it is.

11:05Chris Romeo It's about time. But there are some bypasses to it. That's what I was looking at right now. Your, your AI can bypass it is actually true. Um, if developers just run npm approve scripts --all to unlock their build, the protection collapses entirely. And it says AI coding tools adding dependencies at speed may outpace human review, risking the allowlist becoming a mere formality.

11:28Matt Coles Mm-hmm. Well, so the alternative is they disable the functionality entirely, make it backwards breaking change, you know, making a breaking change. And then, and then what? So now you need to have explicit trust of packages, right? That become— that defeats the purpose of npm perhaps, or has it become like PyPI?

11:48Chris Romeo No, I mean, npm's goal should be the inherent trust of all packages that you get from it. Now, that's an easy thing to say, not as easy of a thing to implement. But isn't that why they exist for the future, at least, is to provide trusted packages? Aren't they a trusted repository of packages?

12:15Izar Tarandach But are they trusted because they said that they are to be trusted, or are they trusted because by use people decided to trust them.

12:24Matt Coles I mean, people trust PyPI, right? Or not.

12:32Izar Tarandach No, I mean, did they wake up in the morning and said, we are going to build a trusted environment? Or did they just say, we are going to be the place where people will come to, to get their packages?

12:44Chris Romeo I think it's option 2.

12:45Izar Tarandach I don't know.

12:46Matt Coles Yeah. Speed over convenience over anything else.

12:49Chris Romeo Right.

12:50Izar Tarandach Yeah.

12:51Chris Romeo But in the second article that we're going to talk about here, there was mention made of OpenSSL's, maybe it wasn't in the second article, but apparently open, no, they have a, they have a signing project for packages.

13:07Izar Tarandach Yeah. The cosign. And, uh, I forget that it's actually a very good. Good project with a lot of very good people in there.

13:15Matt Coles Is it? It's like, um, Let's Encrypt, which—

13:21Chris Romeo that's what I started saying about 5 years ago is like, somebody needs to build the Let's Encrypt certificate version for packages. Because think about, do you not even think about TLS certificates anymore for public sites? It's just a commodity. That you don't even pay for. Like they just get generated by this, this service. If we could get to that point with, excuse me, with packages like that would be to be able to have that provenance, true provenance and cryptographically proven provenance of a package. It's a step.

14:00Matt Coles Interestingly though, so let's, getting a little sidetracked, but let's encrypt verifies that you have ownership of the site before it gives you a certificate. How would it do that for software packages?

14:17Chris Romeo You have to be a repo. You have to be a repo thing, or you do the same exact thing in a repo. You have to put a file in a repo like you would do in a DNS info record or something to prove ownership.

14:30Izar Tarandach Hmm.

14:35Chris Romeo There, I solved it. Somebody can go build it now.

14:37Matt Coles There you go. Somebody write a spec. Somebody write a spec and get Claude to write it for you.

14:42Chris Romeo Yeah. Somebody vibe code it today and let's get this thing deployed tomorrow.

14:47Matt Coles What's the cost of that? Actually, who pays the cost of the certificates?

14:52Chris Romeo I think it's a not-for-profit. That's, uh, charity, a charitable organization. Last I heard, I don't know if some big companies— I feel like some big companies seeded it with money, but I'm double-checking just because with everything else in the world, I don't know anything anymore. I just type words into an AI bot and it tells me, because, because AI has become a has become a search engine. Yeah, there were 5, 5 original sponsors, Mozilla, EFF, Cisco, Akamai, and IdenTrust.

15:32Matt Coles Mm.

15:33Chris Romeo They kicked in a bunch of money. Yes. But now the Gates Foundation's on board.

15:38Matt Coles So there you go. Well, so maybe we can get them to, uh, to make code signing certs. Call to action.

15:45Chris Romeo Issued more than 7— Let's Encrypt has issued more than 7 billion certificates since launch.

15:51Matt Coles And how many of those sites have served malware?

15:55Chris Romeo I mean, some, 30, 40%.

16:01Matt Coles What's in, what's in your thread bottle?

16:04Izar Tarandach We have to do that commercial one of these days.

16:10Chris Romeo All right. Well, let's talk about this other thing. I think we've, we've talked about the npm. Yeah.

16:15Matt Coles It was a good change. By the way, when did GitHub own npm?

16:21Izar Tarandach When what?

16:22Chris Romeo GitHub bought npm?

16:23Matt Coles Well, okay. It's GitHub announces there's an npm change. Why did GitHub announce?

16:29Chris Romeo That's weird. I didn't think of that.

16:32Izar Tarandach Because they're the ones who are going to break the most.

16:37Matt Coles It's, it's, it's a GitHub. Yeah. GitHub blog. About npm, our next npm major version.

16:50Izar Tarandach Huh.

16:50Matt Coles When did GitHub own npm?

16:57Chris Romeo I'm going to click on the actual link up there.

17:00Izar Tarandach Yeah, I did. And it has a label on top, retired.

17:03Matt Coles What's that?

17:03Chris Romeo Yes, that's weird.

17:05Matt Coles I just noticed that too.

17:07Chris Romeo What is that?

17:11Matt Coles What's retired? NPM? The announcement?

17:15Izar Tarandach The announcement? What the? Okay. Now I'm confused.

17:21Matt Coles What?

17:22Chris Romeo Maybe we're not in favor of this now. Now we're confused.

17:25Izar Tarandach I'm confused. GitHub Enterprise. Okay. I need something to drink.

17:31Matt Coles Oh, and then, oh, and then the previous, the previous one is Dependabot version updates now support the Deno ecosystem. GitHub acquired NPM in 2020. 2020. Okay, we're a little bit behind the news.

17:45Chris Romeo What?

17:48Matt Coles Get up.

17:49Chris Romeo My mind is just—

17:50Izar Tarandach what?

17:51Chris Romeo Is there— is there— so upset about this, he just left the studio.

17:55Izar Tarandach Left?

17:55Chris Romeo He just left. He just got up and walked away and said, screw this, I'm out.

18:00Matt Coles He needed a drink. He's going to get something stronger.

18:02Chris Romeo O'clock in the morning.

18:03Matt Coles He's getting a Monster.

18:05Izar Tarandach I went to check if, uh, GitHub by mistake had acquired itself.

18:10Matt Coles Well, apparently GitHub has acquired npm in 2020. Where were we?

18:17Izar Tarandach But wait, wait, wait, wait, was npm a thing that could be acquired? I didn't know that. That's how out of npm I am. Actually, since, since we, we mentioned anything, uh, uh, vibecoded. I want to turn to our listeners and ask for a question, ask for help. So npm, if you do npm audit, it will look into something called a package lock into the directory that you are, go through all those packages and their dependencies and see if there is any outstanding security alerts for them or whatever. You can see these, I don't know. That's, that's all good and nice for the packages in the, the project that you're working on and their dependencies. But there's all kinds of tools that you, you install using npm, which could be -g global or, or private. I haven't found yet a way to scan those. For security issues. So if anybody knows of something like that, drop us a line, give us a comment, poke us on LinkedIn or something. Because if there isn't one, my question is why? That's no less important, right? I mean, even our AI agents are written in, distributed through npm. So it shouldn't be a matter of like, going and say, oh, I remember that once I installed this thing, let me see if I can update it. There should be a—

19:58Matt Coles Will this change break AI installs now?

20:04Chris Romeo I don't know.

20:05Matt Coles Probably they rely on these pre and post install scripts to deploy. In fact, they probably do because you deploy the bits and then you run the post install script to actually do the install.

20:17Izar Tarandach Yep. I guess.

20:19Matt Coles So that's an interesting, that's an interesting thing because if they make this the default behavior, but it breaks all the installs for convenience, they'll probably be disabled by default soon.

20:29Chris Romeo It's set in the last, in the last version of 11, npm 11, they made them all warnings so that people would be getting some visibility that things are about to break.

20:40Izar Tarandach There's a bunch of stuff that you can add with npm. Like Skills and this and that and the other one that are not exactly binaries, but they have post-install scripts because they ask all kinds of questions on the install.

20:54Chris Romeo According to my research, only 2% of npm packages need install scripts to function.

21:01Izar Tarandach I had like, yeah, but the question is which 2%. I mean, that makes sense because a lot of them, most of them, I'd say, are probably libraries that come as dependencies, right? So you need them around in order to be able to run something. But exactly what Matt is saying, that these packages that now are part of our AI— I'm sorry, I can't call them agents— our AI clients, right? Those things do seem to need Postgres. So I remember in Over the weekend, I installed something and it asked a bunch of questions afterwards. I'm guessing that that was a post-install. If it wasn't, then there's another thing that we have to turn off. But, uh, the, the, the derivative here for, for me is that if it becomes a learned behavior that you have to run it with dash dash whatever to get those things to work, then what have we achieved?

22:00Matt Coles It's the security theater, the button, single button click. Where's your, where's your single button keyboard there? Is that, cause that's basically what it is all over again.

22:09Izar Tarandach Thanks for remember.

22:13Chris Romeo Yeah.

22:14Matt Coles So I'm looking at the discussion thread on this. So the functionality exists, but it doesn't exist in a question is one, one, some user to their discussion, will Node 26 ship with npm 12? And it's an ongoing discussion about which version of, of Node will ship with this thing by default.

22:37Izar Tarandach I think we should invite somebody to talk to us about the npm universe and make us more educated about it, me at least, because I don't feel like I know enough of the details there.

22:48Matt Coles I mean, that'd be interesting. That'd be an interesting episode anyway to talk about not just, as you mentioned, there's other things, right? That we RPM, but also Go, right? There's other sort of language with built-in package manager discussions to be had.

23:02Chris Romeo Right.

23:03Izar Tarandach Because now they are environments. They're not languages. Once upon a time you had VI and a compiler and life was good. And now you have—

23:12Chris Romeo Life was not good.

23:13Izar Tarandach Hey, life was great.

23:15Matt Coles Okay. There's no IDE. It was better than having Ed. You remember Ed?

23:24Chris Romeo What was the line-by-line one?

23:26Izar Tarandach Ed. That was Ed.

23:27Chris Romeo Was it Ed?

23:28Matt Coles Yeah.

23:28Izar Tarandach Yeah. It was VI.

23:31Chris Romeo VI was an improvement over Emacs, which is Yzhar's go-to.

23:36Izar Tarandach Hey, hey, hey, no, nobody says a word about Emacs.

23:40Chris Romeo See, I told you. This is his.

23:43Izar Tarandach I wonder if somebody already wrote a Lisp package that runs Claude inside of Emacs. I'm sure they have.

23:49Matt Coles If they haven't, you will have it by next week.

23:53Izar Tarandach Ah, no, I don't touch Emacs anymore.

23:55Matt Coles You don't have to.

23:56Izar Tarandach I'm sorry to say.

23:57Matt Coles You don't have to, Claude will.

23:59Izar Tarandach Yeah.

24:00Matt Coles Have your friend Claude do it.

24:01Izar Tarandach Those were good times.

24:03Matt Coles Those were good times.

24:04Chris Romeo Tell it to use Emacs, it'll be like, no, I can't do that.

24:08Izar Tarandach No, no, no, no, seriously, seriously. I remember Eliza. Do you guys remember Eliza?

24:13Matt Coles Eliza, yes, a little bit.

24:14Izar Tarandach Yeah. Eliza running inside of Emacs. That was one of like the first things that I actually discovered on Emacs and it led me And that led me through a very, very deep rabbit hole of learning Lisp and Prolog.

24:31Matt Coles When did you get colorization in your editor?

24:35Izar Tarandach It was around '91, '92. There was the, what was the name of the package? Transmogrifier, something like that. That would give you syntax. Color in Emacs. And the fun thing was it took me a long time to get to a color scheme that I could work with.

24:59Matt Coles And there was no accessibility at that point. I mean, no.

25:03Izar Tarandach And just last week, just last week, I was trying to like find a color for each different agent that I was— sorry, client that I was running. And I was looking for wheat. Wheat was like the default of XEmux when it came out. And I just couldn't find the right RGB for wheat. And it drove me nuts.

25:28Matt Coles You know, there's a limited set, right? You could test them all. And then, I mean, wheat is mostly white, right? So it's yellowish.

25:36Izar Tarandach No, that looks like work. We don't do work anymore.

25:40Matt Coles You don't have to. That's what your clients slash agents are for.

25:44Izar Tarandach Okay. So what did I do?

25:45Matt Coles I found an agent swarm, test each of these, look for wheat.

25:49Izar Tarandach No, no, no. What you do is I went up in the attic. I found an old laptop that I had that ran Linux circa, I don't remember when. And it had in it like my .files from way back when, and it had .emacs and .x, uh, uh, .x, what was it? .xattributes or something like that.

26:11Chris Romeo .rc?

26:12Izar Tarandach No, no, no, no, no, no, no. The .x files.

26:15Matt Coles All right. I have a surprise for you, Azhar.

26:17Izar Tarandach And in one of them, I had .foreground equals the RGB for wheat. So I was able to find that.

26:24Matt Coles I have something for you.

26:25Izar Tarandach No, don't tell me that Gemini found it for you.

26:28Matt Coles I did. Not Gemini, but there is an Emacs themes site. With GitHub Pages for the wheat.

26:38Izar Tarandach Yeah. You know what? I had much more fun looking at my old laptop.

26:43Matt Coles Including, including the RGB color, color blocks. So, you know, exactly in CSS, so you can apply it to your HTML pages.

26:54Chris Romeo Yeah. I heard wheat's making a comeback. It's supposed to be the color of the year for 2027.

26:59Izar Tarandach It's easier on the eyes.

27:01Matt Coles It is.

27:03Chris Romeo Everybody's gonna be using it. It's gonna be, houses are gonna be painted wheat.

27:08Izar Tarandach Okay. So wheat is the new dark mode.

27:11Chris Romeo Yeah, it is. I heard that too.

27:14Izar Tarandach T-shirt.

27:15Chris Romeo From people in, people in Silicon Valley. I heard that.

27:19Izar Tarandach T-shirt. Okay, cool.

27:20Chris Romeo Wheat. I mean, they were on the TV show.

27:22Matt Coles Wheat on black.

27:25Izar Tarandach What?

27:26Matt Coles Wheat on black.

27:27Izar Tarandach So, oh, we turned black. So we're going to jump into the STL is broken or we're going to keep it for next week.

27:34Chris Romeo I think we should keep it. Oh no, let's talk about the Stride built world longer exists. I kind of said that wrong.

27:41Matt Coles Stride was built for a world that no longer exists is the topic, yes.

27:46Izar Tarandach In a world that doesn't exist anymore, a methodology rose to transform the world.

27:51Chris Romeo You really need that guy. Once again, you need that guy from the movie previews. In a world that doesn't exist, Stride is missing.

28:04Izar Tarandach Hey, we are continuously searching for it.

28:08Matt Coles It's a stride out of time. All right.

28:13Chris Romeo So let's do this.

28:16Izar Tarandach Has anybody come up with a StrideBear agent anymore already?

28:21Matt Coles Probably. I think you just invented it.

28:23Izar Tarandach Yeah, I think I'm going to call this. I'm going to put a stake on the ground for that one.

28:28Matt Coles Stride for client?

28:29Izar Tarandach Stride for client. No, that, that's a consulting gig.

28:33Matt Coles Ah, there you go. So, uh, so we're interesting.

28:41Chris Romeo I mean, do we want to be here? Do we want to be just normal mean levels or do we want to like—

28:45Izar Tarandach No, no, no. Wait, wait, wait, wait, wait. I think I'm in the, in the wrong place. I'm in the STL is broken and that's actually good news.

28:53Matt Coles You're, you're the wrong article.

28:55Chris Romeo We're in Stride Was Built for a World That No Longer Exists.

28:57Matt Coles Or move backwards because it was posted previously.

28:59Izar Tarandach Oh, backwards, backwards. Okay. Okay. Let me go look for it. Okay. You guys start. I'll, I'll, I'll drink it.

29:05Matt Coles It's in chat, by the way. Just watch the Isar just catching up to, because he was still, he's still stuck on his wheat.

29:13Chris Romeo He's still, he's still just looking for the color wheat. So he might tell us.

29:17Matt Coles No, he's playing, he's playing Settlers of Catan and he's looking for wheat.

29:21Izar Tarandach Just, just assume that I'm stuck. Like it's, it's, it's the safe choice.

29:26Chris Romeo Just, he's playing, uh, what's the, what's the game that Oregon Trail?

29:34Matt Coles Oregon Trail.

29:34Chris Romeo He's playing Oregon Trail over there.

29:36Izar Tarandach Oh, you, you just died of, uh, what was it?

29:39Chris Romeo Dysentery.

29:40Izar Tarandach Dysentery. Dysentery.

29:41Chris Romeo I don't know. Izar died of dysentery again and again. All right.

29:48Izar Tarandach So, hey, I played the thing on an Apple II. Yeah.

29:51Matt Coles I didn't play it on Apple II. Apple II Plus. Yeah.

29:54Chris Romeo In, in green.

29:55Matt Coles Uh, yep. Anyway.

29:58Chris Romeo All right. So, yeah. How did I end up in central? It's gonna be normal here when we respond to this.

30:04Matt Coles So Stride. So two things about Stride. Stride is both a threat categorization and a methodology.

30:13Izar Tarandach Yeah.

30:14Matt Coles Right. So you have STRIDE, the spoofing, tampering, repudiation, et cetera. And you have per element and per interaction.

30:22Izar Tarandach Okay. Agreed.

30:23Chris Romeo Correct.

30:24Izar Tarandach So far so good.

30:26Matt Coles Both of those, I would argue, still apply in an AI world. And in fact, it applies, I think, even more so in an AI world because what's an AI? An AI is a process. Uh, AI is a behavior, has behaviors, and Stride, the Stride threat categories are all about behaviors.

31:00Izar Tarandach Oh God, I'm gonna be so mean here.

31:04Chris Romeo To who?

31:05Matt Coles To who are you going to be mean?

31:06Chris Romeo To whom?

31:08Izar Tarandach To a world that no longer exists. I mean, why do people feel this, this, this need to put down something that has been serving us quite well, I might say. Not exactly my choice of where to go, but has its uses, definitely.

31:33Chris Romeo Right? Sure.

31:34Izar Tarandach And, and then start saying, oh no, no, no, doesn't work anymore.

31:37Chris Romeo No, no, no, no, no.

31:38Izar Tarandach The world changed. Guys, for, for, for, for the love of Tulu, it's bytes. They go into CPU, they come out. We're not quantum yet. It's not like all possible things happening and will happen everywhere at the same time. No, it's bytes come from memory, go into CPU, an opcode gets executed, a result comes out, right? It's, it's the same thing as people saying, uh, you know what, we, we, we can't have maps anymore. No, no, cities can't have maps anymore because hey, you know what, cars can take any way they want, right? You never know which way a car is going to take. Hey, it can drive this way, it can drive that way, it can drive the other way. So let's not make maps anymore.

32:19Matt Coles If you're in Boston, like one-way streets don't matter, right?

32:22Izar Tarandach So, well, that, that's a different thing. Jerusalem, same thing. I mean, you can come in a different day and the, the, the, It's going completely different way. But my point is, we are all running around saying, oh, all these things are non-deterministic. Yeah, sure, fine. Yeah, yeah, yeah. You don't know exactly what's the next step, but the whole thing should be bound. Only a certain number of things can happen. You just don't know, okay, how it got there, the order, but—

32:48Chris Romeo That's an important issue that, but I've even got something we can do before that. Can you, can you go to the top of this article? And this example that he has here about the mid-market healthcare company integrated ChatGPT, they ran a formal STRIDE threat model and then the world fell apart.

33:07Izar Tarandach Wait, I haven't seen the world falling apart yet.

33:10Chris Romeo Okay. Well, so then week 3, a patient called their medical records appear in the ChatGPT response, not their records, someone else's. Can't we tie each of these instances, like summarize, and then the next one was summarize my previous chat history. Isn't tampering in a refactored AI world, isn't this just tampering? And maybe Stride needs to be, some additional explanations need to be made for how Stride applies to AI. I keep seeing this.

33:40Matt Coles I was ready to go explode over there.

33:43Izar Tarandach Go ahead. So the thing here is that But what's not being said here, right, is that it's the same thing as, okay, coding agents. We already agreed that we should relate to our code coming out from a coding agent as code from a junior developer, right? Check it, read it, review it, whatever. Just don't accept it at face value. On the other hand. When we're talking about chatbots that could have like a query functionality, people are willing to accept those things as if they are like master librarians that know exactly where to go and get only the right thing and bring it right in front of you and put it in front of you. You know how you don't get things that can do what's being described here? By binding the amount of agency that they can have by using controls beyond the AI that will say, you know what, mine that record, but not that one. Databases have per-role controls and have had them for what, 30 years? Because that stuff works. But just to say, hey, AI, whenever somebody asks for a record, only show their records, nobody else's, okay? That's not non-determinism, that's ridiculous optimism. That's not how things work. So yeah, the behavior of the AI may be non-deterministic, but the controls that you put in it are deterministic. And those controls, they tie to specific scenarios of failure. Those scenarios of failure tie to impacts. Stride likes impacts. You probably, as you said, could bind those things back to Stride. And it's not like all of a sudden there is this new class of stuff that Stride never saw before and oh my God, we need another acronym. We need layers, we need layers.

35:49Matt Coles All right, so I'll play devil's advocate a little bit here. Why did StrideLM exist? It's a rhetorical question. You don't have to answer.

36:02Izar Tarandach Wait, wait, wait.

36:03Matt Coles Do we want to tell people who are not familiar with Uh, Stride LM, right? Stride plus lateral movement. And that's the plus lateral movement that is the important part. Somebody decided that stride was necessary, but it was insufficient or it was lacking something. And so they added lateral movement, right? And so you had the base and then you extended it to fit a particular use case.

36:26Izar Tarandach But that's the, that, that's the thing. What did you extend it with? You didn't extend it with one more impact. You stand to, you, you extended it with one more way of using the previous 5 impacts to get to where you want.

36:41Chris Romeo True.

36:42Matt Coles Right.

36:42Izar Tarandach Right.

36:43Matt Coles Right. So utilize tampering to get a pivot.

36:46Izar Tarandach Exactly. So it's the same thing as prompt injection, right? I, I, the, the, the folks at OWASP who are doing the, the, the whole LLM, uh, top 10 again. I had the chance to go into the channel that's discussing prompt injection itself as a threat and put in there a lot of what I've been putting here on the podcast for a long time, that it's not a threat. Prompt injection is not a threat by itself, right? And I was expecting some pushback or I was expecting to learn something that would completely change my view. And I did learn a lot of stuff for sure, but nothing that disagreed with me. And they were extremely gracious in, in allowing the newbie to step in into something that clearly had been discussed ad nauseam over there. Right. And they said, yeah, it's not really a threat. It isn't. It's a vector. It's a, it's a way to get there. It's something that looks bad. But it's not by itself a trap because it's not doing things. You need other stuff on the tail end to actually have an impact on, on something. Right? So the LM in here, the lateral movement by itself, it, it wouldn't be a vector. It wouldn't be an impact. It, it just would be something that takes you further. It would be even a result. You, you want to get that foothold so that you can get lateral movement so that you can go somewhere else and have more impact.

38:17Matt Coles And you're touching upon something that's very important. Actually, it's mentioned in the next paragraph. It said the threat model said this was unlikely. This was the hallucination part. And, but the attacker made it repeatable. Stride doesn't decide likelihood. Stride is a category of threats.

38:38Chris Romeo True.

38:38Matt Coles Or Stride is a way of identifying threats based on a DFD. It doesn't decide likelihood. Something else decides likelihood. Traditionally, that's the humans who decide likelihood. They look at a particular threat and say, how is it likely to occur? Is it likely to occur? Is it something we should do something about? Right? To some extent, or actually in reality, you're actually asking one of the four questions of the four-question framework when you're applying STRIDE. What could go wrong and/or what are we going to do about it? And one of those answers for what are we going to do about it may be nothing because it's unlikely to occur. So it's not Stride, it's a threat modeling process and the decisions that are made that decide that that threat may be unlikely. And so if the threat model decides something's unlikely because of past behavior, but now you have repeatable behavior that says otherwise, update your threat model. Don't kill Stride away.

39:35Chris Romeo Yeah, I'm looking, I'm looking at this going, the people that should be fired are the people that didn't do a proper threat model considering all of their, all of their threats. Like they ran a formal Stride threat model is what it says at the top. Why wouldn't you, why wouldn't you consider AI in that threat model? Like this is kind of a strange example.

39:56Matt Coles Maybe if you don't know, if you don't know that hallucinations can occur with cross, with cross-conversation chat text.

40:00Chris Romeo Well, then you shouldn't have deployed a ChatGPT-connected API into an application.

40:03Izar Tarandach That's one.

40:05Chris Romeo I didn't have the knowledge to understand how it worked.

40:08Izar Tarandach Should I ask it how it worked?

40:12Matt Coles Can you hallucinate? No, of course I can't hallucinate.

40:15Izar Tarandach Wait, wait, wait, wait. When somebody says something like an hallucination occurred because of a past conversation.

40:25Matt Coles Cross-context.

40:27Izar Tarandach Cross-context.

40:28Matt Coles Which we know. So maybe we know that now. Maybe we didn't know that. No, no, no, no, no, no, no, no, no, let's go back there.

40:34Izar Tarandach Let's go back there. Let's forget the hallucination for a second. Let's talk about the cross-context here. How long have we known about the need to clear your buffers before you start a new session of anything that runs in a loop? How long have we known about mining swap files for passwords? How long have we known about looking for data structures in process memory to figure out what was happening? It's not a new thing people!

41:08Matt Coles How many people understand that npm automatically does things when you install packages?

41:14Chris Romeo But th—

41:14Matt Coles That's the thing... We're talking no-no-no-we've-known-about-it-for-decades-nobody-is-paying-attention-to-it-that-doesn't-make-Stryd invalid.

41:25Izar Tarandach You know what? No, no, no. That's for sure.

41:27Chris Romeo That's for sure.

41:28Izar Tarandach No, that's not what I'm saying.

41:29Matt Coles That's not what I'm saying.

41:30Chris Romeo I know, I know.

41:31Matt Coles What I'm saying again is—

41:31Izar Tarandach I'll just bring it back to— I agree with you completely. What I'm saying again is we are making names for this esoteric things that happen inside AIs, like, I don't know, cross-context contamination. Oh my God. CCC. Oh, it's a new acronym. Yeah, yeah, yeah, yeah. It looks good. But damn it, it's just applied stupidity. I'm starting a new session, I clear the memory.

42:02Chris Romeo Seems to be basic practice and good hygiene.

42:06Matt Coles Well, actually, it is good hygiene, but doesn't it happen for you all the time? And I'm not defending it, by the way. I'm just saying, if you start a new application, you make an assumption. We've talked about assumptions a lot in threat modeling, right? That you're making an assumption that memory gets cleared for you by the compiler, you know, compiler setup, you know, prefix code to take care of it for you.

42:31Izar Tarandach That would be what professionals call a wrong assumption.

42:36Matt Coles As a computer scientist, as a computer scientist, what do you say?

42:41Chris Romeo Wait, are we professionals?

42:42Izar Tarandach No, no, no, no, no, no. Sorry. Sorry. As a computer scientist, I would expect somebody to make that wrong assumption. As somebody who actually wrote software for a living, I would say, no.

42:53Chris Romeo Are we in the professional category though?

42:56Matt Coles No, I don't know.

42:56Chris Romeo 3 of us?

42:57Izar Tarandach Wait, wait, wait. What profession is it?

42:59Chris Romeo I mean, what profession?

43:02Izar Tarandach No, I mean—

43:04Chris Romeo Casino gambler?

43:08Izar Tarandach No, that's when we're talking about the probability. Crypto. The thing here is, the thing here is we, we, we, when I say we, it's not even the royal we because I don't think that we are because I like to think that we are looking at these things in a different light.

43:26Matt Coles We versus we.

43:28Izar Tarandach Yeah, right. The vertical we as opposed to the horizontal we. There is this rush to create this whole—

43:39Chris Romeo I'm really confused right now. I'm not a professional.

43:42Matt Coles A little Steve Martin there, were you?

43:45Chris Romeo Yeah.

43:45Izar Tarandach There is this whole rush to create a new horizon of thing, a new taxonomy, a new ontology, a new something of things, right? And—

43:59Chris Romeo Oh wait, hold on. I got to steal third. He's on first. Who's on first? Who's on third?

44:08Izar Tarandach That there's this whole, uh, let's invent this whole thing. And, and I think that's coming and saying that something like stride all of a sudden lost its meaning or it's not relevant anymore is— it's such a leap in trying to coin a new revolution where there isn't one.

44:29Chris Romeo No, let me give you an illustration. Let me give you an illustration that might, might help to wrap this, this thing up and put this article to bed. So remember the Model T, right? Ford created this very early model car. I can look at the Model T and say, I can't believe it doesn't have airbags. How do they, you know, it's, it's not a car or seatbelts. It's not a car because it doesn't have airbags and seatbelts. Yes, it's still a car. It's still function. You can still drive it down the road. Have, have other things, have cars progressed? In over the years since the Model T? Yes, of course.

45:10Matt Coles Are they still cars?

45:10Chris Romeo That's what we're talking about here. There are newer things. Yes. Is Stride the latest and greatest thing? No, there are things, there are, there are new method, not methodologies, but, um, mnemonics and things that have been created for threat modeling of AI.

45:26Matt Coles Yep.

45:27Chris Romeo And so why would I try to drive a Model T across the country and expect it to be as safe as a modern-day car?

45:36Izar Tarandach I wouldn't.

45:37Chris Romeo I would look for a modern-day car and I would leave my Model T in the museum. So I just suggested Stripe needs to go in a museum. Dang it.

45:46Matt Coles No, no, no, no, no, no, no.

45:47Izar Tarandach Look, look, look, you got something here. You got something here.

45:51Matt Coles He had something, but he completely went off the rails.

45:55Izar Tarandach He tried to go through, through the whole country, but The Ford T is going to take you from point A to point B. Okay. Same way that a Ferrari is going to take you. Probably it's going to be slower. Depends on the angle of the—

46:10Chris Romeo Oh no, it is going to be slower.

46:11Matt Coles It's going to be slower.

46:13Izar Tarandach You, you, you, you have to remember that for all the lack of airbags, for the fact that the brakes were made of wood, for the— they were actually. My family had a Ford T for a while. But, uh, 1929, not a 1910. But, um, for all the things that today we look at them and go, what? You know what, the brakes still stop the car, the engine still pulls the thing, the wheel still turns the, turns the car around. You are probably going to have to drive differently. And so I'm going to say, you know what, instead of a Ferrari, let's talk about, of a Model T and a Tesla. The Tesla is going to do a lot of stuff for you, but it's going to do the same things that the Model T did. Because what you're looking for is the base functionality. You want to get from point A to point B.

47:09Matt Coles I'm gonna say the car analogy is the wrong analogy here.

47:12Chris Romeo Probably.

47:12Matt Coles It's the motor vehicle analogy.

47:13Chris Romeo We just spent 5 minutes on it.

47:15Matt Coles You did, but I think you're going the wrong way.

47:17Chris Romeo I think you're nice and well defined. Oh, we didn't see the sign.

47:20Izar Tarandach We didn't see the sign.

47:21Chris Romeo Yeah.

47:21Izar Tarandach Yeah.

47:22Chris Romeo Well, road signs. Wrong way.

47:23Matt Coles Road signs or motor vehicle driving laws and regulations and conventions are probably the better example. And I'm touching upon that because as we look further down the article, I know we're running short on time on this episode, but it talks later about how the threat model doesn't have a control to address prompt injection. Well, that's great because that's not STRIDE's job, right? STRIDE's job is to find the threat. STRIDE's job is not to define a control. The control comes from you identify a threat and then you figure out what you're going to do about it.

48:08Chris Romeo Yeah, true.

48:08Matt Coles And so you have conventions and you have standards and you have guidelines about how do you deal with certain threats. STRIDE doesn't tell you that. That's, that's one of my, that's one of my gripes about Stride is it expects an understanding of a lot of knowledge around the threats to be able to address them.

48:28Izar Tarandach That's the whole think like a hacker thing that we—

48:30Matt Coles and if you, and if you don't understand, but also think like a computer scientist or think like a developer or think like somebody who knows how to read API standards, uh, API specifications, you have to understand the technology you're using in order to address a threat. Against that technology. So if the AI model has unexpected output and you identified that in your threat model, but you don't know how to fix that because you don't understand how the technology works, that's a different problem than Stride is broken. That's you as a technology deployer don't understand the technology you're deploying.

49:13Izar Tarandach The, the, the fact is that I think that we, we are fast approaching the rise of, uh, if it hasn't yet and I just don't know about it, the rise of a new, uh, uh, profession, which is the, the AI psychologist, right? Because no, seriously, what, what Matt just, just put down that, you know, the LLM could give you, uh, I won't say bad. I won't say inexact. I would say a different kind of output than you were actually expecting. Now, between you and what generated that output, there are a lot of boxes. Some of them are gray, some of them are white, some of them are black. The black ones, at some point, somebody's going to have to rise up and say, I understand what's happening there, and I can explain to you what you have to do in order to get less of that. It's going to be an AI psychologist, you know.

50:13Matt Coles Is the psychologist for the AI or for the person using the AI?

50:16Izar Tarandach I think that's for the person using it. We are on the psychiatrist step already.

50:20Chris Romeo But, uh, so it's for the AI.

50:24Izar Tarandach It's for the AI. I mean, interesting. It's what Matt's saying. You know that something can go wrong, but you don't know what to do about it. And all of a sudden, when you had code to look at and you could exactly trace, and now I'm going to talk a bit against myself, when you had the code to trace and you could figure out what the path was, then you could go back on it and say, oh, here's the bug, I'm going to fix it. Now that you have the LLM, and I'm not talking about what happens outside with the result of the LLM, later on. That part I have established my position quite forcibly. But inside the black box, the non-explicability of what's happened inside to get to that result, right? That's the bit where you can't go back and find, oh, oh, oh, this weight is the one that caused the distance between the thing and the other thing. And that's what caused the output. You don't have that that level of explicability.

51:28Matt Coles Right, we don't have that, right? We don't know how to do that yet.

51:32Izar Tarandach Exactly.

51:33Matt Coles Because it's non-deterministic also.

51:37Izar Tarandach And it's complicated math.

51:39Chris Romeo But—

51:39Matt Coles Yeah, we don't know how many dimensions there were involved and number of parameters and all that sort of stuff, right?

51:44Izar Tarandach Exactly, exactly. And when we do, we forget because it's a lot, right? But what I'm trying to say is that In between that, what could go wrong and what can we do about it? If you're not able to trace back to the root cause of what went wrong, it's going to be very hard to say, this is what I can do about it. So people come up with all kinds of fences and guardrails and whatnot that go around that, that black box bit and hope for good things.

52:12Matt Coles Yeah. I have a thought exercise for, for, for listeners and for you guys as well, because you may have forgotten it. When you use C or C++, actually there's other languages. No, no, no, no, no.

52:26Izar Tarandach Don't go there. C, C, keep it C. Okay.

52:28Matt Coles All right. I'll keep it C. There are, there are things in C that have undefined behaviors.

52:36Chris Romeo Yes.

52:36Matt Coles Did you throw away using C because of undefined behaviors?

52:41Izar Tarandach No, we defined the standard.

52:44Matt Coles And when you had an application that exhibited an undefined, or sorry, when you had an application that used functionality that may have fallen into the bucket of may exhibit undefined behavior, what'd you do?

53:00Izar Tarandach I called it elegant.

53:05Chris Romeo Elegance.

53:05Matt Coles But this is, this is the exact same. This is a similar problem, right?

53:08Izar Tarandach This is exactly the same thing.

53:09Matt Coles You, you have, you have undefined behavior in the technology and you account for it.

53:15Chris Romeo Right.

53:15Matt Coles That's Stride. May, Stride may point you in that direction, but Stride will not tell you how to address that undefined behavior. Right. You just have to deal with it. And as an application developer in the past, you would've said, well, for X number of boundary cases, something bad is going to happen and we're going to, we're going to 6/7 crash, right? We're just going to, we're just going to bail because there's nothing else we can do.

53:39Chris Romeo I thought you said 6/7 crash for a second. But it was SIGSEV.

53:45Matt Coles SIGSEV.

53:46Izar Tarandach SIGSEV, yeah. You know, now you're talking about levels of behavior, right? Sorry, levels of bad behavior. And one thing is to have a memory exception and end up in a SIGSEV. And another one is having your model say that all of a sudden, I don't know, Something ridiculous that has been said lately. So many options. So many options.

54:16Matt Coles Mathematically proven, something complicated.

54:19Izar Tarandach Exactly. No, something as simple as, yes, I don't know, that group of people are responsible for all the problems in the world, right? So what went wrong here? For one, in one side is, hey, you try to write in a memory area that you don't have a bit that says that you can write. So I'm gonna raise my hands up and, and bail out. The other one is, well, you know what, the thing got trained with a lot of texts and a lot of input from different social media, and it got the impression that this was a fact, but we're not quite sure because, you know, that there was just this amount and that amount, but then it went through reinforcement learning and the person who was reading the thing decided, hey, you know what, this is a fact. So yeah, yeah, yeah, sure. Why not? Go ahead, that's a good answer. And it got into the model somehow. So the, the, the, the factors that could influence that, uh, bad behavior, they are so dispersed and there's, there's such a pipeline of them. And then there's the unexplainability and, and undeciblity. I can't with this.

55:28Chris Romeo Wow.

55:29Matt Coles All right. You should probably end it there before Izar goes completely.

55:33Chris Romeo Apoplectic.

55:35Izar Tarandach I can't say that one too.

55:37Chris Romeo Oh yeah, that's one of the words I can say, so I just go with it when I work.

55:41Izar Tarandach It always comes apoplectic.

55:43Matt Coles If you could, if you could spell it, that would be even better.

55:45Izar Tarandach But yeah, so I, bottom line, I think that, you know, to go back and declare that, that the old ways of looking at what's out there are wrong No, it's dead. The old way, the old way of looking at new things is dead. It's a bit premature. It may show a bit of lack of understanding of the old thing itself. And the, the race to create new things just to, well, let's put it as ulterior motives to pop on social media.

56:24Chris Romeo Yes.

56:24Matt Coles There's more to talk about this article, but let's leave it there.

56:27Chris Romeo What, what? No, no, no, no, no.

56:27Izar Tarandach Talk about this article. No, no, no. I'm not talking about this art school. No, definitely not. Definitely not. No, no, no, no, no, no. Please, please, please don't misunderstand me. But other things that we have seen that run to, you know, create these new paradigms and new approaches. And at the end, they end up doing the same thing.

56:48Chris Romeo Well, people are trying to get famous. Yeah, but you don't get famous by just, you know, reciting an old thing.

56:53Izar Tarandach True. But you can get famous by pointing out that you know, you can look at something in a different way without dismissing everything that came before.

57:08Chris Romeo That's, that's a whole other episode right there. That is a bit of a phenomena. You've just, you've just hit on a phenomena of that, that seems like it's in the last 5 years or so that to create something new, you have to break something else down. Is like a pathway that people are approaching fame. And not the fame in the 1980s NBC television program. Not that.

57:37Izar Tarandach I'm gonna leave forever.

57:39Chris Romeo I knew it was in your head, so I had to draw it out.

57:41Izar Tarandach I can't, I can't, I can't.

57:43Chris Romeo All right, with that, we can no longer be here because we don't— we've already used our one 1980s television theme song. That we could sing. And if we let another one sneak out, the FCC will shut us down. So we have to—

57:58Matt Coles it's fair use at this point.

58:01Chris Romeo I like it.

58:02Izar Tarandach The way that you are saying means that anything automatic listening to this thing can actually recognize the song that I am singing, which I'm going to take as a compliment.

58:10Matt Coles Yeah.

58:11Chris Romeo No, I think we knew what it was. It worked.

58:13Izar Tarandach Oh, no, no, no. You baited that one. Come on.

58:17Chris Romeo Of course I did. That's what I do. Folks, thanks for hanging around talking about npm changes, strides forward in the future and whatnot. And when it comes to AI and what—

58:32Matt Coles and Model Ts.

58:33Chris Romeo And Model Ts. Yes.

58:34Izar Tarandach Where are we going? We don't need stride. Yeah.

58:40Matt Coles Or brakes.

58:42Izar Tarandach Wooden or not.

58:44Chris Romeo We do need to refactor the flux capacitor though. And I'll leave leave you with that. As we say, adieu. Adieu. Yes, we do.

Transcript supplied by AssemblyAI. It may contain transcription errors.

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