# The Roller Coaster of Risk: A Threat Modeler's Perspective

URL: https://securitytable.ai/the-roller-coaster-of-risk-a-threat-modeler-s-perspective/
Published: 2025-11-26
Duration: 2734 seconds
Season: 3
Episode: 20
Hosts: Chris Romeo, Izar Tarandach, Matt Coles

## Show notes and chapters

What do roller coasters and threat modeling have in common? More than you'd think. In this episode, we explore how security professionals view risk differently than everyone else—and why that matters. From roller coaster anxiety to the ethics of identifying danger, we dive into the unique mindset that comes with being a threat modeler. Because once you learn to see threats everywhere, there's no going back.

Follow AI Security Table:

➜ Home: [https://securitytable.ai/](https://securitytable.ai/)

➜ X: [https://x.com/AISecurityTable](https://x.com/AISecurityTable)

➜ LinkedIn: [https://www.linkedin.com/company/ai-security-table/](https://www.linkedin.com/company/ai-security-table/)

➜ YouTube: [https://www.youtube.com/@AISecurityTable](https://www.youtube.com/@AISecurityTable)

## Transcript

**Chris Romeo (0:10)**: Hey folks, welcome to a special episode of the Security Table coming from Matt's bedroom.

**Izar Tarandach (0:16)**: Perfekt.

**Chris Romeo (0:16)**: As you can see with the purple walls, if you're watching this thing on YouTube, Matt has a bit of a purple haze going on in his bedroom. We'll let you For the younger generations out there, we'll let you Google that, figure out what that means.

**Matt Coles (0:31)**: Why am I hearing the Watchtower, dude?

**Izar Tarandach (0:34)**: Why am I hearing Prince in the background? Why, Matt?

**Chris Romeo (0:40)**: Have you ever dressed up as Prince for Halloween?

**Matt Coles (0:42)**: No.

**Chris Romeo (0:43)**: Oh God, he's already got a visual effect.

**Izar Tarandach (0:47)**: Oh God, now I got a migraine.

**Chris Romeo (0:50)**: I have not either. I've, I've never been a big Prince fan. I mean, I know Prince's anthology of music, just never been a giant fan that I would be like, hey, put some Prince on.

**Matt Coles (1:04)**: Sure, it's, it's not that kind of music. It's not, he's got some kind of music, at least.

**Izar Tarandach (1:12)**: I mean, anybody who changes their name for a symbol, I'll give them a—

**Chris Romeo (1:16)**: but then changes it back, so it's like, come on.

**Izar Tarandach (1:19)**: Oh, he changed it back?

**Matt Coles (1:20)**: Madonna did the same thing. So, you know, it's—

**Chris Romeo (1:22)**: she did.

**Izar Tarandach (1:23)**: What was the symbol?

**Chris Romeo (1:24)**: I don't remember that one.

**Izar Tarandach (1:27)**: Two forward-pointing cones. What, what, what the—

**Chris Romeo (1:31)**: I was having a conversation with somebody a couple days ago, and they're like— somehow we were talking about Madonna. They're like, Madonna's dead. I'm like, no, Madonna's not dead.

**Matt Coles (1:39)**: Really?

**Chris Romeo (1:40)**: And I had to double-check. No, no, she's not, she's not. My friend had bad information.

**Matt Coles (1:45)**: Of course.

**Chris Romeo (1:45)**: I'm like, what? No, no, not dead. Again, I think it happened in real life. It could have been back to that Purple Haze thing, kind of tying the whole conversation together. No, she's just a material girl living in a material world. Wasn't that Cyndi Lauper?

**Matt Coles (2:01)**: Folk, folk, folk.

**Izar Tarandach (2:03)**: Is it?

**Chris Romeo (2:04)**: No, I just said it because it's so easy to confuse. There's an illustration about threat modeling there somewhere. It's so easy to confuse.

**Matt Coles (2:11)**: We went from '60s to '80s. To '70s.

**Chris Romeo (2:18)**: Let's hit the '90s.

**Izar Tarandach (2:18)**: Wait, wait, wait, you looking for consistency here?

**Chris Romeo (2:22)**: Yeah, you were looking at 100+ episodes, there's no consistency. What about Milli Vanilli?

**Izar Tarandach (2:28)**: Ooh, that was a dig, archaeological dig.

**Matt Coles (2:33)**: Well, at least it wasn't Ice Ice Baby.

**Chris Romeo (2:36)**: Oh, come on, that's one of the best songs of the '90s. Name a better song of the '90s than Ice Ice Baby. It's more iconic.

**Izar Tarandach (2:42)**: Uh, the '90s, the one— I don't think I was listening to songs in the '90s.

**Chris Romeo (2:45)**: One with Marky Mark and the Funky Bunch? Uh, Good Times.

**Matt Coles (2:51)**: Is that the name of it?

**Chris Romeo (2:52)**: Yeah, of course it is. I'm a '90s anthology myself.

**Izar Tarandach (2:56)**: I have to say, music stopped in the '80s, okay? Everything after that is a remix.

**Chris Romeo (3:04)**: I mean, everything's a remix in life.

**Matt Coles (3:08)**: All right, come on. So if you're going to talk about this, we have to talk about Run-DMC and Walk This Way. When they did it live with Aerosmith.

**Chris Romeo (3:16)**: I mean, that was the first really crossover between two major genres of music that really had ever—

**Izar Tarandach (3:26)**: No, a real, a real crossover would be the Monty Python Funny Walk sketch with Walk This Way in the background. Okay, that's a mix.

**Chris Romeo (3:40)**: That's a very, very eclectic mix of—

**Izar Tarandach (3:43)**: there you go—

**Chris Romeo (3:43)**: comedy and music, which is a good thing. So yeah, I rode the Aerosmith roller coaster the last couple of weeks. Well, I didn't ride it for weeks, but I don't know if you're aware of this at Mickey World in Florida, there's this rock and roll coaster.

**Izar Tarandach (4:01)**: Yep.

**Chris Romeo (4:02)**: And it goes upside down twice. So, and so you'll You may get a chuckle out of this. So I'm standing in line waiting to go on this thinking, have I made a bad decision for my future, for my life? Yes.

**Matt Coles (4:16)**: Yes, you have.

**Chris Romeo (4:17)**: And then I look over and there are 7-year-old girls in the line. And so I'm thinking to myself, if I cannot stay in this line yet a 7-year-old girl can ride this ride, then that doesn't say a whole lot about me.

**Izar Tarandach (4:32)**: On the other hand, 7-year-olds are durable.

**Matt Coles (4:35)**: You're, you're, you're not.

**Izar Tarandach (4:36)**: that's one.

**Chris Romeo (4:38)**: But my pride was then—

**Izar Tarandach (4:39)**: On the other hand, you got more experience in life than them, and you know what could go wrong.

**Chris Romeo (4:46)**: So true, it could threat model the whole time, right?

**Izar Tarandach (4:48)**: It actually goes to a very, very important point that I think is not made enough. As threat modelers, we are taking one for humanity constantly, right? Once you're a threat modeler, you never look at life the same way.

**Chris Romeo (5:07)**: Like, that's true.

**Izar Tarandach (5:08)**: We have— we avoid doing a, a whole number of things because we know what could go wrong so that you people can keep doing them. So you're welcome.

**Chris Romeo (5:17)**: Well, I still rode the roller coaster. Nothing went wrong. I survived.

**Matt Coles (5:21)**: Hold on, so what you're saying is you don't need domain expertise in anything if you have threat modeling experience?

**Chris Romeo (5:29)**: Yes.

**Izar Tarandach (5:31)**: And by the way, next Veterans Day, hug a truck modeler, because we are here on the line for you every single day. We know what could go wrong and we keep doing it.

**Chris Romeo (5:42)**: So wait, no domain expertise needed. You can just BS your way through anything that you get put in front of.

**Izar Tarandach (5:50)**: You can't point at anything and say that could go wrong. That's kind of the way it is. Basically just Muppet Show your, your, your, through your life.

**Matt Coles (6:00)**: All right. So the big question, Chris, obviously you survived the roller coaster. Did the 7-year-olds?

**Chris Romeo (6:05)**: Oh yeah. They were, they were, they were the ones with their arms in the air going like this. I'm holding on for dear life going, hmm, this could be it. This could be it. Oh, survived the next one. Come on. Keep that. It was a lot.

**Izar Tarandach (6:16)**: Are you sure they were the same 7-year-olds that went in?

**Matt Coles (6:21)**: They were doppelgangers. Came out.

**Izar Tarandach (6:23)**: They are replaceable, you know.

**Chris Romeo (6:26)**: No, I'm pretty sure, pretty sure they, uh, they survived and probably had more fun than I did.

**Izar Tarandach (6:33)**: Wait, wait, wait, wait, no. Imagine yourself back then, you're going up the first climb, the things that are going through your head, right? You are questioning constantly, what did I do to get here?

**Matt Coles (6:46)**: And what went wrong? Leading up to this.

**Chris Romeo (6:49)**: Exactly.

**Izar Tarandach (6:50)**: And, and, and then I think about that fella that created the— what was it? The roller— the suicide roller coaster. The one that actually will kill you when it goes down. Have you read this?

**Chris Romeo (7:01)**: No.

**Izar Tarandach (7:02)**: Some, some, some fellow actually like planned, projected one where the, the fall is like at such an angle and such a speed and whatnot that there's no way that you're going to reach the bottom alive.

**Chris Romeo (7:14)**: Wow.

**Izar Tarandach (7:15)**: And I keep thinking to myself, what goes through somebody's head as they're doing that climb?

**Chris Romeo (7:23)**: Yeah, I got a 50-50 chance of making it.

**Matt Coles (7:26)**: Yeah, it's a fit to purpose, you know. What could go wrong? Well, they could survive everything.

**Izar Tarandach (7:33)**: Actually, no, because it's designed that way, so it would actually— if it works as designed, nothing would go wrong. So Works in their favor.

**Chris Romeo (7:43)**: We're going to need to bring morality into the threat modeling, the fifth question.

**Matt Coles (7:46)**: You mean ethics?

**Izar Tarandach (7:48)**: Ethics and morality. That's a whole time. We have to get to that one at some point.

**Chris Romeo (7:52)**: We brushed on it a few episodes ago.

**Izar Tarandach (7:56)**: Indeed. Indeed.

**Chris Romeo (7:57)**: Just don't remember what the conclusion was, but I could say that for a lot of episodes.

**Matt Coles (8:02)**: We sort of go off track, which is something that could go wrong on a roller coaster.

**Izar Tarandach (8:07)**: I'll put a call to the guy in Australia and ask what was it.

**Chris Romeo (8:11)**: That's true. Shout out to our fan in Australia. Thanks for tuning in.

**Izar Tarandach (8:17)**: How's it down under?

**Chris Romeo (8:19)**: If we ever have a call-in line going out to Australia, if it happens, we know it got there. Takes another day, an extra day though, to get there. But okay, so I think we've kind of made our way through almost 10 minutes of an episode. Izar, you had what you described, you self-described as an epiphany.

**Matt Coles (8:48)**: You had a Delphi moment.

**Izar Tarandach (8:50)**: A shock.

**Chris Romeo (8:50)**: Delphi, like the car company that makes car parts?

**Matt Coles (8:54)**: Or the programming language?

**Chris Romeo (8:57)**: Never used Delphi because it was Visual Pascal. I was a Visual Basic guy. I like Visual Basic better. I don't know why.

**Matt Coles (9:04)**: Everyone does.

**Izar Tarandach (9:06)**: Nobody does.

**Matt Coles (9:08)**: Better than Pascal?

**Chris Romeo (9:11)**: Or Visual Pascal, even better.

**Izar Tarandach (9:14)**: I had to watch people doing Visual C and C++. Okay, so no.

**Matt Coles (9:20)**: All right. As a C and C++ programmer, visual? It was all visual. If you couldn't see, how were you going to program?

**Izar Tarandach (9:33)**: The only place that Visual has in C and C++ is by writing vi before the file name. That's it. That's all the vi that you need for C++.

**Matt Coles (9:45)**: Not ed?

**Izar Tarandach (9:47)**: No, no, no, no, no. cat. cat to the terminal, and then you correct with sed.

**Chris Romeo (9:53)**: That's some real gangster command line right there. If you're using sed to edit concatenated file, and you're doing it all with like complex regexes on a 24x40 terminal.

**Matt Coles (10:13)**: Green screen.

**Chris Romeo (10:14)**: I'm blinking. It's flashing too the whole time.

**Izar Tarandach (10:18)**: Yes, that's the only way.

**Chris Romeo (10:20)**: Seeing every other sign of the characters. So, all right, well, Izar, what's your epiphany?

**Izar Tarandach (10:26)**: So the epiphany, epiphany. I was reflecting as one does coming back from conferences, and that's that kind of stuff. And I think that threat modeling got to a state of— what was the word, Matt? I always get confused with ending E's.

**Matt Coles (10:48)**: I'm not going to be able to help you on this. I don't know what your epiphany—

**Izar Tarandach (10:51)**: you do, you do. The one from the shoes with the switch.

**Chris Romeo (10:55)**: Oh, Nike.

**Izar Tarandach (10:57)**: Nike. So I think that threat modeling got to a Nike moment. Just do it. Because I went to the Oracle. That's how we got to Delphi.

**Matt Coles (11:10)**: If people are following this, just making sure you didn't go to Larry Ellison's Oracle, I hope.

**Izar Tarandach (11:16)**: No, no, no, no, no, no, no. That one, we know how it ends.

**Chris Romeo (11:19)**: You didn't travel to Delphi, right? Nope.

**Izar Tarandach (11:22)**: Nope. Can't find it on the map.

**Chris Romeo (11:24)**: That was a city, wasn't it? I think that's where the Oracle was. The Oracle of Delphi. Yeah. Okay.

**Izar Tarandach (11:29)**: No, just checking.

**Chris Romeo (11:29)**: I'm, I'm not a history, yeah, his flight got delayed, redirected, you know, and I freaking use ChatGPT.

**Izar Tarandach (11:36)**: Continuing.

**Matt Coles (11:38)**: Well, I asked, oh, pause, pause. Did you just call ChatGPT the Oracle?

**Izar Tarandach (11:46)**: It's what everybody else seems to find their, their, their answers nowadays. And most of the time they come back as clues and enigmas and that kind of thing, and then people just impart whatever meaning they want to what comes back. So I did it to mine, and I asked it, at this stage of the state of the art in threat modeling, what are the 3 top challenges to be solved, and what are the probabilities that these are indeed each of the top 3? So what I got was When I say top 3, I mean if you ask a broad mix of practitioners, researchers, and tool vendors today, what are the 3 problems that most constrain the impact of threat modeling in the real world? Things that we deal with every day.

**Chris Romeo (12:33)**: Okay.

**Izar Tarandach (12:34)**: First one came: making threat modeling truly continuous and scalable in modern SDLC. Second one was usability, skills gap, and democratization. And the third one was reliable automation and AI assistance, especially with LLMs. The first two got more than 80% and the third one got 70%.

**Matt Coles (13:01)**: Hmm.

**Izar Tarandach (13:04)**: So why do I bring this back to Nikkei? Because in my gut, I think that The world has been given enough methodologies and guides and books, like, to cover the whole gamut of where you need to apply this. You can do threat modeling once in a lifetime, you can do threat modeling with, uh, Italian dishes, you can do it continuously with every story and every sprint. You can choose to do whatever you want, right? And on the usability, you can do it with catalogs, you can do it by knowing what you know, you can do by asking people, you can do by imagining stuff, you can do by different layers of cake that has nothing to do one flavor with the other. You can do it in so many ways that today to come and say, no, we have a problem with usability, is to come and say, okay, this whole body of knowledge here, this whole body of experience here, let's ignore it for a second and say, no, no, no, I still can't use this thing. I'm special. I'm a flower. I can't. I have to do it a different way. I have to do a special way. So at this point, I'm just saying, just do it.

**Chris Romeo (14:23)**: I'm trying to figure out what this voice is like. There's two voices and I don't—

**Matt Coles (14:28)**: uh, okay, he used Sora to, to set it to some lilting, uh, sound.

**Izar Tarandach (14:33)**: Only two? Because in here there's way more. But anyway, So at this point I'm asking myself if these are the top challenges today.

**Matt Coles (14:44)**: Well, so interestingly, I asked a different LLM the same question just now.

**Izar Tarandach (14:50)**: My LLM will battle your LLM.

**Matt Coles (14:53)**: Gemini will crush ChatGPT.

**Izar Tarandach (14:56)**: Oh yeah. Very special LLM.

**Chris Romeo (15:00)**: Wow, a lot of smack talk in here. This is like geek smack talking now.

**Matt Coles (15:03)**: So, so I agree with two of yours. And the skills gap and the skillability problem.

**Izar Tarandach (15:11)**: Wait, wait, wait, wait. Look at the top and see if the first sentence is, what did ChatGPT say?

**Chris Romeo (15:16)**: Okay, go.

**Matt Coles (15:18)**: I'll ask it what it thinks ChatGPT said. Just a moment. So, and actually if it asks ChatGPT for real, I'll be really— So, the skills gap at 95%. Scalability at 85% and conflicting with Agile and DevOps speed at 90%. Hmm. So roadblocks in the development process is causing roadblocks in threat modeling. Hmm.

**Izar Tarandach (15:53)**: Hmm. No, that's usability again.

**Matt Coles (15:56)**: Well, no, it's not.

**Izar Tarandach (15:58)**: Why not?

**Matt Coles (15:59)**: It's perception.

**Izar Tarandach (16:01)**: Of what?

**Matt Coles (16:02)**: Of this being a problem. Things that slow me down.

**Izar Tarandach (16:07)**: That's like being in a completely out there example. It's like being in line for a roller coaster and seeing 7-year-olds and saying, this is a problem. Like, I mean, everybody's going to get to the roller coaster one way or another.

**Matt Coles (16:26)**: You, you misunderstand the consternation that Chris was having, although Chris is being really quiet about it right now.

**Izar Tarandach (16:32)**: He's reviving the moment.

**Chris Romeo (16:34)**: I'm riding the roller coaster.

**Izar Tarandach (16:37)**: He's asking Claude.

**Chris Romeo (16:39)**: I don't ask LLMs. I am an LLM.

**Izar Tarandach (16:43)**: Untrained, but an LLM. Yeah, 100%.

**Chris Romeo (16:47)**: But I have a special power. I'm full of opinions.

**Matt Coles (16:50)**: And is our, can you, uh, can you reveal your shirt to all there?

**Chris Romeo (16:58)**: Just because you passed the Turing test doesn't mean you're smart.

**Izar Tarandach (17:06)**: Okay, so what do we do with this? Like, the three of us together should be able to point at some other challenges that the LLMs didn't get, but I'm having a problem here.

**Chris Romeo (17:20)**: Yeah, I mean, scalability is certainly the big one.

**Izar Tarandach (17:25)**: But again, scalability, just do it. Just do it.

**Chris Romeo (17:28)**: Just do it. Just do it doesn't work in the real world.

**Izar Tarandach (17:32)**: Do it.

**Chris Romeo (17:32)**: Tell people.

**Izar Tarandach (17:33)**: Find what didn't work, what doesn't scale in your place, and change that. I know I'm being oversimplistic here, but if you don't do it, you don't figure out those things.

**Chris Romeo (17:43)**: Yeah. I mean, you're discounting organizational friction. Which means you can't just go out and change it.

**Izar Tarandach (17:52)**: HR told me to always discount organizational friction, but, but no, no, seriously, seriously, if you find that organizational friction is the thing holding you back, then you have to find what is it that you need to oil so that that friction disappears or goes down, right?

**Chris Romeo (18:13)**: Sure.

**Izar Tarandach (18:13)**: But if you don't do it and you don't identify that that's your problem, that that's the wheel that you have to oil.

**Chris Romeo (18:17)**: I'm just saying, I'm just saying.

**Izar Tarandach (18:19)**: You're not going anywhere.

**Chris Romeo (18:20)**: The outcome is not as easy as you're making it sound.

**Izar Tarandach (18:24)**: No, no, no, no, no. I'm not saying, I'm not saying that it is. No, I'm not saying that everything has been solved. What I'm saying is we have enough on the table, right? Think Apollo 13. We are in a room looking at the table saying what we have in the capsule that the astronauts can use. We have enough on the table that we can put together something that works. So to keep saying, I'm not going to do it because the perfect thing hasn't come yet. I'm not going to do it because the perfect tool hasn't come yet. I'm not going to do it because the perfect methodology hasn't come yet.

**Chris Romeo (18:56)**: I mean, I haven't heard any of those excuses for why people wouldn't, can't do threat modeling.

**Izar Tarandach (19:01)**: I have. I have heard enough of that will not work here because.

**Matt Coles (19:07)**: I've heard that, I've heard that part, but not for the reasons you mentioned. Maybe consistency, like it's not going to work here because if we're not consistent, we're going to have different, you know, difference of different views of this thing, and it's not going to be practical for us, especially if people change roles, right? So if you have developers who are working on different projects, if you don't have consistency of practice within your organization, you're gonna get— you're gonna have challenges adopting threat modeling. I've heard that, but not that, uh, not— if somebody, if somebody's arguing that there isn't a perfect tool, they're not interested in doing threat modeling, right? That's a non—

**Chris Romeo (19:53)**: it's an excuse, right?

**Matt Coles (19:55)**: It's a non-argument.

**Chris Romeo (19:56)**: Yeah, it's a way to make you go away.

**Izar Tarandach (19:59)**: Actually, it's an excuse is a very, it's a very apt comment. I think that a lot of what's happening out there is people making excuses, especially because we have all these things in the table. So what I'm saying is we are at a point where you stop making excuses, you pick something up from the table and you do it and you see if it works or not. That's a big challenge now for me, getting people to pick stuff from the table and actually do it.

**Matt Coles (20:24)**: So try and trial and error. Is becoming a problem, I think, right? We have people under a lot of pressure to get stuff out the door. There's a lot of pressure to use AI. There's a lot of pressure to just get— remove all the roadblocks. And so trial and error is itself a roadblock. If they have to trial and error something to figure out what works, they're engineering their process, not engineering their product. Yes, and I don't see a problem with engineering the process. That's— but that's our view, but that's not their view often, right? Developers don't want to spend time re-architecting their process. They want to spend time architecting a thing.

**Izar Tarandach (21:12)**: Mm-hmm. That's the thing. So bringing back to a different t-shirt that I usually have. I have this one that says the process is bigger than outcome, right? Because without a process, you can reach an outcome, but you won't be able to reach it consistently because you don't have a process to tweak or a process to follow. Like, you can bake a cake from whatever you find in the cupboard, and it may even come out good, but tomorrow you won't be able to make the same cupcake because you don't have a process to get there. So the process is more important than the outcome, in my view at least, and in the T-shirt's view, and apparently the US Navy SEALs.

**Matt Coles (21:56)**: But, but, uh, but if you, if you have a functioning process, why screw with it? Right? Why?

**Izar Tarandach (22:04)**: Because no, if it's functioning, if it's functioning, yes. But if you're going to add something more like threat modeling to it, then you are by definition already screwing with it. So you might as well tweak, tweak it. Until it works again. And probably the outcome is going to be better than it was before. If your outcome is already perfect, hey, don't touch it. Go for it.

**Matt Coles (22:26)**: Well, so here's another snag in all this. Roles and responsibilities. Whose responsibility is it to screw with the engineering process? And, sorry, to tweak the engineering process?

**Izar Tarandach (22:38)**: Oh, sorry, because for a moment there I thought that you were talking about me, because usually I'm the one screwing the engineering process.

**Chris Romeo (22:44)**: At least that's what people say at the meeting, at the conclusion meetings.

**Izar Tarandach (22:48)**: So that's my responsibility.

**Matt Coles (22:49)**: Retrospective. Isar screwed with the process. Who let him in here?

**Izar Tarandach (22:54)**: Okay, that's a t-shirt. But no, the point is retrospectives are great. Okay. Because they usually, some of them, at least most of them. To me end up in, if only we had threat model that day. But, uh, then people come in and say, yeah, we could have, but it would have been, what's it that they say, big lift in the beginning.

**Matt Coles (23:25)**: Heavy lift.

**Izar Tarandach (23:26)**: A heavy lift in the beginning.

**Chris Romeo (23:28)**: That's the new excuse.

**Izar Tarandach (23:31)**: No, and you know what? Yes, we have this box here on the table. That says heavy lift in the beginning, but we have this other box here on the table that says a bit every time. So you don't like that box, take that one.

**Chris Romeo (23:46)**: Yeah, back to your point that there's multiple options.

**Izar Tarandach (23:49)**: Exactly.

**Chris Romeo (23:50)**: To do this thing. Now here's the— let me ask you this. Let me ask you this question. See if this resonates with you guys. Is part of the problem with enterprise threat modeling adoption that we don't have enough Maverick-style leaders that are pushing the envelope and trying to change things?

**Izar Tarandach (24:13)**: What's a Maverick? No, sorry, leader of what?

**Chris Romeo (24:17)**: So somebody who's on the security team trying to press threat modeling forward, that's people pushing everybody's buttons to try to cause change.

**Izar Tarandach (24:27)**: That is a horrible place.

**Matt Coles (24:29)**: Yeah, go ahead. You first.

**Izar Tarandach (24:31)**: No, I was going to say that that's a horrible place to be pushing the buttons because people in the security team know that that needs to happen.

**Chris Romeo (24:42)**: No, I meant like there is somebody who's outwardly trying to move threat modeling forward across the entire organization.

**Izar Tarandach (24:48)**: We are the guys who sit back and say, well, used to be, well, sometimes still, that sit back and say, if only they would do the things that I'm asking them to do. Okay, we've been telling people to do things, asking them to do things for X amount of years. Here we are. I would say, how come we don't have a maverick enough leader to look at the security team and say, those guys have been repeating the same thing for the last couple of years, perhaps it's time that I listen to them and do something about it?

**Chris Romeo (25:18)**: Yeah, see, like, my approach in the enterprise was always to just start getting people doing it. I didn't go to their leadership structure and go, we have this great idea, we need you to— no, screw you, we're gonna, we're gonna do this from the grassroots until it gets to the point where it's like it starts to catch on and then it's got a life of its own and you can't really squash it because it's, it's got enough of a foundation underneath it.

**Izar Tarandach (25:41)**: The problem nowadays I find is that there is substance in the universe that's more expensive than nobody unobnitonium, and that is developer time. Screw developer time and bad things happen to you. But now perhaps that everybody's using LLM, we'll get some— exactly. The black helicopters come by.

**Chris Romeo (26:06)**: You gotta wear Teflon to work. That's all I'm saying.

**Izar Tarandach (26:09)**: But the thing is, perhaps now with LLMs, now that everybody is vibe coding their way through life, developers will finally have some more time to do the stuff.

**Chris Romeo (26:17)**: They got lots of time. What are we talking about? They got half a day free now.

**Matt Coles (26:24)**: Well, so here's— so the alternative is we're talking to the wrong people. We should be talking to the agents, not to the developers.

**Izar Tarandach (26:31)**: I started talking to the agents. I did. No, no, no, no, I did.

**Chris Romeo (26:34)**: That's how we got here.

**Izar Tarandach (26:36)**: No, no, no, no, no, no, no, that was the Oracle. But I started proposing to my developers that want to use agents that Could we just play with that agents.md file in your directory before we start doing stuff, before we start the planning stage and things? And some good stuff happens there, but it's not threat modeling per se, because what's going to happen there is going to be plan to code. So you're going to end up with code that is I'm not going to say marginally because I don't have numbers, but it might be more secure than code without the agents.md file. But still, it's not direct modeling. The, the thing, oh my God, it's even worse now that the design is emerging and it's not even emerging from somebody's head. It's emerging from somebody's agent's thing.

**Chris Romeo (27:35)**: That's just a way of saying you don't have a design.

**Matt Coles (27:37)**: Right, you're letting it evolve through the Agile process. Again, that's the— that goes back to the Agile development process and threat modeling are mostly incompatible, and not because of process, but because of the way that systems get implemented. As implementation is the design.

**Izar Tarandach (28:05)**: On the other hand, because of the way these agents work, I'm finding that many times you end up with similar designs to different problems because they're taking their input from the body of knowledge out there, right?

**Matt Coles (28:20)**: Yep.

**Izar Tarandach (28:20)**: So what could be more standardized than, than that? And including the fact that they don't have creativity built in, you end up with cookie-cutter copies of systems where just the data fields names and the web UI fields names change.

**Matt Coles (28:37)**: So what you're really saying is if you, if you poison, I mean modify the training data, you can get your pre-threat modeled components in and basically give them paved roads to work with that are already pre-approved and pre-secure.

**Izar Tarandach (28:54)**: So the way that we were talking about it in 2000 and nothing, 2010, about the security toolbox where we had the predefined Legos that are secure. You're saying that now we should feed this thing not to the developers, but to the LLMs that the developers are using. And therefore the LLMs, okay, close everything down, we solve the problem.

**Matt Coles (29:17)**: And then the developers don't have a choice. I want this thing. This thing comes out pre-baked. Now, obviously that's not going to happen.

**Izar Tarandach (29:25)**: Why?

**Matt Coles (29:26)**: Well, because somebody will screw it.

**Izar Tarandach (29:28)**: Somebody will screw it up. Yeah, no, that's for sure.

**Matt Coles (29:30)**: They'll put it in different orders and it won't work the way it's supposed to.

**Izar Tarandach (29:34)**: Might even be me. But in theory, there's no reason why it shouldn't work. Like, take, build enough of a corpus of well-designed systems and use that to fine-tune an LLM. In theory, that should ground the thing enough so that you get good designs out of it.

**Chris Romeo (29:56)**: Yeah. But you know what the biggest catch is? Where you, where are you gonna find well-designed systems from?

**Izar Tarandach (30:02)**: That's, that's the one. And the second is, again, you're limiting creativity because you are basically pointing at a catalog of these are the choices that you have.

**Chris Romeo (30:11)**: Well, I mean, LLMs have never had an original thought.

**Izar Tarandach (30:14)**: Yep.

**Matt Coles (30:15)**: And with the, and with the push towards, you know, validated components and things like that. We're going to that catalog eventually. The problem is the individual building blocks may be secure. It's the integrations where the new security problems enter, right? It's how you take these building blocks and stitch them together in these various ways that you're going to get the problems that you don't know about yet.

**Izar Tarandach (30:42)**: So perhaps we have to go the other way around. Instead of training them to feed us answers that they have seen before and know are secure, we should train them to recognize solutions that they haven't seen before and therefore might not be secure. And that's where the person steps up and says, oh, interesting problem, let's look at it.

**Chris Romeo (31:07)**: Hmm, may have solved something. I don't really understand what it is, but we may have solved something.

**Matt Coles (31:13)**: We also, we also aren't doing threat modeling at this point. We're now, we're now doing solution design.

**Chris Romeo (31:19)**: Yeah.

**Izar Tarandach (31:19)**: Let's see. This is not bad at all. Plus I heard it pays much more.

**Chris Romeo (31:25)**: These are just changed careers live on the air.

**Izar Tarandach (31:30)**: No, threat modeling.

**Matt Coles (31:32)**: Threat modeling. Just do it while the threat modelers are like, go do something else.

**Izar Tarandach (31:39)**: No, but wait, back in the manifesto, we said do threat modeling over talking about it, right? So I think that I'm going back to that and saying, stop talking about it and pick the pieces from the table and do it.

**Chris Romeo (31:53)**: Sounds so simple.

**Izar Tarandach (31:55)**: It sounds so simple, but if you don't do it, then how do you know how complicated it is? That's why I keep— because, you know, I was thinking about back about TMC and the presentation that we saw there. We saw really good stuff, really nice stuff.

**Matt Coles (32:12)**: ThreatModCon.

**Izar Tarandach (32:14)**: Yeah, but did we see anything new? Did we see anything that changes significantly the way things are done?

**Matt Coles (32:22)**: Yes.

**Izar Tarandach (32:23)**: Or that puts a new problem? What?

**Matt Coles (32:25)**: Okay, so we saw a new— we saw a method of gamification that helps, that is a way for folks to get more— to be— for threat modeling to be more approachable.

**Izar Tarandach (32:35)**: Yeah. And I loved it. I really thought that it was really well thought, it was super creative. It was super fun to watch. And I go back to my college days and I think, if I couldn't get 5 geeks back then to play Dungeons& Dragons, what makes me think that now I'm going to manage to get 20 developers, which have the unobtainium developer time in front of their faces, to stop what they're doing to play Dungeons& Dragons so that eventually they may end up thinking that threat modeling is more approachable.

**Matt Coles (33:11)**: You can't solve everything, but you asked, you asked if there was anything innovative and that was—

**Izar Tarandach (33:17)**: Yeah, yeah, yeah. No, no, that is innovative by itself, but in the scope of the things that ChatGPT spewed out as the top 3 problems.

**Matt Coles (33:30)**: By the way, can you refresh my memory? What were the top 3? Because I did ask Gemini what it thought. Scalability, usability.

**Chris Romeo (33:35)**: Scalability, usability.

**Izar Tarandach (33:38)**: Security and the use of LLMs. The third one is just trying to look for a job.

**Matt Coles (33:45)**: So Gemini said, I bet, I bet that, I'm willing to bet that the challenge you mentioned was something like lack of organizational buy-in.

**Izar Tarandach (33:56)**: Wait, wait, wait, let me see if I have it here.

**Matt Coles (33:58)**: I'm going to tell it it was a self-flag for using LLMs.

**Izar Tarandach (34:02)**: Wait, let me see if I have it here. Well, it did say about democratization, right? It says, um, poor onboarding. New engineers and contributors, especially in OSS, rarely get a simple actionable way to participate in TM. Okay, let's talk threat modeling in open source for a second, right? How many open source projects we know that the developers approach with a threat model in mind? And the reason why I'm bringing it out is Open source people usually do it for love. They, they, they love the projects that they are working on. They love the things that they are solving. So these people are doing it with a different motivator and they definitely have the motivation to make it as secure as they can.

**Matt Coles (34:49)**: Mm-hmm.

**Chris Romeo (34:49)**: Mm-hmm.

**Izar Tarandach (34:49)**: How many projects have we seen that start with a good, okay, people, let's sit down and do a threat model?

**Chris Romeo (34:55)**: Uh, only the ones where a security company sponsored the threat model and performed it for them. Trailer.

**Izar Tarandach (35:04)**: And even those, even those, I'm going to go ahead and say they weren't there at the beginning of the project.

**Chris Romeo (35:10)**: All right, you guys want me to put you on the spot completely, potentially embarrass you on a live podcast?

**Matt Coles (35:16)**: You're going to do that, aren't you? Using our own dog food. Yes.

**Chris Romeo (35:19)**: So when you started working on PyTM, did you first sit down and create a design and create a threat model for it?

**Izar Tarandach (35:29)**: If you go back to the first README, of PyTM, one of the first things that you're going to find in there was, yes, we use eval. Yes, we know it's bad. And yes, here it is why we decided to use it. So there.

**Chris Romeo (35:46)**: Now, is that a threat model or is that just one potential issue?

**Izar Tarandach (35:50)**: It was the one threat that was identified back then. It's a script, it's a library. It's not reaching out to anywhere. It's not storing anything.

**Matt Coles (36:00)**: Sensitive.

**Izar Tarandach (36:01)**: That was the one problem that we found. We drew the vector, we said this is how this could be attacked, this is why we don't think that it's an actual issue. Screw you.

**Chris Romeo (36:14)**: Mr. Coles, do you agree with the testimony from Mr. Terendosch?

**Izar Tarandach (36:19)**: I have no recollection.

**Matt Coles (36:20)**: I, I, I, uh, I'm debating between that and we paid attention to the Python guide on using eval and copied its text a bit.

**Izar Tarandach (36:31)**: There you go.

**Matt Coles (36:32)**: That's okay. Yes, yes, we threat modeled the hell out of it.

**Chris Romeo (36:38)**: You know you're under oath, Mr. Kohls.

**Izar Tarandach (36:43)**: But wait, wait, I'm gonna go back and I'm going to say that later on, later on, we may have made a mistake in there in sort of ignoring that when we Okay, so for those who are not familiar with PyTM, so you have a library of threats. Each one of those has a condition, and these live in a JSON file, and the condition gets evaluated in the Python code by an eval, and that creates a true or false about the threat existing or not existing. So later on in life, we said, oh, you know what? People want to have their own threat libraries and be able to load those. And we developed the, the capability, and that basically moves the, the conditions from the protected place where only root can write to that file where it's installed publicly for everybody's use to people's own home directories where they can define their own JSON files and load those. But we never checked the code in. So, the capability exists, but it's theoretical.

**Chris Romeo (37:59)**: So, yeah, I mean, you were, but you were, before I started this line of questioning, you were going down the road of OSS and threat modeling.

**Matt Coles (38:08)**: Yep. Right.

**Chris Romeo (38:09)**: And so, do you think they, so we're agreeing that most people don't, this is not something that's embedded in the OSS mindset.

**Matt Coles (38:16)**: No, it depends on their view. You, right? So I know from looking at crypto libraries and some communication libraries, you know, that they do heavily rely on threat modeling.

**Izar Tarandach (38:31)**: SSL.

**Matt Coles (38:32)**: I'm thinking curl, for instance, right?

**Izar Tarandach (38:34)**: So, oh yeah, yeah, they're strong.

**Matt Coles (38:38)**: So certain projects already have a security mindset. And almost certainly if they're not documenting their threat model, they certainly know what their threat model is and they rely on that information when they produce, when they, when they respond to or find issues, right? So if somebody submits a PR, there's a basis for making that decision about whether it's a problem or not. Yep. But the lion's share of open source projects almost certainly do not know how they're going to be— they do not know how they would use it or how others would use it such that they can build a threat model, and/or they don't know how to do threat modeling in the first place.

**Izar Tarandach (39:23)**: So perhaps something we could do at the OWASP Threat Modeling Project is to offer open source projects a pool of threat modelers that they could engage to create a threat model of their systems at any point. That could be the true threat modeling as a service thing.

**Matt Coles (39:38)**: Talking about a scaling problem, how many open source projects are there?

**Izar Tarandach (39:43)**: How many do you think are running to ask for it?

**Chris Romeo (39:46)**: Probably none.

**Matt Coles (39:48)**: So combine it, combine it with the OpenSSF project that has a bootstrap for security for open source project maintainers where you can maybe drop threat modeling as a requirement into that Oh, I didn't know they had that.

**Izar Tarandach (40:02)**: That's nice. Wow, that's nice. Tell us more about that.

**Matt Coles (40:09)**: Let me look that up for you and we'll get that in the link.

**Izar Tarandach (40:11)**: Please. Because I had no idea that that existed. And it's funny that we are discussing the usability and the scaling and we completely ignore the third one, the reliable automation and AI assistance.

**Chris Romeo (40:30)**: I don't see that as a challenge, though.

**Izar Tarandach (40:32)**: Right?

**Chris Romeo (40:34)**: That's a benefit. Using AI to make the threat modeling person's journey easier, more efficient, more optimized is really the focus.

**Izar Tarandach (40:50)**: But isn't that a shortcut to threat libraries?

**Chris Romeo (40:57)**: Yeah, it's a threat library that you don't have to have as much knowledge of and context of, right, as the human. It's the machine taking some of the context, which is one of our challenges, right? There's a challenge there that the LLMs didn't mention. Developers don't know enough about security and privacy.

**Izar Tarandach (41:17)**: Oh, they do have the skills gap here. Where's the skills gap? Too expert-centric. Most methods assume access to people who understand both security and the system deeply.

**Chris Romeo (41:29)**: I agree. I mean, that's one of the ways you can use AI, though, in threat modeling, is to break down that wall where the AI provides the context so that you don't need a Matt Coles sitting next to you at your desk to be able to unpack these threats.

**Izar Tarandach (41:45)**: Speaking of which, have you guys seen the— I think it's Google— the latest thing that they offered It's called CodeWiki. Look into that. It's like somebody takes NotebookLM, apply it to a codebase, and generate not only documentation, but a deep dive into the architecture. And it even creates videos and diagrams and whatnot.

**Chris Romeo (42:12)**: It's wow.

**Izar Tarandach (42:13)**: It's nice.

**Matt Coles (42:15)**: So the two— there's two OpenSSF projects, just a little tight loop on that. There's OpenSSL Project Security Baseline, and there's—

**Izar Tarandach (42:22)**: Oh, you said OpenSSL! I understood OpenSSL. Sorry, my ear. My bad, my bad.

**Matt Coles (42:30)**: And the OpenSSL Scorecard. Those two projects drive security behavior for maintainers.

**Izar Tarandach (42:37)**: So PyTM, for example, has an OpenSSL scorecard.

**Matt Coles (42:42)**: Yeah, right. Now, if— but if PyTM was part of the baseline, it would be a natural driver for current models.

**Izar Tarandach (42:49)**: Yep, yep, true. Hmm, OpenSSF is doing some good stuff, eh? All right, so where do we land with this?

**Chris Romeo (43:04)**: Uh, do we land anywhere?

**Matt Coles (43:06)**: Some models are— all models are wrong, but some are useful.

**Izar Tarandach (43:11)**: LLMs just do it.

**Matt Coles (43:15)**: LLMs get sued by Nike for—

**Chris Romeo (43:16)**: Yeah, I was gonna say this could be a, this could be the first episode to get shut down by a large corporation.

**Izar Tarandach (43:23)**: And we don't even have background music. Well, we had some in the beginning, but it wasn't actually music. It was just us talking about music. That's meta. Also meta can sue us now.

**Chris Romeo (43:33)**: Yeah. Thanks. Thanks, César. Second lawsuit. Why don't you hold up another product? Oh, like a monster?

**Izar Tarandach (43:41)**: Yeah.

**Chris Romeo (43:41)**: No, hold up another product like a monster so we can add that to the video.

**Izar Tarandach (43:44)**: I have no idea what you're talking about.

**Chris Romeo (43:47)**: People that are going to see, like, line up people, the security table. If we have one thing, we got deep pockets. Not really. Oh yeah.

**Izar Tarandach (43:55)**: No, if you count the holes in mine, they are very, very deep.

**Matt Coles (43:58)**: I got some lint in mine if you want.

**Chris Romeo (44:01)**: That's about all we'll offer in settlement.

**Izar Tarandach (44:04)**: Sorry, we are modern here. We don't lint. We use black.

**Chris Romeo (44:07)**: That's true. We use black.

**Izar Tarandach (44:10)**: We ask Snick.

**Chris Romeo (44:11)**: We're kind of off the linters of the world, but they do provide value.

**Izar Tarandach (44:16)**: So they do.

**Matt Coles (44:17)**: They do.

**Chris Romeo (44:17)**: Leave them be.

**Izar Tarandach (44:17)**: Don't be like a good linter.

**Chris Romeo (44:19)**: Leave them be. All right. Well, I think we're just going to leave this episode with no conclusions.

**Izar Tarandach (44:23)**: Leave you as it is. The conclusion might be that I have to stop asking LLM stupid questions.

**Chris Romeo (44:28)**: But yeah, that could be a conclusion.

**Matt Coles (44:30)**: That could be a conclusion.

**Izar Tarandach (44:30)**: That could be a conclusion. Don't let me touch LLMs.

**Chris Romeo (44:33)**: Yeah, I don't think we're going to go that far because—

**Izar Tarandach (44:36)**: but just do it. No, seriously, seriously, people, just do it. Do what the Threat Modeling Manifesto does, says, and stop talking about it and just go and do it.

**Matt Coles (44:45)**: Let's make this a non-get, don't-get-sued approach.

**Izar Tarandach (44:50)**: Just threat model.

**Matt Coles (44:51)**: Yes, just threat model.

**Izar Tarandach (44:53)**: Just threat model. Let's end on a positive note. Positively, just threat model.

**Chris Romeo (44:57)**: I just trademarked the word just. So now you owe me money. Just in.

**Izar Tarandach (45:04)**: This just in. Justin? No. All right.

**Chris Romeo (45:08)**: We'll leave the world a better place by saying just Threat Model. We're signing off. Have a good time doing your threat modeling.
