# Everything is Boring

URL: https://securitytable.ai/everything-is-boring/
Published: 2024-10-16
Duration: 1799 seconds
Season: 2
Episode: 29
Hosts: Chris Romeo, Izar Tarandach, Matt Coles

## Show notes and chapters

Is everything boring? Chris, Izar and Matt discuss why nothing seems interesting enough lately. Is the excitement of vulnerabilities and ransomware waning? The guys touch on Governance, Risk, and Compliance (GRC) in corporate auditing, the impact of ransomware and the contentious role of cyber insurance, the fading novelty of AI and its influence on security, and examine why essential security tasks might feel mundane yet remain vital. This is a candid conversation you won’t want to miss. 

  
  

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:08)**: Hey folks, welcome to the Security Table where Isar is editing a social media post as we speak.

**Izar Tarandach (0:18)**: Sometimes this thing is too complicated for me, man.

**Chris Romeo (0:22)**: There is a principle of keep it simple. In security?

**Izar Tarandach (0:28)**: I'm trying, I'm trying, I'm trying.

**Matt Coles (0:29)**: But sometimes it can be too simple, right?

**Izar Tarandach (0:31)**: Matt, I don't know what you're talking about because I'm looking at the post right now and it's there.

**Chris Romeo (0:39)**: So wait, is the problem that Ezar cannot properly post or Matt doesn't know how to use LinkedIn to read posts?

**Matt Coles (0:46)**: Could be both.

**Chris Romeo (0:48)**: It could be both.

**Izar Tarandach (0:49)**: Yeah, it could be both.

**Chris Romeo (0:49)**: That would be a loop right there for the ages.

**Izar Tarandach (0:52)**: And it could be a new thing that we haven't identified yet, but I'm sure that once we do, we're going to create a site, give it a cute name, and blast it all over the place, and it's going to become the new thing.

**Chris Romeo (1:05)**: You're going to eventually sell it to Meta for $2 billion.

**Izar Tarandach (1:08)**: Yeah, to become the new—

**Matt Coles (1:09)**: Well, we need something new because, you know, everything is just blah.

**Chris Romeo (1:17)**: That's a good name for this episode. Everything is bleh. So we started the conversation, I guess, before we hit record talking about this idea that everything is boring in security. And—

**Izar Tarandach (1:36)**: Oh, it's right here. One chip.

**Chris Romeo (1:40)**: All right, we have some content.

**Izar Tarandach (1:42)**: I'm gonna screenshot.

**Matt Coles (1:43)**: Actually, no, I can put it right here. See, there's no post there. There's no link. Look in the middle.

**Izar Tarandach (1:49)**: No, man. No, no, no. That's because you're looking at the post by Zoe of my post.

**Matt Coles (1:54)**: But your post doesn't have a link in it.

**Izar Tarandach (1:57)**: I don't put links.

**Chris Romeo (1:58)**: He reposted. Did he repost Jonathan? Yeah. So if he reposted Jonathan, then you only get one layer of the repost.

**Izar Tarandach (2:07)**: So it's not me, it's LinkedIn.

**Matt Coles (2:10)**: Yours is, but yours isn't a rehost either. I mean, it doesn't say, well, anyway. All right.

**Chris Romeo (2:15)**: Well, it's not a bug. It's a feature.

**Matt Coles (2:17)**: It's a feature.

**Chris Romeo (2:18)**: All right. So why is everything so boring? So in security, we, and you can even extend it to privacy. We're scanning. We're looking for something to talk about for this episode. And we found ourselves just going through a whole collection of mindless drivel. So-and-so got compromised and hacked. Yay. Ooh, bummer. This new vulnerability came out. There's a CVE for something that's going to cause all kinds of chaos and peril on the internet. But like, none of it was interesting enough for us to trick into an actual episode.

**Izar Tarandach (2:56)**: So why is that?

**Chris Romeo (2:57)**: What is broken here?

**Izar Tarandach (2:58)**: But do you remember, do you remember from the Muppets, the Swedish chef?

**Chris Romeo (3:03)**: Of course.

**Izar Tarandach (3:03)**: He had basically two modes of operation. He would, oh yeah, yeah, yeah, like excited about the things that he was throwing around. And then he would have like the sad mode. Oh, that cut off. And maybe that's the way that we feel because yeah, it's like one more Volubilis, one more product, one more this, one more that. Security passes and the dogs bark.

**Matt Coles (3:34)**: Yeah. It's, it's, I think we, we must all have attention deficit disorder or whatever that, that illness is that, that requires, that requires us to be constantly on. Like we need that dopamine rush of a named vulnerability or a massive breach or go crazy.

**Chris Romeo (3:54)**: Yeah.

**Matt Coles (3:56)**: As opposed to just the run of the mill stuff.

**Chris Romeo (3:58)**: Is anybody excited about that stuff anymore though? Is it just us? Like, are we jaded perhaps? No. Because we've been in this for, I mean, how, I mean, how long have you guys been at this? I don't know the exact answer.

**Matt Coles (4:07)**: 20, 20 years probably.

**Chris Romeo (4:09)**: Close to 20 years.

**Izar Tarandach (4:11)**: It's, it's behind 15, I think about 30 years.

**Chris Romeo (4:14)**: Yeah. So we've, we've all got multiple decades of this. Perhaps we're just the jaded guys up in the balcony from the Muppet Show. As we've talked about before.

**Izar Tarandach (4:24)**: I, I, I'm going to disagree with Matt in there. I don't think that it's a, it's a dopamine hit. Perhaps for the younger ones. But I think that once upon a time, a security event would be, "Guys, it's a security event, run around, run around, everybody panic, we are so important, we have to fix this thing right now." And now nobody cares, you know, it's like, you can't be the hero of staying up at 3 in the morning fixing the security thing because nobody cares. It's like you're doing your job, you're supposed to be doing that.

**Matt Coles (4:57)**: Yeah, and alternatively, I mean, it's sort of like, Well, the scanner will find it. What do we need to do? Right? I mean, the automatic patching and everything now takes care of it all for you.

**Chris Romeo (5:11)**: Oh, if that was only true. We— Matt is now officially in a dream world where he believes that somehow the issues are going to be scanned for, found, and fixed automatically while he's sleeping.

**Matt Coles (5:30)**: In a perfect world.

**Izar Tarandach (5:32)**: Sorry, I'm allergic to scanners, but, uh, DAX isn't, DAX isn't that, dudes?

**Chris Romeo (5:38)**: That's a, that's actually a DAX attack right there because the thought came to his mind and he started coughing immediately.

**Izar Tarandach (5:43)**: But actually, actually, if you go, uh, if you go back on that, on, on the scanners and stuff, you see every time that I say it, the, the, the thing is that My gut feeling is that today, unless it is a denial of service or a ransomware incident where basically security is stopping everybody else from working, it's always a, okay, deal with it in your own time and let us know how it went.

**Chris Romeo (6:11)**: Yeah. I mean, when's the last time you saw denial of service take out a site?

**Matt Coles (6:17)**: Amazon US East, I think was like—

**Chris Romeo (6:21)**: Ah, that wasn't denial of service. Isn't that just a service, like it's an outage? Oh, they just had an outage.

**Matt Coles (6:26)**: I don't think it was a DDoS attack.

**Chris Romeo (6:27)**: I never heard anybody say.

**Matt Coles (6:28)**: Yeah, it wasn't a DDoS, it was a network upgrade or something.

**Chris Romeo (6:30)**: I mean, I was working incident response in the late '90s, early 2000s. Like DDoS was a real problem in those days. We had to figure out what the traffic was that we could go to our backbone engineers at Exodus and ask them. And we had to have them filtered at the backbone level for DDoSes.

**Izar Tarandach (6:48)**: And it was called network security. Nothing incident response, because we didn't know that this was an incident actually.

**Chris Romeo (6:54)**: It was like— True. Yeah, but I mean, now in these days, when's the last time that I can't even remember. The last time I heard of one was when there was like, it was the biggest one of all time and it was against GitHub. That was a couple of years ago. It was like so many terabits per second or whatever. And I just thought, oh, that's cool. Just because I'd never seen a number that high.

**Matt Coles (7:12)**: I mean, there are—

**Chris Romeo (7:13)**: But in general, DDoS isn't a thing.

**Matt Coles (7:15)**: There is a DDoS that happened recently, but it was like nation state against nation state, but it wasn't like in the US, if I remember correctly.

**Izar Tarandach (7:22)**: But you know, even in those cases, even in those cases, many times people say, oh, the site is not working. Well, fine, I'm going to go do something else and come back in an hour and it's going to be working. So the real big flag here, the real big flag here is, I think, ransomware, right? Because that puts you out of business and has a longer horizon of fixing. But is that still a big problem today?

**Matt Coles (7:51)**: I think it is, but it's not, it doesn't hit like that. Again, it doesn't hit that level of interesting still.

**Chris Romeo (7:57)**: I can't remember the last time I heard about ransomware. Maybe I live in a bubble somewhere.

**Izar Tarandach (8:01)**: No, no, no, no, no, no, no, no. A couple of weeks ago, there was some hospital chain that got hit and that was really bad because they couldn't actually accept new patients. So that was bad. There was a city, I think, 2, one in Britain and one in somewhere in the US that also had all their services interrupted by ransomware. So no, I would say that it's still a big thing. And I would say that when you go up with the board, it's the first thing that they bring up in terms of worrying about it, not only because of the ransomware aspect, but because many times it comes together with later on the extortion of data being with the 2-step hit. And I think that because it still manages to get a big profile in the media, it's the thing that is like front and center in many people's minds. But otherwise, it's like, yeah, sure, okay, another hit, another place that Joris de Sain went away and all that good stuff and whatnot.

**Matt Coles (9:13)**: And there's been no vulnerabilities of note recently, right? Named vulnerabilities causing, you know, log4shell-ish kind of things, right?

**Chris Romeo (9:24)**: I want to go back to ransomware real quick. Apparently I live under a rock because I'm looking at Sophos State of Ransomware 2024.

**Izar Tarandach (9:34)**: Is it a brie de roc at least?

**Chris Romeo (9:36)**: I hope so. It was a heavy one because it's— preventing me from thinking, but SOFO State of Ransomware 2024, 5,000 respondents across 14 countries, 100 to 5,000 employees, so they're not the mega enterprises, they're not the big companies of the world. Across 15 industry segments, 59% of those said they were hit by ransomware in some way. 70% said it resulted in data encryption. 5x increase in ransom bills in the last 12 months. 32% of attacks started with an unpatched vulnerability. So I've been living under a rock, basically. I don't know.

**Izar Tarandach (10:10)**: Maybe that's— there's a bit of confirmation bias in there because they don't go asking people who have not been impacted. So, and possibly the editor of that report has something to say.

**Chris Romeo (10:23)**: But, uh, it does. They have 5,000 respondents and only 59%. So a little bit more than half of them said, so 2,000 of them said they were not impacted by ransomware last year, but are worried about it. Nah, that's not, we're putting words in their mouth now. This is, that's not what their site there.

**Izar Tarandach (10:40)**: Check later, I think that there is something to that. But the point is people are worried about it.

**Matt Coles (10:45)**: Right, and these are small businesses, right? These are organizations that are not the behemoths with a 100-person SOC team or incident responders or whatever. And so they can't afford ransomware, either defense or response.

**Chris Romeo (11:01)**: Yeah.

**Matt Coles (11:01)**: In many cases.

**Izar Tarandach (11:02)**: And apparently, I have heard lately that cyber insurance does not cover ransomware and will not help you pay the ransom. So there is a very big economic incentive here to actually care about that stuff.

**Chris Romeo (11:18)**: Cyber insurance, don't get me started. That's a whole— I've had to carry cyber insurance for the last 10 years or so. you know, through various businesses and whatnot. And like, it's, it's, it's a contractual procurement requirement, right?

**Matt Coles (11:35)**: Was the only reason. It's meant for business continuity basically, right? It's so that, so that somebody can recover damages. If you, if something bad happens, they can recover damages from you to make themselves more whole again. Yeah. Whatever that means.

**Chris Romeo (11:50)**: Whatever calculation you would use to be determine wholeness. And but that's— yeah, I don't want to go down that road.

**Matt Coles (11:56)**: From loss of data and a host of other things. I mean, that's just— yeah, whoever the actuaries are on that, oh my God.

**Izar Tarandach (12:03)**: Yeah. Have you guys ever seen any data coming from Siberian Shores? I find them to be a very silent, very quiet aspect of this whole thing.

**Chris Romeo (12:11)**: I think it's just a sink where all money, all good money goes to die, basically.

**Izar Tarandach (12:16)**: No, I mean, I mean, when we talk about risk management and We, we recurrently go back to, we don't have enough data to, to quantify these things. After all these years, I would guess that those guys do have that data, but I haven't seen it published or, or shared by anybody.

**Matt Coles (12:35)**: Well, actually, do you, I mean, do you get general GRC data? I mean, not just your organization's GRC data, but a collection of data across multiple org—

**Izar Tarandach (12:44)**: uh, organizations. I, I love GRC people and I am very happy to ignore everything that they do to the extent that, uh, I'm not a lawyer. I don't want to be one. I, I'm very happy that they exist. I'm very happy that there are people who want to be that.

**Matt Coles (12:59)**: And you're not a GRCer.

**Chris Romeo (13:01)**: And you're having issues. No, to all the GRC people, you could send complaints to ezar@securitytable.com and that will go nowhere. You will get a bounce back. It doesn't exist.

**Izar Tarandach (13:11)**: Let's, let's make it clear. I, I, I love those people. I love the work that they do. I think it's a very, very hard job. I'm just not exactly, as we're speaking today, I'm not excited by it and I don't see myself doing a good job out of it because you need to look at things in a different way. I don't.

**Chris Romeo (13:32)**: Yeah.

**Matt Coles (13:33)**: But rather just looking at, but rather looking at just at cyber insurance, which, you know, I'm sure will keep the risk models quiet, right? Because that's their IP. But if you look across the GRC space, do you get a sense of like if every organization's GRC organization is obviously pumping out numbers, but what does that look like across the industry?

**Izar Tarandach (13:56)**: But that's the thing. I think that they are so busy running around the next SOC 2 or the next checkmark to check or the next control to control, they don't have time to do that good stuff.

**Matt Coles (14:11)**: So what you're saying is we've shifted the burden of security to them and we just sort of like, ugh, another scanner.

**Izar Tarandach (14:19)**: I think that we may have shifted the visibility of security to them so that today most people think security, they are actually thinking GRC and sometimes, well, not second place, I think, SOC. And the hard work of active security becomes a bit blurred, perhaps in the third or fourth. Plus the exciting aspects of product security and things. You know, nowadays, if you want to excite somebody about product security, the best way to do it is to make a list of things and let them rank by verity.

**Matt Coles (15:00)**: So are you saying top 10 is the way to go?

**Izar Tarandach (15:03)**: I don't even know top 10. I think that's a top 17,456, but then you apply some algorithm to it and everybody applies a different algorithm to it to tell you what the actual most important top 5,000 are that you can actually take action, change your life, move the needle.

**Chris Romeo (15:23)**: Move the needle.

**Izar Tarandach (15:24)**: Ignore them.

**Matt Coles (15:24)**: Shift left.

**Chris Romeo (15:25)**: So you know the top 5,000 to ignore.

**Matt Coles (15:29)**: Yeah. No, no, no, no.

**Izar Tarandach (15:30)**: It's the top 4,999 ones to ignore and the last one to say, uh, this is not actually vulnerability. And, uh, uh, but no, we're being too cynical here.

**Matt Coles (15:47)**: Oh, we always are. That's our job.

**Chris Romeo (15:48)**: It's kind of who we are because we're jaded because of our decades of experience.

**Izar Tarandach (15:54)**: Oh, it was just an observation. I was not complaining about it.

**Matt Coles (15:57)**: All right, so let me throw out a real challenge for you then. So if we've shifted the visibility—

**Chris Romeo (16:07)**: If you say shift left, I'm hanging up. If you say shift— It went that way.

**Matt Coles (16:10)**: It went that way. If we have transitioned the visibility of security to GRC, What's going to happen when we successfully transition? Now you have me do it. Now you got to transition the visibility of security to development orgs. They're not GRC, but they have program managers who like to report numbers, and rightly so, because they want—

**Chris Romeo (16:36)**: Where have you seen security visibility being transitioned to GRC?

**Matt Coles (16:42)**: All right. So, so I'm going to, I'm going to take a leap of faith here. That if we do our jobs properly, and I don't mean you or I and, you know, the three of us here, but us as a security industry, that if we were to make security a quality problem, if we were to get developers on board with security, driving security activities, those are gonna get tracked as part of program management activities, ultimately. Not as part of risk and compliance. Or maybe not strictly as risk and compliance.

**Chris Romeo (17:14)**: I've seen GRC as a very separate animal or beast.

**Matt Coles (17:19)**: They are.

**Chris Romeo (17:20)**: And that's why I'm asking. With very little collaboration and communication. Like, previously in my career working in big companies, we had no connection to GRC at all. Oh yeah. I didn't know them. I didn't, I didn't, there was no No conversation. There was no information sharing. There was nothing. They were doing their thing about the risks to the business off to the side.

**Matt Coles (17:46)**: Do you consider audit? Do you consider corporate audit as part of GRC?

**Chris Romeo (17:50)**: I try not to think about corporate audit because the thought of corporate, of being, of that being my job just makes me want to lay on the ground and sob.

**Izar Tarandach (18:00)**: Which again means that we love the fact that there are people who do that for a living. It's just not us.

**Chris Romeo (18:05)**: It's not me. I don't have the, I would be like, it looks good to me. I have a gut feeling that we're in good shit based on what I know about everybody around me.

**Matt Coles (18:15)**: I have, see, I have a QA background and I think I could, or I don't want to do audit because it's boring as hell, but it's—

**Chris Romeo (18:22)**: Whoa, whoa.

**Izar Tarandach (18:23)**: It's— Trust why, trust why.

**Chris Romeo (18:24)**: We're happy that there's some people that enjoy doing that so that they can carry us forward.

**Matt Coles (18:30)**: So the interesting thing I think is going to come out with Well, what happens when you have quality engineering or a quality process reporting security issues and you have a GRC process, compliance process reporting security issues? They're going to look completely different.

**Chris Romeo (18:45)**: Yeah, because they have different levels of abstraction that are different. GRC, I feel like, is at the 20,000-foot view, looking out the window of the airplane, whereas development security is on the ground looking around for things that have fallen in the forest, right?

**Izar Tarandach (19:00)**: And I'm going to add to that one thing. I think that GRC, Mostly, and I could be completely wrong here, but I think that they are offering a view that goes to the outside rather than the inside. I mean, you can have your risk registry and everybody puts everything in there and it's awesome to have it. A great thing to read on the—

**Chris Romeo (19:20)**: It's regulated, it's regulatory driven, right?

**Matt Coles (19:23)**: Yeah.

**Chris Romeo (19:23)**: Because like GRC is about how am I going to get the package that we have to file for Sarbanes-Oxley or whatever. The legislation is, the regulations that drive corporate reporting and everything. Like, they're worried about a different customer. Their customer is the regulator, whereas our customer in development security is the same customer as the engineering team is building for.

**Izar Tarandach (19:46)**: But GRC at some point is also, their customer is also the board that wants to hear that we have currently a manageable level of risk.

**Chris Romeo (19:56)**: Sure. Right.

**Izar Tarandach (19:57)**: But that risk does not many times include the product security risk.

**Chris Romeo (20:02)**: No, I would say it doesn't. Because there are different— I've not seen it.

**Matt Coles (20:05)**: Right.

**Izar Tarandach (20:05)**: There are different views and different interpretations of risk.

**Matt Coles (20:08)**: Yeah.

**Izar Tarandach (20:10)**: And perhaps what we need here is, and I don't know if that's even a thing or might be a thing where people are talking about that because again, GRC completely opaque to me. Perhaps we need to give GRC the task of also weighing in that risk, the product security risk, which is what interests us and what keeps things interesting for us.

**Matt Coles (20:31)**: I think in order to do that, the compliance is all about the controls that they're measuring. And so a lot of the controls are ISO 27001, 27002-based control, which are not product development controls. Those are about information management and about security reporting. Or business systems and their impact on security.

**Chris Romeo (20:57)**: Good old PCI.

**Matt Coles (20:58)**: And not product risk, right? So, have you deployed your environment in such a way that's resilient to attack? Well, what happens if you're shipping something to customers and it's not your problem? Well, so you should, how do you measure that? What controls do you have? And so.

**Izar Tarandach (21:18)**: Yeah, and then you have the whole PTI handling thing, which takes a lot of time and a lot of resources from those guys.

**Chris Romeo (21:24)**: So I want to circle back towards what our original question was, why things are so boring. What would have to happen in either of your minds for us to say this is an interesting week in security? What's the opposite? What's the—

**Izar Tarandach (21:42)**: No, no, no. Okay, after—

**Matt Coles (21:44)**: after the SpaceX launch and catch yesterday.

**Izar Tarandach (21:48)**: Oh man, that's—

**Matt Coles (21:48)**: Nothing could go— I don't know if anything— well, I don't want— I'm not going to say it, but nothing can go wrong.

**Izar Tarandach (21:54)**: Remember, failure is always an option.

**Matt Coles (21:56)**: Frankly, I was looking for that thing to come down and crash like into the gantry and completely explode all over the place. And it didn't, and it was awesome. And maybe that's— maybe that's what— so maybe that's what it is. Oh, so I was expecting a failure. I was expecting failure. And I was happy when it succeeded.

**Izar Tarandach (22:13)**: It's interesting that you would be satisfied either way. I was making—

**Matt Coles (22:20)**: But is that, is that how to, so take that to security. I'm looking for failure. We always look for failure. Our jobs are to look for failure. But when it doesn't, when nothing's failing or when it's just regularly failing and not spectacularly failing.

**Izar Tarandach (22:38)**: Yeah, but we are looking for interesting things.

**Matt Coles (22:45)**: Be interested to us?

**Izar Tarandach (22:46)**: Yeah.

**Matt Coles (22:47)**: Because we're bored currently. No, I don't care about anybody else.

**Izar Tarandach (22:52)**: But the point here is that, you know what, I'm going to be like, I'm going to age myself here. I'm perfectly fine with boring because boring lets me focus on the things that I myself think are interesting. And not that somebody else is putting on top of me to say, now we focus on this because this thing is not boring and going up in fire and you do your stuff. So I think that earlier in my career, the emergency mode was motivational. Give me that rush, make me feel important, make me feel wanted. But, uh, then it became too much like that, uh, teenager relationship. And, uh, you notice that, uh, no, you're not important. No, you're Content. I don't know. You're just one more cog in the machine. And basically, I am very satisfied with boring because it lets me think about new ways of threat modeling or figuring out new problems to solve, trying to understand this whole AI LLM thing and seeing what I can do with it. And all the shiny stuff, right? Boring to me becomes The ship is going through its course and the pirates are not exactly biting on the sides so I can worry about other stuff. But every now and then—

**Matt Coles (24:14)**: That is the pirates are biting, not the sharks.

**Chris Romeo (24:18)**: Why are the pirates biting? Who are they biting?

**Izar Tarandach (24:23)**: Am I mixing analogies again? No, I'm thinking about those small ships that they have. That down in the south of Africa that they come along with big ships and then they go on board? I'm the captain now! You're not—

**Matt Coles (24:38)**: That would be pirates.

**Izar Tarandach (24:39)**: Have you seen the movie?

**Matt Coles (24:40)**: Pirates but they don't bite.

**Chris Romeo (24:42)**: Why do we need to fight?

**Izar Tarandach (24:44)**: Hey hey hey hey hey hey! You don't tell my parents how to behave. These are my parents and they can behave this way. Anyway they want.

**Chris Romeo (24:55)**: Anyway they want. So, Izar, your conclusion is boring is good.

**Izar Tarandach (25:01)**: Boring can be positive. That's my point. So, like, all the action is cool. It's nice. It makes very interesting war stories later on. But at a certain point, boring is nice. And I think that for a long time, we have been marketing ourselves as professionals whose biggest target in life is to make things boring. We wanted to teach everybody to secure code so that there would be no vulnerability. We wanted to create best practices so that there would be no vulnerabilities. And I think that the underlying message there was, we want everybody to get bored by security. And now that we, I think that we've forepuffed wandered into the vicinity of that neighborhood. I think that now is the time for us to look inside again and say, okay, what's the next big problem that now we have the time to fix? We are constantly saying, oh, I can't do anything because all my time is going to the 5,000 things in the list, right? So perhaps now we have some time, perhaps now we have to look at what the next big problem is.

**Matt Coles (26:11)**: And how do we avoid becoming complacent in that boredom?

**Izar Tarandach (26:13)**: Yep. Yep, yep, yep, yep, yep. That's—

**Chris Romeo (26:15)**: Or irrelevant.

**Matt Coles (26:16)**: Or irrelevant.

**Izar Tarandach (26:18)**: Well, we are, apparently we are irrelevant already because people keep putting out these GPTs that apparently do everything on security. I tried a very popular one last week and I was frankly happily disappointed.

**Matt Coles (26:34)**: Well, not boring?

**Izar Tarandach (26:35)**: No, that was not boring because somebody oversold it as like the next thing. And I hope that it's the next, next thing because it's definitely not the next thing.

**Matt Coles (26:45)**: It's not the thing.

**Izar Tarandach (26:48)**: It's the next nothing.

**Matt Coles (26:51)**: There's a lot of that recently, isn't there? The best thing since sliced bread.

**Chris Romeo (26:56)**: That's a whole other, that's a whole other conversation. The hype train is real in application security and cybersecurity in general. And I think the AI, the, I don't know, the AI wave seems to be losing a little bit of fizz.

**Matt Coles (27:17)**: It was all brand new. Now it's not super brand new. And now people are getting down to, you know, getting down to brass tacks about how do you make this thing work. It's like, there's some problems here we need to address.

**Izar Tarandach (27:29)**: Like, I'm still waiting for one of my other limbs to tell me after I prompted, I can talk to you now, I have a headache. When that happens, then we reached peak.

**Chris Romeo (27:41)**: Artificial general intelligence has been reached.

**Matt Coles (27:44)**: Indeed.

**Izar Tarandach (27:44)**: Yep.

**Chris Romeo (27:45)**: When the LLM says it has a headache and it can't talk to you right now. Yeah. All right. Any final thoughts on the fact that nothing is boring, which is our conclusion?

**Matt Coles (28:03)**: Keep going. Just keep going.

**Izar Tarandach (28:06)**: We said that everything is boring.

**Matt Coles (28:11)**: Everything is not— there is nothing that is outlandishly exciting or needs our attention beyond the normal.

**Izar Tarandach (28:24)**: You know, I always said that if everything is urgent, nothing is urgent. If everything is boring, does that mean that we just calibrated our level of what we call not boring? In other words, did we advance so much that we see the things that we have today as commonplace, and so they're boring? And the next thing, to go back to Matt's dopamine hit, it's going to have to be really major for us to I, this weekend I read something that in China they already used quantum computers to, to hack military encryption.

**Matt Coles (29:01)**: Yeah.

**Izar Tarandach (29:03)**: Quick, let's run in circles if our head's on fire. The encryption is dead.

**Matt Coles (29:08)**: Oh, interesting. Right, currently at steady state, the sky is always falling and we're okay with it.

**Izar Tarandach (29:18)**: Because we got hard helmets. Brutal.

**Chris Romeo (29:23)**: I mean, remember Chicken Little? Sky was only falling early the once.

**Matt Coles (29:28)**: Because the cloud is somebody else's computer, not yours.

**Chris Romeo (29:32)**: Wow, that's a heck of an analogy to leave this conversation with.

**Izar Tarandach (29:36)**: And I thought that I mixed analogies.

**Chris Romeo (29:39)**: That was a pretty mixed analogy. So, all right, folks, thanks for listening to this episode of The Security Table. We will see you again soon at an internet cafe.
