Glitch: Welcome to NPC Grade Security and Architecture, Episode 6, The Logical Song. Zero Trust the Forest, Not the Trees. I'm your host, Glitch. Cypher: and I'm Cypher. Glitch: So, Cypher. Some days I ask myself, what really is zero trust? And I answer myself. At its basics, it's a framework that builds around a philosophy of never trust and always verify. Cypher: Yep, totally. there's different core principles that really drive that. it's like assume breach, verify explicitly, least privileged access, micro segmentation. Glitch: Absolutely. And I think too many organizations think that Zero Trust is buying a shinier lock for the front door while the windows are open and the raccoons are running payroll. I thought you'd appreciate the animal reference there. Cypher: Hehehe. I love that. I love that. I will definitely keep raccoons in mind all episode long now. But in traditional environments, security teams, they often obsess ⁓ over individual alerts and things like that while attackers are studying and maybe even quietly walking around in their ecosystem. Glitch: I hope so. I get it. mean, it's kind of like the old, I don't know if it's an adage, but comparison of the old Castle and Moat model. It worked until the Castle became 47 SaaS apps, 12 cloud environments, and Dave's iPad from 2018. Cypher: 2018 is probably being generous. Glitch: I mean, probably. That was probably when the iPad was starting to get good. I don't know. 2018 sounded like a good round year. So in the title, we say the forest, not the trees. What do we really mean by that? Cypher: OK, that's a good question. So it's the forest mentality. So this boils down to. a lot of other questions to answer your question, if that's possible. So like, what are we protecting? Who truly needs access? What do they need access to? What does normal behavior look like? How do systems continuously validate that trust? How do identity, device health, data sensitivity, and behavior all work together? So yeah, it's not a simple question. So there's no simple answer, especially when the raccoons are running around doing the payroll. Glitch: ⁓ the raccoons have come back around again, have they? So, and that's kind of the thing with security in general, especially in modern times where there's no simple answer to it, right? So, traditional security is like giving someone a backstage pass once and letting them roam forever. Zero trust is more like the airport security crossed with a smart hotel key card. Every door asks a different question. Cypher: Yes. Glitch: I don't know why I put that like that, but I have a feeling you're probably going to bust my chops or roast me on this one, because it kind of makes no sense, it? Cypher: you know, busting chops that are roasted is fantastic. but, you know, back to the forest and the trees mentality. So I think probably the easiest way for us to really kind of drill down to that is to pop different example of what those trees actually look like so that we can stick with that metaphor and get out of that really wonky airport with hotel key card metaphor you just used. Glitch: Ha ha ha ha ha ha ha ha ha ha Maybe a better analogy would be instead of the whole airport thing, what about if ⁓ we're checking in as a guest at a hotel and we go to the front desk, they verify us there, but then we follow it up with, okay, they give us a key card that has time-limited access based off of our reservation, and every time we have to get in that room, we have to re-verify with that card again. Is that a little bit better or? Cypher: That's a little bit better, but it's not nearly as fun as having a wonky one I can bust your chops over. Glitch: I am to please so I thought I'd throw it out there for you. Yeah. Yeah, I don't know what I was thinking, but I'm glad I can do that to your benefit of busting my chops. I know you look forward to that. Cypher: Like, jeez, I feel like the dream crusher right there. There you go. Yeah, OK. So now that we have gotten a much better metaphor in place, ⁓ yeah, it's different. It's better. Trust me, it was better. It was better. But OK, so let's pop different examples of what trees look like when we say the forest and the trees. So throw me one. Glitch: I don't know about much better. It's different, but... Alright. Okay, yeah, so like buying one more security tool. Cypher: Right, because yeah, zero trust in a box or a SaaS or a SASE is like the most absurd thing, that's really minimizing the whole point of zero trust. But anyway, my turn. ⁓ What about chasing compliance check boxes? Glitch: ⁓ so compliance check boxes, that's a good one. And this goes beyond zero trust, but since we're talking about zero trust, there's too many times where I think when we look at the maturity level of, you know, whether it's traditional or the different maturity levels of zero trust, sometimes I think we go in the mentality of we're still looking at it from the single lens or the previous lens of, hey, we think we did We think we did our traditional in the old school sense, not zero trust sense. ⁓ Pretty good. So we go in and we look and we say, all of these things that fall under zero trust traditional maturity level, we're 50 % there. So sure, we're good, right? So we can check that off and kind of keep moving on. That's what I kind of see from a compliance checkbox. I know you have a different mindset from ⁓ being in GRC or having experience in GRC, so maybe you have a different ⁓ outlook on that, but that's how I kind of see it. Cypher: Now you're not too far off there, Like a lot of times, Jason, the compliance checkbox is saying you do a thing. But not really saying the whole truth and nothing but the truth. You're saying a piece of the truth, like you were just saying. We do it here. Don't look over there. We don't do it everywhere. But we do it right here. right here is what I am checking my compliance checkbox. Like I did a thing, and that thing counts. So check my box. Glitch: So. So are you saying that we're missing the devil in the details? Like we're looking at it as a whole instead of saying, ⁓ maybe we need to break this down a little bit and, and be a little bit more precise in our approach. Cypher: Yeah, a rigorous audit would definitely uncheck that compliance checkbox. Glitch: Gotcha. What about alert fatigue and dashboard worship? Cypher: ⁓ my lord, anybody who has ever worked a day in a sock knows that the, well, shall we say the questionable and dynamic quality of alerts would know that worshiping those things is absolutely absurd. Glitch: What do you... There's a term you use about widgets. ⁓ Counting widgets. That kind of falls into the same thing, right? Cypher: Counting widgets? Yes. Yeah. Yeah. ⁓ how many alerts did we get today that we didn't? You know, it's just stupid because that doesn't mean anything. It's like counting security events. You logged in. That's a security event. ⁓ my god, count it. So you know, it's just crazy to count widgets. ⁓ Glitch: You That's because everybody wants to be counted. They don't want to be left out. So let's count widgets, right? Yeah, I did. I took it. Right, right, right. Cypher: I believe you took it there. All right. OK, my turn. My turn, my turn. All right. So what about focusing only on endpoints, or only on identity, or only on dot, dot? Glitch: Well, what about it? Cypher: I mean, so if that's like, you know, that's one of the trees, right? So that's one of the things that I'm popping out there. Glitch: You're right. Okay, so because Zero Trust is way more than that, and we're going to talk about that ⁓ later in the episode about, yes, too many times we focus on just the endpoints or just the identity, but it expands away beyond that. It's behavioral. ⁓ There's so many dynamic things to it. Just because you have, and we kind of touched on this already, just because we let somebody in. That doesn't mean we should trust them because we don't know what they're actually going to do. We're basing it off of, okay, we hired them as an employer, we vetted them out. They're good the whole time. But that doesn't mean that they're necessarily going to do something purposely malicious. They may be doing something by accident. We still need to keep track of that, and we still need to have the proper posture in place so that we can be alerted on those things, whether they're doing it for malicious intent or just ⁓ by accident. All right. No rebuttal on that one? Okay, all right. All right, so treating Zero Trust as a product instead of a strategy. Cypher: I'm good. No, I'm good. ⁓ yeah, no, that one's my favorite because, yeah, between the vendor emails and my inbox business. Glitch: I thought so. Cypher: and personal and LinkedIn messages and spam calls. It is amazing how many total cold call solicitations I get that are trying to market a single product that you deploy out of the box and it satisfies all of the things represented by Zero Trust Security posture and a Zero Trust Security program. The whole thing, it is huge. It is complex. It is cross-functional. It takes years to do it, even not great. It still takes years to do it and a lot of money. yeah, just that whole buy one thing and boom, you're zero trust. That's that's absolute absurdity. Glitch: So, alright, so it sounds like what you're trying to say is that you just can't yell, MFA deployed, we're done here, drop the mic, run away. Cypher: Absolutely no. Yeah, it should be definitely a thoughtful and fit for purpose and that's important, but a fit for purpose design. Glitch: So this brings us into kind of an interesting discussion here about do companies mistake zero trust activities for maturity? Cypher: Yeah, to some degree, but we have to keep in mind that to some degree, it can be. I mean, that really is. If you're actually doing things to get to zero trust, and I'm going to probably maybe talk a little bit about the compliance thing we were talking about a second ago. If I am making improvements by implementing things that are parts of or components of zero trust, even if I'm doing them partially and part of my environment, like let's just say I've got this segment that I've got to be more harsh on. So I start there, and I never even go to the rest of it. I am still, to some degree, improving the security maturity of my organization. So is that kind of like what you were talking about? Glitch: Yeah, I mean, there is still, when you're going into the Zero Trust ⁓ posture program mentality, you can't negate the things that you have been doing, because they may have been working at the time. So you can't just sit here and go, we're horrible, we're not doing any of these things, and we have to start over. I don't think you never fully, you don't have to take necessarily the nuclear approach all the time. You have to take that in consideration because that is some of those pieces that you put in place already. They're probably the starting. ⁓ It's getting you there to the maturity level that you're that you're trying to get to most likely. Cypher: So when you're. Yeah, and that's hard to separate maturity levels with zero trust from a flat maturity level for an organization because we're going to end up muddy and the water's a little bit on accident. for example, if you look at the CISA maturity model, it starts with traditional, which is level zero. That doesn't mean you've not done anything and that your security is absolutely a poop show. What that means is you're doing the traditional things that time has proven and the threat actors have proven are no longer sufficient for data protection in today's environment. So we're not saying they're bad, they're doing what they were designed to do most likely, but we got to get better, which is why then you go to the initial version of Zero Trust, which is the first step to get across. And that's, again, even to go from traditional to initial, lots of different applications potentially, lots of upskilling, lots of internal work and processes and people ⁓ working together. across different domains that all have some sort of a data protection element to them. ⁓ And that's just to get you to initial. And then after initial, you get to ⁓ developing or something, and then it's like an optimal. Glitch: Yeah, so it kind of goes back to using that backstage analogy about how you have the backstage pass and the only thing you have to do to stay there was to keep from making a scene and avoid all of the alerting and responding mechanisms like pesky, scaredy guards, whereas the journey to zero trust actually starts improving your security posture and does then lead to better maturity over time. Cypher: Yeah, yeah, exactly. That is exactly what we're kind of saying because in traditional ⁓ it was pretty much. You know, like you said, you give them that pass, in this case the backstage pass, and unless they did something to alert the authorities or the tools, you know, camera focuses it on you or one of those pesky security guards comes and tracks you down to haul you out, or unless you leave and have to try to get back in, you pretty much had free reign. could, north, east, west, didn't matter. You could do whatever you wanted. And while you're in there, you can tell whatever story you want. So you can elevate your, ⁓ your privilege and your access by saying the right things, right? Because you're social engineering. But again, those things, they were good for their time, but we've gotten too savvy for it. Glitch: Right. Going back to their they were good for their time. That kind of also enforces what I said with ⁓ you felt you were at a good maturity level from the flat traditional sense of security. Don't negate that. Don't just get rid of it and say, OK, we've got to start over. Most likely, it's going to benefit you as you're moving forward. but that also, it's also a psychological thing. If you're going in and you're telling your staff, whether it's your security staff, IT, business, whatever, you're doing it all wrong. We gotta start over. That's not the right approach to that. It is saying, here's what we have to do better because just like everything in this world, everything changes and we need to be lockstep and change with it. Cypher: Yeah, I mean, we're humans, right? We went from going, ⁓ lookie here, I created fire, to sitting here on a podcast leveraging technology that's pretty much wireless and does all these cool things. We have evolved with the time as technology evolves. As the bad guys have evolved with the technology, our security posture and our security program has to mature. So I say all of the time that zero trust. is not like a thing, it's not like a program. It is essentially just making your entire security program more robust and healthier for today's era. Glitch: Right. So the point is zero trust is a more of philosophy. It's not a product. Some of the basics that I've learned over the years is you can't outsource trust decisions entirely. You can get guidance, but you can't outsource all that stuff. Architecture is critical. And yes, I'm kind of being biased because I'm the architecture guy, but it really needs to start with that. If you don't if you don't build a good architectural process or a program, have the standards and governance in place, it's going to make ⁓ putting in zero trust that much harder or you're have to backtrack you're gonna have to do double work whatever it is it it really i'm not saying it's key but it's definitely a very important component to that ⁓ you don't put your sole trust in just the tooling and finally culture matters as much as technology Cypher: ⁓ ⁓ like that's a tirade I could go on. I literally, am doing like a speech ⁓ for a group in like a couple months or something. And literally one of the things that I talk about is how security is very people-centric. You don't just buy a COTS, put it in, and suddenly you're secure. You are so deeply reliant on people to complement all of those things, to drive those things, to really see the nuance in under how the things are working so that they can pick things up. But yeah, I could probably accidentally go on a rant about that one. Glitch: i think you could probably accidentally or purposely ⁓ go on a rant about that but this also goes back to what we i think we always mentioned every episode ⁓ at least multiple times which is communication communication communication communication and we're gonna say this later we can't live in a silo when it comes to this no matter what it is just because it's a i t function it may be driven by an i t function that does not mean that IT necessarily, it's, yes, the business could come and say we need to improve on this. But when, if you don't have the right mindset, there's a lot of times where if it is technology driven, a lot of times people want to automatically blame technology or say, well, this is a technology function. And while, yes, we may be doing the operational things to start, that doesn't necessarily mean that it is, solely a technology function. Cypher: I'm glad that you made that. that delineator there about a technology function as opposed to IT because in many, many, many shops, security, the security tool stack, the whole nine yards is not part of IT, it's part of cybersecurity. So yeah, it is definitely, but at the end of the day, no matter where you are or who you are, if you're in IT, if you're in security, wherever you are, if something bad happens in that organization, the business is the one taking the hit. The business is paying the fine. the brand of the business is taking the hit. We are all just stewards of the programs that we are the professionals for. So yeah, totally. Glitch: That's right. And because we answer to the business, then we all suffer from a technology standpoint. So while Zero Trust is typically being driven, this kind of goes to your point, driven as a technology initiative, IT cannot live in a silo. Zero Trust involves everyone from the frontline worker to the C-suite and beyond. Cypher: Yeah. And again, I don't want to ring that in too much to IT because it's really wherever the security stack lives, whether it's in IT or that. But did you happen to see my LinkedIn post about identity being our new zero day? OK. Because I. Glitch: absolutely I did. Cypher: I firmly believe that identity is our new zero day because it's constantly being exploited and you got to figure out how and identity has really become the new perimeter because the network perimeter has dissolved remote work has accelerated ⁓ identity centric security is really now the perimeter don't you think. Glitch: Yeah, compromised credentials are the skeleton keys of modern attacks. It's freaking fit everywhere. I've seen it in my tenure where when we were heavily on-prem cloud, so private cloud, that's what we relied on. We relied on our network perimeter. That's what was protecting us. Yes, we had some identity. Cypher: They do it everywhere. Glitch: But again, it wasn't based around a zero trust posture. it was, yep, we validated this person, they have credentials, they fit all the things. And then we let them in and let the traditional flat security handle the rest of it. We aren't seeing what their behavior is. We weren't looking at that. Cypher: Yeah, you give them their backstage pass. So hence the reason now for continuous verification versus that one time authorization and authentication. Glitch: all right here's a here's a question for you ⁓ and you and i had you all of these things that the these discussion points that we're talking about you and i have have discussed these so many times because as you know we we like to speculate on lots of things but we also like to play devil's advocate with each other someone ask you this this question of if identity is the new perimeter are most organizations protecting it like one Cypher: That's a toughie, right? Like most organizations, that's a really tough quantification there. I think that a lot of organizations are starting to realize that they have to be more identity-centric. And I say that because of, for example, if you see jobs that are on LinkedIn now, there's a lot more identity IAM-specific. you know, identity governance or, you know, whatever. There's a lot of specifics that I'm seeing now that are really driving an expertise in identity. And then there's a lot of platforms that are being stood up to really help try to validate that. And then if you figure, you know, authentication with your MFA is a backup to validating that identity. ⁓ I think that... that we're making strides in that direction. I don't know that I would say most organizations are protecting it like one, but I would like to think that the majority of organizations are recognizing the need to, and hopefully they're getting ahead of it if they've got any kind of size and scope to their security function. What do you think? Glitch: And I think, yeah, and I think you're absolutely right on that. I 100 % agree. And why shouldn't I? Because you and I have talked about this. But also, what I've also seen is there's a lot of folks where, and I don't want to lay blame on people that are kind of long in the tooth in technology where they don't keep up with trends and keep up with their modernization of security. But that does happen where they can't wrap their head around Identity just doesn't stop at the user. And we'll touch on this in a little bit, but it doesn't stop at the user. You've got devices and again, going back to behavioral tactics and all of these things. you can't just stop at identity being the individual from that standpoint. Cypher: Agreed. Totally. Glitch: So, and we haven't really touched on this, but one of the other things that rolls into this is least privileged, right? So least privileged sounds easy. All right, well, we're going to give this person just a little bit to do their job, but right up until you add the humans. And then you know what happens after that. Cypher: Yeah. Yeah, you know, I always say, yeah, because I always say that, and you know this, I say this to anybody who has ears, technology is easy. It's the people that are hard. Glitch: ⁓ if we didn't have people think how easy our jobs would be, some of us probably wouldn't have jobs if we didn't have the humans. yes. ⁓ Cypher: My best friend's a wildlife biologist, and this is a universal thing. Doesn't matter what you are dealing with, the humans are always the hard part. Glitch: Yep. Because, and tell me if you agree with this or not, because I think we've also talked about this where depending on whether the person is doing something right or wrong by definition, a lot of it is, there's two things, but I think ultimately, a lot of the stuff that people do are driven by either emotion or personality. I think those are the two big things. Would you agree or disagree on that? Cypher: I think that emotion is the hardest thing because there is no logical counter to it. ⁓ Personality, politics of the workplace, there's so many other things that go into that. yeah, I would agree with that, Glitch: Mm-hmm. And to go back to your wildlife piece, and this goes into technology too, what we think in our head is the right thing to do may not be the appropriate thing to do in this situation. Cypher: Yeah. Yeah. Glitch: Yeah. Okay. I thought I was going to get more than that for a minute, but okay. Alright. Alright. I'll leave you to the drink and I'll keep on going. So what have we seen as some of the challenges when adding the proverbial humans? Yeah. Cypher: ⁓ yeah, sorry. I'm good. I'm get drink over here. I'm fine. ⁓ the humans. ⁓ You know, I can protect things, and I can put in huge locks. But if one of my humans hands their set of keys to that pesky raccoon, ⁓ we are right back where we started. ⁓ But in their defense, it is extraordinarily sweet of them to go out of their way to give their credentials away and sometimes their MFA tokens and the whole nine yards. But isn't that sweet of them? Glitch: That is very sweet. Let me ask you, would said raccoons potentially have like a little bell around their neck too? Absolutely. Corn cob pipe. Alright, so let's talk about permission sprawl. ⁓ Temporary admin access that has been around for at least three years. Cypher: I would actually, can they be wearing some like little overalls and a cowboy hat and maybe like that would make me happy. Yeah. Glitch: I'm probably being nice about that. ⁓ Shadow IT and the politics of removing access to the where somebody is like, I can't do my jobby job. Cypher: Yeah. actually, let's talk about that for a minute. Because at least once a month, my teams have to go action lots of things. And I'm usually having to be involved for ⁓ support and incident management. Glitch: All right. Cypher: because somebody has had access that's been around for years or session tokens that never expire or, you know, they want to PIM up to Superman when really they just needed to go to the local store and buy some spandex, you know, to get the job done. But yeah, that it is really difficult to limit people's access ⁓ to tell them, you know, justifiably in a way that they will understand and be okay okay with, why they don't need admin access on their box, for example, or to that application, or why they only need to PIM up to a certain level of role, or you don't really need, there's a lot of just-in-time ⁓ provisioning that's starting to really kind of come into play now, and timed ⁓ authorizations. I think those are getting better, and I think that those will help, because least privilege, in theory is very elegant. But in reality, it's more like you're trying to clean out a garage and every single box in there is labeled important and fragile and do not stack and you name it. Glitch: and I've used this example before, and it was either the last episode or the episode before, like episode four five. But I'm going to go back to this and use this as the example of what you're just talking about, because when I first started in our IT department, if you worked in the IT department, for those of you that are familiar with Active Directory, and I'm sure most of our listeners probably are, everybody was a domain administrator. If you were in IT, you were automatically a domain administrator. We would gasp at that now. But back then it was, you know, your daily business. And as we started to peel that back, even though we told people up front, unless you can tell us what access you need, there's going to be some pain points. We are going to discover things that you're going to lose access to. That doesn't mean that we're not going to give you that access, but we may question why you need access to it. We're still not saying no. we're trying to approach it again going back to that whole communication thing and you're still going to get the the folks that are just adamant and we've run into that before where we took somebody's domain administrator rights away and they didn't like it but also at the same time they weren't willing to work with us so what did they do they went to one of our higher ups in i t and complain that hey they took my rights away and i can't do my job so what did we have to do we had to reinstate it and then have the argument back and forth on going why this is incorrect or he kind of left out, he, she left out the part of, ⁓ well, they were willing to work with us. I just wasn't willing to work with them. Kind of leave out the important things. Cypher: That's so many problems wrapped in one little short story there, Yeah. ⁓ Yeah. I'm not touching it. I'm backing away from the microphone. Glitch: I know, yes. All right. All right. All right. All right. All right. So we'll move on to the next piece, which is environment visibility. How really important is it? Cypher: OK, so there is an old adage in security that you cannot protect what you cannot see. ⁓ I don't know why, but I want to say that in the voice of Mr. Miyagi so bad. Glitch: It does kind of have that Mr. Miyagi feel to it. I kind of was expecting you to call me Danielson after that. Yeah. If done correctly, no can defend. I'm just kidding. ⁓ Cypher: Yeah. Daniel's done. Yeah, and I want to get in the crane posture right now. We probably are so show in our age right now Exactly right exactly that is exactly our point ⁓ If I don't know what's there how can I defend against it? Yeah But it sounds silly. And there's so many people out there that are maybe not in our business that don't comprehend how we can have assets and things in our environment that we have no ideas there. you can't put a freaking agent on absolutely everything every single time perfectly. There's things that happen, and asset management is huge. If you don't know that it's there, how hard is that, ⁓ yeah, we got breached by this asset because, and that's the B word. I used the B word. Yeah. Glitch: Yeah, you did. I can't believe you used the B word. I don't know if you saw, but I kind of flinched a little bit, or at least I felt like I did. Cypher: Cypher used the B word. ⁓ my god, everybody's cringed. But how embarrassing would that be in humbling to a security team and an IT organization who's got the asset management responsibility generally to know that a breach happened because of an unmanaged asset because we had no idea it was there. So we can't monitor it. We can't run the protections on it. It's invisible. Glitch: Sounds like you found Dave's iPad from 2018. Cypher: I did. He should have been on Android. Glitch: Amen. Sorry to all the iOS folks, but we're Android centric over here. So the question to ask yourself, this is more of a rhetorical question, but for our audience is, how confident are you that your asset inventories are accurate? Because that's a huge piece of it. Cypher: Yeah, sorry. You know what? But the explosion of SAS and IoT and everything else has created so many blind spots. Glitch: ⁓ my god, yes. ⁓ my god, yes. But also, you know, we talk about machine identities, including, but it's not limited to IoT, edge core switches, hypervisor, nose, etc. Those have now outnumbered us humans. And we easily forget, again, going back to sometimes, especially if you get people that are kind of stuck in the old way, that identity just is around the user, the person, and we completely forget about the machines. Cypher: user. Glitch: but that's where we're seeing the increase in, I'm not gonna say the B word, but ⁓ attacks, whether it's from phishing campaigns and whatnot, that's where we're seeing them. We're seeing the lateral movements, not necessarily because somebody is impersonating a user identity, but because they're impersonating a machine identity. Cypher: Yeah, legit, legit. Trust is no longer a binary thing either. Glitch: Absolutely not. Trust used to be a yes or no and modern trust is conditional and dynamic. So the context of that trust now matters, right? Device health, the location, behavioral anomalies, risk score, time of day, if the dog is feeling it. I mean, lots of things, things you don't even think about. Like, I didn't even think about the dog was a factor, but apparently it is. No, no, no, no. For our audience, we know the dog is a factor between you and I. I get that. Yeah. Cypher: Yes. Okay, okay, whoa. The dog is always a factor. Yeah, if you're a cat person, then you can have the cat being a factor. I'm cool with that too, but yeah, sorry. The dog is always a factor. Glitch: Bye. Yeah, bow wow wow yippee ⁓ yippee yay. Yes. Yeah, wow. Nope, we're leaving it in. Cypher: Who let the dog? Sorry. OK. That's embarrassing. Post prod edit. Security. Great. So switching something. Quick, look over here. Security friction versus usability. Like, you know. Some of the things though that we're talking about, OK, let's be clear. If security had their way, nobody would have access. There would be no network. Everything would be in a powered off mode because we are secure then. The only problem is we can't actually do business then. And the whole point of us being there is to support the business, ⁓ to enable them to do the things they have to do in the most secure way that they will allow us to do it. So at what point, and this one is a toughie for me as a security security professional. I actually lean more ⁓ probably for lack of a better term, I lean more liberal on this than a lot of security people who are extraordinarily conservative on this. But at what point do you accept the risk as opposed to just being obstinate? know, how do you because you have to and I'm interested to hear your thoughts here because you have to design controls that work to keep you secure, but they allow people to do their job. Glitch: All right, so I'm going to say something that is all in fun, but it's probably still going to trigger people. I thought AI was going to replace us all. There's our solution. I'm just kidding. I'm just kidding. Yeah, exactly. AI will teach the AI. AI will train the AI. AI will fire the AI. You know. Cypher: tonight AI with AI. AI. Glitch: ⁓ Amen. you bring up, it is tough to design controls for that. Again, going back to communication. And that level of communication can span, you have to know when you're coming from a technology sense, you have to understand what your business is doing. And I'm not just saying as a whole, I'm saying the individual business units goes back to you, we can't live in a silo when we're doing this. We can't just talk to technologists or analysts that bridge the gap of the business. We actually have to sit there and talk with the business and understand it. And I'm guessing also from when you're coming from, whether it's compliance or ⁓ security operations, whatever it is, there's probably always going to be a level of risk no matter what you're doing. And it's educating the business to see if that's an acceptable risk. So I'm going to ask kind of a counter question to you of when you get to that point, is there a level, I know we've said in the past that when we're coming from ⁓ a security sense and we're presenting something to the business, we're acting as a, ⁓ what's the word I'm looking for? We're acting as a, ⁓ we're giving recommendations, all right? Cypher: Okay, so we're counsel and advisement. Glitch: Thank you, counsel and advisement. So when you get to that point, is there ever a situation where it's like, no, there's no compromise for this because this puts us at too great of a risk or. Cypher: It's only if I'm regulatorily obligated. ⁓ I mean, don't get me wrong. If my CEO comes to me and he or she says, firewalls are bad. Take them all out. We don't want them. I am going to probably, like that's probably one I would actually be like, OK, fine. You sign here. Press hard. There's five copies. ⁓ Signing this is not an admission of future guilt is just. admitting that I gave you a copy of this risk and by the way the bottom copy is my resignation because I can't work here like that would probably be one of those events but at the end of the day If I have a company that's willing to take the reputational hit and pay every single, you know, regulatory fine or pay the bad guys who pop my environment and want me to, you know, give them 35,000 via Bitcoin, you know, whatever, I can do that. That is my choice. That is it is my business. Like I can run it how I choose. And if I choose to run it willy nilly that way, then and it works. That's cool. Right. I mean, On the flip side, if you're a heavily regulated organization and you have a lot of controls, that's where you've got your leverage from a security stance because you have to have something sometimes that really kind of drives that home. is not often when you. That's the whole reason why they made like compensating and mitigating controls, right? Like if I wanna do a thing, but the thing is too chafing to the business to be able to sustain and they can't do their job and therefore continue to make money to therefore pay my check, you know, it is my job like you just said a second ago. I am here to advise them. I am here to provide them the best counsel that I can and to present the risk to them clearly. It is their choice. They wanna still take that risk. That's fine. That's their choice. And I have to be OK with that. And again, there's going to be that personal stance where at some point I'm like, yeah, I can't work here if it's too willy-nilly. yeah. Does that answer your question? I probably went on a little bit of a rant. Glitch: Yes. No, was kind of expecting and hoping you would because ⁓ there's a lot of nuances in that. it goes back to, it's not a yes or no. There's too much information that has to feed into what the answer is going to be. So I'm glad you expounded on that. All right. So how about user and employee resentment? Let's talk about that one. Cypher: Well, OK. I don't know what you want to talk about on that one other than the fact that they complain ⁓ sometimes that we restrict their access to things. ⁓ If you've got a good culture and you've started to build a good culture, and luckily in my current role I'm starting to see this more and more, in the past where people were afraid to bring certain things to security because they were afraid it was going to have a punitive ⁓ type of outcome, Glitch: you Cypher: If you really, back to it again, glitch, communication, communication. ⁓ If you have built the communication mechanisms and people trust you with what they have to tell you that you're not gonna overreact and that you're not gonna be punitive towards them, a lot of times they'll bring things to you. ⁓ But that doesn't change sometimes the... Glitch: Yep. Cypher: the resentment that you might see if somebody, you know, I didn't click a thing. I didn't do that. I didn't give my creds away. I did not just tell them what my MFA code was. mean, there's those types of things that happen. Is that what you're asking, or is it a different type of user resentment? Glitch: No, I think that plays into it ⁓ because user resentment could be a lot of different things. We've touched on some of them. It's a human nature going back once again to communication, Cypher. The worst thing you can do is not communicate and just do. That's where you're going to get the most resentment out of anybody. There is still going to be a percentage. don't know how big that is, it depends on probably what you're trying to action on. There's still probably going to be some resentment because unless you know how to present the information to the individual, they're not going to be at the same level we are on why we're doing things. So it has to do with the context of how you present it because in their mind, especially if you are restricting down to least privileged, they're going to have the resentment because now they're going to look at it as, well, now I can't do my job. Cypher: The first place, and I have... seen this, read this, like I've seen it in practice, actual operationalization of things, and I've seen it academically in all of the literature. The place where teams go wrong, whether it's in, when we're talking about zero trust, we have to be very clear. This is not just a security function. This does, in fact, it goes across the scope of different types of organizations, and IT plays a very heavy role in that. Glitch: Mm-hmm. Cypher: You have to have that conversation with the business before you start to move to zero trust because there is going to be a lot of change for the employees and what they're doing how they're doing it what they're accessing Potentially the interfaces that they're using to get to different tools. I mean essentially to go back to your original analogy They're used to getting their backstage pass and going and doing whatever they feel like doing All the way until they have to leave the arena and come back the next day with a new backstage pass Now we're saying okay, you can't have that stage pass anymore, we'll still give you a pass, but now this pass gets you to here, and you can go this far and engage with these things. At this point then, we might have to give you another challenge to see your pass and verify your base is who you are. So that's going to impact every single user. Too many times, security and IT think Zero Trust is a security and IT function, let's go do. The very first thing you have to is talk to your business and get them engaged and get their buy-in so that they can start being your disciples for you. Glitch: And interestingly enough, we won't go into detail, but you're kind of dealing with that right now as we ramp up one of the projects that that we're doing is you did that same thing. You talked to executive leadership. You talked to senior leadership. You traveled to different areas to actually talk to the individual business owners and you got that feedback. And what was those responses? It sounded like from what you and I discussed, they were all for it because one, you have Cypher: Mm-hmm. Glitch: hey, somebody from corporate office is actually talking to us and listening to us. And that opened up so many doors. And then it goes back to, yes, we may be taking X away, but you're also gaining Y. And so I think with the way you approach the business from that standpoint, you did it the right way and how it should be. Cypher: Yeah. There's definitely an amount of, and thank you for that, I appreciate that, but there is definitely some marketing and some public relations skills that go into that kind of a thing. Because yeah, you're about to make their life potentially, all of the user's lives potentially more ⁓ challenging for them to be able to do things that before they didn't have to even think about. ⁓ But yeah, it's going to them, here's what I've got to do. Here's the pros. Here's what it's going to do for you. That transparency, that matters right off the bat, because you're building the trust through that transparency. Here's where we think it's going to make your life a little easier. Here's why we have to do it, because we're not doing it because we feel like it. We're doing it because of x, y, and z. And I think the really important thing is their perspective and their perception, right? Like they have then the perspective that they have been part of the solution. And when I say I'm gonna take your feedback and incorporate it into some of our best practices to then deploy to all of those satellite areas of the organization, ⁓ that definitely makes them feel like they were part of the decision. And it's hard to be like just absolutely bad mouthing something when you know you were part of that decision, so. Glitch: Yeah, so now you are gaining more more champions to back you on this, but they're not just backing you, they're backing the business and saying, yes, I agree or I align with this decision. Cypher: Yeah. So back to kind of our forest and our trees analogy. think one of the things about when we were talking about all of those individual trees earlier that you could, you know, we were popping out different examples of what the trees are in the forest rather than looking at the forest. ⁓ and not the trees, is that danger of being hyper-focused on things, like chasing individual alerts, like being fixated on one vulnerability or the one asset. I think the worst one in my perspective is treating some sort of a security alert. ⁓ that we would label as an incident internally, even though it doesn't meet the actual formal definition necessarily of an incident, but treating a security alert as an isolated case and not kind of correlating those. think there's a challenge to being hyper-focused that definitely ⁓ Zero Trust would support a little more. What do you think? Glitch: Yeah, I agree. And ⁓ this goes along with saying that you can't just rely on just the tooling because, the tooling can get you so far, but you still rely on your staff and all of the other supplemental aspects to really make you successful. And it's continuous. Where you were successful one day because you averted a potential ⁓ attack or potential malicious act may not apply the next day. So yes, you cannot be hyper focused because when you get hyper focused, and you get and you start to get into the daily routine, because of the being hyper focused, then you get then you get lax. And I think that also goes back to how important is to have while not really applying to this it does. but having proper run books and incident response plans and all of the things so people are following it. ⁓ can guarantee you the really, really good ones, it doesn't matter if they've been doing it for five years, 10 years, one year, the really good ones will still follow that run book every single time. Even if they know it by memory, they're still following it line by line because it's effective and it works and we make changes when we need to make changes. So what are some of the red flags when Zero Trust has been implemented poorly? Cypher: ⁓ I think that feels like a good game of ping pong right now. Yeah. You ready? All right. I'll use my hand. All right. I'll pop it your way. ⁓ Red flag of zero trust being implemented poorly. I'm going to go with MFA fatigue. Glitch: ⁓ does it? Alright. I don't even have a paddle, I use my forehead. I'm ready. Alright. ⁓ okay, that's a good one. ⁓ A tool or agent for every individual problem. Cypher: definitely, definitely. So that leads me then to no asset inventory. Glitch: Okay, good one. Yep. It goes back to our the accuracy of the inventory to begin with not having it all. ⁓ boy. ⁓ Dave, bring your iPad out. Our policy is so complicated. No one can understand them. ⁓ yeah, I use the P word. You use the B word, I use the P word. Cypher: OK. You're kicking me now where it hurts, right? Yeah. Yeah. So OK, the structure of a policy, a policy should never be complicated. A policy is intended to be brief, like a single page. And then you've got standards. And then you've got the guidelines or the procedures to support those. anyway, ⁓ that serves a low blow. because you have now just devastatingly distracted me. will let you throw another one out while I think of another one. Glitch: Ha ha. Okay, and I didn't plan this, but speaking of the forehead comment, constant headbutting between the security teams and IT. Yeah, uh-huh, been on that one before. Yeah. Cypher: Yeah, yeah. I live in that day to day. I swear to you, actually, you know what? For Christmas, I would like a package labeled to Cypher from Glitch. And I would like a black and white striped shirt and a whistle. Yeah, because I feel like a referee half of the time. So ⁓ because I'm, I don't want to know. Glitch: Okay, I could do that. I could do that. okay. No, no, was going the old school prison uniform. But then you said whistle. I don't know why the whistle came in. So referee makes a lot more sense with the whistle. Yeah. Yeah. Yeah. Cypher: You keep this team, whatever that was, I don't even. referee makes a lot more sense. Yeah, especially if it's constant headbutting between those two teams. All right. Because I'm still kind of stuck because you said policy, I'm going to have to go with ⁓ temporary exceptions all over the place. There's definitely zero trust being implemented poorly. Glitch: absolutely. I've seen that so many times. We still deal with it today. That goes back to the changing of the mindset. I don't see a problem with just doing temporary because you made a change. It locks somebody out from doing their job. But there's always the continuous and constant follow up and review to make sure that it truly is temporary. And you're putting in it temporary because you absolutely need to. Cypher: Yeah. Glitch: not just because somebody says they need it. For example, well, for no, right. But there's also the ⁓ there's also the mindset of people go, let's just take an arbitrary thing where it's like, OK, we'll get it fixed in an hour. It's only going take an hour. Well, I need it now. No, you could probably wait an hour. I mean, there's there's still a conversation to have, but. Cypher: Well, a onesie is not a problem. It's not the onesies that the problem. It's when it's everywhere that it's the problem. Glitch: you know, the priority for some people are not necessarily going to be the priority for other people and there has to be a compromise somewhere to avoid trying to just do that temporary access that you forgot about for three years. All right, so how about this? What are some characteristics that show a mature zero trust program? So since we talked about a poor one, how about a mature one? All right. Cypher: All right, we can ping pong that one too. I'm going to go with because I said that identity is the new zero day and we all are starting to push towards identity being the perimeter. I'm to go with identity where X identity aware access. Glitch: Okay, well I'm going to rebuttal that and say continuous monitoring. Yes, yes. Cypher: ⁓ Kanwan is a good one. Yeah. OK, well, I'm going to go with the thing that is absolutely a total pain to implement, and that is clear data classification. Glitch: ⁓ Lord, yeah, too many people forget about what really that means or maybe not understand how deep data classification is. It's not just about your flat file sitting on your on your storage repository. We're talking about database tables were to I mean AI. I mean we're talking about a whole lot of things from data classification. Cypher: I'm gonna go Southern voice here just to sound silly for a minute, but this is I got data classification. I got policy says it's internal, public, confidential and private. That is not data classification. That is an administrative control with a label like that that gives you data labels. That is not data classification. There is a big difference. And what the hell happens once that data is transformed, you know, and your label just went to the way of the dodo. Glitch: All right. Done. No, nope, we're done. We're done. I'm going southern on you too. Done, D-U-N, we're done. Yeah, done. All right, and we're going to talk about this in a future episode, but strong segmentation is another one for me. Cypher: We're Yeah, network sag is a biggie. ⁓ OK, well, I'm going to up the game, and I'm going to go with automation and adaptive controls. That would be a really fantastic ⁓ zero trust program. Glitch: ⁓ Well, I'll see your automation and adaptive controls and I'll raise you to measured user risk. Cypher: Oh, oh, OK. OK. I'll give you one more. Go ahead. Go ahead and close it out. Glitch: Okay? All right, cross-team collaboration. Wait, is that communication I'm hearing again? Cypher: I feel like, I feel like that's, yeah, like I feel like we need to go hug it out now. ⁓ Not you and I personally, just you know, like I think that the, yeah, the group needs to come and hug it out. Like that feels like a, yes, don't actually do that people, it's probably an HR violation. Glitch: Group, group hug, everybody. We're cross-hugging collaboration. Probably. Cypher: Yeah, all right. So I will say, though, maturity, ⁓ even in a zero trust world, maturity is not equivalent to perfection. Glitch: No, it is reducing implicit trust, improving visibility, and shortening detection and response cycles. Cypher: Yeah, the goal of Zero Trust, ⁓ it's not about building an impenetrable forest. It's about building a forest where you know which trees matter, which ones are diseased, which ones should be in your forest, what they can do, who's wandering around with the chainsaw. ⁓ And I feel like since I said chainsaw that I should probably wrap us up now because I know we've been talking for almost an hour. So are you OK with that? OK. Glitch: Let's do it. I think it's been a good discussion as usual. Cypher: All right, so on that note for NPC grade security and architecture, I am Cypher. Glitch: And I'm Glitch. And remember, in modern security, the biggest risk usually isn't the tree you can see, it's the movement happening quietly between them. We'll see you next time.