1 00:00:04,800 --> 00:00:12,040 This is Identity at the Center. Hi, welcome to the Identity at 2 00:00:12,040 --> 00:00:14,720 the Center podcast. I'm your host, Jim McDonald. 3 00:00:14,880 --> 00:00:19,160 Unfortunately, Jeff Steadman had other activities going today and 4 00:00:19,160 --> 00:00:21,120 wasn't able to make this episode. 5 00:00:21,600 --> 00:00:25,200 This is a sponsor spotlight with a company called Nexus. 6 00:00:26,480 --> 00:00:31,720 They're at nexus-secure.com and I hope you have an opportunity 7 00:00:31,720 --> 00:00:37,040 to check them out at nexus-secure.com/idac. 8 00:00:37,920 --> 00:00:40,200 Again, this is a sponsored episode, so it's a little bit 9 00:00:40,200 --> 00:00:41,960 different than our regular episodes. 10 00:00:42,160 --> 00:00:45,360 We're going to be joined by Doctor Heiko Klarl, who is the 11 00:00:45,360 --> 00:00:50,440 CEO over at Nexus. And that's NEXIS, in case you're 12 00:00:50,440 --> 00:00:55,080 wondering. And Doctor Klarl's going to kind 13 00:00:55,080 --> 00:00:59,520 of give us what they do and how they help solve the identity and 14 00:00:59,520 --> 00:01:03,240 access management practitioner problems that we all kind of 15 00:01:03,240 --> 00:01:07,920 fight with on a daily basis. So walk through the show, Doctor 16 00:01:08,040 --> 00:01:09,800 Heiko. Yeah. 17 00:01:09,800 --> 00:01:11,360 Thanks, Jim. It's a pleasure. 18 00:01:12,400 --> 00:01:15,160 Well, really glad to have you here, the pleasure of all ours 19 00:01:15,440 --> 00:01:20,400 and we really want to learn about Nexus and what you, what 20 00:01:20,400 --> 00:01:24,240 you guys do and what it is that you bring to the market. 21 00:01:24,400 --> 00:01:28,240 So, but of course this is your first time on the Identity at 22 00:01:28,240 --> 00:01:31,040 Center podcast. So maybe you can kind of give us 23 00:01:31,040 --> 00:01:33,320 your background how you got into Identity? 24 00:01:33,560 --> 00:01:36,600 Did Identity choose you or did you choose it? 25 00:01:38,320 --> 00:01:39,400 Yeah, that, that's a good question. 26 00:01:39,400 --> 00:01:41,720 So I would say I've chosen identity. 27 00:01:41,720 --> 00:01:45,480 So back back in time, more than 20 years ago, I started computer 28 00:01:45,480 --> 00:01:49,240 science and at the end I had to kind of make my diploma thesis 29 00:01:49,240 --> 00:01:53,280 and all the kind of security thingies have been super excited 30 00:01:53,280 --> 00:01:56,760 for me. And basically I did research on 31 00:01:56,840 --> 00:01:59,800 service oriented architectures and business process modelling 32 00:01:59,800 --> 00:02:04,400 and how to apply some security things with an example of BA 33 00:02:04,400 --> 00:02:08,560 equilogic security. So the listeners experienced in 34 00:02:08,560 --> 00:02:11,680 a longer time in the market probably remember still BA Yeah, 35 00:02:11,680 --> 00:02:15,080 this was my step into the kind of identity and access 36 00:02:15,080 --> 00:02:18,560 management business and and community. 37 00:02:18,560 --> 00:02:23,640 And after that, I did my PhD also in, in identity and access 38 00:02:23,640 --> 00:02:30,320 management and was researching on how to apply access policies 39 00:02:30,320 --> 00:02:34,120 into business process modelling. So you probably remember back in 40 00:02:34,120 --> 00:02:37,560 time, but the service oriented architectures, everyone had the 41 00:02:37,560 --> 00:02:41,600 hope that business people, business departments can model 42 00:02:41,600 --> 00:02:44,600 their processes and so on. And then what's the question on 43 00:02:44,760 --> 00:02:49,160 how to keep it secure? Can we model it in an, in an 44 00:02:49,160 --> 00:02:56,240 model language like BPMN and kind of having an an, an process 45 00:02:56,240 --> 00:03:00,080 to create a model driven approach to create all the 46 00:03:00,080 --> 00:03:05,080 models that finally are needed to end up into a policy for 47 00:03:05,080 --> 00:03:07,760 commercial of the Chef products? Yeah, the rest is history. 48 00:03:08,200 --> 00:03:10,320 And the rest is history. So now you're part of the 49 00:03:10,320 --> 00:03:14,240 industry and you are the CEO of Nexus. 50 00:03:14,560 --> 00:03:18,120 And I'm wondering, you know, what would, you know? 51 00:03:18,280 --> 00:03:20,800 Give us the elevator pitch. What does Nexus do? 52 00:03:21,560 --> 00:03:25,160 Yeah, Nexus takes care about authorization governance. 53 00:03:25,160 --> 00:03:30,480 So we're taking care about helping large enterprises, 54 00:03:30,480 --> 00:03:36,120 regulated customers such as insurances and, and and banks to 55 00:03:36,120 --> 00:03:39,240 do a proper role mining, role management and role life cycle 56 00:03:39,240 --> 00:03:42,440 management. Or in a wider sense, going away 57 00:03:42,440 --> 00:03:45,800 from a kind of static authorizations also covering the 58 00:03:46,240 --> 00:03:49,640 dynamic part like attribute based access control, policy 59 00:03:49,640 --> 00:03:52,680 driven based access control and this kind of stuff. 60 00:03:52,720 --> 00:03:57,040 And we see that especially in regulated challenges, it's quite 61 00:03:57,040 --> 00:04:01,280 cumbersome to really ensure that everyone is allowed to do what 62 00:04:01,280 --> 00:04:04,000 they should do and not, not more. 63 00:04:04,000 --> 00:04:06,760 And so all the kind of access review things are quite 64 00:04:06,760 --> 00:04:09,440 complicated. And looking back those 20 years 65 00:04:09,440 --> 00:04:14,280 in the industry, basically I started my career with Sun 66 00:04:14,280 --> 00:04:20,240 Identity Manager 20 years ago. Things are still not super 67 00:04:20,240 --> 00:04:22,160 great. So business managers are still 68 00:04:22,160 --> 00:04:26,880 struggling when they have to recertify and review access for 69 00:04:26,880 --> 00:04:29,800 the employees. And this is where Nexus comes in 70 00:04:30,080 --> 00:04:34,320 into a Better Together story, sitting on top of large IGA 71 00:04:34,320 --> 00:04:39,400 products such as say .1 Identity, Savient, Oracle, IBM 72 00:04:39,400 --> 00:04:43,120 Open Text, you name it, in A Better Together story. 73 00:04:43,120 --> 00:04:44,720 And that's the most important thing. 74 00:04:44,720 --> 00:04:48,480 So we are bringing those capabilities that clients are 75 00:04:48,480 --> 00:04:52,200 missing and kind of ensuring happy customers. 76 00:04:52,920 --> 00:04:55,320 Yeah, I I love that Better Together story. 77 00:04:55,320 --> 00:04:58,000 So you, you mentioned a lot there. 78 00:04:58,000 --> 00:04:59,640 We'll get to dive into all of it. 79 00:05:00,880 --> 00:05:03,440 One of the things that I kind of took away from what you're 80 00:05:03,440 --> 00:05:07,080 talking about was creating this visibility over the 81 00:05:07,080 --> 00:05:10,200 authorizations. And I think that's such a key. 82 00:05:10,200 --> 00:05:13,720 It's one of the things that practitioners struggle with is 83 00:05:14,000 --> 00:05:17,600 how do you get visibility to everything, all these identity 84 00:05:17,600 --> 00:05:21,360 systems, identity silos that exists within your organization, 85 00:05:21,680 --> 00:05:23,520 and how do you make sense of it all? 86 00:05:23,520 --> 00:05:28,640 So does that resonate with you? AB Absolutely. 87 00:05:29,000 --> 00:05:32,960 So the, the whole visibility part in getting rid of this of 88 00:05:32,960 --> 00:05:36,400 silos is something the whole industry is, is struggling. 89 00:05:36,400 --> 00:05:40,400 There are so many large enterprise customers out there. 90 00:05:40,720 --> 00:05:44,600 They have at least one most likely 2 or even more kind of 91 00:05:44,640 --> 00:05:50,880 AGIGA focused systems, an old one and a new one and with an M 92 00:05:50,880 --> 00:05:56,120 and a merger a a third one that will have some Pam systems and 93 00:05:56,120 --> 00:05:58,040 probably a couple of access management systems. 94 00:05:58,480 --> 00:06:02,880 And despite every, everyone is moving into a kind of 95 00:06:03,560 --> 00:06:06,840 consolidated identity and access management landscape. 96 00:06:06,840 --> 00:06:10,760 It just takes ages. So recently I was talking to a 97 00:06:11,360 --> 00:06:14,480 big bank here in in Europe with roughly 2 1/2 thousand 98 00:06:14,480 --> 00:06:16,880 applications. They have just managed to 99 00:06:16,880 --> 00:06:20,920 onboard 500 so far into their new IGA solution. 100 00:06:20,920 --> 00:06:25,680 And so basically they have 500 there, 2000 there, which makes 101 00:06:25,680 --> 00:06:29,640 you as a manager, which makes you as a CSO and finally as ACEO 102 00:06:30,320 --> 00:06:34,400 a completely blind whether you can really fulfill your 103 00:06:34,400 --> 00:06:41,280 compliance obligations and building the umbrella on top of 104 00:06:41,280 --> 00:06:43,760 the systems is really that what helps. 105 00:06:43,760 --> 00:06:50,520 So getting the visibility across all kinds of IM vendors and 106 00:06:50,520 --> 00:06:52,840 products and across all kinds of identity. 107 00:06:53,080 --> 00:06:55,960 And not only the visibility, I think and very, very important 108 00:06:55,960 --> 00:07:01,120 part is not just to create a task list of things that are not 109 00:07:01,120 --> 00:07:05,200 looking good, but also to provide a proper remediation in 110 00:07:05,200 --> 00:07:09,440 the sense helping helping IM teams and helping business 111 00:07:09,440 --> 00:07:13,440 departments to clean up things kind of immediately with 112 00:07:13,440 --> 00:07:15,920 automated remediations. Yeah. 113 00:07:16,120 --> 00:07:18,840 I mean, ultimately that's a big part of the why, right? 114 00:07:18,840 --> 00:07:23,160 Like how can you manage what you don't, what you can't see? 115 00:07:23,160 --> 00:07:27,120 You have to be able to see it to have the ability to manage it. 116 00:07:27,840 --> 00:07:32,400 And maybe you just answered my next question already, but I've 117 00:07:32,400 --> 00:07:35,640 got to think a lot of identity practitioners start with the 118 00:07:35,640 --> 00:07:39,720 question of I've got an IGA system, I've got a Pam system, 119 00:07:40,000 --> 00:07:42,960 why can't I just do what I need with them? 120 00:07:42,960 --> 00:07:45,920 Why do I need Nexus? Do you hear that much? 121 00:07:47,680 --> 00:07:50,680 It depends to whom we are speaking, but but we hear this 122 00:07:50,680 --> 00:07:53,560 question. So I would say to those identity 123 00:07:54,040 --> 00:07:56,880 practitioners that are experienced and that who have 124 00:07:56,880 --> 00:08:00,520 done it before or kind of who have progressed and basically 125 00:08:00,520 --> 00:08:02,680 left the honeymoon face with the IGA tool. 126 00:08:03,200 --> 00:08:05,000 Most likely they have experienced. 127 00:08:05,240 --> 00:08:08,720 It's not everything polished and shiny like they have probably 128 00:08:08,720 --> 00:08:13,520 expected and then they get quite quick. 129 00:08:13,720 --> 00:08:17,480 Oh, that's the problem Nexus solving and this is the solution 130 00:08:17,480 --> 00:08:19,960 we are providing. OK, make sense, give us a demo. 131 00:08:20,280 --> 00:08:22,200 And then their understanding is quite there. 132 00:08:22,840 --> 00:08:26,000 When you're in early stage, so you're starting on a Greenfield 133 00:08:26,000 --> 00:08:30,280 approach or having something very, very old, old school, then 134 00:08:30,280 --> 00:08:34,000 people hope for sure that all the new products, their Magic 135 00:08:34,000 --> 00:08:37,919 Quadrant leaders, that they completely fulfill what they're 136 00:08:37,919 --> 00:08:41,919 expecting and, and to be fair, the large players do a good job 137 00:08:41,919 --> 00:08:43,799 as well. They have mature of the 138 00:08:44,039 --> 00:08:47,640 products, but when you are a regulated industry, you have so 139 00:08:47,640 --> 00:08:52,920 many additional add-ons like maintaining a proper segregation 140 00:08:52,920 --> 00:08:58,480 of duty implementation across a variety of system really do a 141 00:08:58,840 --> 00:09:03,120 proper access refuse and recertifications whether it's 142 00:09:03,280 --> 00:09:07,240 often direct assignment, but any policy has to be recertified at 143 00:09:07,240 --> 00:09:10,880 a certain point in time. And this is often a little bit 2 144 00:09:10,880 --> 00:09:14,680 technology focused. So it might be doable for an IM 145 00:09:14,680 --> 00:09:18,920 practitioner, but it might will both be doable for an senior 146 00:09:18,920 --> 00:09:25,000 consultant in finance, for an HR manager and this sort of non IT 147 00:09:25,040 --> 00:09:26,480 folks out there in the companies. 148 00:09:28,360 --> 00:09:32,400 So our mutual friend Rebecca Becky Archambault from Gartner 149 00:09:33,360 --> 00:09:41,080 posted recently about this IVIP space and her research that was 150 00:09:41,080 --> 00:09:45,400 recently published about IVIPI noticed that you are one of the 151 00:09:45,400 --> 00:09:49,880 first person to reply to that post and comment on that post. 152 00:09:50,080 --> 00:09:54,800 So I guess my question is, is IVIP the space that you see 153 00:09:54,800 --> 00:09:59,440 yourself in and you know, even before that, like do you feel 154 00:09:59,440 --> 00:10:04,000 like the boundaries of IVIP make sense to the practitioner? 155 00:10:05,720 --> 00:10:06,960 Absolutely. I, I would say so. 156 00:10:06,960 --> 00:10:11,600 So I really appreciate that this, this term, this box was 157 00:10:11,600 --> 00:10:16,560 coined by Becky and and the Gartner team and that discussion 158 00:10:16,560 --> 00:10:19,160 within the community started. Is it a platform? 159 00:10:19,160 --> 00:10:21,360 Is it not a platform? Is it just a bunch of 160 00:10:21,360 --> 00:10:24,800 capabilities or or? So I think what's really 161 00:10:24,800 --> 00:10:29,280 important is that there is an understanding, there is a kind 162 00:10:29,280 --> 00:10:33,040 of software, a kind of product out there that are building this 163 00:10:33,040 --> 00:10:36,880 umbrella function in order to fulfill this Better Together 164 00:10:36,880 --> 00:10:39,400 story and bring additional capabilities in. 165 00:10:39,400 --> 00:10:43,840 Some products are are missing and missing for often very good 166 00:10:43,840 --> 00:10:48,520 reasons cause larger players have to focus on on other areas 167 00:10:48,520 --> 00:10:52,080 and not going super deep for specific industries or for 168 00:10:52,080 --> 00:10:56,960 specific use cases and everything, every technology or 169 00:10:57,000 --> 00:11:00,680 every area of technology that has a name is far easier to to 170 00:11:00,680 --> 00:11:02,640 discuss. So when you do an industry 171 00:11:02,640 --> 00:11:06,800 comparison, when you do a tool selection, it's far easier if 172 00:11:06,800 --> 00:11:09,800 you have a label, if you have a name for it and say, OK, this 173 00:11:09,800 --> 00:11:12,960 kind of technology, I want to understand better, I want to 174 00:11:13,240 --> 00:11:16,080 make a deep dive. And so this helps at the end of 175 00:11:16,080 --> 00:11:19,640 the day, everyone is you have a clear label, you can do a proper 176 00:11:19,640 --> 00:11:27,280 comparison and you have an answer in the sense of of a 177 00:11:27,280 --> 00:11:29,920 legal brick. So to say that you put on top in 178 00:11:29,920 --> 00:11:34,040 your enterprise architecture and say exactly this IVIP category 179 00:11:34,400 --> 00:11:37,040 is taking care about this in my enterprise, yeah. 180 00:11:38,360 --> 00:11:44,280 What I take from what you said is that Nexus works with your 181 00:11:44,280 --> 00:11:49,280 existing investment in identity technology, which I think very 182 00:11:49,280 --> 00:11:52,600 few companies make these investments and want to walk 183 00:11:52,600 --> 00:11:56,680 away from them every few years. So buying tools that can kind of 184 00:11:56,680 --> 00:12:00,200 enhance the functionality seems to make a lot of sense. 185 00:12:01,000 --> 00:12:04,960 And I think that's a lot of what the IVIP space is about, right? 186 00:12:05,160 --> 00:12:08,920 Increasing visibility, increasing intelligence and 187 00:12:09,440 --> 00:12:14,400 adding on to the capabilities. And I'm wondering, there seems 188 00:12:14,400 --> 00:12:19,240 to be like a lot of companies that kind of their solutions 189 00:12:19,240 --> 00:12:22,640 fall into the space. How do you how does Nexus 190 00:12:22,640 --> 00:12:27,400 differentiate from the pack? Yeah, that's, that's a good 191 00:12:27,400 --> 00:12:31,320 question as well. First and foremost, I think 192 00:12:31,320 --> 00:12:36,960 you're absolutely right and that that hits the nail that IVIP or 193 00:12:36,960 --> 00:12:42,520 IVIP as others are saying, ensures and saves existing 194 00:12:42,520 --> 00:12:46,080 investments into technology. When you have rolled out an IGA 195 00:12:46,080 --> 00:12:49,160 tool, an integrated 1 1/2 thousand or 2000 application, 196 00:12:49,680 --> 00:12:54,200 nobody is really willing to RIP it out three years after and 197 00:12:54,200 --> 00:12:57,440 say, OK, we start completely from from scratch and are now 198 00:12:57,920 --> 00:13:01,040 bringing in another, another tool that's just a slightly 199 00:13:01,040 --> 00:13:03,800 better. Because at the end all the human 200 00:13:03,800 --> 00:13:06,760 related processes, all the integration processes, are they 201 00:13:06,960 --> 00:13:12,400 the cumbersome work and the work that really is creating a lot of 202 00:13:12,400 --> 00:13:16,520 effort for for integrators, for consultants, for IMM teams. 203 00:13:16,880 --> 00:13:20,120 So basically having some something there that's well 204 00:13:20,120 --> 00:13:23,960 integrated that works, where provisioning works is super 205 00:13:23,960 --> 00:13:25,800 fine. And then there are just a few 206 00:13:25,800 --> 00:13:28,760 capabilities missing. It's far, far smarter to sit 207 00:13:28,760 --> 00:13:34,560 something on on top. And coming from the enterprise 208 00:13:34,560 --> 00:13:39,600 engine, you have IGA systems and let's just PEM systems for 209 00:13:39,600 --> 00:13:43,040 example. You want to ensure SOD, you can 210 00:13:43,040 --> 00:13:47,640 figure out on how to do it or you say OK, SOD is done by Lexus 211 00:13:47,640 --> 00:13:52,120 in their IVAP space building an umbrella between IGA system and 212 00:13:52,120 --> 00:13:55,520 the PEM system and you can ensure that no one really 213 00:13:56,160 --> 00:14:01,000 conflicts with your SOD segregation of duty policies. 214 00:14:01,720 --> 00:14:05,960 What's the difference between all the vendors that that are 215 00:14:05,960 --> 00:14:10,720 there? I think IVIP or IVIP is at the 216 00:14:10,720 --> 00:14:13,640 very beginning. So it's kind of in the finding 217 00:14:13,640 --> 00:14:16,880 phase what's really included and what's really not included. 218 00:14:16,880 --> 00:14:22,560 My point is that the visibility part is a very important part of 219 00:14:22,560 --> 00:14:26,880 figuring out across all types of identities and across all 220 00:14:27,040 --> 00:14:31,560 different systems of IM building this umbrella and bringing 221 00:14:31,560 --> 00:14:34,320 visibility to the business side. That's number one. 222 00:14:34,640 --> 00:14:38,360 Number two is visibility is not enough observability. 223 00:14:38,360 --> 00:14:41,920 Like for example, Martin Kupinger, who was also a guest 224 00:14:41,920 --> 00:14:46,000 in the IDSC podcast in in the past says is important. 225 00:14:46,840 --> 00:14:49,560 I do say it's remediation. Basically we have the same 226 00:14:49,560 --> 00:14:53,080 understanding, not just creating a list of findings because 227 00:14:53,080 --> 00:14:56,840 everyone knows his mailbox or his large To Do List. 228 00:14:56,840 --> 00:14:58,360 So basically this doesn't make sense. 229 00:14:58,640 --> 00:15:03,040 Having an automated remediation for at least the most important 230 00:15:03,160 --> 00:15:07,320 findings or the kind of standard routines makes absolutely sense 231 00:15:07,360 --> 00:15:13,760 in order to get get rid, RIP off a task list list that that's 232 00:15:13,760 --> 00:15:16,680 just law at the end of the day. Yeah. 233 00:15:16,680 --> 00:15:21,520 I mean, you know, I think Martin has his finger on the pulse of, 234 00:15:21,800 --> 00:15:25,040 you know, he's got this identity fabric concept that talks about 235 00:15:25,240 --> 00:15:28,360 a lot in his presentations and to me, a spot on. 236 00:15:28,360 --> 00:15:32,120 It's like, you know, enterprises that are complex, you have tools 237 00:15:32,120 --> 00:15:35,480 all over the place, but when it comes to something like 238 00:15:35,480 --> 00:15:39,840 visibility, having tools all over the place, it's, it's not 239 00:15:39,840 --> 00:15:42,280 the solution, right? You need something to be able to 240 00:15:42,280 --> 00:15:45,640 aggregate all of that. You brought up the idea of 241 00:15:45,640 --> 00:15:48,600 segregation of duties. To me that's the perfect 242 00:15:48,600 --> 00:15:52,080 example. It's like how does somebody's 243 00:15:52,080 --> 00:15:56,880 access relate across the enterprise and all these 244 00:15:56,880 --> 00:16:00,720 different identity systems that give access to business systems 245 00:16:00,960 --> 00:16:06,680 and do those capabilities? Or do you know, within your sets 246 00:16:06,680 --> 00:16:10,560 of authorizations, do you have the ability to, you know, maybe 247 00:16:10,560 --> 00:16:14,160 it's not commit fraud in the accounting sense, but do things 248 00:16:14,160 --> 00:16:16,120 that you're not supposed to be able to do? 249 00:16:16,440 --> 00:16:20,480 How would you even have the visibility to that given, you 250 00:16:20,480 --> 00:16:23,240 know, a spattering of different tools in different places, or 251 00:16:23,240 --> 00:16:26,480 tools that really just don't show the full scope of all the 252 00:16:26,480 --> 00:16:30,120 access? App app app absolutely. 253 00:16:30,120 --> 00:16:32,120 And this, this is the, is the big challenge. 254 00:16:32,120 --> 00:16:36,760 And when you have the visibility, you're sitting on 255 00:16:36,760 --> 00:16:40,000 all the identity related data. And then the next place starting 256 00:16:40,560 --> 00:16:43,960 we, we recently released ISPN identity security posture 257 00:16:43,960 --> 00:16:48,200 management for IGA 'cause when you have all this historic data 258 00:16:48,200 --> 00:16:51,480 and then you have the current data and when you will be aware 259 00:16:51,480 --> 00:16:55,320 about the future data, you can find out is there something on 260 00:16:55,360 --> 00:16:59,880 going on that's smelly? Is there some deviation from 261 00:16:59,880 --> 00:17:03,480 what this could look like? Let's say Jim McDonald is an 262 00:17:03,480 --> 00:17:06,920 engineer and you have been an engineer in your company the 263 00:17:06,920 --> 00:17:11,040 last 10 years and out of a sudden on a Sunday you get high 264 00:17:11,040 --> 00:17:15,079 risk HR privileges. That seems not to be OK and I 265 00:17:15,079 --> 00:17:17,760 can immediately make a proper remediation. 266 00:17:18,240 --> 00:17:21,520 Some people might say, OK, that's now a corner case and 267 00:17:21,520 --> 00:17:24,920 cyber attacker is preparing Jim's account and probably it 268 00:17:24,920 --> 00:17:27,920 is, but see it from an from another angle. 269 00:17:28,640 --> 00:17:32,960 You're assigning some authorization, some some roles 270 00:17:32,960 --> 00:17:36,480 or policies to a new employee as as a manager. 271 00:17:36,760 --> 00:17:40,560 And there are, you know, in the US, in Europe and everywhere 272 00:17:40,560 --> 00:17:43,280 around the world, there are this very, very common names. 273 00:17:43,280 --> 00:17:46,240 So you have this John Smith and there are probably at large 274 00:17:46,240 --> 00:17:50,520 companies 20 or 30 John Smith and 10 of them are working in IT 275 00:17:50,680 --> 00:17:54,240 and probably in the same, same department but not in the same 276 00:17:54,240 --> 00:17:56,320 team. So the likelihood that you just 277 00:17:56,320 --> 00:17:58,400 picked the wrong is quite, quite high. 278 00:17:58,960 --> 00:18:04,360 Or giving you another example, the movers process and process 279 00:18:04,360 --> 00:18:07,560 that's quite common. You're moving from Department A 280 00:18:07,760 --> 00:18:12,720 to Department B and most of the time you have some obligations 281 00:18:12,720 --> 00:18:16,920 to fulfill for your former team at least for the next month, two 282 00:18:16,920 --> 00:18:18,920 months or for the next next quarter. 283 00:18:19,240 --> 00:18:21,000 And this is a friendly collaboration. 284 00:18:21,320 --> 00:18:23,880 So what happens? You're getting the new policies, 285 00:18:23,880 --> 00:18:26,680 the new authorization, the new roles for your new department 286 00:18:27,120 --> 00:18:32,560 and you will keep the old one. Does somebody really take care 287 00:18:32,560 --> 00:18:37,440 about that you're getting getting removed from this 288 00:18:37,440 --> 00:18:39,560 policies? Most likely not. 289 00:18:39,560 --> 00:18:45,040 So the old manager doesn't probably really care 'cause he 290 00:18:45,040 --> 00:18:48,000 has you all the time and probably he can approach you 5-5 291 00:18:48,000 --> 00:18:50,840 months in the future and ask for help and the new manager will 292 00:18:50,840 --> 00:18:54,560 probably forget it. So if you figure out, OK, that's 293 00:18:54,560 --> 00:18:59,960 an, that's a move and I apply some dynamic policies on it and 294 00:18:59,960 --> 00:19:03,600 I probably give them an, an, an end date and the rows are 295 00:19:03,600 --> 00:19:06,720 automatically disappearing or before disappearing. 296 00:19:06,720 --> 00:19:09,880 I'm asking you, hey, Jim, are you really using those 297 00:19:09,880 --> 00:19:13,680 authorizations anymore? Do you need them in the future? 298 00:19:13,680 --> 00:19:16,680 Then I can have an automated clean up across the company. 299 00:19:17,120 --> 00:19:21,080 And this sums up in a really, really large work reduction 300 00:19:21,320 --> 00:19:24,840 where managers don't have to refuse some things and confirm 301 00:19:24,840 --> 00:19:26,080 some things. They don't have a clue. 302 00:19:26,600 --> 00:19:29,840 And when I'm talking to customers or when I'm speaking 303 00:19:30,440 --> 00:19:31,720 on a conference, I always laughed. 304 00:19:31,720 --> 00:19:35,160 The example what's when you're a manager, what's the best thing 305 00:19:35,160 --> 00:19:37,320 to do when you have an access review? 306 00:19:38,120 --> 00:19:41,600 It's always saying yes. And I can tell you, I can tell 307 00:19:41,600 --> 00:19:43,920 you why. The moment you say no, you take 308 00:19:43,920 --> 00:19:48,440 something away from somebody. So you always risk that your 309 00:19:48,440 --> 00:19:50,160 team is not working properly anymore. 310 00:19:50,360 --> 00:19:53,280 And then you are the bad guy who kind of messed up the company or 311 00:19:53,280 --> 00:19:56,040 messed up the process or probably messed up an important 312 00:19:56,040 --> 00:19:59,920 delivery when you're just saying yes, that's not good from a 313 00:19:59,920 --> 00:20:02,480 security perspective and that's really bad from an IM 314 00:20:02,480 --> 00:20:05,160 perspective. But the likelihood that you are 315 00:20:05,160 --> 00:20:08,960 the guilty guy who has said yes yesterday and the company will 316 00:20:08,960 --> 00:20:12,440 be attacked tomorrow and basically you are the the guilty 317 00:20:12,440 --> 00:20:17,320 one is super, super low. So most likely the kind of best 318 00:20:17,320 --> 00:20:20,440 individual strategy is just saying, yes, you have less, less 319 00:20:20,440 --> 00:20:23,560 work, you don't have to think and everyone is up and running 320 00:20:23,560 --> 00:20:26,000 again. And from this kind of very human 321 00:20:26,000 --> 00:20:29,680 behaviour, you have to get away from and provide systems that 322 00:20:29,680 --> 00:20:33,040 are kind of incorporating the security and the safety 323 00:20:33,040 --> 00:20:38,120 mechanisms that the company is secured without kind of human 324 00:20:38,120 --> 00:20:42,920 interaction, so to say. Yeah, So interesting that, you 325 00:20:42,920 --> 00:20:45,840 know, you brought up so many different use cases that 326 00:20:45,840 --> 00:20:49,520 resonate with me. And I was trying to think of 327 00:20:49,640 --> 00:20:54,040 what is the the, the Uber use case. 328 00:20:54,280 --> 00:20:58,720 And I thought obviously large global organizations where 329 00:20:59,040 --> 00:21:02,840 there's some level of decentralization happening and 330 00:21:02,840 --> 00:21:09,400 identity systems are just by nature a little bit all over the 331 00:21:09,400 --> 00:21:12,600 place. But then I was thinking, imagine 332 00:21:12,600 --> 00:21:18,160 the private equity scenario where you have a a portfolio of 333 00:21:18,160 --> 00:21:21,960 companies and maybe you're doing some level of shared service or 334 00:21:21,960 --> 00:21:26,560 you have some people who have access across multiple companies 335 00:21:26,560 --> 00:21:28,000 and you're pulling that data back. 336 00:21:28,000 --> 00:21:30,320 I don't know. It just struck me as something 337 00:21:30,320 --> 00:21:34,160 that would be an interesting use case for this type of 338 00:21:34,920 --> 00:21:39,640 technology. One thing that you you also 339 00:21:39,640 --> 00:21:44,320 mentioned that I, you know, just I want to pick on that term 340 00:21:44,320 --> 00:21:48,520 platform for a minute and you guys you have a platform, right? 341 00:21:48,520 --> 00:21:52,720 You have multiple capabilities within the platform. 342 00:21:52,880 --> 00:21:56,160 And I was wondering if you kind of enumerate those for us so 343 00:21:56,160 --> 00:21:59,200 that we have a better understanding of what is the 344 00:21:59,200 --> 00:22:01,920 total product offering from Nexus? 345 00:22:03,800 --> 00:22:06,520 Yeah. So yes, we do have a platform, 346 00:22:06,520 --> 00:22:10,040 but I know also that some people don't like the platform term 347 00:22:10,040 --> 00:22:14,880 cause platform can be gigantic, platform can be a a bit smaller, 348 00:22:14,880 --> 00:22:16,880 a platform can be in, in, in between. 349 00:22:17,120 --> 00:22:21,360 So whether it's a platform or not, I would say it's an it's a 350 00:22:21,360 --> 00:22:24,360 great collection of capabilities that are playing together and 351 00:22:24,360 --> 00:22:28,040 creating value for customers. From an pure Nexus perspective, 352 00:22:28,040 --> 00:22:31,080 I would say it's a platform as a software product. 353 00:22:31,400 --> 00:22:34,680 From an enterprise architecture point of view, referring to the 354 00:22:34,680 --> 00:22:38,000 identity fabrics, I would say we are covering a lot of 355 00:22:38,000 --> 00:22:41,120 capabilities within the identity fabrics and then you draw the 356 00:22:41,120 --> 00:22:44,440 line around then this is this is our platform. 357 00:22:44,840 --> 00:22:48,880 So we, we've been talking about the role in authorization 358 00:22:48,880 --> 00:22:52,120 governance and the analytics piece where we help you to 359 00:22:53,080 --> 00:22:56,280 handle access refuse, probably where we incorporate AI for 360 00:22:56,280 --> 00:23:00,000 access administration, but also kind of role mining and role 361 00:23:00,720 --> 00:23:03,440 discovery in order to help businesses to kind of clean up 362 00:23:03,440 --> 00:23:05,600 the space. We, we have a very cool health 363 00:23:05,600 --> 00:23:09,160 check format that's like going to the doctor, giving them a bit 364 00:23:09,160 --> 00:23:11,760 of your blood and you get an examination later on an 365 00:23:11,760 --> 00:23:14,720 examination report. And we're telling you what's 366 00:23:14,720 --> 00:23:19,960 good, what's bad, and how you can improve within on a on a 367 00:23:19,960 --> 00:23:22,160 written road map and strategy to get better. 368 00:23:23,200 --> 00:23:26,080 That's really interesting. Can you tell me, let's hone in 369 00:23:26,080 --> 00:23:29,800 on that health check, then we'll get back to my I'm sorry to, to 370 00:23:30,240 --> 00:23:32,880 pull you all over the place, but I, you brought up the health 371 00:23:32,880 --> 00:23:37,240 check and that sounds like, OK, there's something actionable 372 00:23:37,480 --> 00:23:40,040 that people can do. Tell us more about the health 373 00:23:40,040 --> 00:23:42,040 check. Absolutely. 374 00:23:42,040 --> 00:23:45,240 And This is why I really love the the health, health tech. 375 00:23:45,560 --> 00:23:50,080 So you're a big company and normally you are having a bit of 376 00:23:50,080 --> 00:23:52,840 a feeling that your role and authorization landscape isn't 377 00:23:53,160 --> 00:23:56,880 looking that good, but you don't have really a clue to convince 378 00:23:56,880 --> 00:23:58,680 your management to get additional budget. 379 00:24:00,000 --> 00:24:03,480 Your pain is probably not documented well enough to move 380 00:24:03,480 --> 00:24:04,560 on. And this is where the health 381 00:24:04,560 --> 00:24:09,080 check comes in. You get a Nexus subscription for 382 00:24:09,080 --> 00:24:14,600 a short term of four to 8, four to 8 weeks either on SAS or as 383 00:24:14,600 --> 00:24:17,680 in a container for on Prem, which makes it sometimes a bit 384 00:24:17,680 --> 00:24:20,360 easier as you don't have to handle all the data protection 385 00:24:20,360 --> 00:24:23,640 thingies as everything stays in in in your company, especially 386 00:24:23,640 --> 00:24:27,720 for European companies. And then we help you to load in 387 00:24:27,760 --> 00:24:31,160 a copy of your production. So nobody in the company has to 388 00:24:31,160 --> 00:24:34,800 be afraid that the production environment will be messed up. 389 00:24:35,040 --> 00:24:37,760 It's then a kind of a read only snapshot and then we do the 390 00:24:37,760 --> 00:24:42,360 investigation and after we've done the investigation, there 391 00:24:42,360 --> 00:24:46,760 are two potential outcomes. Option 1, you have done an 392 00:24:46,760 --> 00:24:49,200 excellent job. Then you can't get off and 393 00:24:49,200 --> 00:24:52,360 certificate from us on how you create your authorization 394 00:24:52,360 --> 00:24:53,880 landscape. Looks like you can go to your 395 00:24:53,880 --> 00:24:57,160 boss and say, hey, I'm I'm the man, I'm your man. 396 00:24:57,640 --> 00:24:59,440 What about a pay raise or something like that? 397 00:24:59,920 --> 00:25:03,720 Unfortunately, that's very unlikely that that's very 398 00:25:03,720 --> 00:25:06,480 unlikely. So that far more likely cases 399 00:25:06,960 --> 00:25:11,000 that we have some findings, but this is good for you as well as 400 00:25:11,000 --> 00:25:15,640 an IM team or an IM practitioner manager whatsoever 'cause you 401 00:25:15,640 --> 00:25:19,800 have this documented findings. OK, we have found your IM 402 00:25:19,800 --> 00:25:23,760 landscapes looks like this. This amount of rows, this amount 403 00:25:23,760 --> 00:25:26,640 of direct assignments. Most of the time it's kind of 404 00:25:26,640 --> 00:25:31,920 quite messy to be honest, but we are not just finger pointing to 405 00:25:31,920 --> 00:25:34,000 those things that are not looking well. 406 00:25:34,440 --> 00:25:37,880 We give you also a road map on how to remediate things and how 407 00:25:37,880 --> 00:25:40,920 to improve things with a kind of effort estimation and how you 408 00:25:40,920 --> 00:25:43,880 can do it in a tool. So you're not going a bit bad 409 00:25:43,880 --> 00:25:47,000 news to your management and saying, OK, that's that's the 410 00:25:47,000 --> 00:25:49,280 bad news because nobody wants to hear bad news. 411 00:25:49,680 --> 00:25:51,320 You can go to them with a solution. 412 00:25:51,320 --> 00:25:55,200 You can say we found out that and we have now the proof that 413 00:25:55,200 --> 00:25:58,880 we have really to take action on in order to make a proper 414 00:25:58,880 --> 00:26:03,120 security within our company. And this is my plan, this is my 415 00:26:03,120 --> 00:26:05,560 strategic road map on how to get rid of it. 416 00:26:06,080 --> 00:26:09,040 And this is a very, very good starting point to have really 417 00:26:09,040 --> 00:26:13,320 this data and fact based discussion, discussion within 418 00:26:13,320 --> 00:26:16,000 the team and not a feeling where some probably have a good 419 00:26:16,000 --> 00:26:19,760 feeling and some don't have a good feeling. 420 00:26:20,720 --> 00:26:24,040 The cool thing is you can decide on your own. 421 00:26:24,040 --> 00:26:29,240 So basically whether you go ahead with us or not, the health 422 00:26:29,240 --> 00:26:32,320 check is a value on its own 'cause you have all the 423 00:26:32,320 --> 00:26:36,960 examination results there, you have an road map there, what you 424 00:26:36,960 --> 00:26:40,920 can improve. So you can use this, this all 425 00:26:40,920 --> 00:26:45,280 this information for improving your, your landscape. 426 00:26:45,480 --> 00:26:48,680 Enemy. I, I always compare it to real 427 00:26:48,680 --> 00:26:50,760 doctor. So you go to the real doctor and 428 00:26:50,880 --> 00:26:53,720 they take your blood and they examine your body and probably 429 00:26:53,720 --> 00:26:57,680 they will say, Haiko, you're a little bit too heavy for your 430 00:26:57,680 --> 00:27:00,480 size. You can probably eat a little 431 00:27:00,480 --> 00:27:03,640 bit less fat and do a little bit more better nutrition, what 432 00:27:03,640 --> 00:27:07,200 whatsoever. But after that, I can decide on 433 00:27:07,200 --> 00:27:09,640 my own. Do I change my behaviour? 434 00:27:09,640 --> 00:27:12,040 Will I increase my sport activities? 435 00:27:12,040 --> 00:27:14,200 Will I change what I'm eating, something like that? 436 00:27:14,520 --> 00:27:16,760 Or am I fine with it? So I'm not forced with the 437 00:27:16,760 --> 00:27:20,080 results from the doctor nor our customers with the results from 438 00:27:20,080 --> 00:27:24,480 our health check. OK, so you might have said it 439 00:27:24,480 --> 00:27:27,440 but I and maybe I missed it. What is the charge to do the 440 00:27:27,440 --> 00:27:29,880 health check? How much do I have to get 441 00:27:29,880 --> 00:27:34,680 approved to pay you for this? That that's a good question. 442 00:27:34,680 --> 00:27:37,840 So it depends on the number of identities and the company size. 443 00:27:38,800 --> 00:27:43,640 Basically it's an always an individual offer. 444 00:27:43,640 --> 00:27:48,320 But let me say this, for most of the companies, it's it's 445 00:27:48,320 --> 00:27:51,640 something which can go either directly below a procurement 446 00:27:51,640 --> 00:27:55,000 level or short, short above. So it's ideally for the end of 447 00:27:55,000 --> 00:27:56,480 the year. Now it's November. 448 00:27:57,240 --> 00:28:02,000 So if you're looking for a last term activity, the Nexus hedge 449 00:28:02,000 --> 00:28:06,200 check that hits the nail. OK, that's good to know. 450 00:28:06,200 --> 00:28:09,800 That's something that I think everybody should look into it 451 00:28:09,800 --> 00:28:15,840 again, kind of go to nexus-secure.com/I DACI think 452 00:28:15,840 --> 00:28:18,680 the information on the health check will be there. 453 00:28:19,960 --> 00:28:24,760 Heiko, you, I so rudely interrupted you as you were kind 454 00:28:24,760 --> 00:28:27,800 of describing the platform. I want to give you an 455 00:28:27,800 --> 00:28:29,640 opportunity to pick up where you left off. 456 00:28:29,640 --> 00:28:33,600 And I'm sitting here thinking you had mentioned the ISPMPS 457 00:28:33,920 --> 00:28:36,520 earlier. I know you're going to save the 458 00:28:36,520 --> 00:28:38,560 best for last, right? That's something I'm very 459 00:28:38,560 --> 00:28:40,200 interested in hearing about as well. 460 00:28:41,880 --> 00:28:46,320 So yeah, I, I already elaborated a bit on on ISPN. 461 00:28:46,320 --> 00:28:50,280 What I really love within the ISPN is the license killer, 462 00:28:52,520 --> 00:28:55,600 which is probably something you don't expect with an IM. 463 00:28:56,840 --> 00:28:58,760 Why did we come to the license killer? 464 00:28:58,760 --> 00:29:04,480 So we, we've started with ISPN that the one thing is assigning 465 00:29:04,480 --> 00:29:09,320 you, whether it's dynamic or static policies for things you 466 00:29:09,320 --> 00:29:14,200 are allowed to do that's good. But when you're not using 467 00:29:14,200 --> 00:29:18,480 things, you should lose it. So use it or lose it as the 468 00:29:18,480 --> 00:29:22,480 saying saying goes. And from that we said, OK, it 469 00:29:22,520 --> 00:29:26,560 makes absolutely sense to figure out is an identity using the 470 00:29:26,560 --> 00:29:29,080 authorizations the identity has been given. 471 00:29:29,760 --> 00:29:31,720 Course, when not I can reduce it. 472 00:29:31,720 --> 00:29:34,520 And then basically I'm following the principle of least privilege 473 00:29:34,520 --> 00:29:41,240 on the one hand and reduce my security exposure out out there. 474 00:29:42,400 --> 00:29:44,960 For a couple of systems, this works very well. 475 00:29:44,960 --> 00:29:47,120 That's Microsoft, enter ID governance. 476 00:29:47,120 --> 00:29:52,040 That's SAP in the cloud as well as all three and all those 477 00:29:52,040 --> 00:29:56,200 systems that provide us the data directly or whether with an 478 00:29:56,200 --> 00:29:58,600 access to the scene. There are applications out there 479 00:29:58,600 --> 00:30:02,360 to be honest that just don't have information who's actually 480 00:30:02,640 --> 00:30:06,400 using what in my application. But given that you can provide 481 00:30:06,400 --> 00:30:10,960 us the data, we can ensure that we kind of cut down your 482 00:30:10,960 --> 00:30:14,080 privileges, cut down your authorizations to the number 483 00:30:14,280 --> 00:30:17,120 you're really using, which makes it easier. 484 00:30:17,120 --> 00:30:20,680 And the less direct assignments you have, the better it is for 485 00:30:20,680 --> 00:30:23,720 everyone. And then they come to the to 486 00:30:23,720 --> 00:30:27,040 thinking, what does it mean if it goes down to zero? 487 00:30:27,640 --> 00:30:29,480 You're not using the system at all. 488 00:30:29,880 --> 00:30:33,480 And imagine a large enterprise with 100K or 200K employees. 489 00:30:33,760 --> 00:30:36,440 How many employees have subscribed for this cloud 490 00:30:36,440 --> 00:30:40,440 service, for this Microsoft add on for this kind of stuff and 491 00:30:40,440 --> 00:30:44,560 this kind of stuff and not using it, but also not giving it back. 492 00:30:44,560 --> 00:30:47,640 So have you ever heard someone approaching an IT team and 493 00:30:47,640 --> 00:30:50,840 saying oh I have too much software, I have too much 494 00:30:50,840 --> 00:30:53,640 privileges, please, please take it back. 495 00:30:53,640 --> 00:30:57,440 So having is better than needing and this is the principle most 496 00:30:57,440 --> 00:31:01,640 most employees are are working. So when we figure out there is 497 00:31:01,640 --> 00:31:06,880 nothing left, we can remove you at all from the application, 498 00:31:07,120 --> 00:31:08,840 which means we can give a license back. 499 00:31:09,400 --> 00:31:14,160 And when you trusted the math with 100K or 200K headcount 500 00:31:14,160 --> 00:31:17,920 company and we have just a fraction of those people that 501 00:31:17,920 --> 00:31:22,520 are not using a certain SAS service Salesforce license or 502 00:31:22,520 --> 00:31:26,400 something like that, it sums up in an into enormous amount. 503 00:31:26,400 --> 00:31:29,600 And so this is really cool. And then we presented it to our 504 00:31:29,600 --> 00:31:32,600 customers and also where we have this kind of discussions with 505 00:31:32,600 --> 00:31:36,320 them when in the, during the signing phase, we've learnt that 506 00:31:36,360 --> 00:31:39,400 so many IM teams are approached by license management. 507 00:31:39,400 --> 00:31:43,680 So can you tell us about how people are using the software 508 00:31:43,680 --> 00:31:47,760 your IM, you're giving all this kind of access thing is, can you 509 00:31:47,760 --> 00:31:49,800 tell us more? And most of the time they have 510 00:31:49,800 --> 00:31:53,360 been suffering and at the end they have to say, oh, no, sorry, 511 00:31:53,360 --> 00:31:57,480 we can't. And you're now kind of kind of 512 00:31:57,480 --> 00:32:03,240 covering this, this white spot and helping customers to follow 513 00:32:03,240 --> 00:32:05,920 the principle of these privileges on the one hand and 514 00:32:05,920 --> 00:32:08,120 on the other hand, saving costs at the same time. 515 00:32:09,880 --> 00:32:15,200 I think he gave a really good overview in like the why of 516 00:32:16,400 --> 00:32:21,440 Nexus and kind of like how you get the value. 517 00:32:21,920 --> 00:32:25,400 Now I'm going to talk about the how in terms of like how it 518 00:32:25,440 --> 00:32:29,520 actually worked, because you talked a little bit about how it 519 00:32:29,520 --> 00:32:35,400 sits on top of an IGA system. It sounds to me like it 520 00:32:35,400 --> 00:32:38,960 leverages a lot of the data that's in the IGA system. 521 00:32:39,280 --> 00:32:43,240 The idea is then to provide managers with the information 522 00:32:43,240 --> 00:32:47,080 they need so they can make good decisions during an access 523 00:32:47,360 --> 00:32:52,280 review campaign, for example. I'm also wondering, is there 524 00:32:52,280 --> 00:32:55,840 some kind of, so you're pulling data from the IGA system? 525 00:32:55,840 --> 00:32:59,240 Are you pushing data back into the IGA system? 526 00:32:59,480 --> 00:33:03,240 Going to talk to me a little bit about how that whole process 527 00:33:03,240 --> 00:33:06,000 works. Absolutely. 528 00:33:07,000 --> 00:33:10,520 You described it very well. So we're sitting on top on those 529 00:33:10,520 --> 00:33:18,200 IM systems, a lot of IHIGH systems where we have very, very 530 00:33:18,200 --> 00:33:21,680 mature connectors, certified connectors reading the data 531 00:33:21,680 --> 00:33:25,640 route and writing the data back. So when we are changing 532 00:33:25,640 --> 00:33:28,240 something, we can write it back at the same time, which is 533 00:33:28,240 --> 00:33:31,360 important because otherwise you can't do any improvements or 534 00:33:31,360 --> 00:33:34,920 remediations then you are trust on kind of read only system. 535 00:33:35,840 --> 00:33:39,600 So, so to say the advantage is that companies save their 536 00:33:39,600 --> 00:33:43,480 investment, they have kind of rolled out say .1 identity or so 537 00:33:43,880 --> 00:33:47,720 then all the integration. So it doesn't make sense to do 538 00:33:47,720 --> 00:33:50,600 it again with Texas. So when we are sitting top of 539 00:33:50,600 --> 00:33:54,560 them reading out the data and kind of providing it back is 540 00:33:54,560 --> 00:33:58,960 quicker for us, a shorter time to value for the customer and 541 00:33:58,960 --> 00:34:03,760 saving a lot of integration, integration efforts when rolling 542 00:34:03,760 --> 00:34:07,320 out new applications. It's always the question, so how 543 00:34:07,320 --> 00:34:11,280 do we do onboard now an application into my IGA system? 544 00:34:11,280 --> 00:34:14,280 And this is where our application onboarding comes 545 00:34:14,280 --> 00:34:18,040 into play where we have this kind of very, very structured 546 00:34:18,040 --> 00:34:22,080 process to collect all this data that's needed for doing a proper 547 00:34:22,080 --> 00:34:26,040 integration into say .1 Identity, Savient, you name it. 548 00:34:26,040 --> 00:34:28,000 Why? Why is that important when 549 00:34:28,000 --> 00:34:31,400 you're talking to IGA practitioners and you have 550 00:34:31,400 --> 00:34:34,800 probably done it so many times in the past, they are suffering 551 00:34:34,800 --> 00:34:38,239 all with speed of application onboarding and with costs. 552 00:34:38,960 --> 00:34:42,840 Coming back to a very, very simple example, doing the math, 553 00:34:43,199 --> 00:34:47,320 you have two and a half thousand applications and you want to 554 00:34:47,320 --> 00:34:50,239 onboard this 2 1/2 thousand applications. 555 00:34:50,800 --> 00:34:54,639 And it takes just one day for doing a bit of conversation with 556 00:34:54,639 --> 00:34:58,200 the application owner, sending him documentation, asking for 557 00:34:58,200 --> 00:35:01,600 documentation back for some technical settings, but also for 558 00:35:01,600 --> 00:35:04,680 business settings. In Europe, for example, there is 559 00:35:04,680 --> 00:35:07,720 an finance regulation called Dora, the Digital Operations 560 00:35:08,040 --> 00:35:12,160 Resilience Act, which requires regulated companies such as 561 00:35:12,160 --> 00:35:15,960 banks and insurance companies to do a proper documentation about 562 00:35:15,960 --> 00:35:18,600 SOD recertification cycles and this kind of stuff. 563 00:35:18,960 --> 00:35:21,920 So it's a lot of things you have to collect and incorporate 564 00:35:21,920 --> 00:35:24,240 somehow. And we've glued that into a 565 00:35:24,240 --> 00:35:26,760 product. And now imagine you're doing 566 00:35:26,760 --> 00:35:30,960 this 2 1/2 thousand time one day and you apply a Trulia 567 00:35:30,960 --> 00:35:34,600 consultant and for the sake of simplicity, just let's say it's 568 00:35:34,600 --> 00:35:37,080 $1000 a day, that the math is easy. 569 00:35:37,080 --> 00:35:40,240 Then we're ending up with two and a half, $1,000,000. 570 00:35:40,640 --> 00:35:45,600 A Trulia consultant is just asking people in the enterprise, 571 00:35:45,600 --> 00:35:47,040 hey, can you give me this information? 572 00:35:47,400 --> 00:35:50,880 And probably they won't react. They're giving you kind of 573 00:35:52,480 --> 00:35:55,360 information in the format of choice, but not in the format 574 00:35:55,360 --> 00:35:58,720 you can can really eat. And our streamlined process 575 00:35:58,720 --> 00:36:03,160 helps exactly to to go there and kind of reduce the workload. 576 00:36:03,480 --> 00:36:06,880 And at the end of the day, you have this kind of collected set 577 00:36:06,880 --> 00:36:12,080 of information in order to either use the IGA soft IGA 578 00:36:12,080 --> 00:36:16,000 software application onboarding tool that does all the kind of 579 00:36:16,000 --> 00:36:19,480 connect the configuration or when you're working with an SI 580 00:36:19,480 --> 00:36:22,760 or a managed services provider, they have often built their own 581 00:36:22,760 --> 00:36:26,560 procedures on how do those to do those things very, very quickly. 582 00:36:26,880 --> 00:36:30,280 You can use all the data you have collected with us, throw it 583 00:36:30,280 --> 00:36:34,160 into these tools and kind of doing quicker on onboarding with 584 00:36:34,160 --> 00:36:36,840 the sake of speeding up enormously. 585 00:36:38,240 --> 00:36:41,360 One of the things that you've done throughout this episode is 586 00:36:41,520 --> 00:36:45,320 really done a good job of kind of sprinkling examples 587 00:36:45,560 --> 00:36:47,680 throughout. And one of the questions we 588 00:36:47,680 --> 00:36:53,760 always like to ask our sponsors is how do customers show value 589 00:36:54,400 --> 00:36:59,600 or how do they measure the value they're getting from the Nexus 590 00:36:59,600 --> 00:37:03,080 solution so they can communicate upward. 591 00:37:03,520 --> 00:37:06,520 You know, hey, this is the difference it's making. 592 00:37:06,680 --> 00:37:08,640 This is why it's worth the investment. 593 00:37:10,040 --> 00:37:13,560 Maybe you can kind of answer that question and again kind of 594 00:37:13,560 --> 00:37:18,680 give some examples where you've seen your clients be able to do 595 00:37:18,680 --> 00:37:21,960 that. Yeah, it's. 596 00:37:21,960 --> 00:37:25,200 It's very manifold and very specific for the use case of 597 00:37:25,200 --> 00:37:28,240 what a success look like and also a bit related to the 598 00:37:28,240 --> 00:37:31,840 customer for sure. But let me pick the example of 599 00:37:32,920 --> 00:37:37,440 excess refuse or policy refuse for recertification by for 600 00:37:37,440 --> 00:37:40,720 regulated companies that have, this is a is a thing that you 601 00:37:40,720 --> 00:37:43,600 have to do regularly, whether you like it or dislike it. 602 00:37:43,960 --> 00:37:48,520 And most of the time this is one of the, let's say, Halloween 603 00:37:48,520 --> 00:37:51,480 month or horror month for the IGA teams. 604 00:37:51,480 --> 00:37:53,920 They have to prepare everything. They're reaching out to the 605 00:37:53,920 --> 00:37:57,000 business departments and everyone has to give feedback 606 00:37:57,000 --> 00:38:01,440 within 3 or 4 weeks to kind of finish your initiative. 607 00:38:02,200 --> 00:38:07,120 And so one very important KPI for them is have things kind of 608 00:38:07,120 --> 00:38:13,800 speed up and especially has the number of manual assignments 609 00:38:14,160 --> 00:38:17,720 being reduced significantly. So when you can assign a lot of 610 00:38:17,720 --> 00:38:21,800 authorizations via birthrights, via dynamic policies, I had 611 00:38:21,800 --> 00:38:25,000 earlier the example that your assignments run out 612 00:38:25,000 --> 00:38:28,240 automatically after 1/4 for example, or after you changed 613 00:38:28,240 --> 00:38:31,720 your organizational unit, something like that, You don't 614 00:38:31,720 --> 00:38:34,720 need that many certifications anymore recertifications 615 00:38:34,720 --> 00:38:37,880 anymore. So the workload is significantly 616 00:38:37,960 --> 00:38:41,240 reduced. And this is some KPI to measure. 617 00:38:41,640 --> 00:38:46,520 Another thing is we had a customer also of finance 618 00:38:46,520 --> 00:38:51,320 institute, they wanted to put everything into business roles. 619 00:38:51,480 --> 00:38:54,880 So no individual assignment of entitlements or so. 620 00:38:55,280 --> 00:38:59,320 And they had a big initiative and basically they succeeded to 621 00:38:59,320 --> 00:39:02,080 do it that that way. And all those things you can put 622 00:39:02,080 --> 00:39:06,120 on your KPIs and really measure whether you have been successful 623 00:39:06,160 --> 00:39:09,320 or not. As my last example, I was 624 00:39:09,320 --> 00:39:12,080 talking about application on boarding or the authorization 625 00:39:12,080 --> 00:39:14,840 concept. And this is exactly the way 626 00:39:15,520 --> 00:39:18,200 imagine for the authorization concept where you have to a 627 00:39:18,200 --> 00:39:23,040 written documentation about your policies about refuse cycles and 628 00:39:23,040 --> 00:39:26,760 so on. And you have to do this for 2 629 00:39:26,760 --> 00:39:30,160 1/2 thousand, 1000 or even just 500 applications. 630 00:39:30,960 --> 00:39:34,560 And you know, the tool of choice for so many people is Microsoft 631 00:39:34,560 --> 00:39:36,800 Word and Microsoft Microsoft Excel. 632 00:39:36,800 --> 00:39:42,080 It's a super flexible tool. You can do everything, but you 633 00:39:42,080 --> 00:39:44,280 have boundaries quite, quite early. 634 00:39:44,600 --> 00:39:48,400 So you're starting and at the moment you're you're ready, your 635 00:39:48,400 --> 00:39:51,280 documents are outdated because your system landscape has 636 00:39:51,520 --> 00:39:54,560 changed. Back in time 20 years ago when 637 00:39:54,560 --> 00:39:58,120 everyone was doing waterfall and then there was probably 4 638 00:39:58,120 --> 00:40:02,080 releases or three releases a year, you might have been able 639 00:40:02,080 --> 00:40:05,120 to kind of align updating your documentation with that release. 640 00:40:05,640 --> 00:40:07,640 Now everyone works in an HR mode. 641 00:40:07,640 --> 00:40:12,680 HR teams are continuously releasing and every basically 642 00:40:12,680 --> 00:40:17,800 everyday something is changing in an enterprise IT landscape. 643 00:40:18,080 --> 00:40:21,360 And so it's an never ending story and it's a nightmare. 644 00:40:21,800 --> 00:40:26,000 Imagine you have now a system that basically gives you an 645 00:40:26,000 --> 00:40:28,880 audit when a non compliant situation pops up. 646 00:40:29,280 --> 00:40:32,840 So you can measure this documentation is not compliant 647 00:40:32,840 --> 00:40:36,000 anymore. You get a red traffic light. 648 00:40:36,040 --> 00:40:39,440 You can work on it and kind of move back into a compliance mode 649 00:40:39,440 --> 00:40:44,000 and reduce the time of being not able to have your proper proof 650 00:40:44,000 --> 00:40:49,880 of audits that you have to show up to the to the auditor, for 651 00:40:49,880 --> 00:40:51,680 example. Yeah, of course. 652 00:40:51,800 --> 00:40:55,160 So I want to shift the conversation a little bit. 653 00:40:55,160 --> 00:40:59,240 And we always have one question. I I feel like if we finish this 654 00:40:59,240 --> 00:41:03,920 episode and I don't ask a question, I'll be I'll feel like 655 00:41:03,920 --> 00:41:06,280 I missed out. So how did you come up with the 656 00:41:06,280 --> 00:41:10,240 name Nexus? And it's NEXIS. 657 00:41:11,400 --> 00:41:15,560 Yeah, so I didn't came up. So the founder of Nexus and my 658 00:41:15,560 --> 00:41:19,880 successor Ludwig Ludwig folks who did also his PhD by the way, 659 00:41:19,880 --> 00:41:23,760 at the same university in in Regensburg, which is Munich 660 00:41:23,760 --> 00:41:28,040 metropolitan area. And I started the business and 661 00:41:28,040 --> 00:41:32,320 had to look for a company name. And this is at least what he, 662 00:41:32,320 --> 00:41:36,480 he, he told me all the the scientists and they do have a 663 00:41:36,480 --> 00:41:39,680 research project. They are inventing this funny 664 00:41:39,680 --> 00:41:45,000 names, approvating some things and sometimes the approvation is 665 00:41:45,000 --> 00:41:47,680 a match and sometimes it's not a match. 666 00:41:48,040 --> 00:41:52,000 And so basically it was Next Generation Information Security 667 00:41:52,400 --> 00:41:55,640 Systems and now you get it. There is no Qi in Nexus. 668 00:41:56,440 --> 00:41:59,640 But anyway, that's some kind of scientific work play. 669 00:42:00,000 --> 00:42:04,040 Originally it was Next Generation Information Security 670 00:42:04,040 --> 00:42:08,520 Systems, now it's Nexus and as I said, NEXIS. 671 00:42:09,600 --> 00:42:10,880 I love it. That's great. 672 00:42:11,160 --> 00:42:15,840 So you mentioned also Munich, is that in Germany where you are 673 00:42:16,200 --> 00:42:19,400 headquartered? So we were headquartered in 674 00:42:19,400 --> 00:42:22,960 Regensburg, which is an old medieval city going back to the 675 00:42:23,240 --> 00:42:28,480 to the Romans, which is 100 kilometers north of Munich where 676 00:42:28,480 --> 00:42:30,840 I'm living. So it's Munich metropolitan 677 00:42:30,840 --> 00:42:35,080 region from AUS perspective. Perspective, it's just a suburb 678 00:42:35,080 --> 00:42:38,200 of Munich, so to say. You know, as you're talking 679 00:42:38,200 --> 00:42:41,160 about the solution today and kept thinking to myself like 680 00:42:41,600 --> 00:42:46,880 this is needed by pretty much every organization that is of 681 00:42:46,880 --> 00:42:54,160 any kind of that is sizable. Is the solution focused on the 682 00:42:54,160 --> 00:42:57,720 European Union or is it applicable? 683 00:42:57,800 --> 00:43:03,160 Do you basically market your product to the United States and 684 00:43:03,160 --> 00:43:07,960 Canada or what are the limitations in terms of what 685 00:43:07,960 --> 00:43:13,720 geographies should cover today? So basically it fits for 686 00:43:14,160 --> 00:43:16,800 customers around the globe. That's the important message. 687 00:43:17,400 --> 00:43:23,040 And then I started back at Nexus beginning of the year, I did a 688 00:43:23,040 --> 00:43:25,960 lot of travelling, meeting a lot of people also in the US 689 00:43:25,960 --> 00:43:30,040 attended various conferences, was talking to customers, was 690 00:43:30,040 --> 00:43:33,160 talking to systems integrators also to get my own perspective 691 00:43:33,160 --> 00:43:35,120 on what they are, are, are are saying. 692 00:43:35,320 --> 00:43:39,000 And it's absolutely clear, as you said, it's, it's a match for 693 00:43:39,000 --> 00:43:42,960 US customers, for North American customers, for Europeans and for 694 00:43:42,960 --> 00:43:45,960 APG customers. So for customers around the 695 00:43:45,960 --> 00:43:50,720 world, our our roots have been determined Truman speaking 696 00:43:50,720 --> 00:43:54,120 region as Nexus was and this is probably a story that's 697 00:43:54,120 --> 00:43:57,480 different to so many of your guests here in the podcast. 698 00:43:58,040 --> 00:44:00,600 Nexus was not an NBC based company. 699 00:44:01,160 --> 00:44:06,480 It was bootstrapped without any money and kind of running up and 700 00:44:07,360 --> 00:44:11,640 by Ludwig, Michael Matthias and and and the team, which is a 701 00:44:11,720 --> 00:44:16,280 great success story being there 15 years and the market and 702 00:44:16,520 --> 00:44:21,360 having done you think becoming mentioned that Gardner without 703 00:44:21,360 --> 00:44:23,880 getting a big load of money where you can invest in the 704 00:44:23,880 --> 00:44:25,880 product. On the other side when you do 705 00:44:25,880 --> 00:44:31,440 so, you don't have this really big sums for GTM for sales and 706 00:44:31,440 --> 00:44:34,680 marketing to kind of pop offices around the globe. 707 00:44:34,680 --> 00:44:38,440 This was not done in the past, but the team started two years 708 00:44:38,440 --> 00:44:41,560 before forever starting three years to kind of professionalize 709 00:44:42,160 --> 00:44:47,000 all all this scale or to prepare the scale up phase, so to say 710 00:44:47,240 --> 00:44:51,720 hiring, marketing, hiring sales and approaching the global 711 00:44:51,720 --> 00:44:54,160 market. And now we've get probably an 712 00:44:54,360 --> 00:44:59,120 extra traction on on on top of it scaling across Europe and 713 00:44:59,120 --> 00:45:03,960 talking to US customers as well, those who are listening and 714 00:45:04,320 --> 00:45:07,200 those who will be attending. Gardner, I am in Dallas. 715 00:45:07,400 --> 00:45:08,640 Michael and I will be there as well. 716 00:45:08,640 --> 00:45:11,920 And we're more than happy to meet or having a coffee without 717 00:45:11,920 --> 00:45:17,600 any sales talk, but just from an identity enthusiast perspective. 718 00:45:17,600 --> 00:45:20,920 So it's always great to talk to identity people. 719 00:45:21,720 --> 00:45:25,320 Yeah, I saw that you had that on your LinkedIn bio or your title 720 00:45:25,560 --> 00:45:27,720 identity enthusiast, and I'd love that. 721 00:45:27,720 --> 00:45:31,320 You know, I, I put on their identity practitioner because 722 00:45:31,520 --> 00:45:35,320 that's how I see what I do professionally as like I'm 723 00:45:35,320 --> 00:45:40,160 writing the game with folks who are doing it on a day-to-day 724 00:45:40,160 --> 00:45:42,240 basis. And I am as well from a 725 00:45:42,240 --> 00:45:46,000 consulting perspective. But I just look at us as we're 726 00:45:46,000 --> 00:45:50,000 all fighting the same battle. You mentioned conferences. 727 00:45:50,360 --> 00:45:53,800 You and I spent some time together at Eici think that's a 728 00:45:53,800 --> 00:45:56,360 fantastic conference. I did want to bring up the 729 00:45:56,360 --> 00:45:59,800 Gartner conference. So if people want to reach out 730 00:45:59,800 --> 00:46:03,680 to you to meet you at any of these conferences, what's the 731 00:46:03,680 --> 00:46:07,040 best way to do that? What's the best way to do so? 732 00:46:07,200 --> 00:46:10,000 Either drop me on a message on LinkedIn. 733 00:46:10,320 --> 00:46:15,240 I'm the only haiku cloud out there, so I'm quite easy to to 734 00:46:15,600 --> 00:46:18,240 to to find. We can put the schedule link or 735 00:46:18,240 --> 00:46:23,560 a contact link on nexusminusck.com/idic as well, 736 00:46:24,040 --> 00:46:28,840 so that's probably the easiest way to to reach out to me. 737 00:46:29,640 --> 00:46:33,080 Yeah, that's fantastic. And I know you're somebody who 738 00:46:33,560 --> 00:46:36,680 is like a kind of an open network or so anybody who's kind 739 00:46:36,680 --> 00:46:39,920 of in our industry, if they connect to you on LinkedIn, 740 00:46:40,240 --> 00:46:43,040 you're always open to those kind of conversations. 741 00:46:44,120 --> 00:46:47,000 The one thing that we like to do kind of our tradition around 742 00:46:47,000 --> 00:46:49,640 here is to always end on a lighter note. 743 00:46:49,920 --> 00:46:52,320 And I've been to Germany a few Times Now. 744 00:46:52,320 --> 00:46:55,800 I've been to Frankfurt and I've been to Berlin. 745 00:46:56,000 --> 00:47:00,760 I've never been to Munich, but putting all that aside, I want 746 00:47:00,760 --> 00:47:05,840 to know from you, what is the thing in Germany or the place in 747 00:47:05,840 --> 00:47:08,480 Germany that people should visit? 748 00:47:11,600 --> 00:47:15,040 I would say that's for sure Nexus headquarter, Reddis Bone 749 00:47:15,480 --> 00:47:19,240 at the Danube River and and Munich and I can tell tell you 750 00:47:19,320 --> 00:47:23,040 tell you why. So Munich is a great, great, 751 00:47:23,280 --> 00:47:26,000 great city, the right size, very international. 752 00:47:26,960 --> 00:47:31,640 We do host Oktoberfest, which is a great event for so many people 753 00:47:31,640 --> 00:47:36,360 out there and it has the right location within Germany, so it's 754 00:47:37,000 --> 00:47:39,560 a short way to the Alps, to the mountains for those who like 755 00:47:39,560 --> 00:47:42,720 hiking. It's not that far to Italy, 756 00:47:43,040 --> 00:47:47,480 where you can go either to the sea or enjoy the mountains as 757 00:47:47,480 --> 00:47:49,440 well. It's a little bit more up into 758 00:47:49,440 --> 00:47:55,320 the north to the North Sea and Baltic Sea, but it's a very 759 00:47:55,320 --> 00:48:00,040 lovely place and why it's Ratisbone, Ringsburg, our our 760 00:48:00,040 --> 00:48:03,440 headquarter, not just because it's it's Nexus head 761 00:48:03,440 --> 00:48:06,560 headquarter, but you're more than welcome to visit us in case 762 00:48:07,840 --> 00:48:11,760 you are you're doing some tourist stuff stuff there. 763 00:48:12,080 --> 00:48:16,160 It's an old mediable city going back to the Roman times. 764 00:48:16,160 --> 00:48:21,120 That was my my friend Andrea Rossi from your mount visitors 765 00:48:21,120 --> 00:48:26,800 us just a few weeks ago during our customer custom event and 766 00:48:26,800 --> 00:48:30,680 the summertime as well. And it's feels like an Italian 767 00:48:30,680 --> 00:48:36,040 city and all the things that are looking like they are old, 506 768 00:48:36,040 --> 00:48:37,560 hundred years, they are really old. 769 00:48:37,880 --> 00:48:43,840 So for especially for Americans that know very very new and 770 00:48:43,840 --> 00:48:49,760 modern city with with a great skyline, Ringsburg is probably 771 00:48:49,840 --> 00:48:53,760 the opposite, being there in an in a time machine experiencing 772 00:48:53,760 --> 00:48:57,280 an old medada diversity that was not destroyed during the war. 773 00:48:58,080 --> 00:49:03,080 Yeah, that sounds really great. So Andrea visited it sounds like 774 00:49:03,080 --> 00:49:06,960 right around Oktoberfest, right? I mean, that's the time to come 775 00:49:06,960 --> 00:49:11,240 to Munich and well, I think that's it's either the time to 776 00:49:11,240 --> 00:49:13,960 come or the time to avoid What what do you say? 777 00:49:15,120 --> 00:49:19,400 So I like Oktoberfest very much. So I would would say it's the 778 00:49:19,400 --> 00:49:23,080 right time to to come back. Prices are are high for for 779 00:49:23,080 --> 00:49:27,920 example, and you have to take care to kind of adopt your 780 00:49:28,440 --> 00:49:32,160 drinking to Oktoberfest style in the sense the beer is larger and 781 00:49:32,160 --> 00:49:35,080 the beer is stronger. So most likely you can't drink 782 00:49:35,320 --> 00:49:38,640 as you're used at home and have to slow down a bit to be fit for 783 00:49:38,640 --> 00:49:40,360 the next day of Oktoberfest as well. 784 00:49:40,720 --> 00:49:44,600 But if Oktoberfest doesn't work out, then Oktoberfest is at the 785 00:49:44,600 --> 00:49:48,120 end of day of September, which is off my voice friend and a 786 00:49:48,120 --> 00:49:51,560 trap. The summertime is is really 787 00:49:51,560 --> 00:49:53,600 nice. So in end of September it's 788 00:49:53,600 --> 00:49:57,880 getting already cold, but in July, August the temperatures 789 00:49:57,880 --> 00:50:01,840 are quite high and nice and it's not as hot as in other places 790 00:50:01,840 --> 00:50:06,160 where you can't go out without any AC or so. 791 00:50:06,400 --> 00:50:09,760 This is a great time for visiting both Leesburg and and 792 00:50:09,760 --> 00:50:12,200 Munich. You know, it sounds like very 793 00:50:12,200 --> 00:50:17,000 wise advice and hopefully we all get an opportunity to take you 794 00:50:17,000 --> 00:50:19,360 up on that and come over and visit. 795 00:50:20,560 --> 00:50:24,240 Was there anything else FICO that you'd like to leave as kind 796 00:50:24,240 --> 00:50:28,080 of like parting advice or parting words for the identity 797 00:50:28,080 --> 00:50:31,320 practitioners who are just learning about Nexus and what 798 00:50:31,320 --> 00:50:37,280 you do? So there is a new report out 799 00:50:37,280 --> 00:50:41,800 there fresh from the press from Martin, not from Martin 800 00:50:41,800 --> 00:50:45,880 Kupinger, but from Copinger Coal analysts, from the analyst 801 00:50:45,880 --> 00:50:47,920 literature and executive view on Nexus. 802 00:50:48,200 --> 00:50:53,320 We'll put it up to the Nexus minor seeker.com slash idic 803 00:50:53,320 --> 00:50:56,120 website as well, which is a great read. 804 00:50:56,120 --> 00:50:59,280 Basically what we've been talking about today written from 805 00:50:59,280 --> 00:51:02,640 the analyst perspective in three to four pages. 806 00:51:02,640 --> 00:51:06,040 So it's a quick read when you're commuting or when you have just 807 00:51:06,040 --> 00:51:08,640 a free, a couple of free minutes to to work through. 808 00:51:09,000 --> 00:51:11,040 I think that's that's really great. 809 00:51:11,480 --> 00:51:15,000 Otherwise, I said I'm regularly attending a variety of 810 00:51:15,000 --> 00:51:17,080 conferences. I'm attending identity as well. 811 00:51:17,440 --> 00:51:21,960 And Enrique, our joint friend is organizing one very, very likely 812 00:51:22,440 --> 00:51:24,360 for Gartner. I am as as well. 813 00:51:25,240 --> 00:51:30,520 So be there if you see me, if you recognize us, say hello, 814 00:51:30,800 --> 00:51:32,840 hello. And I'm more than happy to have 815 00:51:32,840 --> 00:51:36,160 and and chat, whether it's about identity or any other topic 816 00:51:36,160 --> 00:51:39,160 you're interested in. I'll definitely be there. 817 00:51:39,160 --> 00:51:43,360 So add me to the list and if you get a chance, if you're out of 818 00:51:43,360 --> 00:51:45,520 Gartner, please come out and meet us. 819 00:51:46,240 --> 00:51:48,120 Thank you so much for doing this, Haiko. 820 00:51:48,320 --> 00:51:52,720 One more time for everybody's Nexus Dash secure slash idac. 821 00:51:52,720 --> 00:51:57,080 You'll have that paper from Cooper Cole there for folks to 822 00:51:57,360 --> 00:52:00,920 get a copy of, which I think is fantastic. 823 00:52:01,200 --> 00:52:05,200 Those papers that Cooper and Cole puts out are always top 824 00:52:05,200 --> 00:52:08,120 notch. That's going to wrap up the show 825 00:52:08,120 --> 00:52:10,640 for this time. Find us on the web at 826 00:52:10,640 --> 00:52:14,840 idacpodcast.com. Find us on YouTube by just going 827 00:52:14,840 --> 00:52:19,720 to idacpodcast.tv. And we'll talk to you all on the 828 00:52:19,720 --> 00:52:23,680 next one. You've been listening to 829 00:52:23,720 --> 00:52:27,600 Identity at the Center. We hope you've enjoyed the show. 830 00:52:27,800 --> 00:52:31,920 Make sure to like, rate and review, and we'll be back soon. 831 00:52:32,200 --> 00:52:34,440 But in the meantime, hit the website at 832 00:52:34,440 --> 00:52:40,800 identity@thecenter.com. See you next time on Identity at 833 00:52:40,800 --> 00:52:41,680 the Center.