1 00:00:00,040 --> 00:00:04,480 Identity can be an asset, you know, it can be a security 2 00:00:04,480 --> 00:00:08,039 mechanism, it can, you know it, it can be so many different 3 00:00:08,039 --> 00:00:10,080 things. And so when you have all this 4 00:00:10,080 --> 00:00:13,560 information from, you know, backing it up and holding it, it 5 00:00:13,560 --> 00:00:17,000 becomes something that is, is pretty useful. 6 00:00:17,360 --> 00:00:21,120 So we're looking at ways that we can take that information and 7 00:00:21,400 --> 00:00:25,200 and give it, present it to our customers, their information and 8 00:00:25,200 --> 00:00:28,200 present to our customers in ways that is is even more useful for 9 00:00:28,200 --> 00:00:36,640 them. This is identity at the center 10 00:00:37,320 --> 00:00:40,400 if it has anything to do with IAM. 11 00:00:40,400 --> 00:00:46,960 This is the go to podcast now your hosts Jim McDonald and Jeff 12 00:00:46,960 --> 00:00:55,240 Steadman. Welcome to the Identity at the 13 00:00:55,240 --> 00:00:58,920 Center podcast. I'm Jim McDonald and we are 14 00:00:58,920 --> 00:01:02,360 having a special sponsor spotlight episode today. 15 00:01:02,680 --> 00:01:08,320 I've got Chris Steinke here on from Mighty ID and he's going to 16 00:01:08,320 --> 00:01:10,520 tell us all about their exciting solution. 17 00:01:10,760 --> 00:01:15,200 But before we get into the contents of this episode, I want 18 00:01:15,200 --> 00:01:19,960 to let everyone know these are special sponsor episodes that 19 00:01:19,960 --> 00:01:24,360 are created in collaboration with our sponsor, in this case, 20 00:01:24,360 --> 00:01:29,440 my DID to dive more deeply into their viewpoints and specific 21 00:01:29,440 --> 00:01:34,320 solutions in the IM marketplace. To make this crystal clear, the 22 00:01:34,320 --> 00:01:37,200 sponsored episode it's a little bit different than our normal 23 00:01:37,200 --> 00:01:40,120 episodes, but they flow very much in the same way. 24 00:01:41,440 --> 00:01:45,240 Now what the sponsor spotlight episodes allow us to do is 25 00:01:45,240 --> 00:01:49,760 provide you with, you know, in depth insights and expert 26 00:01:49,840 --> 00:01:52,840 perspectives straight from the sources, straight from the 27 00:01:52,840 --> 00:01:55,560 vendors themselves. And we get to hear about their 28 00:01:55,560 --> 00:01:59,120 solutions. A lot of our listeners have told 29 00:01:59,120 --> 00:02:02,360 us that they kind of treat these like first sales calls, right? 30 00:02:02,360 --> 00:02:06,240 They can, you know, hear about a solution and figure out whether 31 00:02:06,240 --> 00:02:09,400 or not it makes sense for them to to look at said solutions. 32 00:02:09,400 --> 00:02:14,040 So like I said, I've got Chris Donkey on from my DID Chris, 33 00:02:14,040 --> 00:02:17,160 welcome to the show. Hey Jim, thanks for having me. 34 00:02:17,160 --> 00:02:18,760 I've been looking forward to coming on and chatting with you 35 00:02:18,760 --> 00:02:20,880 guys. Been big fans of the of the show 36 00:02:20,880 --> 00:02:23,040 for a while. That's awesome. 37 00:02:23,240 --> 00:02:25,240 I've been really looking forward to it as well. 38 00:02:25,280 --> 00:02:27,080 Really interested in your solution. 39 00:02:27,280 --> 00:02:30,280 The more that we've talked in preparation for the show, the 40 00:02:30,280 --> 00:02:32,280 more excited I've gotten. And we're going to talk a lot 41 00:02:32,280 --> 00:02:36,520 about I am resilience today. But before we kind of get into 42 00:02:36,520 --> 00:02:41,160 the meat of things, it would not be us if we didn't start the 43 00:02:41,160 --> 00:02:45,400 show by asking how you got into identity access management in 44 00:02:45,400 --> 00:02:47,320 the 1st place. So kind of tell us about your 45 00:02:47,320 --> 00:02:49,480 journey. How did you get into IM? 46 00:02:49,720 --> 00:02:52,000 Did it pick you or did you pick it? 47 00:02:52,960 --> 00:02:56,920 Probably a little bit of both. Started a long time ago in the 48 00:02:56,920 --> 00:03:00,040 Galaxy far, far away when I was in the Marine Corps. 49 00:03:00,520 --> 00:03:05,440 And I started working inside the technology field and the 50 00:03:06,000 --> 00:03:09,240 emerging security field. Back when I started, there 51 00:03:09,240 --> 00:03:13,680 wasn't a specific job around information or IT security, but 52 00:03:13,680 --> 00:03:17,560 you had to, you know, secure IDs and you had to have, you know, 53 00:03:17,560 --> 00:03:21,520 access and, and security and methods like that. 54 00:03:22,040 --> 00:03:25,280 And then it, it, it moved into, after I got out of the military, 55 00:03:25,280 --> 00:03:28,440 moved into working inside companies like Lucent 56 00:03:28,440 --> 00:03:33,400 Technologies, moving into American Express, other brands 57 00:03:33,400 --> 00:03:36,320 like Zell and, and now I'm here with my DID. 58 00:03:36,320 --> 00:03:40,680 And those journeys have taken me through multiple roles around 59 00:03:40,680 --> 00:03:44,600 security, around infrastructure, around cloud, around application 60 00:03:44,600 --> 00:03:46,560 development. And every, every one of those 61 00:03:46,560 --> 00:03:49,840 roles, either I had responsibility for the identity 62 00:03:49,840 --> 00:03:53,080 and access management environment, or I somehow 63 00:03:53,600 --> 00:03:56,760 touched the identity environment or had something to do with it. 64 00:03:56,920 --> 00:03:59,520 And, and like your podcast says, identity was always at, is 65 00:03:59,520 --> 00:04:01,400 always at the center of, of what I've done. 66 00:04:01,760 --> 00:04:05,640 So that's that's really the, the brief story of of how I've got 67 00:04:05,640 --> 00:04:07,520 here. Yeah, I feel like we hit the 68 00:04:07,520 --> 00:04:09,800 bull's eye with the the name of the podcast. 69 00:04:09,800 --> 00:04:13,240 Yeah, I think so too. A1 take wonder if you will. 70 00:04:13,800 --> 00:04:18,079 So, yeah, yeah. So I think if there's anything 71 00:04:18,079 --> 00:04:21,320 in the world that's going to teach you about being resilient, 72 00:04:21,519 --> 00:04:26,080 it's being a Marine. But you, you've mentioned a kind 73 00:04:26,080 --> 00:04:30,120 of an interesting path and now you're at my DID, you're the 74 00:04:30,120 --> 00:04:33,400 chief operating officer there. Tell us what my DID. 75 00:04:33,400 --> 00:04:35,440 Does what? What did you guys bring to the 76 00:04:35,440 --> 00:04:36,800 table? Right. 77 00:04:36,800 --> 00:04:41,480 So my DID is really focused on solving the problem of 78 00:04:41,480 --> 00:04:46,840 resiliency for your identity platform and your your identity 79 00:04:46,840 --> 00:04:50,840 and access management. Think of it as, you know, not 80 00:04:50,840 --> 00:04:55,680 just backup and recovery, but the ability to have flexibility, 81 00:04:55,880 --> 00:05:00,640 the ability to have migration capabilities, the ability to 82 00:05:00,640 --> 00:05:05,200 have failover across your identity platform or platforms. 83 00:05:05,480 --> 00:05:09,920 You know, really today having the ability to bounce back. 84 00:05:09,920 --> 00:05:13,320 You've got so many threats out there related to identity 85 00:05:13,320 --> 00:05:15,960 spaces. You hear it on, on your podcast 86 00:05:15,960 --> 00:05:19,080 quite often. The, the statistic that is 87 00:05:19,080 --> 00:05:24,480 quoted around like 80% or so of security tax have a vector 88 00:05:24,480 --> 00:05:27,800 through identity. And and so one of those attacks 89 00:05:27,800 --> 00:05:31,240 is your identity system and your identity is not being available. 90 00:05:31,640 --> 00:05:34,440 And so when you think about that, how do you make that 91 00:05:35,320 --> 00:05:38,720 recoverable? How do you make that be able to 92 00:05:38,720 --> 00:05:42,120 absorb an attack, bounce back from an attack? 93 00:05:42,120 --> 00:05:45,760 And we provide a solution that allows you to not only back up 94 00:05:46,040 --> 00:05:50,840 your environment, but quickly recover in, in an emergency, in, 95 00:05:50,840 --> 00:05:55,040 in the face of a ransomware attack or in the face of a, some 96 00:05:55,040 --> 00:06:00,080 type of operational issue. Our solution also focuses on 97 00:06:00,080 --> 00:06:02,120 removing things like vendor lock in. 98 00:06:02,200 --> 00:06:05,320 If you're, you know, if you feel like I've lived this in the past 99 00:06:05,320 --> 00:06:08,120 where you know, you're worried about, Hey, I, I don't want to 100 00:06:08,120 --> 00:06:11,400 move from a very complex platform that I've spent 101 00:06:11,680 --> 00:06:14,200 thousands of hours configuring. And what we make that a lot 102 00:06:14,200 --> 00:06:16,640 easier. We take that from something 103 00:06:16,640 --> 00:06:20,800 that, that, that takes, you know, hundreds, if not thousands 104 00:06:20,800 --> 00:06:25,680 of hours to do and we settle that into, you know, a fraction 105 00:06:25,680 --> 00:06:28,080 of the time by being able to migrate from one identity 106 00:06:28,080 --> 00:06:30,680 platform to the next. And then you know, with that 107 00:06:30,680 --> 00:06:35,000 we've we've seen and work with our customers where they can do 108 00:06:35,000 --> 00:06:38,440 a failover with that and failover between one identity 109 00:06:38,440 --> 00:06:41,800 platform to another identity platform and and essentially 110 00:06:41,800 --> 00:06:45,760 doing like a rapid migration in the event of a of a true 111 00:06:45,760 --> 00:06:48,600 disaster regarding their identity platform. 112 00:06:49,040 --> 00:06:52,440 So those are those are really the the three spaces that we 113 00:06:52,440 --> 00:06:56,880 work in and solve around resiliency for our customers. 114 00:06:57,480 --> 00:07:00,600 I think resiliency is on the tip of everyone's tongue now. 115 00:07:00,880 --> 00:07:06,600 I actually interviewed David Monty from Transfer Security on 116 00:07:06,600 --> 00:07:09,960 the episode that dropped just right prior to this one. 117 00:07:10,360 --> 00:07:13,880 And, you know, that's one of the topics you want to talk about. 118 00:07:13,880 --> 00:07:20,240 It's like this is on the mind of Cisos and CIOs around the world, 119 00:07:20,240 --> 00:07:23,360 right? Is, you know, we need resiliency 120 00:07:23,360 --> 00:07:26,600 in all of our IT systems. And at the core of all that, 121 00:07:26,600 --> 00:07:29,440 what makes it all work is identity systems. 122 00:07:29,440 --> 00:07:32,400 Without the identity infrastructure, you can't get 123 00:07:32,400 --> 00:07:36,080 into IT systems. So and he hit on. 124 00:07:36,320 --> 00:07:38,680 There's so much unpacked with what you talked about there. 125 00:07:38,880 --> 00:07:43,840 But before we start unpacking it, I've got to ask you one of 126 00:07:43,840 --> 00:07:46,160 the the question. I'm sure it's on everybody 127 00:07:46,160 --> 00:07:51,360 minds, which is how did you come up with the name mighty Idi? 128 00:07:51,360 --> 00:07:54,880 Love it by the way. Well, it, it really, it really 129 00:07:54,920 --> 00:07:58,480 summarizes the fact that we're small but mighty. 130 00:07:58,480 --> 00:08:02,640 But, but really, when you think about it, the ID is like we 131 00:08:02,640 --> 00:08:04,280 talked about earlier at the center. 132 00:08:04,280 --> 00:08:08,200 And it is, it is, it is how business gets done. 133 00:08:08,280 --> 00:08:11,800 It is how work gets done. And it is something that is 134 00:08:11,800 --> 00:08:15,840 very, very important. And, and because of that, it's, 135 00:08:16,080 --> 00:08:19,840 it's mighty and, and you want to make it strong, you want to make 136 00:08:19,840 --> 00:08:22,280 it, you know, impermeable, you want to make it secure. 137 00:08:22,640 --> 00:08:24,760 And so there's kind of a dual meaning to that. 138 00:08:24,760 --> 00:08:28,320 We we think of ourselves as a small but mighty team, but that 139 00:08:28,440 --> 00:08:32,400 the ID is also a very mighty component of your environment 140 00:08:32,840 --> 00:08:35,919 and so we we combine it together to come up with mighty. 141 00:08:36,600 --> 00:08:39,600 ID that, that's pretty cool. I like that original story. 142 00:08:40,880 --> 00:08:45,280 So tell me, Chris, if you know, if folks want to find out more 143 00:08:45,280 --> 00:08:48,880 about Mighty ID, what do they do? 144 00:08:48,880 --> 00:08:50,560 What do you recommend that they do? 145 00:08:51,120 --> 00:08:54,320 Oh yeah, Just come visit us over at mightyid.com. 146 00:08:55,080 --> 00:08:57,600 Especially for those listening to the show, they can go to 147 00:08:57,600 --> 00:09:03,720 myid.com/IDAC. You can, we've got a special 148 00:09:03,720 --> 00:09:06,160 white paper that's there too that they can download called, 149 00:09:06,600 --> 00:09:10,280 you know, 6 questions to ask your identity provider, your, 150 00:09:10,280 --> 00:09:13,640 your IDP and, and those are really centered on the, you 151 00:09:13,640 --> 00:09:16,720 know, what if something bad happens when things go wrong, 152 00:09:17,520 --> 00:09:19,920 you should be thinking ahead about what are those things that 153 00:09:19,920 --> 00:09:22,200 could go wrong and what to ask your identity provider. 154 00:09:22,200 --> 00:09:26,200 Because whether it's a security attack, whether it's an 155 00:09:26,200 --> 00:09:29,560 operational issue, whether it's a misconfiguration, how are you 156 00:09:29,560 --> 00:09:32,160 going to handle those situations around your identities? 157 00:09:32,280 --> 00:09:36,400 And so we'd like to make sure that people are informed are 158 00:09:36,400 --> 00:09:38,800 thinking about those questions. So download the white paper. 159 00:09:39,640 --> 00:09:42,720 Bonus points if you want to go sign up for a demo and we'll 160 00:09:42,720 --> 00:09:45,720 send you some cool swag. That's cool. 161 00:09:45,800 --> 00:09:49,240 Yeah, we're always up in this industry. 162 00:09:49,240 --> 00:09:51,240 Everybody's up for a little bit of free swag. 163 00:09:51,240 --> 00:09:53,880 So, but I'm really excited about that white paper that you 164 00:09:53,880 --> 00:09:55,400 mentioned, like the six questions. 165 00:09:55,400 --> 00:09:57,320 I I want to know what those questions are. 166 00:09:57,560 --> 00:10:00,480 I'm going to go out there and, and get that white paper because 167 00:10:00,720 --> 00:10:04,080 I think if you, if you have these six questions on there, 168 00:10:04,160 --> 00:10:06,920 you know, they're really in depth and solid. 169 00:10:07,320 --> 00:10:10,600 If you're going out to RFP and looking at an IDP solution, like 170 00:10:10,640 --> 00:10:15,840 include those questions, if you have an IDP, ask your existing 171 00:10:15,840 --> 00:10:20,280 IDP those questions and you know, make sure they can be 172 00:10:20,280 --> 00:10:22,600 answered. So that's what I would 173 00:10:22,600 --> 00:10:24,200 recommend. Go out there, look at what the 174 00:10:24,200 --> 00:10:27,120 questions are, see if they make sense for you, see if they 175 00:10:27,120 --> 00:10:32,080 resonate with you. So, Chris, I wanted to know a 176 00:10:32,680 --> 00:10:36,800 little bit more about what makes Mighty ID unique. 177 00:10:38,120 --> 00:10:42,840 So what makes us unique is really the, a little bit of, of 178 00:10:42,840 --> 00:10:45,880 the background of us is, you know, we started, we were spun 179 00:10:45,880 --> 00:10:49,040 out of a security company called Tevora. 180 00:10:49,040 --> 00:10:50,800 It's a security consulting company. 181 00:10:51,000 --> 00:10:56,280 So we really started with the security in mind and, and, and 182 00:10:56,280 --> 00:10:58,280 how, you know, how we approach things. 183 00:10:59,600 --> 00:11:03,440 Next is really our architecture. Architecture is built to scale. 184 00:11:04,200 --> 00:11:09,440 We scale up to millions and millions of ID's and and objects 185 00:11:09,440 --> 00:11:13,680 and applications and attributes. And so that makes us unique. 186 00:11:13,680 --> 00:11:19,600 Also on top of that, you know the, the options that we have 187 00:11:19,600 --> 00:11:25,280 for what, whether it's a dedicated or a kind of shared 188 00:11:25,280 --> 00:11:28,400 environment, we have those types of options for our product too, 189 00:11:28,400 --> 00:11:31,120 which make us unique. Then when you get to just how, 190 00:11:31,160 --> 00:11:34,320 how our product functions, we have another set of unique 191 00:11:34,320 --> 00:11:36,800 capabilities. Sure, you can do backup and 192 00:11:36,800 --> 00:11:39,880 recovery and there are other products out there that do that, 193 00:11:40,200 --> 00:11:44,600 but we also do migration where, where you can move from one 194 00:11:44,600 --> 00:11:47,040 identity platform to another identity platform. 195 00:11:47,360 --> 00:11:51,320 That's something that saves our customers thousands of hours and 196 00:11:51,320 --> 00:11:53,480 let alone the headaches and risks of migrations. 197 00:11:53,480 --> 00:11:58,080 I, I remember back in the day when, you know, just doing 198 00:11:58,080 --> 00:12:02,000 e-mail migrations or other types of migrations and you would use 199 00:12:02,000 --> 00:12:03,840 the, you know, the software for that. 200 00:12:03,840 --> 00:12:07,280 And that was always a little bit of stressful. 201 00:12:07,280 --> 00:12:10,440 So Can you imagine identities and all your applications that 202 00:12:10,440 --> 00:12:13,040 are tied to that and all your access as tied to that? 203 00:12:13,040 --> 00:12:17,040 So, so we make the migrations easier and then we also do 204 00:12:17,040 --> 00:12:22,760 failover which allows you to use two different ID PS in a a 205 00:12:22,760 --> 00:12:25,800 disaster type scenario. So those are the things that 206 00:12:25,920 --> 00:12:29,600 make us unique. Yeah, yeah, I, I'll, I'll admit, 207 00:12:29,600 --> 00:12:32,400 I thought I had a gotcha question for you, which was 208 00:12:32,400 --> 00:12:36,400 going to be around, you know, this term resilience means a lot 209 00:12:36,400 --> 00:12:38,240 of things as you're laying out here. 210 00:12:38,520 --> 00:12:42,600 But I, I kind of thought of it in terms of the ability to 211 00:12:42,600 --> 00:12:46,720 recover from a quote UN quote, a disaster. 212 00:12:47,040 --> 00:12:50,320 And my gotcha question was going to be we're in the, you know, 213 00:12:50,800 --> 00:12:55,080 most talking about cloud ID. PS Here you know ping Okta 214 00:12:55,560 --> 00:12:59,600 antra. Why do we need to back them up? 215 00:13:01,160 --> 00:13:05,520 Well, you know, first of all, everyone makes that that initial 216 00:13:05,520 --> 00:13:07,840 assumption that it's in the cloud and it's always available. 217 00:13:08,200 --> 00:13:12,160 But you know, as you know, it's that the service could be 218 00:13:12,160 --> 00:13:15,360 available, but it doesn't mean that everything you've built and 219 00:13:15,360 --> 00:13:19,360 configured is going to be 100% available and in there and how 220 00:13:19,360 --> 00:13:23,600 you expected it, right. So those providers give you 221 00:13:23,600 --> 00:13:25,680 essentially a bucket to put your stuff in. 222 00:13:26,200 --> 00:13:30,000 And, and so if something goes wrong, whether operationally, 223 00:13:30,720 --> 00:13:33,320 you know, I've, I've lived this first hand and maybe some people 224 00:13:33,320 --> 00:13:36,400 in your audience have too. Maybe you have where, you know, 225 00:13:36,400 --> 00:13:40,120 good intentions, you go in there to run a script to, to remove 226 00:13:40,120 --> 00:13:43,880 users or clean some things up. And that script actually, no 227 00:13:43,880 --> 00:13:46,480 matter how, how well you had it peer reviewed and everything 228 00:13:46,480 --> 00:13:51,280 like that, it's, it ends up taking out, you know, a whole 229 00:13:51,280 --> 00:13:54,440 bunch of users or a whole bunch of access or something. 230 00:13:55,000 --> 00:13:57,240 And what do you do and how do you find that? 231 00:13:57,240 --> 00:13:59,080 And how do you recover from that, right? 232 00:13:59,440 --> 00:14:02,440 That, that has nothing to do with with, with whether it's in 233 00:14:02,440 --> 00:14:04,560 the cloud or not, right? And, but that's still a 234 00:14:04,560 --> 00:14:08,160 resiliency factor of being able to quickly recover from that, 235 00:14:09,200 --> 00:14:12,200 you know, whether it's it's something like ransomware where, 236 00:14:12,240 --> 00:14:18,400 you know, being able to recover from or step out of the way of a 237 00:14:18,400 --> 00:14:24,840 ransomware event, or if, heaven forbid, there's a, that the 238 00:14:24,840 --> 00:14:29,280 identity provider has a bad, has a bad operational event happened 239 00:14:29,280 --> 00:14:32,080 to them, right. And, and you have to move out of 240 00:14:32,080 --> 00:14:36,120 the way of, of, of that. So there are, there are those 241 00:14:36,120 --> 00:14:37,840 types of scenarios. And, and really what it comes 242 00:14:37,840 --> 00:14:42,560 down to is, is that shared accountability model that a lot 243 00:14:42,560 --> 00:14:45,960 of people just don't always think about when it went. 244 00:14:45,960 --> 00:14:48,240 They, they know it's there or they, they know it's in the 245 00:14:48,240 --> 00:14:52,040 contract, but they just believe that while it's up there with, 246 00:14:52,040 --> 00:14:54,120 it's an always, always available service. 247 00:14:54,560 --> 00:14:57,720 They're, they're, you know, they're running on a cloud 248 00:14:57,720 --> 00:15:00,600 environment, they're in AWS or something like that. 249 00:15:00,960 --> 00:15:02,320 And it's, it's always going to be there. 250 00:15:02,320 --> 00:15:04,000 It's never going to have a problem, right? 251 00:15:04,120 --> 00:15:08,760 And and our customers have recognized the fact that there 252 00:15:08,760 --> 00:15:12,560 is a huge risk there and that risk is they have to be able to, 253 00:15:12,680 --> 00:15:17,520 you know, take accountability to recover and and you know, bounce 254 00:15:17,520 --> 00:15:20,040 back from those types of issues. Yeah. 255 00:15:20,040 --> 00:15:23,640 I mean, you know, it's this whole shared responsibility 256 00:15:23,640 --> 00:15:28,800 model right in the cloud. I think you brought up a couple 257 00:15:28,800 --> 00:15:32,040 interesting scenarios, which is that people make mistakes. 258 00:15:32,880 --> 00:15:35,240 And by the way, I'll tell you that I've never run a script 259 00:15:35,240 --> 00:15:37,440 that screwed up production, never. 260 00:15:38,600 --> 00:15:42,320 But people make mistakes. And then the other thing that 261 00:15:42,320 --> 00:15:44,680 you brought up was the ransomware attack, which I think 262 00:15:44,680 --> 00:15:50,840 is, you know, I think ransomware was like, you know, at least, 263 00:15:51,080 --> 00:15:55,280 you know, I think my, my immature self used to think 264 00:15:55,960 --> 00:16:00,240 ransomware was like some hocus pocus thing that happens. 265 00:16:00,240 --> 00:16:05,840 And a lot of times is someone gets a credential by phishing or 266 00:16:05,840 --> 00:16:09,880 social engineering, or if they buy it from the dark web and now 267 00:16:09,880 --> 00:16:14,320 they're onto your network And, you know, maybe they spread some 268 00:16:14,320 --> 00:16:19,480 kind of virus that gets on to an administrator's computer, locks 269 00:16:19,480 --> 00:16:22,880 them out. And then they connect to the IDP 270 00:16:24,480 --> 00:16:29,080 credentialize, authenticate in an appropriate normal fashion, 271 00:16:29,480 --> 00:16:33,640 and then just start changing configurations in your, you 272 00:16:33,640 --> 00:16:37,640 know, IDP tenant. And whose fault was that? 273 00:16:38,160 --> 00:16:42,680 Is that the IDP's fault? Because you, you know, you 274 00:16:42,680 --> 00:16:45,200 authenticated in a way that that appeared normal. 275 00:16:45,640 --> 00:16:47,800 You had the username, you had the password. 276 00:16:47,800 --> 00:16:52,040 Maybe you're able to complete the MFA because if you're using 277 00:16:52,040 --> 00:16:56,680 Ubikeys or something and or, or whatever the reason is you're 278 00:16:56,680 --> 00:17:01,240 able to, to authenticate and now you start changing settings. 279 00:17:01,680 --> 00:17:04,560 Now if you don't have a backup of those settings, you can't 280 00:17:04,560 --> 00:17:06,599 restore them. I mean, do you really want to be 281 00:17:06,599 --> 00:17:09,880 having to call Microsoft to say, restore all my settings through 282 00:17:09,880 --> 00:17:16,640 my my Antra instance and I've got 25,000 users who can't log 283 00:17:16,640 --> 00:17:20,079 in anymore? Like you want to have some 284 00:17:20,079 --> 00:17:22,000 insurance policies to that, right? 285 00:17:22,000 --> 00:17:23,599 And that's what a lot of this is about. 286 00:17:24,000 --> 00:17:25,680 Right. And, and in many ways, they're 287 00:17:25,680 --> 00:17:29,240 not going to be able to restore all that configuration to, to 288 00:17:29,240 --> 00:17:33,280 the level that that you had said it or in your scenario, you 289 00:17:33,280 --> 00:17:36,280 know, and as you were saying, sure, if, if that, if that 290 00:17:36,280 --> 00:17:40,640 attack vector was in through the IDP, it's their fault, right? 291 00:17:40,640 --> 00:17:43,920 If if someone broke in through, the IDP hacked in through that 292 00:17:43,920 --> 00:17:47,200 through. Through their through their back 293 00:17:47,200 --> 00:17:49,280 channel. Then then, yeah, that's, that's 294 00:17:49,280 --> 00:17:51,320 on their end of it. But if it, if it's they called 295 00:17:51,320 --> 00:17:55,960 your help desk and social engineered their way in because 296 00:17:55,960 --> 00:17:59,760 that never happened. And, and what do you do then? 297 00:17:59,920 --> 00:18:04,680 And and so that's, that's really where you're taking control and 298 00:18:04,680 --> 00:18:07,520 you're getting control of that environment and you're having 299 00:18:07,520 --> 00:18:11,000 it's just, it's it's like what you and I talked about before. 300 00:18:11,000 --> 00:18:15,320 It's just the, the good old days of having those backups, right? 301 00:18:15,360 --> 00:18:19,440 But in this type of scenario, you can rapidly recover, you can 302 00:18:19,440 --> 00:18:22,240 recover in minutes. You can, you know, our, our 303 00:18:22,240 --> 00:18:26,720 abilities allow you to recover down to the individual attribute 304 00:18:26,720 --> 00:18:29,440 to individual user, the individual, you know, if you 305 00:18:29,440 --> 00:18:31,560 just need to recover something like that, if you run a script 306 00:18:31,560 --> 00:18:35,560 that you know, deleted everyone's, you know, something, 307 00:18:35,720 --> 00:18:38,600 an attribute on the user that is all their phone numbers, you can 308 00:18:38,600 --> 00:18:39,880 recover all the phone numbers, right? 309 00:18:39,880 --> 00:18:43,280 That's not necessarily a big critical thing, but it, it, it 310 00:18:43,280 --> 00:18:46,080 still can be a big headache. I mean, I, I've, I've, like I 311 00:18:46,080 --> 00:18:49,760 said earlier, I, I live that nightmare where we had the, the 312 00:18:49,760 --> 00:18:54,840 entire C level and senior executive leadership accounts 313 00:18:54,840 --> 00:18:57,320 removed by accident through inherent script. 314 00:18:57,720 --> 00:19:00,640 And I would have loved to have, this is many years ago before 315 00:19:00,640 --> 00:19:02,560 Mighty ID existed. And it was part of the reason 316 00:19:02,920 --> 00:19:05,880 the, the, the passion project that is Mighty ID and why I'm 317 00:19:05,880 --> 00:19:08,080 here. But you know, I wish I would 318 00:19:08,080 --> 00:19:11,400 have had something like that, that I could have recovered from 319 00:19:11,400 --> 00:19:15,840 in minutes instead of spending hours trying to reassess what 320 00:19:15,840 --> 00:19:19,120 happened and, and how do we build those accounts back and so 321 00:19:19,120 --> 00:19:21,040 on and so forth. Well, yeah, if you're an 322 00:19:21,040 --> 00:19:26,480 administrator and of an IDP, this is like a little bit of an 323 00:19:26,480 --> 00:19:30,080 insurance policy from the ransomware perspective. 324 00:19:30,080 --> 00:19:34,600 To me, that's the, that's the new disaster, that's the new 325 00:19:34,600 --> 00:19:39,520 earthquake or the new tornado. Like, you know, you mentioned 326 00:19:39,520 --> 00:19:42,760 the scenario like, OK, the IDP, like the data center goes down. 327 00:19:42,760 --> 00:19:47,200 The IDP is in that's kind of the ID, that is kind of the ID PS 328 00:19:47,640 --> 00:19:51,040 situation to restore from. And, and when you look at like 329 00:19:51,040 --> 00:19:54,320 Amazon with their, you know, their different availability 330 00:19:54,320 --> 00:19:57,200 zones sometimes like you don't, if you configure things 331 00:19:57,200 --> 00:19:58,840 properly, you don't have to worry about that. 332 00:19:59,360 --> 00:20:03,680 This doesn't save you from, you know, poor practices in your 333 00:20:03,680 --> 00:20:07,440 identity management where somehow you cough up an ID or. 334 00:20:07,920 --> 00:20:11,200 You know, you get compromised in a ransomware attack. 335 00:20:11,760 --> 00:20:15,680 You could very well be running into the situation where you'd 336 00:20:15,680 --> 00:20:17,880 be really happy if you have a backup. 337 00:20:19,240 --> 00:20:21,880 So that's that's the backup side of things. 338 00:20:21,880 --> 00:20:27,000 But you mentioned a few others. So the migration vendor lock in, 339 00:20:27,200 --> 00:20:32,320 I would imagine that the organizations that get most 340 00:20:32,320 --> 00:20:36,240 excited about this are mid size to large organizations where 341 00:20:36,480 --> 00:20:39,720 they've got pretty big instances, even though like from 342 00:20:39,720 --> 00:20:43,920 an enter ID perspective, I think like it's got to be 90% of 343 00:20:43,920 --> 00:20:46,680 companies from enter ID of all sizes now. 344 00:20:46,680 --> 00:20:51,040 But when you get into that very large organization and this 345 00:20:51,040 --> 00:20:54,920 seems like a tool where they could be doing mergers and 346 00:20:54,920 --> 00:20:59,000 acquisitions and, you know, buying a larger company or 347 00:20:59,000 --> 00:21:03,760 smaller company and having to migrate them from whatever their 348 00:21:03,760 --> 00:21:06,800 IDP is to whatever your corporate standard is, a 349 00:21:06,800 --> 00:21:09,480 divestiture where you need to carve them out and get them 350 00:21:09,480 --> 00:21:11,040 running on to their own instance. 351 00:21:11,040 --> 00:21:13,040 Is that kind of what you're talking about here? 352 00:21:13,040 --> 00:21:15,240 Yeah, Yeah, that's exactly what we're talking about. 353 00:21:15,240 --> 00:21:18,600 There's obviously a few different scenarios that you can 354 00:21:18,600 --> 00:21:21,520 use that this, you know, migration feature for because we 355 00:21:21,520 --> 00:21:23,680 look at migration as, as two things. 356 00:21:23,680 --> 00:21:27,760 You can migrate between the same identity platform, just two 357 00:21:27,760 --> 00:21:31,120 different instances or you migrate between two different 358 00:21:31,200 --> 00:21:35,760 vendor platforms, right. So how we, how we've built the 359 00:21:35,760 --> 00:21:40,000 product and how our, our users or our, our customers have given 360 00:21:40,000 --> 00:21:42,960 us feedback and are using it is exactly that. 361 00:21:42,960 --> 00:21:45,960 They're using it for mergers and acquisitions, divestitures. 362 00:21:46,280 --> 00:21:49,600 They're, they're using it to make test environments. 363 00:21:50,080 --> 00:21:53,880 They're using it to test their, their BCDR plans, right. 364 00:21:54,160 --> 00:21:57,280 I mean, you go from a tabletop exercise, which is great in 365 00:21:57,280 --> 00:22:02,080 theory, but to actually be able to restore a tenant and test it 366 00:22:02,520 --> 00:22:07,920 and, and you know, really know that it works in, in, you know, 367 00:22:07,920 --> 00:22:10,680 in, in real time is, is, is pretty powerful. 368 00:22:11,040 --> 00:22:14,000 And and then you've got those big strategic projects where 369 00:22:14,000 --> 00:22:17,400 you're talking about a company that wants to move from one 370 00:22:17,400 --> 00:22:21,800 platform to another or a company that says, hey, we, we want to 371 00:22:21,800 --> 00:22:28,360 move our Siam onto a different platform for diversity of 372 00:22:28,760 --> 00:22:31,040 capabilities. So we don't have all of our debt 373 00:22:31,040 --> 00:22:34,600 identities on one platform from a risk perspective. 374 00:22:35,000 --> 00:22:38,040 So we might put our customer identities on one platform and 375 00:22:38,040 --> 00:22:41,520 use our enterprise internal identities on another platform, 376 00:22:41,520 --> 00:22:43,320 but we need to split those out, right? 377 00:22:43,320 --> 00:22:46,120 So let's migrate those off. So, so there's a lot of 378 00:22:46,120 --> 00:22:49,160 different use cases for how our migration capabilities get used 379 00:22:49,160 --> 00:22:51,040 by customers. And we, we learn new things 380 00:22:51,040 --> 00:22:53,560 everyday from them. We learn, we get new feedback 381 00:22:53,560 --> 00:22:55,200 from them and, and, and how we develop. 382 00:22:55,200 --> 00:22:58,960 And we've got some pretty cool ideas in our in our future road 383 00:22:58,960 --> 00:23:03,920 map for that too. Kind of feels to me like there's 384 00:23:03,920 --> 00:23:08,800 one kind of like the main feature, which is, yeah, I 385 00:23:08,800 --> 00:23:11,320 always go back to Veritas backup exact. 386 00:23:11,320 --> 00:23:16,400 That was like the the backup to tape platform that I used for so 387 00:23:16,400 --> 00:23:20,480 many years. I remember like going out of 388 00:23:20,480 --> 00:23:24,560 style, backing up the tape and shipping tapes to off site 389 00:23:24,560 --> 00:23:27,640 locations. And you picture some, like mine 390 00:23:27,640 --> 00:23:31,440 under the earth that you're storing your tapes and like it's 391 00:23:31,440 --> 00:23:36,520 cooled and everything but that. That's a really old analogy, 392 00:23:36,520 --> 00:23:40,200 right? But it has to show my age really 393 00:23:40,200 --> 00:23:43,080 early. But I'm kind of like picturing 394 00:23:43,080 --> 00:23:48,000 this as like the main features, like the ability to back up and 395 00:23:48,000 --> 00:23:52,400 to restore. But I'm also seeing this as like 396 00:23:52,440 --> 00:23:57,480 a tool because you've got the ability with this thing to do 397 00:23:57,480 --> 00:24:00,720 the migrations. I also could see a scenario 398 00:24:00,720 --> 00:24:05,920 where you're using this mighty ID to say, all right, we're 399 00:24:05,920 --> 00:24:10,600 going to migrate configurations from, you know, pre production 400 00:24:10,600 --> 00:24:14,840 environments to production rather than kind of the stare 401 00:24:14,840 --> 00:24:17,840 and compare, which I know a lot of right words. 402 00:24:18,040 --> 00:24:20,480 And So what I mean by that is that they don't have an 403 00:24:20,480 --> 00:24:24,440 automated way to take configurations from earlier 404 00:24:24,440 --> 00:24:28,280 environments to, you know, closer to production. 405 00:24:28,560 --> 00:24:32,960 And so to me, that's like a huge benefit. 406 00:24:33,360 --> 00:24:35,560 Well, it is, it is. And you can, you know, it, it 407 00:24:35,560 --> 00:24:40,440 gives you that ability to, you know, build and and destroy 408 00:24:40,440 --> 00:24:44,320 environments and, you know, use those identities in an 409 00:24:44,320 --> 00:24:49,040 environment for those purposes. And like I said, there's once 410 00:24:49,040 --> 00:24:51,720 you have that, once you have that data, the configuration 411 00:24:51,720 --> 00:24:55,000 data and you want to build a, another tenant or, you know, 412 00:24:55,000 --> 00:24:58,640 another IDP like that, it's, it's pretty easy, right? 413 00:24:58,640 --> 00:25:01,000 And you can just put it out there. 414 00:25:01,000 --> 00:25:04,520 And it, it's, it's always interesting to see the different 415 00:25:04,520 --> 00:25:06,960 use cases and different scenarios which our customers 416 00:25:07,360 --> 00:25:10,440 like to like to use it. And and like I said before, they 417 00:25:10,440 --> 00:25:12,120 they give us great ideas all the time. 418 00:25:13,200 --> 00:25:18,240 You dropped the a a term on me when you you and I were chatting 419 00:25:18,240 --> 00:25:21,360 earlier. You called it change 360. 420 00:25:21,480 --> 00:25:24,160 Oh yeah, yeah, yeah. Yeah, I just wrote that down and 421 00:25:24,160 --> 00:25:25,640 I didn't tell you. I was going to ask you about it 422 00:25:25,640 --> 00:25:29,960 but it was Change 360. Yes, Change 360, I'm, I'm glad 423 00:25:29,960 --> 00:25:34,960 you brought that up. So change 360 is one of our key 424 00:25:34,960 --> 00:25:40,040 capabilities around being able to identify changes inside your 425 00:25:40,040 --> 00:25:43,840 configuration of your tenant and being able to trace that back to 426 00:25:43,840 --> 00:25:47,200 a patient zero. So now that we're backing up 427 00:25:47,240 --> 00:25:50,480 your tenant and you're, you're generally doing backups in a 428 00:25:50,800 --> 00:25:53,240 regular manner. Some of our some of our 429 00:25:53,240 --> 00:25:56,120 customers like to do it daily or weekly. 430 00:25:57,040 --> 00:26:00,360 We have the ability to do it continuously and we recommend 431 00:26:00,360 --> 00:26:02,920 just just let it run continuously and do it in an 432 00:26:02,920 --> 00:26:05,400 incremental continuous backup. Anytime there's a change that's 433 00:26:05,400 --> 00:26:06,760 done, it automatically backs it up. 434 00:26:07,320 --> 00:26:10,200 But anytime that change is done, is back backs up, you can, you 435 00:26:10,200 --> 00:26:13,040 can be alerted to that change and you can go investigate it 436 00:26:13,040 --> 00:26:17,960 and investigating it and see was that, was that something that 437 00:26:18,200 --> 00:26:19,880 should have happened? Was that something you can 438 00:26:19,880 --> 00:26:22,040 reconcile that if you want against the change record. 439 00:26:22,040 --> 00:26:23,880 Hey, was that, was that an authorized change? 440 00:26:24,240 --> 00:26:29,200 You can go back and, and see how far back did that change go to? 441 00:26:29,200 --> 00:26:31,560 Does it tie back to a specific user? 442 00:26:31,560 --> 00:26:34,040 Right. And so as you're keeping those 443 00:26:34,040 --> 00:26:37,400 incremental backups and keeping, keeping it over time, you can 444 00:26:37,400 --> 00:26:40,440 eventually through our Change 360 capability, create a, a 445 00:26:40,440 --> 00:26:46,480 timeline map of changes on a user and buy a user. 446 00:26:47,160 --> 00:26:50,160 So it, it, it turns into a really powerful investigative 447 00:26:50,160 --> 00:26:53,600 tool. You know, our customers think 448 00:26:53,600 --> 00:26:55,840 it's pretty cool. They like, they like to play 449 00:26:55,840 --> 00:26:59,920 around with it and use it a lot. We, we've got some, some new 450 00:26:59,920 --> 00:27:02,720 features coming up around it, new enhancements coming up 451 00:27:02,720 --> 00:27:05,640 around it in the future. So look for some announcements 452 00:27:05,640 --> 00:27:08,040 coming out around what we're going to do differently and add 453 00:27:08,040 --> 00:27:10,800 on to change 360. But it's it's, it's really 454 00:27:10,800 --> 00:27:14,160 powerful, really insightful and great tool. 455 00:27:15,000 --> 00:27:19,880 Yeah, it sounds like a really powerful feature and I just want 456 00:27:19,880 --> 00:27:24,000 to remind folks that if you're interested in learning more 457 00:27:24,000 --> 00:27:30,840 about the my DID platform, my DI, d.com/IDC, there's a white 458 00:27:30,840 --> 00:27:34,320 paper out there. You can get a demo, sign up for 459 00:27:34,320 --> 00:27:38,360 a demo and they're also send you some some cool swag. 460 00:27:40,120 --> 00:27:43,800 One of the things I wanted to ask you, Chris, is you know, you 461 00:27:43,800 --> 00:27:45,640 guys work with a lot of customers. 462 00:27:47,200 --> 00:27:52,120 How did they measure their success with your platform? 463 00:27:53,640 --> 00:27:55,720 Yeah. So measuring success obviously 464 00:27:55,720 --> 00:27:59,680 is is around a lot of those different user stories of the 465 00:27:59,680 --> 00:28:01,840 product right around backup and recovery. 466 00:28:01,840 --> 00:28:05,160 So there's different measures of success around that compared to 467 00:28:05,160 --> 00:28:08,720 migration. The failover measure of success 468 00:28:08,720 --> 00:28:13,000 is kind of similar to that of the backup and recovery, but the 469 00:28:13,000 --> 00:28:14,760 first measure. RTO. 470 00:28:14,960 --> 00:28:18,640 Yeah, is around RTO. So the first ones around RTO and 471 00:28:18,640 --> 00:28:23,320 being able to recover quickly in the in the event of a of a some 472 00:28:23,320 --> 00:28:29,160 type of failure or issue. The the second measure, the 473 00:28:29,160 --> 00:28:33,320 second measure of success is, you know, project based measure 474 00:28:33,320 --> 00:28:35,880 of success. How, how quickly and how, how, 475 00:28:36,200 --> 00:28:41,040 how you can de scope risk in your projects around things 476 00:28:41,040 --> 00:28:46,680 like, you know, migrating around projects like, you know, 477 00:28:46,680 --> 00:28:49,640 divestitures or acquisitions and things like that. 478 00:28:49,640 --> 00:28:51,640 Because those all you know, all those things are going to have 479 00:28:51,640 --> 00:28:53,440 risks associated with them. They're going to have project 480 00:28:53,440 --> 00:28:54,680 timelines are going to have costs. 481 00:28:55,040 --> 00:28:58,440 So those measures of success reduce those costs, reduce those 482 00:28:58,440 --> 00:29:02,160 timelines, reduce the, the risks and even the risks around 483 00:29:03,000 --> 00:29:05,920 operational issues that can happen because of that project. 484 00:29:06,240 --> 00:29:09,200 So you're, you're working now with this, with the Mighty ID 485 00:29:09,200 --> 00:29:12,320 and a tool that automates these things and, and you know, 486 00:29:12,320 --> 00:29:16,480 significantly reduces the risks around human error and just the 487 00:29:16,480 --> 00:29:21,440 manual work involved with it. And, and the, the, the failover 488 00:29:21,440 --> 00:29:24,760 piece of our component is, is measured in, in a sense of very 489 00:29:24,760 --> 00:29:27,360 similar to RTO. When you get into some of our 490 00:29:27,360 --> 00:29:30,560 other features like our Change 360 and our new features that'll 491 00:29:30,560 --> 00:29:34,040 be coming out here in the next few months around our health 492 00:29:34,040 --> 00:29:36,520 check and dashboarding health check capabilities. 493 00:29:36,960 --> 00:29:40,520 There's going to be, you know, success measures. 494 00:29:41,080 --> 00:29:44,160 Obviously the Change 360 success measure is around, you know, 495 00:29:44,160 --> 00:29:47,160 security investigations even, and even change management like 496 00:29:47,240 --> 00:29:49,560 being able to understand what changes are happening. 497 00:29:50,080 --> 00:29:54,360 Our, our, our health health check capabilities will 498 00:29:54,760 --> 00:29:59,120 obviously enable success measures around, you know, the 499 00:29:59,120 --> 00:30:02,600 health of your tenant and, and the configuration of your tenant 500 00:30:02,600 --> 00:30:07,000 in the way of do you have, you know, you know, best practices 501 00:30:07,000 --> 00:30:09,720 applied? Do you have things like, you 502 00:30:09,720 --> 00:30:13,080 know, MFA enabled for all your applications or, you know, do 503 00:30:13,080 --> 00:30:17,240 you have, you know, too many users with administrative 504 00:30:17,240 --> 00:30:20,560 privileges and things like that? So those are other additional, 505 00:30:20,680 --> 00:30:23,800 you know, capabilities that will help give, you know, 506 00:30:23,800 --> 00:30:28,560 administrative and and and other pieces of information for for 507 00:30:28,560 --> 00:30:33,360 users to to measure. So obviously your Mighty ID 508 00:30:33,360 --> 00:30:37,040 solution is built around allowing customers or helping 509 00:30:37,040 --> 00:30:41,800 customers be more resilient. How is Mighty ID resilient? 510 00:30:41,800 --> 00:30:47,400 Like are you guys in a globally diverse and a failover 511 00:30:47,400 --> 00:30:48,520 configuration? How? 512 00:30:48,640 --> 00:30:52,120 How are you managing that? Yeah, I'm glad, I'm glad you 513 00:30:52,120 --> 00:30:53,680 asked that. You know, we, we touched on that 514 00:30:53,680 --> 00:30:56,920 earlier, I believe a little bit. But you know, we do operate in 515 00:30:57,000 --> 00:31:01,920 a, you know, in AWS in both regions in the US and we operate 516 00:31:01,920 --> 00:31:06,080 in, in Europe and Canada. And so we, you know, we have 517 00:31:06,080 --> 00:31:09,880 diversity in our, in our, in our architecture there. 518 00:31:10,600 --> 00:31:14,840 And then, you know, besides having all, all the built in, 519 00:31:14,840 --> 00:31:18,120 you know, diversity in the architecture and resiliency 520 00:31:18,120 --> 00:31:24,160 built in there, we also run our, our backups and, and back it 521 00:31:24,160 --> 00:31:28,320 backing up ourselves in a different cloud in Azure. 522 00:31:28,560 --> 00:31:33,040 So we're, we're about making sure we're resilient around our 523 00:31:33,040 --> 00:31:36,920 architecture and how our application operates so that, 524 00:31:36,920 --> 00:31:40,720 you know, we're not going to fall prey even to the issue of 525 00:31:40,720 --> 00:31:43,760 a, of a, of a huge cloud failure or something like that. 526 00:31:45,000 --> 00:31:50,200 That's that sounds good. What is the future for my DID? 527 00:31:50,200 --> 00:31:51,160 Where? Where are you taking the 528 00:31:51,160 --> 00:31:54,240 product? You know that that's an 529 00:31:54,240 --> 00:31:56,800 interesting question. You know, our, our product is, 530 00:31:56,800 --> 00:32:00,400 is focused around resiliency and I think we can go multiple 531 00:32:00,400 --> 00:32:04,320 places. We can continue to grow the 532 00:32:04,320 --> 00:32:08,440 product in the way of how do we cover more identity platforms. 533 00:32:08,920 --> 00:32:12,760 And that's, that's a natural kind of growth trajectory for 534 00:32:12,760 --> 00:32:14,680 us. It can be a little tricky 535 00:32:14,680 --> 00:32:18,680 sometimes because the more you start to grow all those identity 536 00:32:18,680 --> 00:32:22,440 platforms, it's just it, you know, it becomes a lot of work 537 00:32:22,440 --> 00:32:25,640 to keep parity and to keep, you know, everything running that 538 00:32:25,640 --> 00:32:27,520 way. So we have to be, we have to be 539 00:32:27,520 --> 00:32:30,600 smart about it and we really, we really try to listen to, you 540 00:32:30,600 --> 00:32:34,440 know, perspective customers and our customers needs on where 541 00:32:34,440 --> 00:32:37,200 that, you know, where we should drive that piece of it. 542 00:32:38,120 --> 00:32:40,800 You know, the other piece of it is, is really how do we, how do 543 00:32:40,800 --> 00:32:45,400 we help enable the security story and the change management 544 00:32:45,400 --> 00:32:51,040 story and, and, and the what, what we would call the, the 545 00:32:51,040 --> 00:32:57,080 health and metrics story of, of, you know, identities overall. 546 00:32:57,440 --> 00:33:00,320 And so that's, that's where we're taking this because we 547 00:33:00,320 --> 00:33:05,120 really look at, you know, the identity can be an asset. 548 00:33:05,360 --> 00:33:08,080 You know, it can be a security mechanism. 549 00:33:08,600 --> 00:33:11,320 It can, you know, it, it can be so many different things. 550 00:33:11,320 --> 00:33:14,880 And so when you have all this information from, you know, 551 00:33:14,880 --> 00:33:18,520 backing it up and holding it, it becomes something that is, is 552 00:33:18,880 --> 00:33:21,520 pretty useful. So we're looking at ways that we 553 00:33:21,520 --> 00:33:26,160 can take that information and and give it, present it to our 554 00:33:26,160 --> 00:33:29,040 customers, their information and present it to our customers in 555 00:33:29,040 --> 00:33:31,280 ways that is is even more useful for them. 556 00:33:33,080 --> 00:33:36,640 Sounds pretty exciting. Yeah, I expect you just rattle 557 00:33:36,640 --> 00:33:38,920 off products, but I think you made a good point there. 558 00:33:38,920 --> 00:33:43,280 It's just like that's really not easy to maintain and that's 559 00:33:43,280 --> 00:33:46,360 probably not the right way to to go about it, right? 560 00:33:47,720 --> 00:33:51,200 Is it better to be broad and shallow, or is it better to be, 561 00:33:52,560 --> 00:33:55,640 you know, more narrow but deep? That, that, that. 562 00:33:55,640 --> 00:33:57,800 That's your. Customers who are on your 563 00:33:57,800 --> 00:34:00,880 platform in those areas, they want you to go deeper and 564 00:34:00,880 --> 00:34:02,840 deeper. They do, they do. 565 00:34:02,840 --> 00:34:06,560 And and that is, you know, and we certainly want want to be 566 00:34:06,560 --> 00:34:09,960 there with them and sometimes you can and sometimes you can, 567 00:34:10,120 --> 00:34:13,639 you know, it it all depends on what you're able to access 568 00:34:13,639 --> 00:34:17,920 inside that vendors platform. So what and how you can access 569 00:34:17,920 --> 00:34:22,600 inside of Okta, inside of Ventra or paying or, or IBM or, you 570 00:34:22,600 --> 00:34:24,679 know, to start going down the list. 571 00:34:25,040 --> 00:34:28,960 And, and you know, we're, when you're doing that, you can go 572 00:34:28,960 --> 00:34:33,360 deep and deep and deep and deep and, and we, we will always try 573 00:34:33,360 --> 00:34:35,840 to meet our customers needs in that space. 574 00:34:36,159 --> 00:34:38,960 But it is a dilemma and there's a balance that we have to strike 575 00:34:38,960 --> 00:34:40,840 because there's always going to be customers out there that are 576 00:34:40,840 --> 00:34:44,760 on some other platform and they want that backup and recovery 577 00:34:44,760 --> 00:34:48,280 capability too. So, you know, it's, it's, it's a 578 00:34:48,280 --> 00:34:52,159 constant, you know, push and pull, tug of war, so to speak, 579 00:34:52,239 --> 00:34:56,080 within our, within our strategy. So let's be clear, what are the 580 00:34:56,199 --> 00:34:58,720 the platforms that you currently support the? 581 00:34:59,160 --> 00:35:05,680 So, so today, yeah, we support ACTA, Microsoft, Entra and Ping 582 00:35:05,800 --> 00:35:10,120 ping one and and you know, we've got, we've got other ones in the 583 00:35:10,120 --> 00:35:11,960 in the road map in the future. You know, we're even looking at 584 00:35:11,960 --> 00:35:15,080 the big boys like, you know, AWS and Google. 585 00:35:15,080 --> 00:35:17,000 And should we be looking at doing things like that? 586 00:35:17,000 --> 00:35:20,400 Because we, we've heard from our customers that even our 587 00:35:20,400 --> 00:35:24,760 customers that have Microsoft or have Ping or have Octa, they're 588 00:35:24,760 --> 00:35:27,320 looking at these other platforms, maybe not just as a 589 00:35:27,320 --> 00:35:30,360 replacement, but they're looking at these as augmentation. 590 00:35:30,360 --> 00:35:33,480 Because I, I don't, you know, although some companies and some 591 00:35:33,480 --> 00:35:36,560 of our customer strategy is to have a single identity provider, 592 00:35:36,840 --> 00:35:39,320 like I said earlier, some are thinking about, some are 593 00:35:39,320 --> 00:35:42,920 thinking about splitting them up, some are, some are accepting 594 00:35:42,920 --> 00:35:47,280 that a hybrid identity platform is, is better for them, even 595 00:35:47,280 --> 00:35:50,040 though there's a little bit more overhead in the management and 596 00:35:50,400 --> 00:35:53,640 so forth. So that's where we can really 597 00:35:53,640 --> 00:35:56,680 provide value too, because we can help back up and recover 598 00:35:57,000 --> 00:35:59,960 both of their platforms or all of their platforms and they can 599 00:35:59,960 --> 00:36:04,440 have one, one tool to do that. Well, it's not just ID PS. 600 00:36:04,440 --> 00:36:08,520 I mean, you know, you could kind of extend into the IGA market. 601 00:36:09,000 --> 00:36:11,320 You can look at privileged access management. 602 00:36:11,320 --> 00:36:15,920 There's a bunch of other ITIIM spaces that are maturing. 603 00:36:15,920 --> 00:36:21,520 I mean, you know, it's certainly when it comes to ID PS it's like 604 00:36:22,200 --> 00:36:25,960 if it goes down even for 5 minutes and people can't log in, 605 00:36:26,160 --> 00:36:28,680 that's a major issue. Usually from provisioning 606 00:36:28,680 --> 00:36:32,080 standpoint, it's not. But there are a lot of large 607 00:36:32,080 --> 00:36:35,960 organizations that have whole teams managing those IGA 608 00:36:35,960 --> 00:36:38,800 platforms. And I bet you there are a lot of 609 00:36:38,800 --> 00:36:41,240 times where people would like to go back and see what was the 610 00:36:41,240 --> 00:36:44,800 configuration before we've rolled all these changes in or 611 00:36:44,800 --> 00:36:46,160 what were all these changes like. 612 00:36:46,440 --> 00:36:51,840 Let's run a a differential. You know, I could definitely see 613 00:36:51,840 --> 00:36:53,160 that. Yeah, yeah, yeah. 614 00:36:53,200 --> 00:36:56,000 So Chris, before we wrap things up, I wanted to talk to you 615 00:36:56,000 --> 00:36:59,560 about the Gardner I Am Summit. When this episode drops, the the 616 00:36:59,560 --> 00:37:02,760 Summit is only a few days away. For those who haven't 617 00:37:02,760 --> 00:37:05,040 registered, by the way, we do have a discount code. 618 00:37:05,040 --> 00:37:10,320 It's IDAC 375, save you 375 on your registration fees. 619 00:37:11,560 --> 00:37:14,920 Chris, are you guys going to have a Mighty ID booth on the 620 00:37:14,920 --> 00:37:18,200 Expo floor? We sure are and we look forward 621 00:37:18,200 --> 00:37:19,720 to having everyone stop by and see us. 622 00:37:19,720 --> 00:37:23,000 We'll be there. I'll be there Monday, Tuesday 623 00:37:23,000 --> 00:37:24,920 and Wednesday. So stop by and say hi. 624 00:37:24,920 --> 00:37:27,480 We'd love to talk to you, tell you more about what we do and, 625 00:37:27,920 --> 00:37:31,920 and hear hear from you too. Like these are great 626 00:37:31,920 --> 00:37:36,800 opportunities for us to not only interact with with with everyone 627 00:37:36,800 --> 00:37:39,480 in the community, but a lot of times too. 628 00:37:39,480 --> 00:37:43,800 We hear some of the pain points, we hear we get great ideas and 629 00:37:43,800 --> 00:37:48,480 and we collaborate with everyone there to come up with new ideas 630 00:37:48,480 --> 00:37:51,080 and come up with new solutions. Some of some of the features in 631 00:37:51,080 --> 00:37:54,080 our products today have come directly from collaborations 632 00:37:54,080 --> 00:37:55,960 like that. So love to hear from you. 633 00:37:55,960 --> 00:37:58,360 Stop on by and hopefully I'll see you there too, Jim. 634 00:37:59,000 --> 00:38:01,680 I love that. That's like a very good 635 00:38:01,680 --> 00:38:05,400 perspective and it's a unique opportunity for folks. 636 00:38:05,400 --> 00:38:08,600 Like how often do you have an opportunity where you can go to 637 00:38:08,600 --> 00:38:11,880 somebody, whether or not you use their product, give them your 638 00:38:11,880 --> 00:38:15,440 ideas and potentially end up seeing them come to fruition. 639 00:38:15,440 --> 00:38:19,440 So I definitely encourage everyone to to take the time to 640 00:38:19,440 --> 00:38:25,200 swing by the booth. Chris wanted to take us out on 641 00:38:25,200 --> 00:38:27,840 the letter notice kind of tradition here at the Identity 642 00:38:27,840 --> 00:38:31,000 of Center podcast. And you and I, we're sports 643 00:38:31,000 --> 00:38:33,680 dads. I was a baseball coach and dad 644 00:38:33,680 --> 00:38:38,640 for many years. Now you are on the on the 645 00:38:38,640 --> 00:38:42,440 lacrosse side with your son and he's doing some big tournaments. 646 00:38:42,640 --> 00:38:46,800 One of the things you mentioned to me was that lacrosse, and by 647 00:38:46,840 --> 00:38:50,640 the way, when you said this, you said lacrosse builds resilience. 648 00:38:50,840 --> 00:38:54,360 And I just pictured what you meant was the guys hitting each 649 00:38:54,360 --> 00:38:56,640 other with the sticks. And I'm not even sure if that's 650 00:38:56,640 --> 00:38:58,160 what you call them sticks or what. 651 00:38:58,520 --> 00:39:03,400 I've seen some of those those tournaments on TV and it's not a 652 00:39:03,400 --> 00:39:07,560 gentle sport and the guys aren't padded up as much as they are in 653 00:39:07,560 --> 00:39:11,280 football. So I mean, you got to be, you 654 00:39:11,280 --> 00:39:15,200 got to be pretty resilient to do that part. 655 00:39:15,440 --> 00:39:18,200 You got to be willing to take, Yeah, you got to be willing to 656 00:39:18,200 --> 00:39:20,960 take a few hits. You know, you know, I, I, I grew 657 00:39:20,960 --> 00:39:24,600 up playing hockey and, and soccer and baseball. 658 00:39:24,760 --> 00:39:28,600 I didn't play lacrosse, but I started, I, I gained an interest 659 00:39:28,600 --> 00:39:31,440 in it when my son started gaining an interest in it at 660 00:39:31,440 --> 00:39:33,640 about nine years old. He's, he's 14 now. 661 00:39:33,640 --> 00:39:35,280 So he's been playing for about 5 years. 662 00:39:35,280 --> 00:39:40,080 And quickly into the sport he, he realized he didn't like 663 00:39:40,080 --> 00:39:43,640 running a lot. He likes playing and playing 664 00:39:43,640 --> 00:39:46,360 around, but he just didn't like having to run a lot. 665 00:39:46,360 --> 00:39:48,080 And it's a, it's a run a lot sport. 666 00:39:48,120 --> 00:39:50,600 I mean, you are running all the time. 667 00:39:51,080 --> 00:39:56,000 And, and so he, he decided to switch to goalie as a lot of 668 00:39:56,000 --> 00:39:58,240 goalies, if you talk to a lot of goalies in lacrosse, the reason 669 00:39:58,240 --> 00:40:01,600 they moved into goalies is because either one, they were 670 00:40:01,600 --> 00:40:04,920 the younger brother and their older brother put them in goal 671 00:40:04,960 --> 00:40:09,000 at home and would just shoot on them or they didn't, they didn't 672 00:40:09,000 --> 00:40:12,360 like running. And so, you know, he falls into 673 00:40:12,360 --> 00:40:13,960 that other category, not running. 674 00:40:13,960 --> 00:40:17,600 And so he started playing goalie and quickly learned that it's a 675 00:40:17,600 --> 00:40:19,400 it's a very, very difficult position. 676 00:40:19,400 --> 00:40:21,560 It's even. More difficult than than the 677 00:40:21,560 --> 00:40:25,080 other the you know, the other positions on the field and, and 678 00:40:25,080 --> 00:40:27,000 goalie in general. When you think about something 679 00:40:27,000 --> 00:40:31,680 like, you know, soccer goalies or, you know, hockey goalies and 680 00:40:32,120 --> 00:40:34,760 things like that, that it's, it's, it's different than any 681 00:40:34,760 --> 00:40:38,200 other position on the team. And, and it's a very, it can be 682 00:40:38,200 --> 00:40:41,480 very high stress position because all eyes are on you at 683 00:40:41,480 --> 00:40:43,360 that moment when someone's taking a shot. 684 00:40:43,480 --> 00:40:47,720 And, and in a, in a sport like lacrosse, that the lacrosse 685 00:40:47,720 --> 00:40:52,200 goalie, a good goalie is generally 5560%, you know, save 686 00:40:52,200 --> 00:40:54,640 average. And that can be pretty tough 687 00:40:54,640 --> 00:40:57,200 when you're thinking that, you know, just about every other 688 00:40:57,600 --> 00:41:01,440 shot on you is going to go in the goal no matter what you do, 689 00:41:01,440 --> 00:41:04,160 no matter how hard you try it, It can be like that. 690 00:41:04,160 --> 00:41:07,040 Now, that's not always the case for all of them, but you know, 691 00:41:07,040 --> 00:41:08,480 that's, that's generally how it goes. 692 00:41:08,480 --> 00:41:13,240 So building up that mental resiliency is a, is a big thing. 693 00:41:13,240 --> 00:41:15,520 And, and he and I have worked on that a lot. 694 00:41:15,520 --> 00:41:17,800 And I've, I've learned a lot about myself, learned a lot 695 00:41:17,800 --> 00:41:20,240 about him and learned a lot about just the idea of 696 00:41:20,240 --> 00:41:23,160 resiliency overall. And it's how it's become such a, 697 00:41:23,280 --> 00:41:27,160 a big concept in technology and security. 698 00:41:27,600 --> 00:41:32,560 I mean, I've seen, you know, all the old BCDR and, and, and 699 00:41:32,560 --> 00:41:36,760 whatever concepts and terms and, and teams are now becoming 700 00:41:36,760 --> 00:41:39,320 resiliency teams. the IT operation teams are becoming 701 00:41:39,320 --> 00:41:42,920 resilient IT resiliency teams. I've even seen security 702 00:41:42,920 --> 00:41:45,960 resiliency teams. So resiliency is becoming a 703 00:41:45,960 --> 00:41:50,280 very, you know, kind of strong concept and in the technology 704 00:41:50,280 --> 00:41:54,440 world and the security world. And, and so, you know, and then 705 00:41:54,440 --> 00:41:57,200 in my personal world, I live this, you know, almost every day 706 00:41:57,200 --> 00:42:01,600 with my son on how he becomes more resilient as as a goalie 707 00:42:01,600 --> 00:42:05,600 and learning how to, you know, bounce back and, and you know, 708 00:42:05,600 --> 00:42:09,280 be stronger again. And, and you know, whether 709 00:42:09,280 --> 00:42:11,920 whether someone's, you know, cranking on him at, you know, 710 00:42:11,920 --> 00:42:16,720 from 30 feet away and it with a 7080 mile mile an hour shot. 711 00:42:16,720 --> 00:42:19,120 And, you know, he's either got to be able to just stand there 712 00:42:19,120 --> 00:42:20,680 and take it, not be afraid of it. 713 00:42:20,760 --> 00:42:24,240 And, you know, or it could, you know, that person could put it 714 00:42:24,240 --> 00:42:26,480 right on the right spot and shoot it by and he's got to be 715 00:42:26,480 --> 00:42:29,000 OK, like, all right, then get going to get it next time. 716 00:42:29,000 --> 00:42:33,520 So, you know, the whole idea of resiliency is just something 717 00:42:33,520 --> 00:42:37,280 that has become a a strong kind of center in my life. 718 00:42:37,360 --> 00:42:41,240 And it just, I think it really just is a focus on how how we 719 00:42:41,240 --> 00:42:46,960 just become better every day. Yeah, I mean, I think youth 720 00:42:46,960 --> 00:42:50,600 sports is full of, you know, the popular term nowadays is 721 00:42:50,600 --> 00:42:54,280 teachable moments. Teachable moments. 722 00:42:56,000 --> 00:43:01,880 I remember coaching, you know, 8-9 year olds and I'm crying 723 00:43:01,880 --> 00:43:05,320 after they struck out. And I would not in the moment, 724 00:43:05,560 --> 00:43:08,440 you know, after the game or at the practice the next day, just 725 00:43:08,440 --> 00:43:12,480 say, unless you're crying when your teammates strike out, I 726 00:43:12,480 --> 00:43:14,600 don't want you crying when you strike out. 727 00:43:15,200 --> 00:43:17,680 It's a team game, man. It's not about you. 728 00:43:18,640 --> 00:43:24,000 And so I think if you, you know, if you want to try to drive a 729 00:43:24,000 --> 00:43:28,080 certain kind of thinking that's, you know, there's there's a lot 730 00:43:28,080 --> 00:43:33,000 of opportunities and being a coach to young people is like 731 00:43:33,400 --> 00:43:38,240 such a privilege. It really is to really mold 732 00:43:38,240 --> 00:43:41,640 them. You know, I, I agree and, and 733 00:43:41,920 --> 00:43:44,600 you know, especially the, the concept, I know it seems like 734 00:43:44,600 --> 00:43:47,680 we're overusing it, but the concept of resiliency is, is so 735 00:43:47,680 --> 00:43:49,800 important. Even, you know, even more so 736 00:43:49,800 --> 00:43:52,400 today, because when you think about the environment our kids 737 00:43:52,400 --> 00:43:56,560 are growing up in, you know, I, I just think about it like, you 738 00:43:56,560 --> 00:43:58,800 know, he's got a, he's got a smartphone, he's got social 739 00:43:58,800 --> 00:44:01,240 media, he's got all this other pressure around them, things 740 00:44:01,240 --> 00:44:03,800 that I didn't even think about when I was growing up, right? 741 00:44:04,160 --> 00:44:07,360 And how do you be resilient and in, in the face of all those 742 00:44:07,360 --> 00:44:10,360 pressures and in the face of all that stress and, and 743 00:44:10,360 --> 00:44:14,800 expectations and, and, you know, just be able to, you know, put, 744 00:44:14,800 --> 00:44:18,960 you know, move forward every day and, and make yourself just a 745 00:44:18,960 --> 00:44:22,440 little bit better every day and, and push out all the noise, You 746 00:44:22,440 --> 00:44:26,400 know, like you said, and, and life is a team sport And, and 747 00:44:26,400 --> 00:44:29,560 it's not always just about you and, and resiliency isn't just 748 00:44:29,560 --> 00:44:32,040 about how you cope, cope with it yourself. 749 00:44:32,040 --> 00:44:35,920 It's how you cope as a team and with the people around you and 750 00:44:35,920 --> 00:44:38,600 the people you have and the type of people you have around you, 751 00:44:38,600 --> 00:44:41,320 right. So that, that's also very, very 752 00:44:41,320 --> 00:44:43,240 important. And that's what, you know, he 753 00:44:43,240 --> 00:44:44,720 loves about it too. It's his team. 754 00:44:44,720 --> 00:44:46,960 It's his, you know, he loves being around his team. 755 00:44:47,080 --> 00:44:50,760 You know, even when it, if they don't win, they do it as a team. 756 00:44:51,000 --> 00:44:56,560 So it's it's, it's great to see. Great, great points, Great 757 00:44:56,560 --> 00:44:58,640 discussion. Chris, I really appreciate you 758 00:44:58,640 --> 00:45:03,840 coming on the show today. Really enjoyed this discussion. 759 00:45:04,040 --> 00:45:07,360 Again, I think you mentioned you're good with people find you 760 00:45:07,360 --> 00:45:11,880 on LinkedIn searching you up and just connecting to you. 761 00:45:12,160 --> 00:45:14,840 I'm open to the same thing. So if you're a listener of this 762 00:45:14,840 --> 00:45:18,440 podcast, especially committed to this point in the show, please 763 00:45:18,440 --> 00:45:21,960 look me up on LinkedIn, send a connection and know Jeff is of 764 00:45:21,960 --> 00:45:25,680 the same mindset. Mighty ID can be found on the 765 00:45:25,680 --> 00:45:31,680 web of mightyid.com/adac. If you're interested in getting 766 00:45:31,680 --> 00:45:35,400 that white paper as well as signing up for a demo and and 767 00:45:35,400 --> 00:45:40,480 enjoying some swag. Also look for Mighty ID. 768 00:45:41,160 --> 00:45:44,280 Look for their booth at the actual Hall Gardner IM Summit if 769 00:45:44,280 --> 00:45:48,680 you're there next week. And the Identity Center podcast 770 00:45:48,680 --> 00:45:52,800 is available on all of your podcast listening platforms. 771 00:45:52,800 --> 00:45:56,960 Well as on YouTube, go to idacpodcast.tv. 772 00:45:57,200 --> 00:46:02,080 Our website isidacpodcast.com. If you get an opportunity to 773 00:46:02,080 --> 00:46:06,640 give us a like a five star review, any of the good stuff, 774 00:46:07,080 --> 00:46:08,640 we certainly would appreciate it. 775 00:46:08,640 --> 00:46:12,360 It helps us get the word out and more people to find the show for 776 00:46:12,360 --> 00:46:14,480 now. Thanks for listening and we'll 777 00:46:14,480 --> 00:46:19,440 see you all on the next one. You've been listening to 778 00:46:19,440 --> 00:46:23,320 Identity at the Center. We hope you've enjoyed the show. 779 00:46:23,520 --> 00:46:27,640 Make sure to like, rate and review, and we'll be back soon. 780 00:46:27,880 --> 00:46:30,160 But in the meantime, hit the website at 781 00:46:30,160 --> 00:46:36,520 identity@thecenter.com. See you next time on Identity at 782 00:46:36,520 --> 00:46:37,440 the Center.