1 00:00:09,700 --> 00:00:13,000 You're listening to the identity of the center podcast, this is 2 00:00:13,000 --> 00:00:15,600 the show that talks about identity and access management 3 00:00:15,700 --> 00:00:18,600 and making sure you know who has access to what let's get 4 00:00:18,600 --> 00:00:25,600 started. Welcome to the identity at the 5 00:00:25,600 --> 00:00:27,900 center podcast I'm Jeff and that's Jim. 6 00:00:27,900 --> 00:00:29,900 Hey Jim hey Jeff. How's it going? 7 00:00:30,100 --> 00:00:32,600 Not so bad yourself. Good hair just got back from a 8 00:00:32,600 --> 00:00:37,500 week of vacation. I took my family to Orlando to 9 00:00:37,500 --> 00:00:41,700 the land of the mouse and stood in a lot of long lines. 10 00:00:41,700 --> 00:00:45,900 We were supposed to be a 50% capacity, I honestly couldn't 11 00:00:45,900 --> 00:00:49,100 tell felt like the lines were longer than ever. 12 00:00:50,300 --> 00:00:54,000 That's, you're a brave person to take that. 13 00:00:54,200 --> 00:00:57,100 Annie, I know you'll you and I work, I talked about earlier 14 00:00:57,100 --> 00:01:00,800 today and you weren't able to actually get onto a lot of the I 15 00:01:00,808 --> 00:01:03,300 think attractions because they were sold out ahead of time, 16 00:01:03,300 --> 00:01:05,600 right? Well, that's the, something is 17 00:01:05,600 --> 00:01:07,600 sold out. But now, it's even though you 18 00:01:07,600 --> 00:01:12,000 have a paid Park admission and you have, you know, you prepaid 19 00:01:12,000 --> 00:01:15,400 to be gone. All those attractions, you have 20 00:01:15,400 --> 00:01:20,500 to reserve them using the app. So word to the wise, if you're 21 00:01:20,500 --> 00:01:27,100 going to Orlando for Disney and All the parks, download the app 22 00:01:27,300 --> 00:01:30,900 reserve, your spot in different attractions ahead of time. 23 00:01:31,400 --> 00:01:34,500 That's probably a good idea. I think so, I was able to 24 00:01:34,500 --> 00:01:36,600 actually switching topics real quick because this is going to 25 00:01:36,600 --> 00:01:39,100 hopefully get me into a spot where I can go elsewhere, as I 26 00:01:39,100 --> 00:01:41,600 finally got my first covid shot, so I'm very excited about that. 27 00:01:42,100 --> 00:01:43,300 So I'm only a couple of days into it. 28 00:01:43,308 --> 00:01:45,500 Everything's been fine. So so good deal. 29 00:01:45,700 --> 00:01:50,300 Oh, and you know, my story, I went to get my shot and it just 30 00:01:50,300 --> 00:01:53,900 happened that it was right? As they stopped giving the 31 00:01:54,200 --> 00:01:56,700 Johnson Johnson shot and that's what they have lined up for me. 32 00:01:56,700 --> 00:02:01,700 So I get turned away. Yeah, well I mean I guess an 33 00:02:01,700 --> 00:02:03,500 abundance of caution is probably good but that's got to be 34 00:02:03,500 --> 00:02:07,500 disappointing. Yeah, well I'm out there are 35 00:02:07,500 --> 00:02:09,199 scouring working to get my shot now. 36 00:02:09,199 --> 00:02:12,600 So we'll see. It'll all work out in the end. 37 00:02:12,600 --> 00:02:13,900 I'm sure. I'm sure it will. 38 00:02:15,000 --> 00:02:17,200 So why don't we shift gears a little bit and maybe Taco. 39 00:02:17,200 --> 00:02:20,000 But identity, access management we're going to introduce our 40 00:02:20,000 --> 00:02:21,700 guest in a minute. But before we get to that 41 00:02:21,700 --> 00:02:23,900 subsume, some kind of, you know, odds and ends that we've got 42 00:02:23,900 --> 00:02:25,900 out. There, we still got a universe. 43 00:02:25,900 --> 00:02:29,100 That's still taking place June 21st to 23rd. 44 00:02:29,700 --> 00:02:31,500 It's in Denver, but it's also online. 45 00:02:31,500 --> 00:02:33,800 I know we talked about this originally, maybe a few weeks 46 00:02:33,800 --> 00:02:36,400 ago and I was like, no way I'm in my going on-site. 47 00:02:36,400 --> 00:02:40,500 Well, now that I'm actually have the vaccine and I'm scheduled 48 00:02:40,500 --> 00:02:42,500 already for my second wife, right. 49 00:02:42,600 --> 00:02:47,700 Maybe I think I think I've gone from zero percent chance to 40 50 00:02:47,700 --> 00:02:50,800 percent chance that I might try to attend in person. 51 00:02:51,200 --> 00:02:53,100 Has your thought process, change the now because I know that you 52 00:02:53,108 --> 00:02:55,500 were kind of looking forward I was looking forward to it. 53 00:02:55,500 --> 00:02:58,800 And, you know, I've got to get at least gold status on Delta 54 00:02:58,800 --> 00:03:01,700 Airlines or my life is meaningless. 55 00:03:01,700 --> 00:03:05,500 So, I've got to start traveling again soon, Jeff soon. 56 00:03:05,700 --> 00:03:07,700 So the only reason you're going is for that phrase for the 57 00:03:07,700 --> 00:03:11,900 mileage as status, uh, the status, mainly the status of 58 00:03:11,908 --> 00:03:13,400 Tennessee, who cares about the identity stuff. 59 00:03:13,400 --> 00:03:17,600 And I mean, you have to admit, as well as, as a former Road 60 00:03:17,600 --> 00:03:21,800 where you have to admit that, you know, traveling without 61 00:03:21,800 --> 00:03:25,300 status of you, you know, going and are A line to save a couple 62 00:03:25,300 --> 00:03:29,000 of bucks and you get treated, like, not as good. 63 00:03:29,500 --> 00:03:31,100 It's not leave it at that, not as good. 64 00:03:31,100 --> 00:03:33,000 Yeah, you know, it sucks. But I think traveling some of 65 00:03:33,000 --> 00:03:36,500 those things where it's, it's hard to at the very beginning 66 00:03:36,500 --> 00:03:38,400 because you may not have a cumulus ask, but once you've got 67 00:03:38,400 --> 00:03:40,100 the status, it's actually not so bad. 68 00:03:40,100 --> 00:03:42,900 At least, you know, from my perspective, I do like to travel 69 00:03:42,900 --> 00:03:45,100 but it's certainly a lot easier when you're, you know, 70 00:03:45,100 --> 00:03:47,100 constantly getting upgraded and you've got things like, you 71 00:03:47,100 --> 00:03:49,700 know, Club, memberships and hotel statuses. 72 00:03:49,700 --> 00:03:50,700 You can kind of get late check-out. 73 00:03:50,700 --> 00:03:52,800 It's an early check outs and then obviously that bleeds over 74 00:03:52,800 --> 00:03:55,600 into, you know. All travel which is great too. 75 00:03:55,600 --> 00:03:59,300 So, I certainly miss that, you know, I'm gonna have a hard time 76 00:03:59,400 --> 00:04:03,000 achieving any type of status for next year, based on this year. 77 00:04:03,100 --> 00:04:08,800 So hopefully, hopefully the travel status God's will be kind 78 00:04:09,000 --> 00:04:12,700 and extend a little bit more. Imagine showing up at the 79 00:04:12,700 --> 00:04:17,100 airport and going to check a bag and they said that'll be $40 at 80 00:04:17,100 --> 00:04:20,800 sorting it's like 70 or 80. Now I think at least always 81 00:04:20,800 --> 00:04:23,200 right yeah it's ridiculous. That's that's why I'm a fan of 82 00:04:23,200 --> 00:04:24,400 the one bag. Pavel. 83 00:04:24,400 --> 00:04:26,700 So if I can get everything underneath underneath the seat 84 00:04:26,700 --> 00:04:30,200 in front of me even better. So, you are a fan of doodads, an 85 00:04:30,200 --> 00:04:32,200 evangelist of doodads and of one bag. 86 00:04:32,200 --> 00:04:34,000 Travel, gotcha. You got it, right? 87 00:04:34,000 --> 00:04:35,100 Yeah. I certainly have a bag clutch, 88 00:04:35,100 --> 00:04:37,500 and that is for sure, but enough about that. 89 00:04:37,500 --> 00:04:41,100 Why don't we talk about identity management a real quick that 90 00:04:41,100 --> 00:04:45,500 took place on April 13th, which is a Tuesday and it will be last 91 00:04:45,500 --> 00:04:47,600 week by the time. Folks are listening to this. 92 00:04:48,000 --> 00:04:50,600 Want to give a congratulations out to Tom Malta. 93 00:04:50,600 --> 00:04:53,900 Who was awarded the Evangelist of the Year from Navy. 94 00:04:54,100 --> 00:04:56,200 Federal Credit Union. And then also the city of 95 00:04:56,200 --> 00:04:59,600 Boston, which is kind of cool, which was the winner for the 96 00:04:59,600 --> 00:05:02,500 organization of the Year. Always interesting to see. 97 00:05:02,500 --> 00:05:07,800 I think a government service, when a organization of the year 98 00:05:07,800 --> 00:05:09,400 for anything. Because you don't really 99 00:05:09,400 --> 00:05:12,300 typically associate efficiency, you know with that. 100 00:05:12,300 --> 00:05:14,900 But it sounds like they've done, a great job of kind of getting 101 00:05:14,900 --> 00:05:18,200 the, I am space into a much better position maybe than it 102 00:05:18,200 --> 00:05:19,600 has been. Not that I have very much 103 00:05:19,600 --> 00:05:22,600 familiarity of Boston, but I think any recognition is 104 00:05:22,600 --> 00:05:23,600 probably good. What do you think? 105 00:05:24,000 --> 00:05:27,000 Well, very big kudos to them City of Austin. 106 00:05:27,400 --> 00:05:29,800 Congratulations. You know, that, you know, behind 107 00:05:29,800 --> 00:05:32,400 the scenes when that anything like that happens, you know, 108 00:05:32,400 --> 00:05:37,000 there are individuals who worked to burn the candle at both ends 109 00:05:37,000 --> 00:05:38,900 to make things happen. That's fantastic. 110 00:05:39,700 --> 00:05:43,500 I know Tom from my past and my career and identity management, 111 00:05:43,508 --> 00:05:51,700 he's a great person and I been seeing mostly, you know, recent 112 00:05:51,700 --> 00:05:53,600 interactions with Tom pin through Linkedin and he's doing 113 00:05:53,600 --> 00:05:56,100 a great job. All those really being an 114 00:05:56,100 --> 00:05:58,900 evangelist, right? So that was the award that he 115 00:05:58,900 --> 00:06:00,700 received. And I think it was well deserved 116 00:06:00,700 --> 00:06:03,200 he's getting out there and making sure that, you know, 117 00:06:03,200 --> 00:06:06,000 people are staying up-to-date with what's happening in the 118 00:06:06,000 --> 00:06:08,500 industry, and I think he's been doing a great job at it. 119 00:06:08,500 --> 00:06:13,400 So, very good picks, I think and big, congratulations to both 120 00:06:13,900 --> 00:06:16,200 yes, aggressive, both winners, maybe at some point, we can try 121 00:06:16,200 --> 00:06:19,700 to get one or both of those guys or at least representatives from 122 00:06:19,700 --> 00:06:22,500 the organization's to be on the show at some point. 123 00:06:23,700 --> 00:06:24,900 So why? Don't we talk a little bit about 124 00:06:24,900 --> 00:06:28,000 what we're going to get into today and that'll give us a 125 00:06:28,008 --> 00:06:31,800 chance to introduce our guests. Our topic today is around the 126 00:06:31,800 --> 00:06:35,800 convert converged identity and access management and to help us 127 00:06:35,800 --> 00:06:38,200 with that conversation. We've got Arun Singh. 128 00:06:38,200 --> 00:06:40,100 He's the CEO and board member at. 129 00:06:40,100 --> 00:06:41,900 I Lantus. Welcome to the show Arun. 130 00:06:42,300 --> 00:06:44,200 Thank you so much, Jim and Geoff. 131 00:06:44,300 --> 00:06:47,400 Thanks for having me today. Yeah, thanks so much for joining 132 00:06:47,400 --> 00:06:49,500 us. And you know, I think one of the 133 00:06:49,500 --> 00:06:52,300 things that we want to get into is really what, you know, how 134 00:06:52,300 --> 00:06:53,900 the market has been responding to a few different. 135 00:06:54,100 --> 00:06:56,100 Things, especially in the identity space, we've seen a lot 136 00:06:56,100 --> 00:06:58,400 of Acquisitions. We've heard things about zero. 137 00:06:58,400 --> 00:07:00,100 Trust will probably get into a bunch of different things like 138 00:07:00,100 --> 00:07:03,500 that but you know, seeing as how this is your first time on the 139 00:07:03,500 --> 00:07:06,700 show with us, our first question, always lines up with, 140 00:07:06,700 --> 00:07:08,500 you know, how did you get into the identity and access 141 00:07:08,500 --> 00:07:10,800 management space? Is that something that you chose 142 00:07:10,800 --> 00:07:15,200 or did you choose it? So in my case, it was both 143 00:07:15,200 --> 00:07:18,100 actually. So when I started my career as a 144 00:07:18,100 --> 00:07:21,900 practice had for application security, during that time 145 00:07:21,900 --> 00:07:24,500 identity and access management was Pretty hot. 146 00:07:24,500 --> 00:07:27,900 So, I chose that to start building up that practice. 147 00:07:28,600 --> 00:07:33,400 And you may not know, but about 20 years back. 148 00:07:33,500 --> 00:07:38,200 When I was at Wipro, you know, we had actually created our own 149 00:07:38,200 --> 00:07:42,400 product called Wipro web secure which got listed in Gartner's 150 00:07:42,400 --> 00:07:44,500 magic quadrant. So there was a lot of Buzz 151 00:07:44,500 --> 00:07:49,000 around that the single sign-on access management, Enterprise 152 00:07:49,000 --> 00:07:53,500 SSO, all of that were you know so very popular but later on I 153 00:07:53,500 --> 00:07:56,500 moved. To look at all different aspects 154 00:07:56,500 --> 00:07:59,900 of cyber security including identity and access management 155 00:07:59,900 --> 00:08:03,500 of course. But Focus was all across IMS, 156 00:08:03,800 --> 00:08:05,900 all across, cyber Security Solutions. 157 00:08:06,500 --> 00:08:09,600 And later when I move to Accenture as the managing 158 00:08:09,600 --> 00:08:13,800 director there, I built the cybersecurity managed services 159 00:08:14,200 --> 00:08:17,100 that was covering, you know, end-to-end cyber Security 160 00:08:17,100 --> 00:08:20,800 Solutions, and identity, and access management was one of the 161 00:08:20,800 --> 00:08:23,300 core pillar. Their sin was the story at you, 162 00:08:23,308 --> 00:08:25,700 why? Where I work as a partner and 163 00:08:25,700 --> 00:08:29,800 there, we created cyber security as a service offering and 164 00:08:29,800 --> 00:08:33,700 digital identity as a service, which was my favorite. 165 00:08:33,700 --> 00:08:36,700 You know, pillar where we build that entire solution from 166 00:08:36,700 --> 00:08:40,700 scratch and the quad multiple customer, and very interestingly 167 00:08:40,700 --> 00:08:44,400 in my current role, when I joined Islanders as the CEO. 168 00:08:44,800 --> 00:08:48,700 So I'll enter that had been focused, you know, past two 169 00:08:48,700 --> 00:08:51,700 decades on identity and access management. 170 00:08:52,100 --> 00:08:55,500 And this time, I will say I am chose me. 171 00:08:55,600 --> 00:08:58,300 Okay, to be able to you know, come and come back home. 172 00:08:58,300 --> 00:09:02,200 So it was kind of a full circle coming back to I am and that's 173 00:09:02,200 --> 00:09:07,400 my full project Focus right now. That's an interesting story. 174 00:09:08,100 --> 00:09:09,900 You know. So what we want to talk about 175 00:09:09,900 --> 00:09:14,200 today is this trend of convert the convergence of I am and you 176 00:09:14,200 --> 00:09:17,900 know I've been in Jeff and I both getting the I am space for 177 00:09:18,000 --> 00:09:22,800 over 15 years and you kind of seen the industry go from sweets 178 00:09:22,800 --> 00:09:25,700 to best-of-breed read and back to sweets. 179 00:09:25,700 --> 00:09:31,100 And you think back around 15 years ago is when Oracle started 180 00:09:31,100 --> 00:09:34,800 buying best-of-breed Solutions and pulling them together into a 181 00:09:34,800 --> 00:09:37,000 sweet. And in a way you could call that 182 00:09:37,000 --> 00:09:39,900 a convergence of I am. But I think the the trend in 183 00:09:39,900 --> 00:09:43,600 convergence of I am today is about making all these parts and 184 00:09:43,600 --> 00:09:49,500 pieces work together seamlessly. So I really wanted to talk about 185 00:09:49,500 --> 00:09:53,600 or have you talked about how you see this? 186 00:09:53,600 --> 00:09:57,400 I mean Your company kind of coined the term compact 187 00:09:57,400 --> 00:10:00,400 identity, maybe you talk a little bit about what that is 188 00:10:00,400 --> 00:10:04,700 and you know maybe key off of what I was talking about there 189 00:10:04,700 --> 00:10:07,700 with the convergence of. I am being more than just a 190 00:10:07,700 --> 00:10:11,700 suite of different solutions for each of these you know single 191 00:10:11,700 --> 00:10:16,200 sign-on identity, governance and thing and privileged access 192 00:10:16,200 --> 00:10:18,700 management. For example yeah so this is very 193 00:10:18,700 --> 00:10:22,500 good question and in fact of you have so much focus on the 194 00:10:22,500 --> 00:10:26,000 convergence. So let me Start with your first 195 00:10:26,000 --> 00:10:30,600 question that why we call our product as compact identity and 196 00:10:30,600 --> 00:10:33,400 what is, you know, the meaning of compact identity. 197 00:10:34,300 --> 00:10:38,200 So, basically, when we coined, this term compact identity that 198 00:10:38,200 --> 00:10:41,900 time convergence, you know, story was not that very popular, 199 00:10:42,300 --> 00:10:46,500 but when I'll enters created this product compact identity, 200 00:10:46,500 --> 00:10:50,400 the idea was to bring all the components of identity into a 201 00:10:50,400 --> 00:10:54,600 single platform and compact them together to create a Platform. 202 00:10:54,600 --> 00:10:56,200 That's how we started our journey. 203 00:10:56,200 --> 00:11:01,300 And if you look at that, why we chose to create this compact 204 00:11:01,300 --> 00:11:05,500 identity solution. So our experience has been, as 205 00:11:05,500 --> 00:11:09,300 you rightly mentioned that in the beginning, it was a very 206 00:11:09,308 --> 00:11:12,900 simple requirement for identity and access management people who 207 00:11:12,908 --> 00:11:15,500 are all looking for single sign-on solution. 208 00:11:15,500 --> 00:11:18,700 Then slowly, the provisioning de-provisioning came into 209 00:11:18,700 --> 00:11:21,900 picture, then the role engineering came fine-grained 210 00:11:21,900 --> 00:11:25,700 access management, multiple different Type of authentication 211 00:11:26,100 --> 00:11:29,800 and authorization Solutions, which came up like are back 212 00:11:29,800 --> 00:11:34,700 context-based, you know, access and attribute-based access 213 00:11:34,700 --> 00:11:37,700 management. And then very recently this 214 00:11:37,700 --> 00:11:41,300 identity governance, identity, Administration, and Pam, all of 215 00:11:41,300 --> 00:11:45,200 that came into picture. Now, when you look at, from any 216 00:11:45,200 --> 00:11:49,500 customer perspective, so on an average, any client need to 217 00:11:49,500 --> 00:11:52,600 choose a minimum of five to seven different. 218 00:11:52,600 --> 00:11:56,300 I am product. And then stitch them together to 219 00:11:56,300 --> 00:12:00,200 be able to meet the control requirement of identity and 220 00:12:00,200 --> 00:12:04,600 access management. Now, this approach is not just, 221 00:12:04,900 --> 00:12:07,700 you know, brings lot of complexity from integration 222 00:12:07,700 --> 00:12:11,700 perspective but also managing so many different vendors. 223 00:12:12,100 --> 00:12:15,200 It's a highly cumbersome activity. 224 00:12:15,800 --> 00:12:19,100 So, when we were looking at this market and what are the gaps, 225 00:12:19,100 --> 00:12:23,200 okay, we thought about this problem to create a platform 226 00:12:23,300 --> 00:12:27,200 ground up And we can converge the full Suite of excess 227 00:12:27,200 --> 00:12:30,600 management, requirement the full Suite of identity governance 228 00:12:30,600 --> 00:12:33,800 Administration, requirement. And then create a platform where 229 00:12:33,800 --> 00:12:37,100 client don't have to buy multiple tool and they can buy 230 00:12:37,100 --> 00:12:42,000 one platform and using that you can you know address your I am a 231 00:12:42,000 --> 00:12:45,100 requirement that is another element. 232 00:12:45,100 --> 00:12:49,400 Also I would like to highlight here is that if you look at, you 233 00:12:49,400 --> 00:12:53,000 know, application onboarding onto I am platform, so 234 00:12:53,000 --> 00:12:56,200 traditional, Coaches that were first to deploy an access 235 00:12:56,200 --> 00:12:59,100 management solution whether it's a doctor, Microsoft, any 236 00:12:59,100 --> 00:13:02,800 solution you pick up and then you on board your thousands of 237 00:13:02,800 --> 00:13:05,200 application onto that access management platform. 238 00:13:05,600 --> 00:13:09,200 Then you need to repeat the same story with IG a solution. 239 00:13:09,200 --> 00:13:12,200 So any idea tool you deploy and then after you do the same thing 240 00:13:12,500 --> 00:13:15,500 and then the third is when you deploy the Pam solution, 241 00:13:15,500 --> 00:13:17,400 privileged access management solution. 242 00:13:17,400 --> 00:13:21,900 So again, the same story need to be repeated it's not just time 243 00:13:21,900 --> 00:13:25,200 consuming but it's also Most intensive. 244 00:13:25,400 --> 00:13:28,600 And that's the problem which we are solving with the help of 245 00:13:28,600 --> 00:13:33,100 convergence of, I am Solutions onto a single platform, what we 246 00:13:33,100 --> 00:13:35,500 call compact identity. You know, it's really 247 00:13:35,500 --> 00:13:37,800 interesting because it's almost like the definition of insanity, 248 00:13:37,800 --> 00:13:39,600 right? Doing the same thing over and 249 00:13:39,600 --> 00:13:41,900 over. It's like, okay, we just went 250 00:13:41,900 --> 00:13:44,000 through our integration of, you know, X number of systems 251 00:13:44,000 --> 00:13:45,400 through our access management platform. 252 00:13:45,400 --> 00:13:47,500 Now, we got to do the same thing for IGA and now we've got to do 253 00:13:47,500 --> 00:13:49,900 same thing for Pam and, you know, maybe there's things that 254 00:13:49,900 --> 00:13:53,200 you're doing through Sim integration right for analytics 255 00:13:53,200 --> 00:13:54,100 and etcetera. Ra. 256 00:13:54,100 --> 00:13:56,800 So I think it's, I think it's interesting point you bring up 257 00:13:57,000 --> 00:13:59,600 one of the things you mentioned before was also this kind of as 258 00:13:59,600 --> 00:14:01,400 a service model. And I think there's we've seen a 259 00:14:01,408 --> 00:14:05,800 lot of organizations that have expressed a desire to move away 260 00:14:05,800 --> 00:14:09,300 from on-premise type Solutions, right and even if that 261 00:14:09,300 --> 00:14:12,300 on-premise really means virtualization they really want 262 00:14:12,300 --> 00:14:15,900 to go to something as a service. So that's kind of what I was 263 00:14:15,900 --> 00:14:19,200 thinking is, you know, maybe we can cut kind of talk about, you 264 00:14:19,200 --> 00:14:21,200 know, what have you seen from your perspective when it comes 265 00:14:21,200 --> 00:14:22,800 to as a service model? Yeah. 266 00:14:22,800 --> 00:14:26,800 So as a This model is started catching lot of momentum, past 267 00:14:26,800 --> 00:14:30,400 56 years. And when I was working at Ernst 268 00:14:30,400 --> 00:14:34,300 & Young as a partner, so we actually decided to build the 269 00:14:34,300 --> 00:14:37,100 entire cyber security as a service model. 270 00:14:37,600 --> 00:14:41,400 And the reason for building up, you know, as a service model was 271 00:14:41,400 --> 00:14:45,600 because it actually cuts down the time to deploy the solution, 272 00:14:45,600 --> 00:14:50,100 the time to value is one of the co-driver and traditional 273 00:14:50,700 --> 00:14:53,500 General model will require you to buy the tool. 274 00:14:53,500 --> 00:14:55,900 You need to By the infrastructure deploy that. 275 00:14:55,900 --> 00:14:59,900 And the amount of time it takes for any large organization, like 276 00:14:59,900 --> 00:15:01,500 procurement cycle. Etc. 277 00:15:01,800 --> 00:15:04,800 At to be able to deploy a test and then roll it out. 278 00:15:04,800 --> 00:15:06,800 All of that can be cut short, okay? 279 00:15:06,800 --> 00:15:10,000 Because you have the base solution available in the SAS 280 00:15:10,000 --> 00:15:13,900 model, but apart from that, there are two other reasons. 281 00:15:13,900 --> 00:15:17,900 I'll know mention which are very prominent which are driving this 282 00:15:17,900 --> 00:15:22,100 as a service model. The first one is, you know, very 283 00:15:22,100 --> 00:15:26,100 easy, upgrade and maintenance. So in identity and access 284 00:15:26,100 --> 00:15:29,800 management to, you might remember that deploying a 285 00:15:29,800 --> 00:15:33,300 particular version of the product is just the starting of 286 00:15:33,300 --> 00:15:35,900 your opening very soon. You will find the product, 287 00:15:35,900 --> 00:15:37,800 vendor will come up with the next version. 288 00:15:38,400 --> 00:15:42,100 And then upgrading from the old version to the new version is a 289 00:15:42,100 --> 00:15:45,600 full-blown project. It's not just changing the 290 00:15:45,600 --> 00:15:48,500 product, but all the integrated application, you need to take 291 00:15:48,500 --> 00:15:51,100 through this entire journey and where you need to retest all of 292 00:15:51,100 --> 00:15:53,300 that. And if this had been a constant 293 00:15:53,300 --> 00:15:57,100 pain in the The streak, the SAS model, or as a service model 294 00:15:57,100 --> 00:15:59,600 actually takes away. This major pain, we are product 295 00:15:59,600 --> 00:16:02,200 vendor as a vendor, we can upgrade and building the new 296 00:16:02,200 --> 00:16:05,600 version new feature functionality without, you know, 297 00:16:05,600 --> 00:16:08,900 breaking the entire, you know, Continuum of integrated 298 00:16:08,900 --> 00:16:13,200 application onto the system. So not just lowers the 299 00:16:13,200 --> 00:16:17,200 operational cost but also some of those implementation value, 300 00:16:17,200 --> 00:16:20,800 you can avoid and also that, you know, the team and the talent 301 00:16:20,800 --> 00:16:23,800 which is required to upgrade the system, all that is. 302 00:16:24,000 --> 00:16:27,800 You know, kind of you can get rid of and then, you know, the 303 00:16:27,800 --> 00:16:30,800 second more most important factor which is driving as a 304 00:16:30,800 --> 00:16:35,500 service model adoption is, you know, the operation from 305 00:16:35,500 --> 00:16:39,300 anywhere or, you know, you can call it as a driven by the 306 00:16:39,300 --> 00:16:41,700 pandemic. The cloud first, or Mobility, 307 00:16:42,200 --> 00:16:45,000 just kind of, you know, initiative where there is a 308 00:16:45,300 --> 00:16:48,600 clearly defined business need where we need to enable our 309 00:16:48,600 --> 00:16:52,900 employees, the contractors and business associates to be able 310 00:16:52,900 --> 00:16:55,900 to access system. From anywhere and from the cloud 311 00:16:55,900 --> 00:16:58,700 adoption perspective. Having this as a service model 312 00:16:58,900 --> 00:17:02,100 actually brings lot of facilities because you can bring 313 00:17:02,100 --> 00:17:06,500 the I am discipline to all the SAS application, the identity 314 00:17:06,500 --> 00:17:08,900 and access management. You know, controls can be 315 00:17:08,900 --> 00:17:12,099 applied to all those SAS applications seamlessly. 316 00:17:12,099 --> 00:17:16,400 And that's the, you know, kind of main advantage why people are 317 00:17:16,400 --> 00:17:18,500 adapting to as a service approach. 318 00:17:18,700 --> 00:17:21,200 I think one of the challenges that I've seen with the as a 319 00:17:21,200 --> 00:17:24,800 service technologies that are that are out there Especially if 320 00:17:24,800 --> 00:17:27,300 they were not originally designed for as a service. 321 00:17:27,300 --> 00:17:30,800 Is that the feature parity is not exactly there between an 322 00:17:30,800 --> 00:17:33,400 on-premise solution that might have been there historically 323 00:17:33,400 --> 00:17:36,100 versus maybe the SAS version of that product. 324 00:17:37,200 --> 00:17:39,100 A lot of times we see organizations that may be of 325 00:17:39,100 --> 00:17:42,600 customized a lot of their on-premise solutions to meet 326 00:17:42,600 --> 00:17:45,900 particular business needs. And when you start to shift into 327 00:17:45,900 --> 00:17:48,800 the, as a service model, you know, you really have to figure 328 00:17:48,800 --> 00:17:51,600 out, you know, how can you adjust your business processes 329 00:17:51,600 --> 00:17:55,100 to meet the capabilities that are Actually available, you 330 00:17:55,100 --> 00:17:57,100 know, in the new versions of those products because it may 331 00:17:57,100 --> 00:18:00,200 not be as customizable as you might be used to. 332 00:18:00,400 --> 00:18:02,900 I'm curious as what your, your thoughts are on. 333 00:18:02,900 --> 00:18:06,000 That kind of feature parity that we've seen between different, 334 00:18:06,000 --> 00:18:08,600 you know, vendors that are out there and maybe they're not 335 00:18:08,600 --> 00:18:10,600 quite exactly the same, but maybe good enough is good 336 00:18:10,600 --> 00:18:13,600 enough, you know, for now and you know what your experience 337 00:18:13,600 --> 00:18:17,000 has been in in that specific area around features. 338 00:18:17,600 --> 00:18:21,700 So I think this is a very strong observation which you have and 339 00:18:21,800 --> 00:18:24,700 the way I would like to Define it as that that there are two 340 00:18:24,700 --> 00:18:28,400 kinds of products which are there in the market, the, some 341 00:18:28,400 --> 00:18:32,300 of the Legacy product, okay? When they found that cloud first 342 00:18:32,300 --> 00:18:35,200 strategy is being adopted by majority of clients. 343 00:18:35,600 --> 00:18:39,000 So they actually upgraded the new feature functionality to 344 00:18:39,000 --> 00:18:44,100 support cloud and there are second category of products, 345 00:18:44,100 --> 00:18:46,000 okay? Which are Cloud native and those 346 00:18:46,000 --> 00:18:48,700 other products, which were born in cloud, and there's a very 347 00:18:48,700 --> 00:18:51,500 clear cut difference. You will see as you implement 348 00:18:51,500 --> 00:18:53,800 those solutions that cloud native. 349 00:18:54,000 --> 00:18:57,000 Lucian's, they adapt to various different feature functionality 350 00:18:57,000 --> 00:19:00,900 and the cloud services seamlessly but where you are 351 00:19:00,900 --> 00:19:04,800 trying to patch on those additional features to just make 352 00:19:04,800 --> 00:19:08,400 it compatible with the cloud there the integration 353 00:19:08,500 --> 00:19:11,900 implementation and integration poses several challenges. 354 00:19:12,400 --> 00:19:16,600 So I would strongly recommend that, you know organizations who 355 00:19:16,600 --> 00:19:20,500 are looking for the as a service solution they should look at 356 00:19:20,500 --> 00:19:24,900 whether the product vendor is cloud, native or They are trying 357 00:19:24,900 --> 00:19:27,800 to get onto the cloud as after Mark. 358 00:19:28,300 --> 00:19:30,500 Yeah. That that's a really good point. 359 00:19:30,600 --> 00:19:35,200 If if it's okay, I'd like to pull the discussion back to kind 360 00:19:35,200 --> 00:19:40,700 of the industry Vision or where the industry is adding kind of 361 00:19:40,708 --> 00:19:45,200 talked about that in terms of the convergence of I am and and 362 00:19:45,200 --> 00:19:49,500 kind of where I was introducing from was you know, taking that 363 00:19:49,500 --> 00:19:52,100 view of how the industry has gone through consolidation 364 00:19:52,100 --> 00:19:54,400 phases. And then that Created 365 00:19:54,400 --> 00:19:59,400 opportunities for startups to kind of fill niches and to 366 00:19:59,400 --> 00:20:03,800 specialize in, you know, become a best of breed solution. 367 00:20:04,900 --> 00:20:08,200 I think that's a good backdrop for this question, which is, you 368 00:20:08,208 --> 00:20:13,700 know, what, we just saw recently was this major purchase by OCTA 369 00:20:13,700 --> 00:20:17,700 of the auth0 platform and kind of building out their 370 00:20:17,700 --> 00:20:21,100 capabilities. Plus we see, you know, OCTA kind 371 00:20:21,100 --> 00:20:24,700 of building out capabilities around I ND governance and 372 00:20:24,700 --> 00:20:27,500 privileged access management. We see that with other vendors 373 00:20:27,500 --> 00:20:30,500 as well. I'm picking on OCTA primarily or 374 00:20:30,500 --> 00:20:33,200 picking out octave primarily because of the recent 375 00:20:33,200 --> 00:20:35,700 acquisition. I'd like to get your feedback on 376 00:20:35,700 --> 00:20:37,600 that. But you know, another Trend that 377 00:20:37,600 --> 00:20:39,600 I'm seeing is a lot of platforms. 378 00:20:40,600 --> 00:20:44,000 The Microsoft platform building out identity management as a 379 00:20:44,008 --> 00:20:48,300 component of that Salesforce servicenow doing kind of the 380 00:20:48,300 --> 00:20:50,500 same thing where they're building out there. 381 00:20:50,500 --> 00:20:53,800 I am capabilities and saying, hey, you can just come on. 382 00:20:54,000 --> 00:20:57,300 Platform and use all of our, I am tools as well. 383 00:20:57,500 --> 00:21:01,100 So I guess a room to you, you know, what are your thoughts on 384 00:21:01,100 --> 00:21:05,200 the OCTA austere acquisition? And then, where do you see the 385 00:21:05,200 --> 00:21:07,800 industry going as a whole? Is it more towards that? 386 00:21:08,300 --> 00:21:10,300 It are we going to see the cycle again? 387 00:21:10,300 --> 00:21:13,800 Where we see a consolidation, but it creates opportunities for 388 00:21:13,800 --> 00:21:15,100 other vendors. Yes. 389 00:21:15,100 --> 00:21:18,800 So these are the recent market. Dynamics are actually proving 390 00:21:18,800 --> 00:21:22,000 our Point, okay? Which we had been actually, you 391 00:21:22,000 --> 00:21:26,600 know, trying to bring Yup. Since past many years, that 392 00:21:26,600 --> 00:21:30,200 converts the I am is the future of identity and access 393 00:21:30,200 --> 00:21:33,300 management. If you look at the recent report 394 00:21:33,300 --> 00:21:39,500 published by Gartner in December 2020, they actually leave 395 00:21:39,500 --> 00:21:43,900 published this IGM Market guide. Their they have very clearly 396 00:21:44,100 --> 00:21:49,000 given the market prediction that the next 24 months by year 2023 397 00:21:49,600 --> 00:21:54,500 more than 45% of new. I am deployment will be Skin for 398 00:21:54,500 --> 00:21:58,200 converged. I am solution and that's a very 399 00:21:58,200 --> 00:22:03,700 big statement because In the market, people are now realizing 400 00:22:03,800 --> 00:22:06,100 there is a fatigue. They don't want to buy those 401 00:22:06,100 --> 00:22:10,100 Niche products separately. They want a single platform 402 00:22:10,100 --> 00:22:13,600 where all these Solutions are big tin and the recent 403 00:22:13,600 --> 00:22:18,000 acquisition by OCTA, you know. It actually kind of confirms 404 00:22:18,000 --> 00:22:21,700 this Market Trend that traditionally they had been very 405 00:22:21,700 --> 00:22:24,700 strong in the market on access management side. 406 00:22:25,200 --> 00:22:28,400 But now they are seeing that, you know, the IGA and Pam if 407 00:22:28,400 --> 00:22:30,500 they bring both of that into their portfolio. 408 00:22:30,700 --> 00:22:32,200 Go. So they can address the new set 409 00:22:32,200 --> 00:22:33,700 of requirements which are coming in. 410 00:22:34,600 --> 00:22:39,800 And if you look at, you know, the the approach what time were 411 00:22:39,800 --> 00:22:43,200 dark, and many of the other, I am players, they are also 412 00:22:43,200 --> 00:22:45,300 taking. They are also trying to expand 413 00:22:45,500 --> 00:22:48,400 from their current domain, like bam product vendors. 414 00:22:48,400 --> 00:22:51,400 They are trying to move into IGA and access management. 415 00:22:51,400 --> 00:22:54,000 Likewise the IGA vendors very soon you will find. 416 00:22:54,000 --> 00:22:57,100 They will also start moving left and right, okay? 417 00:22:57,100 --> 00:23:01,000 To start, you know, getting into access management and Privileged 418 00:23:01,000 --> 00:23:05,600 access management, you know, his face and one of the core Point, 419 00:23:05,600 --> 00:23:07,000 okay? Which we feel a little bit 420 00:23:07,000 --> 00:23:10,200 positive about it. That there are two ways by which 421 00:23:10,200 --> 00:23:11,900 you can actually build this converged. 422 00:23:11,900 --> 00:23:16,200 I am a story one, what OCTA is doing like, acquiring the 423 00:23:16,200 --> 00:23:19,400 different product and then, you know, either you do the pre 424 00:23:19,700 --> 00:23:23,400 integrated solution, which you present to your client, or maybe 425 00:23:23,600 --> 00:23:26,600 you sell each of these Solutions separately to the client. 426 00:23:26,900 --> 00:23:30,000 So, from customer perspective, it will be single, vendor from 427 00:23:30,000 --> 00:23:33,500 whom you can. All these product, however, the 428 00:23:33,500 --> 00:23:37,000 way we look at it, that true convergence is where you have 429 00:23:37,000 --> 00:23:39,500 created a product right from the beginning. 430 00:23:39,500 --> 00:23:43,200 The entire code base is a single code base, which is addressing 431 00:23:43,300 --> 00:23:46,900 the access management IGA and, you know, Pam requirements 432 00:23:46,900 --> 00:23:50,300 together and there are several advantages in doing. 433 00:23:50,300 --> 00:23:53,300 So, because you are not looking at it as a, you know, three 434 00:23:53,300 --> 00:23:56,300 different product. But it's a tightly integrated 435 00:23:56,300 --> 00:23:59,800 right from the beginning. And some of those risk analytics 436 00:23:59,800 --> 00:24:03,100 data, or Identity analytics data, which you require to pass 437 00:24:03,100 --> 00:24:07,100 on from one tool to another tool that all can happen seamlessly. 438 00:24:07,600 --> 00:24:11,500 So we still feel that you know clients will look at the 439 00:24:11,500 --> 00:24:15,700 difference between you know the Stitch the converged IM solution 440 00:24:15,700 --> 00:24:18,300 versus through. Converged IM solution where we 441 00:24:18,900 --> 00:24:21,000 are right now. Positioned as a market leader 442 00:24:21,000 --> 00:24:23,800 and we created this entire solution from, you know, 443 00:24:23,800 --> 00:24:27,800 grounder talking about, you know, the Microsoft coming onto 444 00:24:27,800 --> 00:24:30,400 the platform or, you know, the other player. 445 00:24:30,600 --> 00:24:35,200 Like Salesforce, I think those are also corroborating to the 446 00:24:35,200 --> 00:24:40,400 same point that convergence is, you know, a big Trend in the 447 00:24:40,400 --> 00:24:42,900 market. Number one, number two, that the 448 00:24:42,900 --> 00:24:46,800 entire space of identity and access management is so very hot 449 00:24:47,200 --> 00:24:51,200 that many of these large package solution, vendor, okay? 450 00:24:51,200 --> 00:24:55,100 They are realizing the client demand and adding more features 451 00:24:55,100 --> 00:24:58,400 and functionality to be able to cater to those customer need. 452 00:24:59,000 --> 00:25:00,400 I'd also like to add to your list. 453 00:25:00,500 --> 00:25:04,200 List of the servicenow and the kind of, you know, the new 454 00:25:04,200 --> 00:25:07,800 feature capabilities, what they are, you know, kind of bringing 455 00:25:07,800 --> 00:25:13,000 onto the market, okay? They are also confirming to the 456 00:25:13,000 --> 00:25:17,400 same Trend that even though it is started as a itsm tool. 457 00:25:17,600 --> 00:25:20,700 But since clients are putting up the request for access 458 00:25:20,700 --> 00:25:24,000 management Etc, why not to service that request directly? 459 00:25:24,200 --> 00:25:27,300 And from that perspective they are bringing the IGA 460 00:25:27,300 --> 00:25:32,500 capabilities into the you know, they are itsm to So many of 461 00:25:32,500 --> 00:25:35,000 these overlapping capabilities, which will be coming up in the 462 00:25:35,000 --> 00:25:39,800 market and they simply defined two Trends. 463 00:25:39,800 --> 00:25:42,100 One is the convergence. Another, that I am is pretty 464 00:25:42,100 --> 00:25:44,200 hot. It's a huge investment with 465 00:25:44,200 --> 00:25:47,900 people are making into this area to address this issue and both 466 00:25:47,900 --> 00:25:51,000 of them are really good from, you know, the I am professionals 467 00:25:51,000 --> 00:25:53,200 perspective, I think it's really interesting. 468 00:25:53,200 --> 00:25:59,400 When you talk about the platform well how many organizations that 469 00:25:59,400 --> 00:26:04,500 have Servicenow don't also have Microsoft or you know also have 470 00:26:04,500 --> 00:26:09,100 Salesforce and so if you making the pitch that hey you know, 471 00:26:09,200 --> 00:26:12,300 pull it all together, you still have this heterogeneous 472 00:26:12,300 --> 00:26:15,600 environment unless you're a very small organization, you saw as 473 00:26:15,600 --> 00:26:17,900 heterogeneous environment that you need to connect. 474 00:26:17,900 --> 00:26:22,500 So it is somewhat challenging but I wanted to bring you back 475 00:26:22,500 --> 00:26:27,000 in all through this up to your room but also to Jeff is around 476 00:26:27,000 --> 00:26:32,300 the OCTA and all that 0dr auth0. You can because I just find it 477 00:26:32,300 --> 00:26:36,700 fascinating. I think it's going to be really 478 00:26:36,700 --> 00:26:38,700 see the impact play out of the next few years. 479 00:26:38,800 --> 00:26:43,500 I'm wondering, you know, Jeff and I are in the Consulting 480 00:26:43,500 --> 00:26:46,400 space, right? So, we get involved with a lot 481 00:26:46,400 --> 00:26:51,100 of product evaluations with our clients and product bake-offs, 482 00:26:51,100 --> 00:26:54,700 and it's just surprising, however, maybe not surprising, 483 00:26:54,700 --> 00:26:58,800 but it was just happening so much that Octonauts 0 would be 484 00:26:58,800 --> 00:27:02,900 finalists kind of pacing off. With one another in product 485 00:27:02,900 --> 00:27:06,000 evaluations, they have a different story to tell, right? 486 00:27:06,000 --> 00:27:10,700 Octus kind of the, you know, my perspective was it was a tool 487 00:27:10,700 --> 00:27:15,700 built so, you know, from the UI system administrator kind of 488 00:27:15,700 --> 00:27:19,900 tool for doing identity. Access management. 489 00:27:19,900 --> 00:27:22,700 Where is also 0 was kind of a developer tool, right? 490 00:27:22,700 --> 00:27:26,100 You need to be able to go in and kind of look at the code and do 491 00:27:26,100 --> 00:27:28,800 a lot of code samples so you could play with and things like 492 00:27:28,800 --> 00:27:30,900 that. I guess, turning all Didn't do a 493 00:27:30,900 --> 00:27:35,500 question. Is what does OCTA need to do 494 00:27:36,700 --> 00:27:38,200 now? There's made the author's, 0 495 00:27:38,200 --> 00:27:40,800 acquisition to make it successful or it it's got to be 496 00:27:40,800 --> 00:27:46,300 more than just a Runners, two separate products forever, 497 00:27:46,300 --> 00:27:47,900 right? And you have their wisest just, 498 00:27:47,900 --> 00:27:50,900 they would have been better kind of running off on their own. 499 00:27:51,500 --> 00:27:54,700 What do what do they need to do? You have a perspective on that? 500 00:27:54,700 --> 00:27:58,300 Or is it just sit back and wait? And see a room. 501 00:27:58,300 --> 00:27:59,900 One, that you take that one first? 502 00:28:00,100 --> 00:28:03,700 So, So my feeling is getting that look, I would say that we 503 00:28:03,700 --> 00:28:06,800 should wait and watch because OCTA had actually acquired 504 00:28:06,800 --> 00:28:09,900 multiple different tools with some overlap in the 505 00:28:09,900 --> 00:28:13,100 capabilities. So how they are going to, you 506 00:28:13,100 --> 00:28:16,600 know, create you know, homogeneous solution and 507 00:28:16,600 --> 00:28:19,900 integrate all of them together to bring the capability for 508 00:28:19,900 --> 00:28:22,500 their end. Customer will be something. 509 00:28:22,500 --> 00:28:26,500 Which will be really interesting for us to watch also like 510 00:28:26,600 --> 00:28:31,000 treating each of these products separately and bring Benefit. 511 00:28:31,000 --> 00:28:35,100 If you add the licensing cost. That goes very, very high. 512 00:28:35,100 --> 00:28:37,000 So it will be really interesting. 513 00:28:37,000 --> 00:28:44,100 I probably, I prefer to reserve my comment and see that, how it 514 00:28:44,100 --> 00:28:47,400 shapes up in coming days, because it's not just about 515 00:28:47,400 --> 00:28:50,700 zero, but the other very recent acquisition, what they did, for 516 00:28:50,700 --> 00:28:54,600 IG. And okay, let's see how all of 517 00:28:54,600 --> 00:28:57,900 that plays together, and that's a great CEO answer for sure. 518 00:28:57,908 --> 00:29:02,200 You know, the way that I I would approaches is I don't, I'm not a 519 00:29:02,208 --> 00:29:05,900 CEO but my two cents would be, you know, I think you have to 520 00:29:05,900 --> 00:29:07,900 take a look at the different markets that they've 521 00:29:07,900 --> 00:29:10,300 traditionally served so austere. All like you said, Jim has been 522 00:29:10,300 --> 00:29:12,900 more developer focus. And I think OCTA has been seen 523 00:29:12,900 --> 00:29:16,100 more as an Enterprise kind of inside the firewall type tool, 524 00:29:16,100 --> 00:29:18,800 right for employees. But they have been making 525 00:29:18,800 --> 00:29:21,300 inroads to the customer side of things, maybe it's out roads, 526 00:29:21,300 --> 00:29:23,000 not sure if it's in roads, if you're talking about customers 527 00:29:23,000 --> 00:29:26,100 in that case. But I think one of the things 528 00:29:26,100 --> 00:29:29,900 that what I would probably look at is in the short-term, 529 00:29:30,000 --> 00:29:31,500 nothing. It's right there to big 530 00:29:31,500 --> 00:29:34,000 companies, they're going to have to kind of navigate the 531 00:29:34,000 --> 00:29:36,800 different Technologies and integration where it makes 532 00:29:36,800 --> 00:29:39,200 sense, so that they don't disrupt customers of their own. 533 00:29:39,200 --> 00:29:43,500 But I think long-term, I think this strengthens octaves API 534 00:29:43,500 --> 00:29:48,100 situation and gives them a more developer focused capability 535 00:29:48,100 --> 00:29:51,400 with in that regard. And then, you know, at some 536 00:29:51,400 --> 00:29:53,900 point there's going to be a lot of overlap because they do a lot 537 00:29:53,900 --> 00:29:57,000 of the same things. So you know it is a year from 538 00:29:57,000 --> 00:30:00,600 now or maybe it's two years from now, you know, which API are You 539 00:30:00,600 --> 00:30:03,500 actually using. Is it an original OCTA one? 540 00:30:03,500 --> 00:30:05,500 Or is it an Oscar one? And at the end of the day, it 541 00:30:05,500 --> 00:30:08,200 doesn't matter as long as it's, you know, leveraging, whatever 542 00:30:08,200 --> 00:30:10,900 it is, you're trying to do. So I think it'll be interesting 543 00:30:10,900 --> 00:30:12,900 to see how it works out because, you know, they're certainly not 544 00:30:12,900 --> 00:30:15,500 the only ones making Making Waves in that space made act as 545 00:30:15,700 --> 00:30:18,400 we're coming out of octane which was their yearly conference. 546 00:30:18,400 --> 00:30:21,500 This year. They announced Pam capabilities 547 00:30:21,500 --> 00:30:22,800 and the privileged access management space. 548 00:30:22,800 --> 00:30:26,100 They announced IGA and identity governance capabilities but a 549 00:30:26,108 --> 00:30:28,500 lot of that stuff isn't really coming until next year so they 550 00:30:28,500 --> 00:30:30,300 made a lot of waves with announcements. 551 00:30:30,500 --> 00:30:33,400 But this isn't anything that's real until it hits the market. 552 00:30:33,600 --> 00:30:36,900 And that's not slated, until I think q1 of 2022. 553 00:30:36,900 --> 00:30:40,300 So we're still a ways away and it's as always the devil's in 554 00:30:40,300 --> 00:30:42,100 the details, right? What does that actually mean? 555 00:30:42,100 --> 00:30:44,700 When you're saying you're doing IGA, what does it actually mean? 556 00:30:44,700 --> 00:30:46,900 We're doing privileged access management, is it going to be as 557 00:30:46,900 --> 00:30:49,100 full featured as something like a cyber-ark? 558 00:30:49,100 --> 00:30:51,500 Which is kind of the dominant player in that space, right? 559 00:30:51,800 --> 00:30:54,300 So I think I'll be interesting to see how it works out. 560 00:30:54,300 --> 00:30:56,600 And I think this kind of drives towards where I wanted to take 561 00:30:56,600 --> 00:30:59,000 the next question which was around investments in the I am 562 00:30:59,000 --> 00:31:03,100 space because As we see organizations start to look at 563 00:31:03,100 --> 00:31:06,200 different platforms, sometimes that means making an investment 564 00:31:06,200 --> 00:31:10,900 in that platform and divesting from existing infrastructure or 565 00:31:10,900 --> 00:31:12,500 tools that they might already have. 566 00:31:12,900 --> 00:31:15,500 And I'm curious to run from your perspective, I guess, couple 567 00:31:15,500 --> 00:31:16,800 questions right. What are you're seeing from that 568 00:31:16,800 --> 00:31:20,600 perspective of investing and new platforms and new tools and 569 00:31:20,608 --> 00:31:24,300 trying to build that converged? I am capability where it makes 570 00:31:24,300 --> 00:31:26,600 sense. And then from a just from a 571 00:31:26,600 --> 00:31:30,000 market perspective, do you see any differences in the way that 572 00:31:30,000 --> 00:31:32,300 the you This has been approaching those types of 573 00:31:32,300 --> 00:31:34,400 scenarios versus maybe what's been taking place 574 00:31:34,400 --> 00:31:35,700 internationally? Yes. 575 00:31:35,700 --> 00:31:39,400 So, this is a standard question and the way I would like to 576 00:31:39,400 --> 00:31:43,600 answer this, that there are a couple of, you know, standard 577 00:31:43,600 --> 00:31:47,600 driver for investment in. I am a space that are Universal 578 00:31:47,600 --> 00:31:51,900 all across the globe, like Regulatory, Compliance, and 579 00:31:52,000 --> 00:31:55,700 audit, and compliance needs are standard across the globe. 580 00:31:56,000 --> 00:32:00,600 Whether you look at, you know, America's us has got Tree 581 00:32:00,600 --> 00:32:05,600 specific regulations and you know same way in Europe, the GDP 582 00:32:05,600 --> 00:32:08,900 are the government regulation or here in the CCP. 583 00:32:08,900 --> 00:32:12,000 All of that are driving and each country has got their own 584 00:32:12,000 --> 00:32:14,300 regulation. So that's one of the primary 585 00:32:14,800 --> 00:32:20,000 driver for I am investment, but apart from that, you know, the 586 00:32:20,800 --> 00:32:24,500 some of the new drivers which had come up is like digital 587 00:32:24,500 --> 00:32:29,600 transformation and especially in American Market, many of the 588 00:32:29,600 --> 00:32:32,500 organization. You know, they are going through 589 00:32:32,500 --> 00:32:35,500 the digital transformation and this had created a very 590 00:32:35,500 --> 00:32:40,000 different need for looking at identity and access management 591 00:32:40,300 --> 00:32:44,000 primarily because they want to, you know, handle the user 592 00:32:44,000 --> 00:32:47,900 experience and the user consent management, and all those 593 00:32:47,900 --> 00:32:53,100 Associated single user ID and those you know whole lot of 594 00:32:53,100 --> 00:32:57,300 those experiential input which they want to handle differently. 595 00:32:57,700 --> 00:33:00,100 That's actually driving in a big way. 596 00:33:00,500 --> 00:33:02,900 Adoption of identity and access management. 597 00:33:03,300 --> 00:33:09,600 And the you know the other area is the risk mitigation and the 598 00:33:09,600 --> 00:33:13,600 overall maturity of the security cannot be achieved by you know, 599 00:33:13,600 --> 00:33:16,200 keeping things manual or semi-automated. 600 00:33:16,400 --> 00:33:20,700 So without having identity and access management solution, you 601 00:33:20,700 --> 00:33:24,500 know, deployed or without making this investment, you cannot get 602 00:33:24,500 --> 00:33:27,500 to the modern cyber security architecture. 603 00:33:28,600 --> 00:33:32,700 I am Solutions are driving you. No identity Centric analytics 604 00:33:32,700 --> 00:33:35,300 like a behavior analytics and those kind of things which you 605 00:33:35,300 --> 00:33:39,800 can bring into the picture. And, you know, using those 606 00:33:39,800 --> 00:33:43,000 identities and click or behavior analytics, you can identify the 607 00:33:43,000 --> 00:33:47,500 indicators of compromise early on, and you can feed in, you 608 00:33:47,500 --> 00:33:51,200 know, more enriched information to your security operations 609 00:33:51,200 --> 00:33:55,200 center. And also based on the risk 610 00:33:55,300 --> 00:33:58,500 associated with the transaction, there are different level of 611 00:33:58,500 --> 00:34:03,300 authentication, which you can. Provide so risk mitigation is, 612 00:34:03,600 --> 00:34:08,100 you know, Big, Big Driver, you know, for I am investment. 613 00:34:08,699 --> 00:34:12,600 Now, looking at the geographical differences, I would say in US 614 00:34:12,600 --> 00:34:16,000 market, digital transformation is one of the co-driver a part 615 00:34:16,000 --> 00:34:20,199 from Regulatory Compliance, or operational efficiency, but in a 616 00:34:20,199 --> 00:34:24,199 media Market you know it's a bring your own device or 617 00:34:24,199 --> 00:34:28,900 Mobility Trend that's also creating a major push towards 618 00:34:28,900 --> 00:34:32,300 adoption. And affect Market is primarily 619 00:34:32,300 --> 00:34:35,199 because of security concerns, because there have been so many 620 00:34:35,199 --> 00:34:36,699 different breaches which happened. 621 00:34:37,000 --> 00:34:40,800 So just to prevent the Cyber theft, that's the core reason 622 00:34:41,000 --> 00:34:43,900 and the government regulation, as I mentioned earlier, that's 623 00:34:43,900 --> 00:34:48,100 the driver for investment in. I am it's interesting that you 624 00:34:48,100 --> 00:34:54,199 finished off with the security One driver, you know, we're we 625 00:34:54,199 --> 00:34:58,600 hear from even from clients, now they're looking at a zero, trust 626 00:34:58,600 --> 00:35:02,500 model. So used to be We would recommend 627 00:35:02,500 --> 00:35:05,900 or ask have you looked at your Charles servers your trust on 628 00:35:05,900 --> 00:35:08,900 your plate? I'm wondering, you know, is that 629 00:35:08,900 --> 00:35:10,500 a driver that you're seeing as well? 630 00:35:10,500 --> 00:35:13,700 Where clients are actually saying we are, we are tracking 631 00:35:13,700 --> 00:35:15,500 towards has your trust framework? 632 00:35:16,200 --> 00:35:20,500 And I'm wondering are you designing your Solutions or your 633 00:35:20,500 --> 00:35:25,200 messaging around the zero trust framework and using the 634 00:35:25,200 --> 00:35:30,200 converged, im as a as a way to achieve store troughs. 635 00:35:30,800 --> 00:35:33,800 Yeah of course. Yes you know on zero cost is 636 00:35:33,800 --> 00:35:37,700 definitely pretty hot in the market and I'll quote you know 637 00:35:37,700 --> 00:35:41,000 the reasons that we've done by October that itself indicates 638 00:35:41,000 --> 00:35:44,300 that more than 60% you know Enterprises. 639 00:35:44,300 --> 00:35:48,100 They are trying to be are working towards introducing 0 640 00:35:48,100 --> 00:35:52,100 trusting to their environment and in our experience also like 641 00:35:52,100 --> 00:35:55,300 ailanthus being a global company when we you know interact with 642 00:35:55,300 --> 00:35:58,500 the clients in Southeast Asia or Europe or in the US. 643 00:35:58,500 --> 00:36:02,200 So could we find that 0? Stays one of the common element. 644 00:36:02,200 --> 00:36:05,900 Okay, which people are asking about, and if you look at zero 645 00:36:05,900 --> 00:36:10,600 trust primarily it is, you know, pushing the entire requirement, 646 00:36:11,100 --> 00:36:14,900 you know, we are never trust, always verify model towards 647 00:36:15,000 --> 00:36:18,900 continuous authentication. So I would say that gone are the 648 00:36:18,900 --> 00:36:21,300 days. Okay, we are clients are happy 649 00:36:21,300 --> 00:36:24,700 with one time authentication. Now they are looking for 650 00:36:24,700 --> 00:36:29,700 continuous authentication to be able to boost their overall 651 00:36:29,700 --> 00:36:34,300 maturity of the cybersecurity. And if you look at the, you 652 00:36:34,300 --> 00:36:37,700 know, core requirement of zero trust framework where people 653 00:36:37,700 --> 00:36:41,500 start with, you know, the creating separate zones and then 654 00:36:41,500 --> 00:36:45,500 identifying their high-value asset into the most secure Zone 655 00:36:45,900 --> 00:36:49,100 you require to continuously monitor the traffic which is 656 00:36:49,100 --> 00:36:52,800 going in and out and who are the people who are accessing those, 657 00:36:54,000 --> 00:36:57,600 you know, high-value critical assets and the traditional 658 00:36:57,600 --> 00:37:01,500 approach of having this login ID, password, And every time you 659 00:37:01,500 --> 00:37:06,000 pop up and people need to login, you know, enter those password, 660 00:37:06,100 --> 00:37:08,600 or if you have taken the authentic credentials first 661 00:37:08,600 --> 00:37:10,300 time, and then you are playing it again. 662 00:37:10,300 --> 00:37:12,900 And again is not going to help at all. 663 00:37:13,400 --> 00:37:18,500 So one of the roadblock, 40 trusted option is the password. 664 00:37:19,100 --> 00:37:23,100 And that's where we are actually noticing that there is a, you 665 00:37:23,100 --> 00:37:26,400 know, new trend which is catching up in a big way, the 666 00:37:26,400 --> 00:37:31,900 password less authentication and This is a primarily, you know, 667 00:37:31,900 --> 00:37:35,500 bringing cryptographically techniques to be able to you 668 00:37:35,500 --> 00:37:40,100 know, pass on the credential and you know handle it in a manner. 669 00:37:40,100 --> 00:37:42,900 We are without involving the user at the back end. 670 00:37:43,000 --> 00:37:47,700 You can do it in a more secure Manner and then you know, enable 671 00:37:47,700 --> 00:37:50,500 the organizations and the businesses to be able to deploy 672 00:37:50,500 --> 00:37:52,700 the zero trust solution. Yeah. 673 00:37:52,700 --> 00:37:57,100 I'll say, we here at the the identity of the center podcast, 674 00:37:57,300 --> 00:38:00,000 have a strong disdain for the password. 675 00:38:01,100 --> 00:38:04,000 So, you're hitting on a lot of good points, but so let me put 676 00:38:04,000 --> 00:38:06,900 it to you like this. Finish the sentence, the 677 00:38:06,900 --> 00:38:12,500 password is dead, dot dot dot. I say password is dead, and it's 678 00:38:12,500 --> 00:38:16,100 a time for you to upgrade your identity and access management 679 00:38:16,100 --> 00:38:19,100 solution. I strongly recommend people to 680 00:38:19,100 --> 00:38:22,800 try out the password less authentication and, you know, 681 00:38:22,800 --> 00:38:26,000 try it out for a pilot set of users first. 682 00:38:26,000 --> 00:38:29,400 See that how delighted they are in terms of their experience and 683 00:38:29,400 --> 00:38:31,400 then you can roll it. Out for other stuff. 684 00:38:31,400 --> 00:38:36,600 The users in your organization. That's I think that's a great 685 00:38:36,600 --> 00:38:40,400 answer, you know. I think password lists is one of 686 00:38:40,400 --> 00:38:43,500 the few Technologies where you can improve the customer 687 00:38:43,500 --> 00:38:47,200 experience and improve security at the same time. 688 00:38:47,900 --> 00:38:52,200 So let me pass this one to Jeff. Jeff, the password is dead dot 689 00:38:52,200 --> 00:38:56,900 dot dot again. I've been here in the passwords 690 00:38:56,900 --> 00:38:59,500 dad's, I don't know. For the last seems like five 691 00:38:59,500 --> 00:39:02,900 six, seven years, Um, I don't know anybody who doesn't want to 692 00:39:02,900 --> 00:39:07,000 kill the password, but we're still stuck in this mode of you 693 00:39:07,000 --> 00:39:09,600 know, organizations having not made the investment in there. 694 00:39:09,600 --> 00:39:12,400 I am platforms to be able to support that or they're just 695 00:39:12,400 --> 00:39:15,400 starting to get into it right. Hardware Cycles can be very long 696 00:39:15,400 --> 00:39:17,900 in an organization. You may have like a three or 697 00:39:17,900 --> 00:39:20,800 five-year laptop refresh or, you know, Hardware refresh. 698 00:39:20,800 --> 00:39:24,900 And maybe people are just now getting into things like 699 00:39:25,200 --> 00:39:29,100 Windows, hello, right? Or the touch of Touch ID on a 700 00:39:29,107 --> 00:39:31,100 MacBook. There's always the mobile 701 00:39:31,100 --> 00:39:32,800 option, but there's always been hesitancy. 702 00:39:32,800 --> 00:39:38,400 I think to allow people to use a non corporate device to do 703 00:39:38,800 --> 00:39:41,500 corporate E-Type things, right? And I'll be waiting is out 704 00:39:41,500 --> 00:39:44,300 there, but sometimes made there is another good mobile device 705 00:39:44,300 --> 00:39:47,600 management plan in place. So, I guess I'll see it when I 706 00:39:47,607 --> 00:39:49,600 believe it. I really hope I'll believe it 707 00:39:49,600 --> 00:39:50,600 when I see it. I should say. 708 00:39:51,800 --> 00:39:53,800 I hope it comes sooner rather than later. 709 00:39:53,800 --> 00:39:56,700 It's a fantastic feature. When you've got it enabled, you 710 00:39:56,700 --> 00:40:02,000 know, for your organization. But yeah, I think let me know 711 00:40:03,000 --> 00:40:06,600 when it actually is real in the majority of organizations and 712 00:40:06,600 --> 00:40:08,800 maybe not just you know the folks who are trying to be 713 00:40:08,800 --> 00:40:11,400 cutting edge. So I know we're coming up here 714 00:40:11,400 --> 00:40:15,800 towards the you know, our time for this conversation but before 715 00:40:15,800 --> 00:40:18,500 we go, I wanted to know. One, thanks so much for joining 716 00:40:18,500 --> 00:40:19,100 us. A rune. 717 00:40:19,500 --> 00:40:22,900 Are there any final kind of Pearls of Wisdom that maybe you 718 00:40:22,900 --> 00:40:25,600 can drop on the folks that are listening here or for Jim? 719 00:40:25,600 --> 00:40:29,700 And I so just one point I wanted to add here like the point, 720 00:40:29,700 --> 00:40:31,500 which you And regarding password less. 721 00:40:31,500 --> 00:40:35,700 Authentication is so very true. And, you know, I have actually, 722 00:40:36,300 --> 00:40:41,000 I'm publishing one paper on Forbes regarding this particular 723 00:40:41,000 --> 00:40:43,900 point, the observations around, what are the reluctance in the 724 00:40:43,908 --> 00:40:46,900 minds of the people? And it's kind of based on my 725 00:40:46,900 --> 00:40:49,200 conversation with many of those clients. 726 00:40:49,200 --> 00:40:52,700 Okay, who are interested in password less authentication but 727 00:40:52,800 --> 00:40:55,400 still thinking. So I tried compiling those 728 00:40:55,400 --> 00:40:59,100 thought process together. So please look out for this 729 00:40:59,100 --> 00:41:04,200 folks article, which is Coming up next week on the same topic. 730 00:41:04,300 --> 00:41:06,400 Now, I'll be great. Yeah, if you can we can get a 731 00:41:06,408 --> 00:41:07,500 link. We can certainly include it in 732 00:41:07,500 --> 00:41:09,000 the show notes that people can come check it out. 733 00:41:09,000 --> 00:41:10,800 And I'm always interested to hear what the thoughts are 734 00:41:10,808 --> 00:41:15,300 around it, because it is a no-brainer until someone has to 735 00:41:15,308 --> 00:41:17,400 spend some money to make it happen. 736 00:41:17,700 --> 00:41:20,600 And hopefully, that will take place sooner rather than later. 737 00:41:21,300 --> 00:41:23,400 Jim. Any final words of wisdom for 738 00:41:23,400 --> 00:41:26,400 us? Yeah, two things for me first, 739 00:41:26,600 --> 00:41:28,300 my answer in the password is dead. 740 00:41:28,300 --> 00:41:30,200 Its Jester's dead. No. 741 00:41:30,300 --> 00:41:34,900 No, it's not. But the problem is that a lot of 742 00:41:34,900 --> 00:41:40,500 the core information, security issues that we Face will not go 743 00:41:40,500 --> 00:41:45,200 away until it actually is said, so you know, is it going to be 5 744 00:41:45,200 --> 00:41:47,100 years? We're still laughing at the 745 00:41:47,600 --> 00:41:51,700 statement, the password is bed, or is there going to be a great 746 00:41:51,700 --> 00:41:54,700 movement toward and, you know, it's really on the b2c side? 747 00:41:54,700 --> 00:41:57,700 Where is the biggest problem? That's things that basically 748 00:41:57,700 --> 00:42:00,200 internet even more than is on the corporate side? 749 00:42:00,500 --> 00:42:04,000 So that's that's my number one comment on this number to 750 00:42:04,000 --> 00:42:06,900 comment is really, we talked a little bit about the space. 751 00:42:06,900 --> 00:42:12,300 We talked about, you know, evaluating I am Solutions and we 752 00:42:12,300 --> 00:42:15,900 have the CEO on from one of the companies are not saying that's 753 00:42:15,900 --> 00:42:21,100 just the, as a service to him. But just as overall, I think, 754 00:42:21,400 --> 00:42:25,600 you know, the approach that most organizations take when they're 755 00:42:25,600 --> 00:42:29,200 evaluating, I am solutions to look at like the magic quadrant, 756 00:42:29,200 --> 00:42:32,200 for example, and say Say we're just going to look at vendors in 757 00:42:32,200 --> 00:42:35,900 the upper, right but my perspective is always been that 758 00:42:36,100 --> 00:42:40,000 you know that is a guidance guidelines so you kind of can 759 00:42:40,200 --> 00:42:43,700 survey the space and know who's in it and who has the most 760 00:42:43,700 --> 00:42:48,500 complete solution, get all that information is valuable but all 761 00:42:48,500 --> 00:42:52,500 the organizations that are kind of within that realm even if 762 00:42:52,500 --> 00:42:54,300 they're in the lower left quadrant doesn't mean they're 763 00:42:54,300 --> 00:42:58,200 not good Solutions and that they don't fit a certain use case 764 00:42:58,200 --> 00:43:01,700 that you have, right. Although Solutions are in 765 00:43:01,700 --> 00:43:08,400 business because they they fit and need for some organizations, 766 00:43:08,400 --> 00:43:11,400 right? And so I would encourage folks 767 00:43:11,400 --> 00:43:14,800 that if they're going into the product evaluation phase that 768 00:43:15,000 --> 00:43:19,900 they set their their Vision, their field of vision as widely 769 00:43:19,900 --> 00:43:25,200 as possible to evaluate organization or evaluate, I am 770 00:43:25,200 --> 00:43:29,000 products that are maybe not in the upper right-hand quadrant 771 00:43:29,700 --> 00:43:32,800 that's just The only thought is because I think if you open that 772 00:43:32,800 --> 00:43:35,700 field of vision you may find something that is actually the 773 00:43:35,700 --> 00:43:39,100 perfect fit for your particular circumstances. 774 00:43:39,800 --> 00:43:42,000 And that's a really good point. I think, you know, at times 775 00:43:42,000 --> 00:43:43,800 organizations get their blinders on, right? 776 00:43:43,800 --> 00:43:46,900 And they kind of follow Gartner's gospel, which you 777 00:43:46,900 --> 00:43:49,100 know, they're great. They're a great research firm 778 00:43:49,100 --> 00:43:50,300 but they're not the end-all be-all. 779 00:43:51,500 --> 00:43:55,400 There are really really good products that are in the Gartner 780 00:43:55,400 --> 00:43:57,900 magic quadrant and any of them. They're also really good 781 00:43:57,900 --> 00:44:00,200 products that aren't rated because there is, you know, 782 00:44:00,300 --> 00:44:03,100 Certain thresholds to even be considered that in that spot 783 00:44:03,100 --> 00:44:06,400 kind of analysis. So, you know, take the time to 784 00:44:06,400 --> 00:44:09,500 do the research, take a look at what's actually important to 785 00:44:09,500 --> 00:44:12,400 your organization, what are the capabilities and services that 786 00:44:12,400 --> 00:44:15,300 you need and make the right choice for your organization 787 00:44:15,300 --> 00:44:16,900 based on, you know, that kind of knowledge. 788 00:44:16,900 --> 00:44:20,300 So I think that's a really good advice Jim, so I appreciate 789 00:44:20,300 --> 00:44:22,200 that. So I think with that, we're 790 00:44:22,200 --> 00:44:24,600 going to go ahead and close it out for this week Arun. 791 00:44:24,600 --> 00:44:26,800 Appreciate you being part of this gym as well. 792 00:44:27,200 --> 00:44:31,000 You can also you know visit us again at the show at W dot 793 00:44:31,000 --> 00:44:34,500 identity at the center.com. We're on Twitter at idac 794 00:44:34,500 --> 00:44:36,400 podcast. You know, we're always open to 795 00:44:36,408 --> 00:44:39,400 linking and Linkedin connections and messages that way. 796 00:44:39,400 --> 00:44:41,600 If you've got ideas for the show, you'll feel free to 797 00:44:41,600 --> 00:44:44,100 connect with Jim and I a rune I'm going to assume that you're 798 00:44:44,100 --> 00:44:45,600 open to connections as well on LinkedIn. 799 00:44:45,600 --> 00:44:46,900 Is that right? Yes. 800 00:44:46,900 --> 00:44:50,300 Absolutely great. So I'll include your information 801 00:44:50,300 --> 00:44:52,600 as well in our show notes that people can check out. 802 00:44:52,900 --> 00:44:56,700 And then with that I hope everyone is staying happy and 803 00:44:56,700 --> 00:44:58,800 healthy and we'll talk with you all in the next one. 804 00:44:58,800 --> 00:45:01,400 Thanks. Thank Thanks Jim and Jeff. 805 00:45:05,800 --> 00:45:08,700 Thanks for listening to the identity at the center podcast. 806 00:45:08,800 --> 00:45:11,100 If you like what you heard, don't forget to subscribe and 807 00:45:11,100 --> 00:45:14,300 visit us on the web and identity at the center.com.