# Numb to Data Breaches, and How it Impacts Security of the Average Feature

URL: https://securitytable.ai/numb-to-data-breaches-and-how-it-impacts-security-of-the-average-feature/
Published: 2024-09-18
Duration: 1942 seconds
Season: 2
Episode: 27
Hosts: Chris Romeo, Izar Tarandach, Matt Coles

## Show notes and chapters

In this episode of the Security Table with Chris Romeo, Izar Tarandach, and Matt Coles, the team dives into the evolving landscape of modern security approaches. They discuss the shift from strategy to tactics, the impact of data breaches, and why people are becoming numb to such incidents. The episode also touches on the importance of understanding the business side of security and the role of product managers as security champions. 

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

**Izar Tarandach (0:09)**: Approach nowadays.

**Chris Romeo (0:13)**: So your security approach is that you have no idea why you got out of bed this morning?

**Izar Tarandach (0:17)**: Basically, yeah.

**Chris Romeo (0:18)**: Okay. Well, I don't think that's really a strategy. I mean, technically it's a strategy.

**Izar Tarandach (0:23)**: I don't do strategy anymore. I think that's tactics. Tactics is where I live. Okay. Because that's the only way that you get some success nowadays.

**Chris Romeo (0:32)**: Yeah, but strategy gets to do all the travel.

**Izar Tarandach (0:36)**: I will forego the travel, probably. But with some success.

**Matt Coles (0:41)**: You, you, you did the whole, you did the whole conference circuit for the past 2 years. You're, you're done, right?

**Izar Tarandach (0:46)**: Not only the conference. I remember when, uh, Dell took me around the world in a week and I spent more time in a plane. Than actually in the ground.

**Matt Coles (0:57)**: Why?

**Chris Romeo (0:58)**: I did a couple of those trips in my career. So I went from, I went from Raleigh to Shanghai to Bangalore to Raleigh on the circuit.

**Izar Tarandach (1:13)**: Same one, but I have Eugene, San Francisco, Shanghai, Kuala Lumpur, Bangalore, Frankfurt, San Francisco, Eugene again.

**Chris Romeo (1:23)**: Wow.

**Matt Coles (1:23)**: Why did they take you to Kuala Lumpur? What's there?

**Izar Tarandach (1:27)**: Uh, we stopped there and for reasons of passport, I had a bit of a, an anxiety stay.

**Chris Romeo (1:38)**: Probably don't tell that story.

**Matt Coles (1:41)**: That's good.

**Chris Romeo (1:42)**: That'll stay in the vault for future. All right. Well, I just realized we're a minute 40 in and people don't even know why they're here. So welcome to the Security Table. This is Chris Romeo joined by Izar Tarandot, Matt Coles. All right. We're going to topic. We're going to topic. What is that? I can't even complete a sentence this morning. We're going to topic about data breaches. Izar, set this up because I don't 100% have in my brain where you want to go here. So set it up for us.

**Izar Tarandach (2:15)**: Actually, it's not so much about data breaches. It's more about not knowing what, why we got out of bed. I think it's, I don't know, I've been observing the, the, the past few months or even more sparsely in the past few years that the once upon a time security was that domain with all the jobs security and the big budgets and, uh, we could ask and it would be given and this and that and the other, other one. But, uh, lately, and, and to be totally honest, even me personally, like just last week, I think I got 3 pieces of mail, real mail, snail mail saying you got breached.

**Matt Coles (3:01)**: Like it was, oh, you got, you got one of those too?

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

**Izar Tarandach (3:05)**: 3 of those. 3 of those.

**Matt Coles (3:07)**: 3 of those.

**Izar Tarandach (3:07)**: Different, different, uh, companies completely. I mean, if I were, if I were able to put like, apart from what I'm already paying, but if I were able to, to put sequentially in order the years of credit monitoring that I have, I mean, how many times over? No, seriously. I mean, That's a bandaid, right? And, and, and that's, that's where I'm going with this, that nobody cares anymore. And we spoke about this sometimes that there's almost no consequences to data breaches.

**Chris Romeo (3:46)**: Yeah. But I think that why should we care?

**Izar Tarandach (3:47)**: Just to, just to wait, just to close the, the, the, the preamble here. I think that we are starting to see that reflect into those budgets and into those approaches to security that we do. April security, information security, all kinds of good security. And people are just starting to say, so what? Yeah.

**Matt Coles (4:09)**: Okay.

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

**Matt Coles (4:14)**: So yeah, I agree with you. I'm 100%. I mean, we have the big, the massive Social Security data breach. Couple weeks ago. First off, nobody sent, nobody sent any notices. Nobody sent any notices around.

**Chris Romeo (4:29)**: Um, I honestly, I had no idea.

**Izar Tarandach (4:31)**: They would have to send everybody.

**Chris Romeo (4:33)**: But I had no idea that, I had no idea that actually happened. I did not even—

**Matt Coles (4:36)**: Yeah, there was a big breach of, there was a big breach of Social Security data and, uh, it wasn't through the Social Security Administration.

**Izar Tarandach (4:44)**: It was through some company that had—

**Matt Coles (4:45)**: A third party.

**Izar Tarandach (4:46)**: Yeah. Third party. Yeah.

**Matt Coles (4:47)**: And you know, the way I found out I was impacted was I looked at haveibeenpwned.com. Mm-hmm. And everyone else, and I'm sure everyone, I mean, it's some billions, billions of records and there's only 339 million Americans.

**Izar Tarandach (5:03)**: So I, I mean, it's historical data, right?

**Matt Coles (5:07)**: So yeah, it's historical data.

**Izar Tarandach (5:10)**: Yeah. And, and the way that people are just shrugging it off and going, okay, it happened. What are you gonna do about it?

**Matt Coles (5:19)**: What are you gonna do about it? Right?

**Izar Tarandach (5:20)**: What's it gonna do about it?

**Matt Coles (5:22)**: Right.

**Izar Tarandach (5:22)**: And, and the answer is not much because not only apart from taking all the measures regarding your, your credit score, by, by the way, I, I don't understand why we still rely on social security numbers in the US so much. Why are they, them being like secret?

**Matt Coles (5:39)**: Why are they authentic? Yeah. Why are they credentials and not, not just identity?

**Izar Tarandach (5:42)**: I mean, why?

**Matt Coles (5:45)**: But anyway, somebody didn't— somebody's— whoever designed this thing failed the threat model.

**Izar Tarandach (5:50)**: Right, right, right. And you know what, I'm sure that this is— this whole thing is making the life of security vendors so much harder. And from the size— from the side of somebody who doesn't have mind power, but gets to see a lot of products, I have to bet on the fact that I have very limited Budget, I have requirements of functionality. And as we already said before, keep seeing the same tool looking the same way, doing the same thing again and again and again. It just changes the color, right? And basically everything looks like the same thing now. Everything does the same thing now.

**Chris Romeo (6:31)**: The title of this episode is Jaded Security Pro.

**Izar Tarandach (6:35)**: You sit down waiting for Gartner to tell you what's the next acronym that you have to pay attention to or that you have to laugh at.

**Chris Romeo (6:44)**: He serves in rare form, rare form right now. Just keep going. I'm just going to sit here and listen. Keep going. Keep going.

**Izar Tarandach (6:50)**: You know, I just keep asking myself, why did I get out of bed this morning? I mean, you know, nobody cares about what's going to happen. Nobody cares about how I'm good. Nobody cares about doing the things that I say should be done.

**Chris Romeo (7:04)**: Wait, so you're giving up? Why? Are you giving up? Are you giving up?

**Izar Tarandach (7:09)**: No, because I still have like the good parts of it. I get to go to conferences. I get to talk to very smart people. I get to share. I get to commiserate with you guys.

**Matt Coles (7:17)**: So it keeps you employed.

**Izar Tarandach (7:20)**: That's true. I like to eat.

**Chris Romeo (7:22)**: Yeah.

**Izar Tarandach (7:22)**: That's an important thing.

**Matt Coles (7:24)**: We need the illusion of, we need the illusion of doing something in security.

**Izar Tarandach (7:28)**: No, that's, that's the thing. Okay. When you start commiserating, it's easy to go. Off the deep end, right? The, the, I think that the fact that we still have teams in security that day in, day out do the hard thing and try to do it the best they can because we believe in protecting our customers and we believe in protecting IP. But again, it's, it's, I, I, I keep asking myself when the, when, when does the numbness that we got to at this point for data breaches and their, their, uh, and the results becomes again pain. And, and then we can move forward with what needs to, to, to be done.

**Chris Romeo (8:13)**: I don't think it's ever gonna be pain again. I don't see consumers somehow being impacted by data breaches in such a way that I feel personal pain because the systems have been architected in such a way that I get, use a credit card data breach, right? My credit card gets stolen by somebody. The system, the bank/credit card processor knows long before I ever would when somebody tries to use the card and they shut it down and they notify me, hey, there's a new card in the mail to you. So there is no, and I don't lose any money. None of my money gets tied up. Like the system had the, the mitigation or the security control has been architected in such a way as to remove the pain point from me completely.

**Matt Coles (9:02)**: And, and so that convenience, that convenience lulls people into a false sense of security, right? They, the bank is taking care of the security for you, right? You have no, you have no control and, and like you said, no knowledge of the event until it, until it resolves itself on your behalf.

**Izar Tarandach (9:21)**: That, no, that the bank, the bank is taking care of the impact. Because you're not feeding it in your what?

**Matt Coles (9:25)**: But the bank is, the bank is detecting, the bank detected the condition in the first place, right? So it detected that fraud can occur.

**Chris Romeo (9:32)**: They saw the fraud event, they reacted to the fraud event, they blocked the transaction.

**Matt Coles (9:37)**: So there's no money on the bank. The impact to you, the impact to you as the user is, oh, it was all taken care of behind the scenes. I don't have to do anything. What's the personal impact to you?

**Izar Tarandach (9:47)**: But the truth is that These systems, as everything, are fallible, and that failing results into still losses to fraud. So if you are, uh, uh, if you are using a card processor and if you are getting hit with a lot, a lot, a lot of different card numbers, you will incur a loss in there, and that loss does get passed to the consumer. It's just that you don't feel it because it's small.

**Chris Romeo (10:17)**: It's not my problem though, right? It's not my problem.

**Izar Tarandach (10:20)**: That's, that's the problem.

**Chris Romeo (10:21)**: It's not my problem. It's been, it's been isolated from me. But isn't this great security?

**Izar Tarandach (10:28)**: Yeah, that's sort of starting to think it, it, it sounds like we got to a good place.

**Chris Romeo (10:33)**: Wouldn't, wouldn't it be ideal if we were to build a feature and it had security controls in such a way that it protected the user without them doing anything? Isn't that a secure default?

**Izar Tarandach (10:49)**: That's what we aim at.

**Matt Coles (10:51)**: So the problem is there's a psychological problem with that, right? If, if it ain't, if it ain't broke, you have to fix it. The problem is it is broke and you have to fix it, but it takes care of itself. It's self-healing, right? We've, you know, self-healing resilient systems. That's what we strive for. And that's correct. But without the user knowing that there's an impact, right, they're not going to change their behavior. And if their behavior was the cause of the problem in the first place, using card on, you know, using credit card on random site that they don't trust, or I guess it could go, go in either direction because if it's due to the customer bad behavior, then there really should be a feedback loop. Bad behavior caused some issue to occur. Here's what happened, right? And yes, the system can be self-healing, but you need that feedback loop so that you alter the behavior of the user. If the problem was entirely the fault of the bank or of a third-party processor or whatever, then having the system be self-healing and, and transparent to the user, uh, or I should say opaque to the user. Um, is probably okay because there's nothing they could have done and nothing they did do, and therefore nothing they had to do. So I would be careful about making that blanket statement that self-healing and resilient systems is what we really want. If the behaviors, if there are behaviors we need to correct, uh, by the users as opposed to—

**Chris Romeo (12:21)**: I would say in this use case, the behavior is corrected by the inconvenience of having my card replaced. So if I go use my card in some stupid place that, that I really should have known better and my card gets compromised, I still have a 7 to 10 day window where I can't access that card. If it's a bank card, that's a little more difficult than if it's a credit card. I don't use credit cards, but if it's a bank card, Now I don't have access to my account, uh, for 7 to 10 days. So I see that as like a self-correcting, like if you do that 5 times in a row, you're so miserable because you have to go change your auto, your online bills 7 to 5 times. Like it, so in that case, I think it's gonna be self-correcting, but I get your point. Like there, there's a psychological issue here. Could a guardrail or could a security control make things so good that the users make even worse decisions? Or do you need to prevent them from being able to make the worst decisions?

**Matt Coles (13:29)**: Well, I, I think that, I think, I think they do, right? If, if everything, if, if any bad, if anything bad happens and the system takes care of itself, at some point a user might, a user might either consciously or, or unconsciously, you know, consider I can do whatever I want because the bank is gonna take care of it, right? In this situation. So if the system continually knows, and, and by the way, with AI, if it gets like smart and, and is able to predict this sort of thing, then they're, they're insulating the user from, from negative consequences. And at some point that's probably bad for two reasons. First off, we don't want to encourage bad behavior. But also what happens if that safety net fails? The user will have no knowledge of what they need to do and no knowledge of, you know, the negative consequences that can occur. You know, it would be wonderful, I think, if the bank said, well, your credit card was compromised. You know, if they sent you a letter, if they, if they self-heal the system, but they sent you a letter in the mail that says, well, you know, the system, the system was, was compromised. Your card was compromised through bad behavior, through, through some action. And here's all the, here's all the chain of events and costs, like a breach report, right? This is what, this is what happened in the backend that, and you know, maybe that's a marketing thing, but, but also that sort of brings out the reality of what happens when bad things—

**Izar Tarandach (14:58)**: Wait, that gets sent to whom?

**Matt Coles (15:01)**: To a, to the consumer, to the user. Hey, waste or make it, or make it available or make it available.

**Izar Tarandach (15:09)**: Making it available is a different thing.

**Chris Romeo (15:11)**: Nobody opens their, uh, the mail from their mailbox.

**Matt Coles (15:14)**: So that's true. Uh, so I don't know if you guys seen, if you get available, that's, that would be, I think, uh, a good step.

**Chris Romeo (15:20)**: Have you seen privacy.com? So if we're going to use this, we're going to keep pulling on this credit card example. What they do is they're a virtual credit card provider. Or virtual card provider. So you make a connection from their site to your bank and then you can generate valid card numbers. So like you can set up a val— you can set up a card number for each of your online bill pays.

**Izar Tarandach (15:49)**: Yeah. My credit card does that.

**Matt Coles (15:50)**: Yeah.

**Izar Tarandach (15:50)**: Yeah. Google Pay does that.

**Chris Romeo (15:51)**: One per—

**Izar Tarandach (15:51)**: Chase does that. One per, per transaction.

**Chris Romeo (15:54)**: Okay. Yeah.

**Matt Coles (15:55)**: Yeah.

**Chris Romeo (15:56)**: So that kind of insulates you even more from—

**Izar Tarandach (15:58)**: it, it does, but then it falls into the, the customer approach of what? I have to press one more button? No, no, can't do that.

**Chris Romeo (16:06)**: Complexity. I guess we're not really normal users, the three of us. We're like, ooh, you got a new security feature? Cool. Let's turn it on. Let's see what it can do. Oh wow, that's neat.

**Matt Coles (16:19)**: We're going to kick the tires on this one. Can you kick the tires? Can you open? Can you slam? Can you close the trunk?

**Chris Romeo (16:24)**: Yeah. Okay. Most people are like, No.

**Matt Coles (16:27)**: Nobody remembers that commercial, do you?

**Chris Romeo (16:29)**: I don't watch TV commercials anymore.

**Matt Coles (16:31)**: So you used to, maybe back in the '70s or '80s?

**Chris Romeo (16:34)**: In the '70s, I was a child. I was a small child.

**Matt Coles (16:36)**: Yeah.

**Izar Tarandach (16:37)**: Wait, wait. You don't use credit cards. You don't watch TV commercials anymore. Which cavern should we send Harper Mail to you?

**Chris Romeo (16:47)**: So I am, I'm basically in my bunker right now. I'm about a mile under the earth. So just getting ready to hatch a plan.

**Izar Tarandach (16:57)**: Do you have any white cats around?

**Chris Romeo (17:00)**: That's right. It's 1 million.

**Matt Coles (17:05)**: Do you have one of those little pit traps with the button?

**Chris Romeo (17:07)**: Of course.

**Izar Tarandach (17:08)**: Well, it doesn't everybody have one. Freaking lasers in their hands. All right.

**Chris Romeo (17:13)**: So where do we land here?

**Izar Tarandach (17:16)**: No, I, I mean, okay. So. I, I like the idea that in some aspects we may have reached the goal of peak security and things are working so well that we don't notice when they fail. That's definitely where, where we would like to be. But, uh, to do that, we need effort, and that effort costs energy and money. And I'm, I'm still zeroed on the fact that the impacts out there, society at large, are not being, uh, uh, big enough that we can use to justify those efforts. For someone, one of the breaches that I got this week was from a security provider, uh, not a security, uh, a health provider. And they're telling me that, hey, you know what? Somebody may have touched my medical records. I'm sure that a lot of people in fact that have medical records that they don't want out there. So that's, that's real impact. It has a, like, I won't say life and death, but it has a very large life impact.

**Matt Coles (18:27)**: You know, you know that, that, you know, that, that may term is used because it's easier to send you a, it's easier to send you a breach notification than it is to actually know that you were actually specifically breached.

**Izar Tarandach (18:38)**: That's the legal side of it, but the practical side of it is sometimes you don't have a way to know what, what, what, what, uh, uh, extracted whatnot, right? So it's both a technical and a legal, uh, problem.

**Chris Romeo (18:53)**: So if we come back around though, you kind of started this conversation talking about the fact that it didn't seem, it seemed like budgets were being hindered by this. And then we kind of dove, we dove into the deep end of a different pool. So let's kind of get outta that pool.

**Matt Coles (19:08)**: I think it's actually related though. I'll just counter with, with, I think that's related to, let's go back to if the system, if the system is working and the system takes care of the problem for you, why do you need to spend money on it?

**Izar Tarandach (19:22)**: Yes.

**Matt Coles (19:23)**: What's the problem? What problem are you solving by throwing money at it? The pro— the system's already doing its job. It's already working. Why do I need to invest?

**Chris Romeo (19:32)**: There's a maintenance.

**Matt Coles (19:33)**: Yeah, but maintenance is a lot, a lot different than—

**Chris Romeo (19:36)**: And there's an operational side, right? There's a, when you think about a process like the credit card thing that we've been discussing here, there's an ML, I don't even think it's AI, I think it's ML because they've been doing it for longer than AI has been hot, right? Where they've been able to detect fraudulent transactions. But there's still an operations team driving that. It's not like the machine is completely making all of those decisions for you. So it's an operational security feature, which then your security program, you have some that are operational that still require care and feeding though.

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

**Chris Romeo (20:09)**: Because you've got teams that are, you got people that are driving it. You've got machines that you're, you're working on making the algorithms better all the time. Right. So, but it's a, you raise a good point there, but I want to offer a counter to, I think you may be the events of the last year or two. Could throw off that argument that people just, that budgets are impacted because people just don't care as much as they used to. I think it's important to look at the macroeconomic situation that we've been in the last couple of years.

**Izar Tarandach (20:43)**: True.

**Chris Romeo (20:43)**: Budgets in general are down across the board. Now, it seems from what I'm, what I've been hearing, what I've been looking at, cybersecurity is kind of, is, is, is, is re, is coming back up as a hot topic. From a budgeting perspective.

**Matt Coles (20:59)**: Wait, back up. When did it go down?

**Chris Romeo (21:01)**: Oh, it's been down. I mean, yeah, budgets definitely went down across the board. I mean, from, you know, I get an opportunity to see from my own companies and then some other companies I advise. And yeah, it's been a tough, it's been a tough couple of years here for a lot of companies. Yeah. Because spending definitely, cyber budgets definitely got hit. If we look at the global perspective, maybe not individual, some companies probably spent more than they used, than they did in previous years. But I would say in general, my experience has been that people's budgets were cut just as a result of inflation and belt tightening, all the other things, all the other corporate adages that got thrown into the process.

**Matt Coles (21:47)**: Does that include VC funding for like new startup?

**Chris Romeo (21:50)**: VC funding has been very challenging in the last 2 years or so, other than in the AI space. If you had an AI idea, everybody was like, woo-hoo, here's a billion dollars. You know, your valuation is a trillion. But wait, we just gave you one piece of paper that said we have an idea, AI idea. They're like, you're worth a trillion. Come on. I'm exaggerating just a tiny bit. But yeah, I mean, AI is the only thing that's been super hot. right, in the VC space as far as people throwing money at it. But in general, the, what I've experienced is people are looking for around $1 million in revenue as their entry point to, and my answer was like, if I get to $1 million in revenue, I don't need you. I wouldn't want you on my board if I'm at $1 million in revenue.

**Matt Coles (22:40)**: So it's self-selecting is what you're saying?

**Chris Romeo (22:43)**: To some degree. To some degree. So yeah, what do you guys think? Have you seen this macro impact as well?

**Izar Tarandach (22:51)**: Yes. And actually, I even saw a bit of a golden lining in there. I had a bunch of people ask me, okay, so if I have a choice on where to put my dollars in application security, what's the most effective place to put those dollars? And 8, 9, or 8 out of 10 times it would be, hey, you know what, if you just do your threat modeling right, you're going to get a lot of bang for the buck. And, and if you push like the other activities based on that threat model, you're going to, to get something back that you wouldn't otherwise. So on a very self-serving note, uh, it did have a, a golden lining. But, uh, no, I, I, I think that the, the very fact that people find themselves in a situation where they have to choose where to put their dollars. Should I go more for this or more for that? I think that it's caused people to take, take some, to, to take a deep breath and think, okay, where is my return of investment? Which tools are actually giving me something back? And, uh, that is the truth. I think that it's healthy. I think it's healthy. I think it's, it's, it's going to, to, to lead to the market not reinventing itself, but at least reevaluating itself in some form.

**Chris Romeo (24:13)**: I mean, considering the business case for your security budget is only going to make you, is only going to get you promoted into an executive leadership position. Because if you, if you have the ability to, if you want it or not. Yeah. But I mean, if you, if you can push aside, I mean, and, and I'm sure you guys have had the same experience. I've seen people that can't do that. They can't become, they can't think through, they can't look through the lens of the business because they're security people. I'm a security person and this is what we have to do.

**Matt Coles (24:46)**: Okay.

**Chris Romeo (24:47)**: But wait, there's a business running behind this and the business experiences ebbs and flows. And so we may not have as much money, so you may have to go through a prioritization exercise, but You know, any, anybody that wants to be a security leader inside of your organization, learn how the business works, learn how budgeting works, learn how to prioritize and how to run a business and you'll be wildly successful.

**Matt Coles (25:13)**: So basically a security person with an MBA is, is your recommendation.

**Chris Romeo (25:17)**: Oh, boom.

**Izar Tarandach (25:19)**: Boom, boom, boom, boom, boom, boom, boom, boom.

**Chris Romeo (25:22)**: I mean, you know, listen, I just had a, I heard a, have you guys followed this whole founder mode? Argument that's been going on in the startup world, or this, this idea that, that, uh, Brian Chesky from Airbnb did this talk at YC where he was, he was talking about this idea of, um, of founder mode. But one of the things that they said is, um, I heard it on another podcast when in PayPal's very early days, they would not hire MBAs. They had a policy. We do not hire MBAs. And the reason was because they came in with preconceived notions about how you manage and run a business. Which a startup and a Fortune 500 are very different entities in how you operate with them and how you, how you, uh, how you, how you run them. Right.

**Izar Tarandach (26:08)**: And so, so I, I, I don't want to, to talk too much about that cuz I'm married to a scholar in, in that field. But, uh, I, I always had the feeling that, uh, you know, MBAs was more of a rite of passage thing than, uh, as a practical thing. But, uh, over time I, I, I understood the other side of the coin that they do look at a lot of things. The people who rose in the business sometimes don't look at, and that there's value to that as well. But, uh, it's, it's interesting cuz going down, not one level, but looking at, at, at closer to the product. Last Friday, I was in a panel and we were discussing security champions. And one of the things that I offered there was that in the past few years, I managed to work with some security champions who were actually product managers. And they did bring a different view to the whole security champion thing because they had an understanding of the product and of the business and of the customer, which purely security people or purely developers who are security champions. Would find it a bit more, a bit harder to, to, to offer. So I do think that that's soft, soft in comparison to writing lines of code, uh, uh, side of things that an MBA perhaps could, could bring, or a product management manager or somebody like that. I think that there's a lot of value there for us, and we have not explored that enough yet.

**Chris Romeo (27:38)**: Mm-hmm.

**Matt Coles (27:39)**: There is a downside of that though, is that you need somebody to you need somebody to balance that, that perspective, right? You know, so the, so the developer is going to be done all about getting code changes made, you know, to get security built into the design implementation or, or not, but it, you know, by and large they're going to, whereas a product manager champion may be more aligned to the, to the business cycle. Therefore not push as hard. You need somebody to do both, right? You need somebody like, I think that's what Christian was saying earlier, you need somebody with technical capabilities, but also to have business, business experience to know what's pragmatic, what's appropriate, how to, how to negotiate your way through that, right? That's probably the most important part for a champion. Is not to drive, not to force something, but to negotiate, right?

**Izar Tarandach (28:42)**: And knowing how—

**Matt Coles (28:44)**: right. And knowing how the business operates and how the development cycle and everything goes, you know, applying deep technical knowledge to a negotiation like that is probably the best case scenario an organization could hope for when it comes to security campaigns.

**Izar Tarandach (29:02)**: Come to think of it, I did notice a significant change in my, in the way that I was effective doing what we do when I started adopting more of the side of the business people and the people who were selling what I was trying to protect than just going, well, it's when reasonable security came to be, right? It's the whole idea of you just need that amount of security and not more than that. So yeah, that, that made a, looking back now, that, that made a big difference in my career.

**Chris Romeo (29:34)**: Yeah.

**Matt Coles (29:36)**: Wow. You mean risk management actually works?

**Izar Tarandach (29:40)**: Not as much risk management, because sometimes you, you, you have to say, you have to come and say, you know what? Yeah, it's risky. Yeah, it's bad, but yeah, I have to go for it. And sometimes you gotta run the business. Yeah. And, and having that realization as a security, uh, uh, person. That's going to keep you from waking up at 3 in the morning in a sweat and a panic saying, oh my God, how, how, why, why?

**Matt Coles (30:02)**: Because the risk not accepted, you know, GRC was right.

**Izar Tarandach (30:06)**: It's, and now you are overdoing it.

**Matt Coles (30:13)**: Uh-oh.

**Chris Romeo (30:15)**: Now he's pushing, pushing his buttons now.

**Matt Coles (30:17)**: Yeah.

**Chris Romeo (30:17)**: He's just picking on you. Look at the look on his face. He's just, he's just doing this to pick on you.

**Izar Tarandach (30:22)**: Oh, it's okay. Listen, most of my most enjoyable moments in this whole journey has been when Matt picked on something and I go, oh no, he's right. It's got something there. No, GRC— no, I think that you may be going overboard here.

**Matt Coles (30:43)**: Go back to Matt?

**Izar Tarandach (30:46)**: With all my love for my GRC people.

**Chris Romeo (30:48)**: Much love. Little shout out.

**Matt Coles (30:51)**: Yeah.

**Chris Romeo (30:52)**: Shout out to GRC, yo.

**Matt Coles (30:56)**: First person. All right. I think with 4 1 0 for juicy. Oh man.

**Chris Romeo (31:06)**: Right when I thought we were coming to a conclusion.

**Izar Tarandach (31:09)**: Yeah, I think that we came to a conclusion.

**Chris Romeo (31:14)**: For some reason Matt keeps leaving.

**Izar Tarandach (31:17)**: It's the GNC people pulling the cable.

**Chris Romeo (31:20)**: Matt keeps getting offended and, and just leaving. He's like, I'm hanging up. Okay, I'm back. You guys are stupid.

**Izar Tarandach (31:26)**: GNC Gremlins pulling his cable. Although, God.

**Matt Coles (31:28)**: Yeah, that's what it is.

**Chris Romeo (31:31)**: All right, well, I think that with that we can, we can call this an episode. I feel like we, we, we made some progress there. Thinking about and talking about the impact of how data breaches have been numb. We've become numb to them, but also from a positive perspective, it's because the security control is working. So I think there was some, I think we made some headway on understanding how that impacts, and it'll be interesting to see how that comes up in future conversations when we start to—

**Izar Tarandach (32:02)**: And now I have an idea why I got out of bed.

**Chris Romeo (32:07)**: Well, folks, thanks for listening to another episode of the Security Team.
