WEBVTT 00:00:00.000 --> 00:00:06.900 I think something which struck me was just the sheer size growth in the IGA market, the 00:00:06.900 --> 00:00:11.500 number of vendors that we are covering, I think that clearly demonstrates the IGA market 00:00:11.500 --> 00:00:16.400 is growing. And what was struck me as well is that several of these vendors were really 00:00:16.400 --> 00:00:21.600 newcomers and they were really focused a bit more on the core capabilities of IGA. But 00:00:21.900 --> 00:00:28.300 it will be interesting to see how these, you can say, emerging vendors now progress in 00:00:28.300 --> 00:00:32.900 the next one year, two years, and how they expand on the capabilities. So I'm looking 00:00:32.900 --> 00:00:34.900 forward to that side of segment as well. 00:00:49.800 --> 00:00:54.100 Welcome to the KuppingerCole Analysts chat. I'm your host. My name is Matthias Reinwarth. 00:00:54.100 --> 00:01:01.000 I'm analyst and advisor with KuppingerCole Analysts. Today, we want to talk about a topic 00:01:01.000 --> 00:01:04.363 which is without any doubt one of the flagship 00:01:04.363 --> 00:01:07.800 topics that we at KuppingerCole Analysts cover. 00:01:08.600 --> 00:01:14.000 And for this, I have invited the author who was behind that flagship research that we 00:01:14.000 --> 00:01:16.932 are looking at. We want to talk about Identity 00:01:16.932 --> 00:01:19.800 Governance and Administration, IGA. For this, 00:01:19.800 --> 00:01:24.600 I have invited my colleague Nitish Deshpande. Hi, Nitish. Good to have you. 00:01:25.500 --> 00:01:27.884 Hi, Matthias. Good to be here as well. It's 00:01:27.884 --> 00:01:30.600 been a while. And I think you correctly mentioned 00:01:30.600 --> 00:01:36.300 IGA has been a very important topic for us and everyone else in the industry. So looking 00:01:36.300 --> 00:01:38.400 forward to the quick discussion with you today. 00:01:39.500 --> 00:01:46.300 Yeah. So really, we want to really draw from your research, from your experience. And IGA 00:01:46.300 --> 00:01:51.900 is a market segment that is around for quite a while. But that does not mean that it's 00:01:52.000 --> 00:01:55.067 stalling or getting boring or does not evolve. 00:01:55.067 --> 00:01:58.200 All of this is completely wrong. It's changing. 00:01:58.700 --> 00:02:05.800 So when we look at IGA, from your research, where does IGA stand today? What has happened? 00:02:06.000 --> 00:02:07.600 Where it is now? What's the state of the union? 00:02:08.800 --> 00:02:13.000 Absolutely. Completely agree with you. I think most of the people would say that IGA is a 00:02:13.000 --> 00:02:17.800 very mature market. There's not much happening, but it's completely the opposite. You can 00:02:17.800 --> 00:02:22.300 say IGA traditionally was definitely more driven towards more strategic models and more 00:02:22.300 --> 00:02:27.700 towards siloed components. But what we are seeing right now, when we did this report, 00:02:27.900 --> 00:02:30.980 when we did our current analysis on this IGA 00:02:30.980 --> 00:02:34.200 report, is that the vendors are moving towards 00:02:34.200 --> 00:02:37.401 a more, you can say, converged platform for 00:02:37.401 --> 00:02:40.900 lifecycle management, access governance, access 00:02:40.900 --> 00:02:43.248 intelligence capabilities. Then also some are 00:02:43.248 --> 00:02:45.700 also providing password management capabilities 00:02:45.700 --> 00:02:50.400 as well. So it's all being done on one single platform. And that seems to be the new theme 00:02:50.400 --> 00:02:57.000 as well. But what is also interesting right now is that due to the current demand as well, 00:02:57.200 --> 00:03:01.900 now the types of identities that are being supported is not just limited to workforce, 00:03:02.200 --> 00:03:08.700 contractors or partners. It is now also being expanded to this new genre of identities 00:03:08.700 --> 00:03:14.100 called the non-human identities. And the IGA vendors are now also covering this part of 00:03:14.100 --> 00:03:18.700 the, you can say, workforce identities as well. So it is definitely moving to that side. 00:03:19.100 --> 00:03:24.800 It is also equally driven by the customers as well as the customers are looking for a 00:03:24.800 --> 00:03:30.500 more integrated solution for all types of identities and all types of modules. But that 00:03:30.500 --> 00:03:35.100 said, you can say that some organizations are still currently preferring, depending 00:03:35.100 --> 00:03:37.919 on what is their industry and what is their 00:03:37.919 --> 00:03:41.000 focus, to have a bit more, you can say, central 00:03:41.000 --> 00:03:45.500 control into their own premises rather than just having a more fully deployed into the 00:03:45.500 --> 00:03:50.100 cloud. So it's a bit of a mix of both right now. So it's definitely an interesting time 00:03:50.100 --> 00:03:56.000 to be here. But I think with the current advancement in IGA, I think we are at a really 00:03:56.000 --> 00:03:56.900 interesting point right now. 00:03:57.200 --> 00:04:02.200 Right. From what I've seen with I'm doing advisory in the IGA area quite a lot. So I 00:04:02.300 --> 00:04:08.100 also see differences between customer groups, how they consume IGA. Do they use the 00:04:08.100 --> 00:04:16.200 traditional front end focused, workflow focused, user facing way of doing IGA? Or are 00:04:16.200 --> 00:04:23.500 they more modern, more cloud native? Are there more API users? So really using the 00:04:23.500 --> 00:04:29.000 platform as the driver under the hood in the machine room, but not necessarily as a 00:04:29.000 --> 00:04:33.800 content. I think that is also something that is currently evolving in parallel, even at 00:04:33.800 --> 00:04:38.100 the same vendors or specific vendors that focus on one or the other. But I think that 00:04:38.100 --> 00:04:43.300 is also something that is really changing. So it's really something that is embedded 00:04:43.300 --> 00:04:48.600 into an overall architecture rather than having log in and clicking and now I'm in 00:04:48.600 --> 00:04:50.000 IGA and now I do a workflow. 00:04:50.500 --> 00:04:57.800 Right. Definitely. People are also trying to understand if they can, you know, try to 00:04:58.400 --> 00:05:02.300 not connect to the whole IGA solution or implement the full solution. They're also 00:05:02.300 --> 00:05:06.100 looking for a bit more flexibility in there is to maybe just they want to implement just 00:05:06.100 --> 00:05:10.500 the access governance part of it or maybe just the lifecycle management part of it. So 00:05:10.500 --> 00:05:14.300 it's definitely driven more towards that as well as to have a bit more flexibility and 00:05:14.300 --> 00:05:16.600 also support in all the scaling as well. 00:05:16.700 --> 00:05:21.400 Right. And when we say that the market is evolving, of course, there needs to be a 00:05:21.400 --> 00:05:26.900 driver for this evolution. The question is, what is already well working? Is it only 00:05:26.900 --> 00:05:32.700 just the traditional use cases that we have or are these vendors also targeting new use 00:05:32.700 --> 00:05:40.200 cases? You've mentioned NHI as a new type of identities. We see AI supported use cases 00:05:40.300 --> 00:05:47.200 where generative AI supports the end user or the admin in doing their job better. But 00:05:47.200 --> 00:05:51.400 evolution means that there's room for improvement. There's room for evolution. Are 00:05:51.400 --> 00:05:57.700 there areas where IGA actually also still falls short and where there's new tendencies, 00:05:58.800 --> 00:06:03.000 new emerging technologies to be embedded here? 00:06:03.600 --> 00:06:09.000 Yeah, absolutely. I agree with you. I think no solution is 100% perfect. There are 00:06:09.000 --> 00:06:18.800 definitely areas for improvement. When we did this report for the IGA, we had several 00:06:18.800 --> 00:06:22.800 types of vendors in this report, not just your traditional big vendors, but also smaller 00:06:22.800 --> 00:06:28.100 vendors, upcoming vendors, emerging vendors, innovative as well. But I would say the 00:06:28.300 --> 00:06:33.600 more recurring theme amongst all of them, in most cases, was that there were some 00:06:33.700 --> 00:06:39.200 limitations in some, you can say the app automation side and governance side. So 00:06:39.200 --> 00:06:45.700 especially if you look at more around the anomaly detection, then there was one quite 00:06:45.700 --> 00:06:50.700 common theme was limitations around role mining as well. So that was again, you can 00:06:50.700 --> 00:06:55.400 say a shortcoming or an area which is currently being worked on, which needs to be 00:06:55.400 --> 00:07:00.300 improved. AI driven recommendations is another part which is still on the roadmap of 00:07:00.300 --> 00:07:06.200 several vendors. So you can say the access intelligence side is currently where the 00:07:06.200 --> 00:07:10.200 vendors are also innovating and are focused right now and they are addressing these 00:07:10.200 --> 00:07:14.200 challenges as well. But if you also maybe look at from policy management point of 00:07:14.400 --> 00:07:18.700 view, there are again a few inconsistencies or shortcomings there, such as in most cases, 00:07:18.700 --> 00:07:23.300 the support for something like a policy simulation, policy testing is not being 00:07:23.300 --> 00:07:27.600 provided right now. Even support for policy as a code is currently missing. But I think 00:07:27.600 --> 00:07:32.600 that again depends on what kind of customers you have. If the vendor is focused on 00:07:32.600 --> 00:07:37.900 customers who are mainly around the business users and not really, I can say, 00:07:38.000 --> 00:07:42.000 developer focused. So the vendors are making this conscious decision to not provide 00:07:42.000 --> 00:07:47.500 policy as a code as they believe their own client is not really going to be utilizing 00:07:47.500 --> 00:07:52.200 this capability to the full. But another area again is around workflows. Workflow 00:07:52.200 --> 00:07:57.700 automation, workflow graphical designing is also missing in a few vendors, which I 00:07:57.700 --> 00:08:01.200 would like to see as well. But again, the vendors are doing their best. They're 00:08:01.200 --> 00:08:05.600 trying to address these challenges and hopefully, I would say maybe the next time 00:08:05.600 --> 00:08:10.500 we do this report again, which is next year, I guess, then we will have a bit more 00:08:10.500 --> 00:08:14.300 understanding on what has been the progress of the vendors and have these kind of 00:08:14.300 --> 00:08:19.100 shortcomings been really addressed. I mean, the challenges around deployment and 00:08:19.100 --> 00:08:23.600 flexibility are being addressed as well because you have vendors providing different 00:08:23.600 --> 00:08:27.800 kinds of deployment models. You have vendors providing fully SaaS model or they're 00:08:27.800 --> 00:08:32.300 also providing support for on-premise deployments. But then that again leads to 00:08:32.300 --> 00:08:37.500 different conversation as well is that what is the feature parity in both kind of 00:08:37.500 --> 00:08:41.900 deployment models. So these are some of the, let's say, a few areas where IGA 00:08:41.900 --> 00:08:44.600 solutions are currently evolving and developing. 00:08:44.900 --> 00:08:48.800 But let's unpack this. This was actually really my next question because when I had 00:08:48.800 --> 00:08:53.500 this conversation five years ago, six years ago, seven years ago, there was a clear 00:08:53.800 --> 00:08:59.400 move from on-premise IGA towards just consuming it from the cloud with all the 00:08:59.400 --> 00:09:04.000 benefits that you have, continuous updates, no downtime, not having to provide any 00:09:04.100 --> 00:09:09.300 infrastructure, having always the newest capabilities and the newest version 00:09:09.300 --> 00:09:12.300 available without really having to care about that. 00:09:12.700 --> 00:09:15.800 That has changed for many of our customers, not for all. 00:09:16.300 --> 00:09:19.300 So we see still this tendency as a big trend. 00:09:19.400 --> 00:09:24.600 But on the other hand, we see with the geopolitical situation, where do I consume 00:09:24.600 --> 00:09:27.300 the cloud from? Where is it actually run? 00:09:27.300 --> 00:09:29.800 Who runs the system on behalf of the vendor? 00:09:29.800 --> 00:09:35.900 There's a strong call also for solutions that can be handled autonomously within a 00:09:35.900 --> 00:09:38.600 private cloud or even still in own data centers. 00:09:39.000 --> 00:09:43.300 So we have the full breadth of potential when it comes to deployment models. 00:09:43.700 --> 00:09:49.100 But what the customers that I talk to actually are asking for, does the market cater 00:09:49.100 --> 00:09:51.400 for that? What you hinted at, I think, yes. 00:09:52.300 --> 00:09:53.700 Yeah, absolutely. I agree with you. 00:09:53.700 --> 00:09:57.700 Yes. And that has been a recurring theme, as you mentioned, around the geopolitical 00:09:57.700 --> 00:10:02.300 situation is several vendors from Europe positioning themselves as EU sovereign. 00:10:03.300 --> 00:10:07.500 So which is, again, attractive for EU customers right now is they're looking for more 00:10:07.500 --> 00:10:09.600 and more EU-based vendors. 00:10:10.000 --> 00:10:13.400 Definitely that has been one driver in this transition as well. 00:10:13.600 --> 00:10:18.900 But if you talk about the shift from, let's say, shift to the cloud models or the status 00:10:18.900 --> 00:10:24.700 of the on-premise models, again, the same thing is still the recurring theme since last 00:10:24.700 --> 00:10:29.700 couple of years is customers from highly regulated industries are still preferring a bit 00:10:29.700 --> 00:10:35.900 more of an on-premise control or in, let's say, in the best case scenario, something 00:10:35.900 --> 00:10:37.100 like a private cloud deployment. 00:10:37.700 --> 00:10:40.500 So that is, you can say, the shift right now. 00:10:40.700 --> 00:10:46.200 In fact, we did a survey last year trying to understand what is the status of IGA 00:10:46.300 --> 00:10:49.000 deployments, on-premise, cloud or hybrid. 00:10:49.000 --> 00:10:56.500 And the responses that we got were a bit, you can say, interesting because we did the 00:10:56.500 --> 00:11:00.600 same survey three years in a row and we tried to compare the responses of all the 00:11:00.600 --> 00:11:07.100 surveys. In 2023, the theme showed that on-premise definitely was the predominant 00:11:07.600 --> 00:11:12.400 deployment model. In 2024, there was a good shift, you can say, towards hybrid 00:11:12.400 --> 00:11:19.400 deployments. But in 2025, we saw from the responses that we got is that there was 00:11:19.400 --> 00:11:22.300 deployment shift again back towards more on-premise deployments. 00:11:23.200 --> 00:11:29.300 Maybe this is an outlook of how IGA deployments are complex. 00:11:29.700 --> 00:11:34.400 And some of the respondents who were participating in this service for the last 00:11:34.400 --> 00:11:38.700 three, four years had to roll back to on-premise deployments due to some complications 00:11:38.700 --> 00:11:44.300 with cloud. But it will be interesting to see again this year what's the status. 00:11:44.700 --> 00:11:48.600 But once we have some more information, definitely we'll be happy to share with 00:11:48.800 --> 00:11:53.600 everyone who's listening to this podcast and also who is a regular visitor of our 00:11:53.600 --> 00:11:54.000 website. 00:11:55.400 --> 00:11:59.700 Right. And I think with the target systems moving more and more to the cloud and IGA 00:11:59.700 --> 00:12:05.000 are actually running somewhere, hybrid, on-prem, wherever, there needs to be 00:12:05.300 --> 00:12:09.900 connectivity, at least to the outside world, to SaaS, to infrastructure as a service, 00:12:10.100 --> 00:12:11.100 to whatever you have. 00:12:11.700 --> 00:12:17.300 So I think that there is also a strong move to have at least the provisioning somewhere 00:12:17.300 --> 00:12:21.500 else, not on-prem, because it's closer to the target systems. 00:12:22.200 --> 00:12:28.800 One question that you've hinted at very briefly when we talk to our customers, when 00:12:28.800 --> 00:12:35.200 they say, I want to have a tools choice, I want to have a good IGA product and I have 00:12:35.200 --> 00:12:40.400 a choice between on-prem and software as a service or self-hosted or containerized 00:12:40.000 --> 00:12:43.800 somewhere. Do I get the same product? 00:12:44.400 --> 00:12:46.000 Is there feature parity? 00:12:46.400 --> 00:12:50.100 Are they the same wherever I consume them? 00:12:50.400 --> 00:12:56.800 And can I even change over time, moving from on-prem to hybrid to the cloud without 00:12:56.800 --> 00:12:58.600 sacrificing any functionality? 00:12:58.600 --> 00:13:00.300 Yeah, definitely. 00:13:00.600 --> 00:13:06.100 That has been again, an issue that, not an issue you can say, but a common observation 00:13:06.100 --> 00:13:11.200 from our side is that the requirements for having full feature parity between the 00:13:11.200 --> 00:13:12.300 different deployment models. 00:13:13.100 --> 00:13:16.900 Now, in most cases, let's say the more established vendors are providing a full 00:13:16.900 --> 00:13:23.000 feature parity in all of the deployment models, but there is still some inconsistency 00:13:23.200 --> 00:13:24.700 in some of the vendors. 00:13:24.700 --> 00:13:32.000 So definitely their SaaS deployments receive the updates and the latest features much 00:13:32.000 --> 00:13:34.800 more sooner compared to their on-premise deployments. 00:13:35.500 --> 00:13:40.300 But I would say that's also another observation is that some vendors are providing 00:13:40.300 --> 00:13:42.500 different products for the SaaS and on-premise. 00:13:42.600 --> 00:13:47.400 So they are focused completely differently, but they're focused on providing equal 00:13:47.400 --> 00:13:48.900 capabilities for both the products. 00:13:49.200 --> 00:13:51.300 So that has been again, an observation. 00:13:51.900 --> 00:13:56.100 Main differences have mainly been around providing the access intelligence 00:13:56.100 --> 00:14:01.100 capabilities, the overall support for, let's say now the NHI governance aspect as 00:14:01.100 --> 00:14:01.400 well. 00:14:01.800 --> 00:14:07.200 So yeah, definitely on-premise provides a bit of a challenge right now, but I think 00:14:07.200 --> 00:14:11.600 soon we will try to understand a bit more in the next report as well as what is the 00:14:11.600 --> 00:14:14.000 state of this feature parity between different deployment models. 00:14:15.000 --> 00:14:15.600 Right. 00:14:15.600 --> 00:14:20.400 And now that you have just published the report, it's a bit unfair to ask the 00:14:20.600 --> 00:14:21.500 question, what's next? 00:14:21.700 --> 00:14:22.100 What's coming? 00:14:22.300 --> 00:14:22.800 What do you see? 00:14:23.300 --> 00:14:28.500 What I see is really to provide human identities for non-human identities. 00:14:28.700 --> 00:14:35.000 So to add the governance layer, to understand who is an owner for a group of NHIs 00:14:35.000 --> 00:14:38.900 that have unfortunately still long-lived credentials and they need to be monitored. 00:14:39.000 --> 00:14:43.000 I think that is something where what people are asking for is for really to add a 00:14:43.000 --> 00:14:46.600 governance layer while the NHIs stay where they are. 00:14:46.700 --> 00:14:48.800 So stay within their system of records. 00:14:48.800 --> 00:14:52.200 That is something that I think will be happening and I expect that to happen 00:14:52.200 --> 00:14:53.600 because there is a demand for that. 00:14:54.100 --> 00:14:57.500 What else do you expect to cover in the next edition of this report? 00:14:58.300 --> 00:14:58.900 Yes, definitely. 00:14:59.100 --> 00:15:02.300 I think you made a really good point around the governance layer as well. 00:15:02.900 --> 00:15:09.200 What I'm also seeing is having a more, let's say, requirement or desire to have 00:15:09.200 --> 00:15:12.200 more real-time governance for different kinds of identities. 00:15:12.400 --> 00:15:16.400 Again, I think for the next report, when we will do next year, my expectation 00:15:16.400 --> 00:15:20.700 would be is that all the things which I mentioned, which are currently being 00:15:20.700 --> 00:15:25.000 under development or as a challenge for IG solutions right now around the access 00:15:25.000 --> 00:15:30.200 intelligence part, automation part, support for more policy management, even 00:15:30.200 --> 00:15:31.800 for workflow capabilities as well. 00:15:32.000 --> 00:15:36.400 I hope to see the vendors address those capabilities first as basis and then 00:15:36.400 --> 00:15:40.900 maybe focus a bit more around the AI and machine learning part as well. 00:15:41.200 --> 00:15:45.800 So maybe that is something which I would be interested to see again next year and 00:15:45.800 --> 00:15:47.700 how the IGA market is developing on that side. 00:15:49.300 --> 00:15:49.600 Right. 00:15:49.600 --> 00:15:53.500 Before we hint at the report, my personal question to you, I think 00:15:53.500 --> 00:15:56.000 the IGA market is a huge market. 00:15:56.200 --> 00:15:58.300 How many vendors did you cover for this? 00:15:58.600 --> 00:16:00.900 This is definitely a very huge market. 00:16:01.200 --> 00:16:06.100 When we did the report a couple of years back, we had around 25 to 30 vendors. 00:16:06.400 --> 00:16:10.600 This year, when we did the report, we had almost 44 vendors who 00:16:10.600 --> 00:16:11.700 were willing to participate. 00:16:12.300 --> 00:16:15.800 But based on the inclusion criteria that we defined, the exclusion criteria 00:16:15.800 --> 00:16:19.800 that we defined, we had to narrow it down to again around 30 vendors, which 00:16:20.100 --> 00:16:23.400 you will see soon in this report, which should be live already, I 00:16:23.400 --> 00:16:24.600 guess, on the Google website. 00:16:26.000 --> 00:16:26.300 Yeah. 00:16:26.500 --> 00:16:28.600 And so it's a continuous process. 00:16:29.200 --> 00:16:32.200 Soon we will be also launching the access governance report, which will be 00:16:32.200 --> 00:16:34.300 also a subset of the IGA report. 00:16:34.600 --> 00:16:39.100 And then we will also focus a bit more around a new type of IGA report. 00:16:39.200 --> 00:16:40.200 So it's still in the progress. 00:16:40.200 --> 00:16:44.100 We still haven't finalized the name yet, but we are planning to definitely 00:16:44.100 --> 00:16:45.600 publish it by the end of this year. 00:16:45.700 --> 00:16:49.800 It will be a different kind of customer and market segment that we'll try to 00:16:49.800 --> 00:16:51.300 address in this different report. 00:16:51.600 --> 00:16:54.100 That sounds interesting and really forward-looking and really also 00:16:54.100 --> 00:16:55.700 covering the market as it evolves. 00:16:56.000 --> 00:17:01.000 But for now, if you as the audience are interested in learning more about the 00:17:01.000 --> 00:17:06.500 state of IGA per today and per the research that Nitish just has completed, 00:17:07.000 --> 00:17:11.300 please head over to our website and find the Leadership Compass Identity 00:17:11.400 --> 00:17:12.500 Governance and Administration. 00:17:13.000 --> 00:17:15.800 It's been published on day one of EIC. 00:17:16.000 --> 00:17:21.600 If I remember correctly, EIC is over, but the topic still remains with us. 00:17:21.900 --> 00:17:25.400 And IGA as being one of the key foundation set of building 00:17:25.400 --> 00:17:26.900 blocks for our identity fabric. 00:17:27.000 --> 00:17:32.100 I think that is a key element that every organization should be aware 00:17:32.100 --> 00:17:33.400 of what's happening in there. 00:17:33.400 --> 00:17:36.500 Even if you have chosen a solution, where is your vendor heading? 00:17:36.700 --> 00:17:37.400 What does change? 00:17:37.600 --> 00:17:39.100 I think that's really of importance. 00:17:39.800 --> 00:17:45.300 And if you have any questions towards Nitish, towards the topic of IGA or 00:17:45.300 --> 00:17:49.600 just around this podcast episode, please leave your comments on YouTube 00:17:49.600 --> 00:17:54.300 in the comment section, reach out to Nitish or to myself. 00:17:54.400 --> 00:17:57.400 We are easy to find and the email address is really not well hidden. 00:17:57.500 --> 00:18:01.600 So you can reach out to us and we are happy and glad to reply, to share 00:18:01.600 --> 00:18:07.100 our information if it has not been covered in this podcast, or if you can't 00:18:07.100 --> 00:18:10.700 find it in the Leadership Compass, don't think so, but if there are any 00:18:10.700 --> 00:18:13.300 additional questions, please reach out to us. 00:18:13.900 --> 00:18:17.800 So Nitish, before we close down, any final observation that you had that 00:18:17.800 --> 00:18:21.400 really struck you when you looked at this large market segment, what was 00:18:21.900 --> 00:18:26.000 the most unexpected evolution in IGA that you came across? 00:18:26.900 --> 00:18:27.500 Yes, definitely. 00:18:27.500 --> 00:18:33.700 I think something which struck me was just the sheer size growth in the IGA 00:18:33.600 --> 00:18:38.100 market, but the number of vendors that we are covering, I think that clearly 00:18:38.200 --> 00:18:40.000 demonstrates the IGA market is growing. 00:18:40.700 --> 00:18:44.400 And what was struck me as well is that several of these vendors were really 00:18:44.400 --> 00:18:48.900 newcomers and they were really focused a bit more on the core capabilities of 00:18:48.900 --> 00:18:51.400 IGA, which is really, really good. 00:18:51.700 --> 00:18:54.700 We had to first address the basics and they were doing that. 00:18:54.700 --> 00:18:58.900 But it will be interesting to see how these, you can say, emerging vendors 00:19:00.600 --> 00:19:05.400 now progress in the next one year, two years, and how they expand on the 00:19:05.400 --> 00:19:08.000 capabilities, so I'm looking forward to that side of segment as well. 00:19:08.400 --> 00:19:15.100 But for all the IGA market, definitely it's a constant evolution and it might 00:19:15.100 --> 00:19:19.400 appear mature, as I said earlier, but it's definitely evolving into the right direction. 00:19:19.700 --> 00:19:20.000 Perfect. 00:19:19.900 --> 00:19:20.600 Thank you very much. 00:19:21.200 --> 00:19:25.800 First of all, for your research, then of course, for being here and being my 00:19:25.800 --> 00:19:29.100 guest today and talking about your research, this is really one of the key 00:19:29.100 --> 00:19:32.600 markets and I think it's interesting for almost any of our listeners 00:19:33.000 --> 00:19:35.600 because IGA is a must somehow. 00:19:35.900 --> 00:19:37.500 So this is really an interesting market. 00:19:37.900 --> 00:19:39.900 So thank you, Mitesh, for being my guest today. 00:19:40.300 --> 00:19:43.400 Looking forward to talk about this new evolution also of the leadership 00:19:43.400 --> 00:19:44.700 compass by the end of the year. 00:19:45.200 --> 00:19:48.500 And until then, thank you very much and looking forward to having you 00:19:48.500 --> 00:19:50.000 soon as a guest in this podcast. 00:19:50.600 --> 00:19:51.000 Perfect. 00:19:51.000 --> 00:19:51.700 Thank you, Mitesh. 00:19:51.900 --> 00:19:53.800 I look forward to our next session as well. 00:19:54.000 --> 00:19:54.600 Thank you very much. 00:19:55.100 --> 00:19:55.600 And yeah. 00:19:55.800 --> 00:19:56.300 Thank you. 00:19:57.100 --> 00:19:57.400 See you. 00:19:57.700 --> 00:19:58.000 Bye bye. 00:19:58.200 --> 00:19:58.500 Bye.