A Zero Trust Leadership Podcast

Spotify logo with text 'Listen on Spotify' on a dark rectangular button.Button with Apple Podcasts icon and text 'Listen on Apple Podcasts'.
Why Zero Trust Fails (And How to Get It Right) | Erik Jacobsen
Season Four
· Episode
16

Why Zero Trust Fails (And How to Get It Right) | Erik Jacobsen

Erik Jacobsen joins us to talk about what happens when Zero Trust strategy collides with the real world.

Transcript

Raghu Nandakumara  00:00

Welcome back, everyone, to another episode of The Segment. We spend a lot of time in cybersecurity talking about what organizations should do, and when it comes to Zero Trust, the principles themselves aren't particularly difficult to understand. But then you actually have to implement them. You have legacy systems, applications no one wants to touch, dependencies no one knew existed, different teams with different priorities, and of course, a business that still needs to operate while you're changing the way it's secured. That's the part of Zero Trust I want to dig into today. What happens when the strategy meets reality? And joining me is someone who has spent a lot of time in exactly that world. Eric Jacobson is a director in KPMG's technology strategy practice, where he helps government and commercial organizations implement Zero Trust. Eric, welcome to the segment.


Erik Jacobsen  00:54

Well, thank you, Raghu, and it's great to be here. Very much looking forward to talking about this. Zero trust is a it's a topic that I'm very passionate about. I've lived through a lot of IT changes in my career, 25 plus years, and I think that one of the biggest and most exciting for me is Zero Trust. And I'm so grateful that I'm able to do this kind of work day in and day out, helping organizations, both large and small, really achieve their Zero Trust goals. Now, I'm very happy to talk a lot about what I've seen in industry and where I where I've seen pitfalls, and you know where organizations sometimes struggle when they move from the conceptual to the reality. I do want to be clear on one thing, though. You know, this is this is a topic I'm very passionate about, and but I do want to be very clear that the views that are expressed by me today on the observations, any tea leaf reading I'm doing for the market or anything like that, these are all my own. These are strictly my personal views, and do not reflect the views or opinions of KPMG as a whole. This is just my personal observations from what's going on in industry today.


Raghu Nandakumara  02:10

Awesome. Well, Eric, you used two words that are very personal: passion and excitement. So tell me exactly why you are so passionate and excited about Zero Trust.


Erik Jacobsen  02:24

Well, that's a good question. You know, when I started in this industry, and I'm going to take you way back here. When I started in this in this industry, and we were talking about 10 megabit hubs and all of those fun things, really, security was kind of an afterthought. We, I, I often saw. This is back when I was working in industry. You would go deploy something; it'd be very coarse because the assumption was just bad people aren't going to find us. They're not skilled. They don't know we exist. And I've seen this transition as the bad people, as the malicious actors, are getting more and more mature. I'm seeing a lot. I've seen both in industry and in my you know in my consulting role. I have seen this really evolve. They're getting smarter. They're getting sharper, and a lot of these legacy environments just can't keep up. And candidly, I don't like the 3 AM phone calls. Something bad happened. We need to fix it. That's why I get so passionate about Zero Trust. Because when properly implemented, Zero Trust can fix a lot of these porous legacy environments. It can keep the bad guys out, or more in in in all reality, breaches happen. Breaches happen. It's not a if they're going to happen. It's a when, and the way I see it is when the breach happens, Zero Trust helps contain it, so that really, it's a bad afternoon, not a bad bad set of all nighters followed by a gang called before the board and trying to explain things. It's not a career-ending event, shall I say? And that's where I get really passionate about it. Is as I said, I don't like getting those 3am. phone calls. Anything we can do proactively to improve organizational security posture and get them to the point where they, their teams, I none of us are getting woken up because you know somebody in China or somebody in the basement of their parents' house. You know, there's some somebody with too much time on their hands and some malicious goals at Yale Broken. And anytime we can keep that from happening, anytime I can get that full night's sleep, that's important to me. But also, you get some tangible additional benefits out of a Zero Trust program, things that people don't normally think of. People think of Zero Trust, really. I find as a it's a security program. It's protecting my network. It's protecting my assets, and that's a critical part of it. That is the you know that's the north star for any Zero Trust program. But the ancillary benefits are huge. A lot of times, especially in large and large environments and legacy enterprises, things like that, you have all of these legacy applications. You have this entire legacy footprint. Problem number one: you need to be able to secure it, but problem number two: person who wrote that, person who built it out, yeah, they've been retired for 18 years. Even you know, even if you've got a good security posture, or you think you have a good security posture, at some point you're going to need to upgrade servers. You're going to need to buy a newer mainframe. You're going to need to migrate between data centers and some, or maybe even modernize and go up to the cloud. And that person who retired 18 years ago, they're not going to answer your call. And so it's a big black hole. And when Zero Trust is properly done. Not only does it secure these legacy applications, but it also provides this wealth of ancillary data, this contextual data that you can then consume through like API access. You can feed into a data lake. You can map against other things, and you can really build out this wonderful picture that really helps your current team understand what they have. I get excited about that. I think it's really cool.



Raghu Nandakumara  06:31

So I love I love the excitement, Eric, and I can say for sure, having done I don't know we've done like 4050 episodes of the segment, no one has brought that level of excitement and passion to Zero Trust right from the get-go that like you have today. But I'll ask you this: so we hear a lot of organizations that say, "Yeah, Zero Trust sounds fantastic on paper." However, we're just not convinced that its ability to achieve essentially the outcomes that you've just described. What do you say to them?



Erik Jacobsen  07:09

Well, that's a good question, and you actually have to peel back the onion a little. Whenever I hear someone say something like that to me, what I like to do is try and understand the underlying driver. Why do they feel that way? Do they feel that way because they believe their organization is too complex and it would be be too difficult to implement properly? Do they feel like it's great on paper but it's not going to achieve their goals because they have doubts about the platforms and technology that they're looking at for Zero Trust. The question really is, why do they think it's not going to achieve their organizational goals? With of course the related question of what are their organizational goals anyway, and that is something critical that you always have to unpack. When someone comes to me and it says that the first thing I want to come back to them with is, okay, I hear you. So, what are the organizational goals that you feel Zero Trust cannot achieve? Usually, I'll get an earful about, well, there's this, there's that. Oh, we're organizationally complex. Oh, we're running a lot of legacy systems. Oh, you know, we haven't refreshed these servers that since 1998. You know, or they'll come back and say, "Well, I just don't have the staffing. I'll deploy this tool and, or these tools, or I'll deploy this whole strategy, but I won't be able to operate it, or they'll come back and say, "I just don't simply see the value. It's spend, and yeah, I don't. I don't see the value here. I'm never going to get hacked." You know, there's a variety of different underlying drivers. So really, the first thing you have to do is you have to identify what the actual business goal. What are they trying to solve for, and then once you've unpacked that, then you need to understand why they believe Zero Trust is not for them, given these organizational goals. Once you understand both of those, then you can really have an intelligent conversation. Now, I can go into a lot of detail around the way those conversations can go, but that's going to be me talking for like six hours now because there's so many different permutations of organizational goal and underlying driver. So I'm just going to give you kind of the great tips, maybe the two or three top ones. The biggest ones I hear when someone says Zero Trust is not for me is either they are operationally concerned. I don't have the staff. I run a lean organization. I can't. I don't have the funding to hire. Or Zero Trust is is operationally intensive. I'm going to need to hire 20, 3050 people to run this and. I don't have that kind of budget, or I don't have the budget to hire anyone. And my team is so heavily, you know, occupied with just keep the lights on work, other projects that are in the pipeline that I can't have them focus on this. So when you have that sort of operational concern, that. a pretty easy conversation to have because Zero Trust, and you know Zero Trust is conceptually it's incredibly simple on paper, but it gets very operationally messy very quickly, especially when you are talking about a existing environment with a you know non homogeneous environment been around for 50 years 100 years it's been around since before there were computers you know it grew organically it it is operational it can get operationally messy I mean trying to deploy Zero Trust I'm just giving an analogy here trying to deploy Zero Trust to a complex organization with a lot of technical history, shall I say, it's it it's a lot like trying to rebuild the jet engine of an airplane while you're piloting the plane across the country, and the plane's loaded with all of your core revenue for your business. That's that's really and so as I said, it can get very organizational. It can get very operationally complex very easily. So what I like to tell them is, don't boil the ocean. Yeah, you know, or throw another to throw another um thing that my grandmother used to say to me: Rome wasn't built in the day. What you you you can break a Zero Trust journey, and truly, Zero Trust is a journey. It's not a destination. Attackers are evolving. Technology is evolving. I mean, we see like with Mythos and everything else, like the attack vectors are changing constantly. It's you're never going to complete a Zero Trust journey. What you are going to do is you are going to get on a sustainable path, and so now taking that back to your original, all of that back to your all that context back to your original question, what I tell them is break it down. Don't boil the ocean. Let's start small. Where are your single biggest threat vectors? Okay, how can we solve them? What opportunities are there in the market to solve them? Is there a managed service that can do it? Is there a tool or a technology that can do it? And once you sort of answer that question of how can you do just the first step? That's all I'm asking. Take the first step. How can you do that sustainably? Success breeds success. Okay, great. You got east-west traffic controls up, so attackers can't hop across your network anymore. Now let's start looking at identity a little bit. How can we, you know, how can we do this non-intrusively, just baby steps? You don't have to do it all in one big bite, but the key thing you have to remember is, when you are doing these baby steps, you just need to make sure that everything you're doing ties back together. So it's important to sit down and develop a gradual implementation strategy, something that ties together the various tools, the various technologies, the various organizational capabilities into a nice cohesive whole, and then it's just and and then it's easy. It is a journey, but it's easy. Now, the second answer would be if they believe that they just are not. the The second biggest one is they just don't believe they're a big target. I sometimes hear people say, “Oh, well, I'm not a Fortune five company.” Attackers aren't interested in me, or you know, I don't need Zero Trust. You know, I'm I you know I'm I I'm a small regional bagel chain, or I'm a you know you know in in you know I I I have one office in Peoria, Illinois. Not picking on Peoria, Illinois. Love Peoria, Illinois. Been there before. Great great place. Has some good restaurants, but you know I'm a small office in Peoria, Illinois. I don't have anything else. Most of my stuff is in the cloud. Why do I care? And again, that comes back to really understanding where that mindset comes from. But I hate to say this, and this is this is sort of the tough talk moment that you have to have with people. Is I understand that you're a small organization. That doesn't mean that malicious actors don't see value in breaking in; that they don't find value. Do you? Who are your suppliers? Who do you work with? Do you have any trust relationships with larger organizations? They're going to see you as a low-hanging fruit target. Get in here. And then use you use the foothold in your organization to get to this other organization that they're actually interested in. So you just have to sort of flip the narrative there. You have to make them think more than just about well, I'm small, I don't matter, but put them in the context of sort of the bigger tapestry of all of their business relationships. Surprisingly, then you'll find they realize they do matter.



Raghu Nandakumara  15:24

So, just firstly, you mentioned bagel shops. I love bagels, and definitely, if there's a campaign for bagel shops adopting Zero Trust to ensure that they don't got a guard of business, I'm here to sponsor it. I love a good...



Erik Jacobsen  15:36

Well, hey, you know, I am. I live in New York, so bagel shops are near and dear to my heart.



Raghu Nandakumara  15:42

Oh my God! That's that's the thing that living in the UK when I come to the U.S., it's it's the thing that I one of the things that I enjoy the most. So you you kind of left that at a at a point where it kind of leads on to nicely onto my next question, which is when do you see that aha moment happening where they go from being skeptics to being okay. I should try this. I should give it a go. Like, what is that tipping point?



Erik Jacobsen  16:09

Again, good question. And I'm going to give you a probably not the answer you're looking for because I'm going to go back to just like with value drivers, it varies based on business. I find that a lot of times, when there is a publicized breach in the industry they're in, when something like that happens, then all of a sudden it becomes real. I'll you know I'll give you an example from the news, not not something I was involved in, but this is just sort of my observation from reading the news, staying on top of things. There was a rather large southern city, and a malicious actor got into a very junior employee's computer, and then from there they were able to spread ransomware across the entire network, brought the entire city to a screeching halt. Prior to that, a lot of cities kind of didn't really think that much about attack vectors and east-west traffic control, and how do they? They thought a lot about like, oh, we'll throw up firewalls, we'll build a nice strong perimeter. They didn't really think about once you get through the perimeter, what's to stop people from moving around. And following that, following that, and it was well publicized. This was all over the news. I'm sure all of your listeners know what city I'm talking about. I've seen a lot of local, state, and local governments. They they've started asking the question: Wait, am I vulnerable? Do I need to look behind my perimeter, beyond just perimeter security? So that's one. That that that's one. And that is not my favorite way to change the script because that means something bad happened to someone, and I hate when that happens. The other way I really find that helps to change the script is to get them to that aha moment. Is going back to what I talked about earlier on the podcast, getting them to understand the ancillary benefits of a Zero Trust program. It's not operating in a vacuum. You're getting all this other X, Y, and Z out of this, and these drive benefits. I've seen in industry even what I one thing I've seen is sometimes organizations that maybe weren't that interested in Zero Trust. That's nice. It's not for me, or that's nice. I really want to do it, but that's five years down the road. You know that that that's further on my roadmap. Have become very interested when you can draw a parallel behind or between what you are doing in Zero Trust and the sort of data, the sort of insights. Because that's the thing; it's not just a lock and a key; it's also the insights, and so when you are getting, when you can draw that parallel between the insights and the additional data you're getting, and map it back to some an initiative that they're currently interested in, when you can get there, I I I find I I find it kind of funny, but it's almost like they fall into a Zero Trust program. You know, you're backing into it. You're not coming from that security angle. You're coming from the, you know, you're coming from a different angle. And really, I think that's that ties back to the second the second question that you had, which is that ties back to understanding the value drivers of the business understanding their goals and their goals may not be Zero Trust, but understanding their goals and understanding why they think Zero Trust isn't for them. Really, it's knowing your audience, understanding your audience.



Raghu Nandakumara  19:58

Fantastic. So. Kind of, you've taken us through this progression, right? Because you you start essentially with the like why organizations should adopt Zero Trust, how you address skeptics, how you get them over that hump. But what we still see is is that a number of organizations who are who acknowledge that Zero Trust strategy is the right thing for them. They kick off a project, but it fizzles out, right? And there are so many Zero Trust projects that are that are essentially failures. So, again, my question is: is that what are the common patterns with failures, right? Why do those organizations fail?



Erik Jacobsen  20:39

I would say I'm going to give you three. They're sort of, I would say. In fact, I would say there are as many reasons as they fail as there are organizations who fail. But when you again peel back the layer of the the layers of the onion, when you get to the heart of it, it really comes down to one of three things: Money, technology, or people really that's the thing. And I'm going to take them in reverse order this time because I find the people aspect incredibly fascinating. A lot of times, I find that people at at a technical level and they're you know and maybe they're at the organizational level, but not at the or maybe maybe at the um you know at the organizational level, but not at like the corporate level. I think that a lot of times folks there understand they get it because they're the ones getting the 3am. phone call. But there have been some horror stories out there in the news about failed implementations of various technologies, and a lot of times when you're talking about the ultimate decision makers, the C-level folks, the boards, the whoever, that's what they're seeing. They're seeing my peer tried to implement X and spent millions of dollars and ended up having to back out. My peer tried to implement Y, you know, spent billions of dollars, and again had to, and you know, and it failed. They're seeing a lot of that, and by the but by their very job description, folks at folks at the C-level and folks who are on boards have to be risk averse. They have to be good stewards for their companies, and so they're always going to be looking at this from, or they're often going to be looking at this. I don't want to say always, but they're often going to be looking at this from. I hear about failures. You don't hear about successes. So what I see a lot of times when it comes to the people aspect is senior leadership sometimes is just not they're concerned about making changes that could negatively impact the Business that sort of that that sort of the people aspect that's the biggest stumbling block and that's where really a coherent Zero Trust strategy and you're going to hear me talk Zero Trust strategy off and on throughout this but that's where your coherent Zero Trust strategy has to come into play. You can't just start throwing Zero Trust eggs at the wall, you know, to create a nice little Jackson Pollock painting. You can't do something like that. You need to. It needs to be paint by numbers, and it has to be. And when you can develop a good strategy, good things follow. And also when you could articulate a good strategy, senior leaders, ones who are concerned with risk for the business, they understand why Zero Trust is good idea. The second one is technology. You know what I find interesting is a lot of times, like I'll go to various websites. I, as I said, I'm passionate about Zero Trust. I'm passionate about this this whole space. I've been passionate about it for longer than some of my younger colleagues have been alive, which is kind of terrifying to me. But I've been doing this a long time, and what I see is a lot of times you go out there, you read about Zero Trust, you read the Gartner’s. You read the Forrester’s. You read analysis. You read thought leadership. And what I find interesting is so much of it is written as if you're going to be doing a green fields implementation. And so it's like here's you know here is best in class. Here it here is you know the perfect architecture. Here is how you want to do things. Everything ties together nicely. It plays together well. It doesn't take into account that every organization that's been around for more than a year has legacy tech debt. They have some form of tech debt somewhere. I guarantee you. Every organization is tech debt, and every organization has legacy equipment, legacy applications, legacy architectures, and so that becomes a stumbling block because you you know you've got this legacy tech debt, you've got this legacy environment, and yet I'm going to go read about. I'm going to go investigate Zero Trust. I'm going to go do X, Y, or Z, and it's telling me about how I can do all this green fields implementation. And that it just it doesn't resonate. It doesn't resonate. What we all collectively as Zero Trust practitioners, have to do. And if I would, if I would say, if I can give you one call to action out of all of this, what we have to do is get better at translating Zero Trust from a legacy environment lens, because when you again, it comes back to people in the end. Because people make the the decisions. AI might become our overlords in 50 years, but for now, people at the end of the day still are the ones making the decisions. And if they're the ones making the decisions, at the end of the day, you you know you have to communicate back. We have to be able to communicate back to the decision makers that yes, we understand this is a legacy environment. Here is our strategy to implement Zero Trust, uplifting where necessary, but adapting to current conditions where possible. That's a very different message than what you read in a lot of um the white papers and a lot of the technical briefings that are things like that, and then finally of course funding. That that I I say that one for last because funding can be a touchy subject. You know how you know what are you everyone you know these days everyone's trying to do more with less. That's what the great you know, and I'll touch on this more in a little bit. But that's both, I think, one of the biggest advantages to AI and what's coming down the pipeline in AI, but also one of the biggest challenges. But it's it's funding. But from a Zero Trust perspective, and even more just generally from an organizational perspective, we're all trying to do more with less, And so, finding the funding.



Erik Jacobsen  27:27

If there is not a strong business understanding that this is needed, if something bad hasn't happened, bluntly, if something bad hasn't happened to an organization or to a peer organization of theirs, then there's probably not a sense of urgency, and I will put I will give you one caveat there. If you operate in a regulated industry or in some other way you are regulated, and the appropriate regulator says you must do Zero Trust, and when I look at this, I think about like CMMC is a great example.



Erik Jacobsen  28:04

You have a law saying that if you operate and you are dealing with any sort of confidential and class information, doesn't matter if you're prime contractor sub, the sub do a sub, the sub do a sub do a sub. It doesn't matter if you're touching CUI, you must be CMMC compliant. That sparks a Zero Trust conversation. But outside of a regulator coming in, outside of applicable regulations, and outside of a moment of a moment of realization of wow, you know, my my sister organization over here, my brother organization over there, they had a security problem. I need to be concerned. A lot of times, there's just not that sense of urgency. And if there's sense of urgency, your your leaders in your technology organization are going to put in the budget. It'll probably get stripped out. It'll probably get pared down to a point where you can't actually do anything. The way around that I find is to really make again make it relevant to the organization, for to the decision makers, the financial people, the business leaders, making it relevant, making it making them understand that it is a having that conversation, helping them understand that it is a bigger risk to not do it, and the financial impact of not doing Zero Trust is greater. It's like, do you want to spend $10 now? Do you want? Do you want to go dig through the couch cushions, find $10, and spend it now, or do you want to get hit for a bill for $100 in six months? Yeah, I think most of us would say at the end of the day, it's better to spend a small amount now. So, but you have to frame it that way. And again, it's interesting because all of these. Yeah, all of these finance, technology, all of these organizational roadblocks. They all come back to people, and really having that open and honest and clear conversation, making it relevant to the decision makers.



Raghu Nandakumara  30:14

So you gave us three things there, right? I did. People, technology, urgency, right? Or finance. Finance. Finance. I mean, yeah, finance. Ultimately, unlocking, unlocking finance through sort of driving, driving the need and driving that urgency. So, and I want to just explore all three of those in a bit more detail. Let's come back to the people thing because one of the things that we hear about Zero Trust and and actually John John Kindervag, who I'm sure you're familiar with, one of the things he says is that Zero Trust. Yeah, it's fantastic. Zero trust is essentially a, in many ways, it's a people problem, right? And one of the challenges is is that you need to get buy-in beyond just the security team, because it does touch sort of every part of your your technology organization and potentially beyond that. So, how do we collate that collective engagement and moving in that same direction?



Erik Jacobsen  31:10

I hear you. And before I answer that, big shout out to John. He is he is truly amazing, and he is he says it much better than I can. I'm going to be honest. There, you know, he's he's thought about this for a long time. He really is the thought leader in Zero Trust, not a, but the thought leader of Zero Trust. And I had the pleasure of sharing a stage with him about going. I guess not sharing a stage exactly, but going on immediately after him on the stage, and big shoes to fill. But he says it really well. You have to get the stakeholder buy-in. Zero trust cannot be. And I'm glad you brought this up because this again ties back into the underlying concept of Zero Trust is a people problem, not a technology problem. You have to get the buy-in. It can't. Zero trust cannot be a security project. Zero trust has to be an organizational change, and that ties back into what I was saying earlier about you need to know your audience when you're talking Zero Trust. Whether you're a network engineer and you know whether you're a junior network engineer working at a small company, some somewhere, and you want to bring it up to your boss to try and get your organization to focus on this, or whether you're a third party who is trying to help do the right thing for your for for an organization and get get Zero Trust happen, or whether you're a vendor and you're trying to bluntly sell Zero Trust success, it you know it does it doesn't it doesn't matter if you can't it it you're not going to be successful if it's a security project.



Raghu Nandakumara  32:58

Yeah, it is



Erik Jacobsen  33:00

not a security project. Zero trust has to be an organizational culture shift because Zero Trust goes beyond. And I mean, we all talk about technology. We're all technologists here, but Zero Trust goes beyond just the simple east-west traffic controls, identity and access management, enhanced, you know, enhanced boundaries. It goes way beyond. You know, I could continue rattling down the pillars of Zero Trust. I'm going to save your. I'm going to save your listeners some time here. It goes beyond this. Zero trust is also this guy. This person just walked in behind me when I swiped my badge to walk into the the building, challenging them. Hey, what you doing, man? And that is a culture shift. That is a mental that that is a culture shift. That is a mental shift that every employee has to have. But getting back to Zero Trust. So I want to be clear. It's not just Zero Trust is not just technology. Zero trust has to permeate every aspect of your organization. But stepping back, when you're talking Zero Trust and technology as we are today, you have to make it relevant outside security. It can't be the security project. It can't be oh, security's rolling out this new tool. We're doing this cool thing. Zero Trust. At the end of the day, it should never be a security program. It should be an organizational culture change. And changing organizational culture is hard. People like the way they do things, even if there is even if there is a better way. People like doing it, doing their activities. They're they're you know they're doing their business doing executing their job functions the way they know because it's what they know and Zero Trust really does touch every aspect of an organization and Zero Trust really does require a mindset shift for everyone. You have to do organizational change, but the easiest way to do organizational change is to make sure that everyone feels like they've got skin in the game, to make it relevant. And this is where I go back to: it can't be just security. Tie in with your app with your application teams, you know, help the they'll help them with help them understand their application architecture for their legacy applications. You know, provide you know configure set things up so that you're showing um you know you're showing HR into you know give HR interesting new data points. Give your application team um actual architectures rather than what's on paper from 18 years ago, you give your compute teams a better understanding of the utilization of their servers, or give your cloud team a better understanding of what is actually what what applications in the cloud are actually relevant. Provide this interesting data to them, get them bought in. Make it less about we're trying to lock everything down, and more about look at all the cool data I can give you. Look at this additional bit of information. Give your finance team information around assets that are being underutilized, or maybe not utilized at all, and can go away. You get this broad organizational buy-in. You give, and I do personally believe it comes back to data in a lot of cases because data is currency in large organizations. If I can give you data that helps you do your job better, or that helps you do your job more efficiently, or that helps you get a leg up on your competitors, if if through a Zero Trust program, I can give you that. You're going to be bought in. You're going to be like, that is a great idea. Sign me up. Yeah. And once someone's bought in, or culture change is easy.



Raghu Nandakumara  36:51

Yeah, I think I think that's a that's a great point, right? That that getting buy in by showing them something that they care about, right, gets them on the train, and that's essentially you. You that's how you get everyone on the train going in the right direction. Okay, next item. You you spoke about essentially technology, and the the point you made was that vendors, practitioners, thought leaders, etc., very much kind of frame Zero Trust in this idea. Like the starting point is a greenfield estate, right? You're starting from zeros. You can put all of this in place as you go along. And as you kind of said, which is like if you're more than if you're an organization that's more than let's say 12 months old, you are carrying technology debt, whether you like it or not, whether you want to admit it or not, you've got technology debt, and you are not a green field. You're a brownfield, but there is just not enough best practice advice about how to do Zero Trust for for brownfield. And your CTA was, we need more of that. So let me flip that question back to you, right? And what? How would you essentially document frame Zero Trust for brownfield environments.



Erik Jacobsen  38:06

Find the pain points of the brownfield environment. Seriously, find the pain points. Is it that you? Is there something happening on you know you're having intermittent network connectivity issues and you don't know why, or you have this application. I know I talk a lot about application legacy applications. No, people don't people don't buy systems. People don't go buy a mainframe or big a big some big iron system. They don't buy that to buy the system. They don't buy it. It's not like going to buy in a Ferrari where then you're going to park it in your um you know in your driveway, and let your neighbors ooh and ah. You're not buying it to say, "Look, I have a mainframe." You're buying it because you have a specific business need, and more specifically, that business need for this compute power, this transactions per second power, this insert, you know, insert your business need here, is driven by a core application, and that's the other thing to remember: is that a lot of these most critical legacy and you know components of the environment, the things that are probably the most challenging from a Zero Trust perspective, are also some of the most critical to business viability, because you're not going out and buying a mainframe to host your file that file share that your employees are putting their cat pictures on. You're not buying it for that. You're buying it because you need to. You you you're a financial institution. You need to process millions of you know financial transactions per second. You're buying it because you're a air traffic control organization, or you know, and you need to process millions of flights and where they are in position to each other in all four dimensions. You know, you're you're buying you're you're buying big iron gear, the most like the. The most legacy stuff you have, it's not there because you want legacy. It's there because it's critical to the function of your business. So, tying that back to your question, the what you have to understanding why they have what what are the critical components of their legacy environment, and then being able to show again, because at the end of the day, Zero Trust is people problem. Being able to show how Zero Trust can help. I've got this legacy application. I don't, you know, I I gave this analogy at the beginning. I'm going to give it again because I think it's very important, and I see this in a lot of places. I have this very important application in my business, it runs on very legacy hardware. I maybe want to modernize it. I want to do X, Y, or Z with it. I don't understand much about it because everyone who built it, maintained it, and evolved it is retired. They're they're they're they're living their best life in in the Bahamas. They're not going to answer my phone call, and so giving that, I think that is a great again. That's a great entry point. Is I can give you this information through Zero Trust because again, Zero Trust is a journey, and Zero Trust really starts, and the Zero Trust journey really starts with understanding. You understand, you define, you build, you secure. It's sort of this journey, and that understanding piece, that intelligence, that additional detail you can provide really is a business value driver, and that's where these core applications, these legacy applications that are business critical, that's where you can flip the script. That's where you know. But but again, when you're talking to people, you have to understand what is important to them, what is important to their business? So, hopefully, that answered your question.



Raghu Nandakumara  42:06

Yeah, it's a, it's a, it's a, it's, it's a, it's a good solid. I'm glad that you had the answer to your to the challenge that you've posted to to to the rest of us. So, the the third thing, um, on the finance side of things, right? So today, of course, the and you've kind of touched on AI a few times. The what is driving all the all the noise, news, hysteria, hype, whatever you want to call it, at the moment is of course kind of like on one side organizations adopting AI in all of its flavors, in all of its kind of manifestations at a rapid pace, and on the other side, the the perceived sort of acceleration of cyber capabilities in the AI models, and then their use by attackers, and all of this seems to be accelerating the need for organizations to essentially accept that Zero Trust is the strategy that is best suited to essentially protect their organizations from this. So, and from that unlocking, essentially helping to accelerate that sort of financial approval. Are you seeing this manifest in reality that sort of the the AI hype train is driving more Zero Trust budget.



Erik Jacobsen  43:25

Yes, but not in a positive way. And what I mean by that is, I look at I I look at ways you drive budget in two ways, positive or negative. You're either achieving something new that is valuable for your company, and this is great, or you're acting defensively because something scary is out there. And AI hype train right now is extremely scary. I know we've talked about. I mentioned Mythos before. I'm sure a lot of your listeners are very familiar with it. Mythos is. It is a very scary. Like personally, it's very it's it's very scary because it's basically turning decades of security patches in some cases irrelevant. You know, Mythos is finding all of these zero days. Mythos is, you know, it's and mythos is really providing this stack vector. It's it's extremely scary, and I think it's good to be scared about it, honestly. So people are reacting, and you know, mythos, you know, and I I find it interesting because what I see in industry is I see manufacturers have upped the cadence of their security releases. You know, you have manufacturers, hardware manufacturers, who maybe spent six months, nine months vetting out a firmware update, or a software update, or a system patch, or things like that, vetting it out before releasing it. It's really speeding the release cycle, and it's. But again, they're reacting defensively. If not, we're speeding the release cycle because we can, and because it's going to drive value for our customers or value for us. We're speeding the release cycle of our firmware, our software, our security patches, etc. Because we are in a defensive mindset. Yes, it opens a lot of it opens a lot of wallets. Mythos really has brought vulnerability to sort of the forefront of the decision makers, and that goes back to what we were talking about earlier: board members, C levels, people who normally aren't in the weeds with technology, are now asking, "What's Mythos? What's this AI thing? I heard I'm vulnerable. I'm heard bad things are going to happen because of it. You know, I watched The Matrix too many times, and now I'm worried about the AI apocalypse. Okay, that last one is a bit of a joke, but no, you're suddenly like, people are reacting from a you know position of fear, but and it is opening, it it is releasing funding, it is allowing funding to be prioritized towards implementing Zero Trust and towards protections, towards trying to keep the big scary out. But the problem, the the challenge, and and so well, I will say so from on one on one respect, even though I find some of what's going on in AI, you know, rather terrifying. From at the same time, I also see it as you know it is a way to get that conversation started, but the challenge in that, and tying this back to funding. The challenge in that is, people are if if some you know is that leads to defensive thinking, reacting defensively. You're spending money defensively, but if the if you're spending money defensively, your engineering thought process, everything is that follows is going to be defensive. It's not going to be forward-looking. It's going to be how do I plug this hole over here? How do I protect myself over here? And you end up doing a lot. You end up having a lot of sort of hair on fire. We need to execute this. This is the top priority. Okay, it's done. Now we need to execute. This is the top priority. It's sort of the scatter shot approach, without taking that step back and really developing the Zero Trust strategy, tying the various components of Zero Trust together, aligning it to your environment, and really making sure that it is relevant for you. That's that that that that's that that's downside to people spending money defensively.



Raghu Nandakumara  47:44

So let let me just ask a follow up question to that because I I I think the the expression of it of like essentially differentiating between defensive spending, which is very much around, we've got a hole here, we need to plug it and plug it as quickly as possible. So of course, right, the whole all these frontier AI developments have definitely, at least, brought to the sort of, to sort of the the front top of mind that the possibility that these holes exist, right? So there is absolutely that very real defensive hair on fire mentality. How do you take that opportunity, but but to your point, turn it into a offensive is not the right word because then people think about defensive and offensive security, but more about use this use this moment, but in a way that very much couples the benefits of the strategy with aligning it to kind of where you want to be going from like a business perspective, without losing the urgency, I should add, right?



Erik Jacobsen  48:47

I, there is, and I appreciate that clarification. Without losing the urgency, the it's a people problem again. But in this case, it's a people relations problem. It's and and it's very different depending upon where you're coming from, as you, the Zero Trust practitioner who needs to, I don't want to say speak truth to power because that's not entirely accurate, but needs to try and ensure that what you're doing is going to be long term productive, long-term sustainable is not just you know throw the paint at the wall. It's the paint by numbers. You know you need to make sure that you are you know you you need to make sure that your organization is doing doing this properly, doing it methodically, doing it logically, doing it with sense of urgency. But again, as a Zero Trust practitioner, different folks come. You know, there's a lot of different Zero Trust practitioners out there. Is I guess the way to put it, you have people who are in you who work for the organization who maybe are very junior and need to bring this up. You have people who are more senior in the organization who, you know, maybe want to bring this. You want want to try. Shape the defensive spending into something that is a long-term benefit for their organization. Then you have again you have third parties, whether that's you know your managed service provider, whether that's your value-added reseller, whether that's your advisory partner, your consultant, you know whether that's your vendor, and depending upon which persona you fill, that conversation is very different. But what it comes down to is, you need to make it relevant, and you need to speak from a position of trust, and that's a you know we talk about Zero Trust technologically, but now now we're talking personal people to people trust. You need to be able to speak from a position of relevance. You need to be able to speak from a position of trust, and you need to be able to speak from a position of knowledge. And depending upon what persona you fill, that path is going to be very different. I can I can tell you that in my professional life I am very lucky to have to be part of a well known and trusted organization. So when I speak my when I speak to my clients when I speak to organizations when I speak to your listeners, you know, even though these views are my own views, I'm still I still have that sort of inherited authority from the organization, but not everyone has that. You know, as a vendor coming in, when you're speaking, you have a very different path to speaking from a position of trust because people are going to look at a vendor and say, "Hey, you're just trying to sell me something. We know I need to. I need to get this done. Why are you trying to talk to me about this? You're trying to sell me something." And then that's very different from your um from your internal stakeholders. Your internal stakeholders a lot of times how they they probably have those personal relationships, you know. My boss trusts me, so I'm going to raise this to my boss. My boss thinks about it, understands. I help him understand or her understand that this is, you know, this is important. That we need to approach this not from a defensive perspective, but from a opportunity perspective. What what positive can that come from this? You know, and then and then my boss is trusted by their boss, and you know you feed up the food chain that way. Or if you're a leader, if you're a technology leader, you know, hope I would hope that at this point you have trust built up and you can speak from a position of authority. But again, it's depending upon the persona. It's a very different approach. But at the end of the day, once you have that trust, and again, it goes back to knowing your audience. Once you have that trust, once you know your audience, making it relevant. That's that's the biggest thing. You want to okay? You heard about this big scary thing happening. You suddenly want to spend money on an identity an identity program. That's great. I love it when you want to start thinking seriously about identity.



Erik Jacobsen  53:17

But can we take a quick look at how you at. Let's make this not just a security thing. Who else can you cite? Any? How can we really take that step back and look at how to be productive rather than just go out and buy from the first um the first person who shows up and says, "Hi, I can sell you an identity solution." Yep, that's that. That's the thing. Is again, know your audience, know what their drivers are other than reacting defensively and be able to speak to them from what's important to them and to their to the organization. Yeah, and unfortunately, I can't give you a secret magic formula. There is none. It what it comes down to is it comes down to knowing who you're talking to, having that trust so that they will listen to you, and being able to articulate, and if you can do that, you can shift a defensive mindset. That's you can you can you can you or you can maybe harness the defensive mindset to a purpose that's beneficial for the organization.



Raghu Nandakumara  54:19

Yeah, in fact, Eric, I'll slightly disagree. I think the the you you say that you don't have a secret formula, but I think that that secret formula that you've encapsulated throughout this conversation is this: is that in order to get people sort of saying, "Okay, yeah, I think Zero Trust is the right thing for us to do," for them to get them over the hump, to get them progressing, right? And you laid out sort of people, technology, finance. In each case, that word that you've used repeatedly, relevance, showing each of these groups that it's relevant for them in a particular way that is going to benefit them. That's the key to kind of progressive success.



Erik Jacobsen  55:00

Well, you know what? I would agree with you on that. I would agree with you. I think that is the number one thing: relevance. Make it important. You know, articulate. Make it important to them. Make it important to your stakeholders. Make it important to your non-stakeholders. So I guess I guess in that case, you're right. There's your secret formula there.



Raghu Nandakumara  55:19

So okay. So I know we've kind of. I think that's a good point for us to move on to a bit of a a a lightning round before we wrap up, right? So, oh dear, you are incredible at long form responses, but this time for these questions, you have to give a very very short response, right? So the the first question, in your opinion, what is the cybersecurity truth that most organizations don't want to hear?  



You will get hacked.  



Okay, something that the industry treats as accepted wisdom that you think is absolutely wrong.



Erik Jacobsen  56:00

Security is hard.



Raghu Nandakumara  56:01

I I like that. That's that's a good one. Okay, let's. The last time you were significantly wrong about something in this field, and what was it? Oh,



Erik Jacobsen  56:13

AI never is going to matter because um, all it is is a bunch of decision trees, and you know it's a it's a bunch of really fancy for loops. Oh my! Oh how we're wrong. I will be very, I will be very clear. You know there are people way smarter than me who are working on AI, and they made it a lot more than just something they can pass a Turing test. They have they have actually I I'm very impressed, both scared and impressed with AI. And I did not think in my lifetime I would see AI as as advanced as it is today.



Raghu Nandakumara  56:44

Yeah, totally. Okay, fine. So for the listeners out there, what is one thing every listener can start putting into practice from the moment they finish listening to this podcast episode that you believe will result in significant transformation over 12 months.



Erik Jacobsen  57:06

Know your audience and understand their value drivers. You everything is and and everything is a people problem. It's not a technology problem. So you have to know your audience, learn your value drivers. This is something, and I'm sorry. I know this is lightning round. I'm going to give you a slightly long form response. This is something that earlier in my career I really struggled with because I get, I've done a lot with technology. I enjoy technology. I am your quintessential nerd about technology, but it takes a lot for me to get excited about a specific technology. There are only five or six, and I'm not going to throw around brand, you know, brand names, but um, there are about five or six technologies throughout my lifetime that have just really been like, oh wow, this is cool. I really want to tell everyone about it, and I think that's great. I think it's great to be passionate about something. Zero Trust is something I'm currently passionate about and love telling people about. But at the end of the day, I find a lot of us as technologists, as zero, as as Zero Trust practitioners, a lot of us get kind of myopic, and we think it's important to me. So of course it's important to you. I find it cool. So of course you find it cool also, and that's just not true. And that's the trap that we fall into is we start talking about stuff we think is cool and relevant, and the other person is just tuning out. It's not. They don't get it. It's not. You know that you're excited about this. They could care less. And so that's again where I go back to my lightning round answer: know your audience and find their relevance.



Raghu Nandakumara  58:52

So you are passionate and excited about Zero Trust. So for us to before we wrap up, leave us with your favorite Zero Trust analogy,



Erik Jacobsen  59:03

oh gosh, that one, that that one. You know, I've always it it I've always liked the submarine analogy for network segmentation because at my part I'm a network nerd, and it's it's better as a picture, but I I love that submarine analogy. Your traditional network is like a submarine with no bulkheads. You get a hole in anywhere, the whole darn thing sinks. Yo, the water, the bad guys, the water surrounding you rushes in. You flood, you sink. Network segmentation, zero. Yo, microsegmentation. is like building all these bulkheads. You're still going to get a hole, but the water isn't going to flood your submarine. I like that one, and I've got a, and I'm going to be honest. I've got a really pretty picture that um I I. A really pretty visual that I use for that because I just I I like that. The other one is again, as as I've said before, um, I'm going to give you two. Sorry. Um, but the other one I I really want to give you is that uh jet that jet engine analogy I gave you at the beginning. You know, you're building you're building a Zero Trust program and implementing zero, trusting the jet engine on your airplane while you're flying cross country, and all your revenue is inside that airplane.



Raghu Nandakumara  1:00:35

Well, Eric, that was fantastic. Thank you so much for your time today, and it's brilliant to get so in depth with Zero Trust. Not talking about sort of the ins and outs of the program and the stages of maturity, but really just about getting people together collectively, aligning on the train and getting the train moving forward. That's been enlightening, eye-opening, and incredibly practical. Thank you so much.



Erik Jacobsen  1:01:07

Well, it's always a pleasure to talk with you, and I enjoyed this. It's as I said, something I'm passionate about. Love to spread the good word.



Raghu Nandakumara  1:01:15

Thank you. All right. Thanks for tuning in to this week's episode of the segment. For even more information and Zero Trust resources. Check out our website at illumio.com. You can also connect with us on LinkedIn and Twitter at Illumio. And if you like today's conversation, you can find our other episodes wherever you get your podcasts. I'm your host Raghu Nandakumara, and we'll be back soon.