Good afternoon, ladies and gentlemen, welcome to our webinar. Upgrade your IM with Ida IGA. My name is Martin Kok. I'm principle Analyst at Koa Cole. And I'll walk you through this webinar and provide you with some of our insights and information. Also looking at our reasonably published leadership on Ida IGA and some of the trends we serve in the market. And some of the thinking we have around where is identity management, specifically the area for IGA, but also beyond that.
So the core capabilities such as lifecycle management and access governance, which are commonly called IGA for identity governance, registration, where are these things heading before we start some quick information about cutting a call, copy a call. As you probably know, as an Analyst company, we head called watered in Germany, and we are delivering services in three practices, which are identity and access management and digital identity, which are cybersecurity, and which is artificial intelligence.
We do this by delivering research, such as our activity view reports, which cover certain products and services, our leadership compasses, which compare the vendors and services in certain market segment and others. We do it through our events, such as our webinars, our conferences, and other formats. And we also support customers with concrete advisory, wherever required.
If you want easy access to our research, I'd like to you on our Casey plus offering, which is our new content and research platform. And that gives you very easy access to all of the content we are producing.
Very easy research works and various types of interfaces. So you can use in the mobile device on your PC or still download the PDF. And I think it's a very fair offer. You can get a full year access to all of our new research, including the leadership documents for only 800 euros. So don't miss to book your own personal Casey plus license. We also have a series of upcoming events in 2020. So obviously the flagship event first, which is our European identity conference, 2020 already. Addition number 14, we run it mid may in Munich.
In October, we do our customer tech event in Amsterdam, which focuses on consumer identity on customer onboarding, registration, marketing, automation, related topics, all around how to really deal with your customer in the age of digital transformation.
In November, we do our cybersecurity leadership summit and our cyber access summit in Berlin, which are our cybersecurity events. And then finally we do our cybernetics world, which brings together AI security and all the related topics.
So how will this world look like with all the new digital services is all the smart cities and other stuff in future. This event will be run in Stockholm and Abuja in end of November with transmissions between the various locations, all in the same time zone, definitely don't miss event. You should be there as well for the webinar. We are your muted centrally. So we are controlling. These features now need to care about that. We are recording the webinar and we will provide a slide deck for download usually by tomorrow, maybe the day after. And we will have a Q and a session by the end.
You can end the questions at any time.
The more questions we have the better, the more likely the Q and a session will be is that let's directly Trump into our topic. And where I wanna start with is I look at structure of IDAs. So IDAs for identity as a service defines the offerings, which are delivered as a service and pitch for identity management capabilities. And at the core of this, we find the three sort of key areas of identity management.
So in IGA, so to speak is the left and the right hand pillar here, which are on one hand identity administration or life cycle management. Progressioning so connect to systems, user provisioning slash service, user profile and password management, stuff like that. And the access governance piece, which is around access review, access requests, all the related things, access intelligence, cetera.
And in the middle tier, we have the access management pillar, which is then covered in a separate leadership in that case, our leadership compass IAM or access management, which we published a little earlier this year, which also find that our KC plus platform and access management is done on Federation on onboarding, social integration, single sign on experience and all that stuff.
So in all these areas, we see IDAs capabilities. We also see IDAs extending to new areas, such as the customer identification during and onboarding process. We see it moving into Pam.
So the P should access management space. And there's a very strong tendency of more and more traditional identity management capabilities, which have been delivered when you go back a couple of years, mainly on premises, they are gradually and, and so very significant speed shifting into, as a service deployment models, we have different maturity and I'll touch this in a minute in different areas, but we see also a strong uptake of offerings, which go into delivering IGA as this key area as a service. So what are the market drivers?
What are the reasons for that, for this shift to Ida, to, as a service models, does the obvious time to value proposition as a service model provides overall premise IM deployments? There's I think to some certain extent also correct this, this experience and impression that identity management projects can take quite long can be cumbersome, can be challenging.
Not all of this will disappear because a lot of the challenges come from it, the IMT working with the business, gathering information, understanding the entitlements of the business and other stuff, but platform deployment potentially is simplified. And there's this promise that things can get fairly better also in operations.
It is also a focus that towards supporting the crewing SaaS portfolio, which is more important for the Ida access management than for the Ida actually, where it's also important to obviously to provision to all these SaaS and other types of cloud services.
But it's only part of the story. If you have it as a service, you frequently are more in a standard. The tendencies that as a service solutions, things are provided. Things are delivered more in a, in a standard, in a best practice model that makes it easier, or is a promise of IDAs. And there's a potential for that. Obviously reducing internal costs, moving to operational expenses are another aspect. And I already touched the, the, the risk of, of failures, which is one of the aspects we see as a driver.
And then I think there maybe biggest drive of finally, and we see this more and more these days when we talk with customers is that I would say there are not that many organizations anymore, which say, okay, we will stay on premises as our primary operation operating model for our it services, the vast majority of businesses, even over here in Europe, even over here in Germany, where the entry to the cloud was a little bit more reluctant than in other regions.
This is the standard model today.
So the expectation obviously also is that such services such as identity access management run in quotas, modern operating model run in an, a service model and all these things are driving the adoption. So maybe talk about Ida today. We are looking at I IHA, which is the part which, which, which is about, as I've said, identity, lifecycle management and provisioning and the access governance and intelligence capabilities. And in that leadership, we, we look at today, it is about offerings, which are provided in a S a service model, which not necessarily is a full SaaS model.
So this click paper credit card use it. A lot of IGA implementation or typical, I implementation still will have a, a decent amount of customization of integration with success, existing directory. So it's usually that it takes some time to make this right, that can be in a SA model, but it's that absolutely mandatory.
And if vendors have a modern architecture, so following a, a microservice architecture, well, well defined services done, even in, in such models, it's fairly straightforward to, for instance, run updates continuously across a large number of tenants, because the good mode on architecture based microservices automatically will lead to a scenario where the customization happens in segregated services, but not in the core capabilities. So then riot, this can be well managed. And so the requirements we look at are it's managed.
It is elastic the use, it's also paper use model, and the platform also supports continuous updates in a centrally managed way. So it's not necessarily about full multitenancy. We still observe that many customers are even somewhat reluctant regarding having a fully multitenant solution and prefer having a solution, this critical space of digital identities and entitlements, which is single tenant, but centrally managed and delivered in an asset service.
Well, what we don't count are on premise solutions, which are run by someone as a managed service, where the elastic paper used to continues handling off updates, and etcetera is, is widely missing. Obviously there is a, there can't be some discussion about who's in who not. We in general, for this addition of the leadership compass went to be relatively open regarding inclusion, obviously over the next couple of years, the, the, the level of requirements we, we, we had set on who is in that will increasingly change.
And when we look at the entire evolution, I wanna bring up a topic, which I also touched on a couple of other webinars recently in which I discussed very heavily with the ceases. And I am leads of a great number of organizations. And that is, we also should understand that we need to reconsider the way we did identity management over the years, and we need to do more.
It is not that what we did so far is, is fundamentally wrong, but there are TRS we are facing, we need to support. And we talk these days a lot and write a lot about the concept of identity fabric fabrics term.
We created a while ago. So the identity fabric is, is your set of identity services, which support this basic challenge of identity management, which is provide controlled access of users to all the services. And it means all the users, the customers, the consumers, the partners, etcetera, to all the services you have, regardless of whether, and, and you need a set of services enable it, which support the authentication, the authorization. That would be the, I am part, but which also support user onboarding life cycle, entitlement management, which would be the I part.
So the FD access management, the J and we have obviously far more services such as content, privacy, cetera.
And obviously there's what we need to do these days. What we need to add is the ability to manage all of our SAS services, which is still, and I've called it outside in, which is still from outside of the application, into the application. So identity management, managing the SAS services, the access to them to doing federated provision, et cetera. But we also have this change in how businesses act.
And when we look at the business today, the very huge portion of businesses today are in some way, software businesses, they create digital services part as part of the transformation as part of the new business models. And these digital services must be able to consume identity services. There's no way to create identity services per digital service that will lead to a negative customer experience because the experience in using digital identity of a, of a single company will vary between the true services.
It also will kill the time to market because it takes too long.
So our future platform for IDAs, and it's also aim, it's IDAs actually a must support an identity API layer, which can be used by digital services. This is turning the way we do identity management to run. It's an inside out access. Why are APIs from the services to identity management? Clearly we also need to support. And that is a key requirement that has been a key requirement for this leadership compass. We also need to support what we have. So let's call it legacy integration capabilities of all these on-premise systems, maybe of an existing IM you have.
And we need to be able then to convert at our pace. So we have the need for a high flexibility speed for digital services. And that speed only can come from very fast and rapid deployment.
And that is where IDAs helps with IDAs. We can set up our new set of services for supporting the service for the inside out access faster than we can do typically with a traditional on premise approach, identity management. And it's where we need it somewhere out.
And the, as a service work, we also add the services for site, but we also need to integrate and gradually migrate what we have into it as a service environment. So we need to have this hybrid support at a very higher level. That leads us to the key criteria for this IDAs I leadership compass. And I took 10 of the, so the 10 most important areas of capabilities we are looking at there's integration with directories it doesn't Meanda AI chain must come with directory.
There might be an integration to existing directories frequently, to some extent, both there's the ability to onboard users for all types of users beyond the employees.
So the join processes to go back to a very traditional identity management term, but frequently beyond that, so flexible registration flows. And we look at business partners. For instance, we have a variety of registration flows, far more complex capabilities for a user who still frequently comes insulin, human capital management system or HR system. Then number three, we have to connect our press.
We have to connect our desks. And that is still important. Both is important. So support the systems, you have allow easy integration, come with them, whatever connector factory, easy way to create new connectors, but also deliver the deaths because many of these systems are not just, I create an account it's about complex entitlement structures, and that is what makes projects finally RA complex and cumbersome. So the better the breadth and depths of connectors, the more likely you will succeed through project.
We have the workflows provisioning flows, approval flows are all types of workflows. Yes. Easy to configure configuration of coding.
Obviously, when we are talking about IDAs, it's mainly configuration, there should be little to no coding set service interfaces, mobile interfaces for variety of use cases. So credential management, profile management, etcetera, the access request management, because it goes back to the, the workflows easy way to ask or access to get access to what you need.
Maybe even when you, when it's very innovative, some in the product sense, AI behind at least for some recommendations, etcetera, access reviews and analytics, one of these things, which also need to be easy to use flexible approaches for entitlements. And that is a, would be a very different topic, but I, I'm not a, not a big believer in traditional role management approaches. They feel far, far too frequently.
Nice believe there are better ways, and we will publish a lot around this over the next couple of months, but it's important that there are various ways to define and handle entitlements well beyond roles.
They need some baseline items access, or it's nice, good to have some baseline Analyst, access management, not they're all products, but in many, it helps them that you say, okay, I can also federate in federated.
I integrated with federated provisioning, etcetera, and last not least hybrid support and architecture that supports hyper deployment, which brings us back to microservices, architecture deployment in containers. If it's not a pure SaaS model and broad support, and clearly defined ways to connect back to your existing infrastructure. These were some of the criteria and our, our question as far longer, it consists of very long list of questions. So when we create such a leadership, what do we do? We start as a market segment definition.
So we define, describe the market segment, the key criteria we select the relevant vendors. We invite all vendors, meeting the criteria, and we are trying to invite and include as many as we can.
So also the regional layers, also the smaller, the more in way vendors, not only the big ones with very consider already very considerable revenue, we do the evaluation, we circle and extensive questionnaire guys, additional information to briefings in whatever, do additional briefing stem talk with vendors, do our rating.
Then when we collected all the data, create leadership compass crafts, and then finally run this into, create it and run it into an extensive fact check. So all of these results are again as cost for the vendors and we listen to the vendors, but obviously as Analyst, we also take our own strong position. We look at from a product and service perspective and at five categories. So one is security security. One is functionality.
So security, obviously security features doesn't need baseline capabilities, the internal security model, and a lot of other things authentication, approaches, whatever functionality is the sort of the main area where it's really looking at all the various functional aspects, all the capabilities, the features, then we have the integration approach.
So is this one product or our vendor?
Many, the more we look at as a service models, the more we also look at the hybrid architectures, the flexibility in deployment, the various deployment models. So how can you run that in still integrated way? But most of decent amount of flexibility, we have interoperability. So how does it work with other services, APIs that are provided, stuff like that. And then we have the usability part, which is about UI, easy to use, consistent interfaces, consistent APIs, and all that stuff.
And that information we put together with also information we have about the size, the revenue, the ecosystem, other information, we put this together into four categories of leadership. The first one is our product leadership. So it's functionality to complete the submission. So it's just a comprehensive offering. There's the market leadership, which is about not only the revenue, it's about the number geographic distribution of customers, the average size of customers, the partners that have to support ecosystem, all that stuff.
So some vendors are, are very strong in a certain region, but that doesn't make vendor, a global player. And then we have innovation leadership where we look at new and useful features that are coming up and which are sort of changing the market all this together then forms the overall leadership we add to this pro vendor. So roughly one page of more detailed and lysis and a specific perspective on certain feature areas, which we put together in spider craft.
So for instance, the target system support, which I already mentioned, the access request and workload the overall access governance capabilities. So how good are they in access cover governance, authentication Federation. So are the baseline capabilities in there or not the mobile support, the architecture, which as I've said, is very important when we look at where other requirements heading. So what do we need to have in future as an identity management system, self-service interfaces, and finally the hybrid environment support.
So how good does this run for hybrid environments?
As I said, one of the major things we looked at 15 vendors, we took into the rating. We looked at far more vendors for this leadership. A couple of them are than a section we call vendors to watch that are vendors, which ISA didn't respond to a question which sometimes, but rarely happens or vendors, which are not yet fully meeting our requirements should be mean by the way I IGA here. So the vendors, you can read them. I don't want to read all of these vendor names.
Actually, there are 15 of these and we then created our leadership graphs, as I've said. So we have our overall leadership rating for the IDAs market, which is influenced by also the, the market size, which obviously helps some of the very large players to benefit more than some of the more specialized players that is a good entry, but for all these graphics, let, let me give one important advice, never, ever select a product by trust, looking at such graphics from whichever Analyst company, they are go into the details.
And there's a reason that our leadership is a 60 page, more or less report because it's about details. And even for shortlist decision, not only go to the ones on the very right or for the other graphics on the upper right edge, try to understand what look at, where are the specialists, where are the specifics in our leadership compass for every vendor. We also have some information in which, in the text portion, when they are for instance specialists and why they for, they might be a good fit and maybe that are the best fits for you.
So that is the perspective product leadership, which is I believe a more important aspect than the overall leadership from my perspective, then shows the ones we see as the functional leaders, which are, have a strong and broad set of capabilities here with a couple of vendors. Currently, we see some in the head of the others, which is one of the very few, not only, but one of the few really cloud born I IGA players.
And they started relatively early, but you also see a couple of them, which either have both offering sale point as an on-prem and a SaaS offering, or which are in some sort of a migration phase.
The other aspect is, is innovation where Microsoft is a broad set of capabilities is catching up where we also see a couple of, of vendors here, plus a variety of challenges, big number of challenges. And many of these are, as you can see, very close to entering the, the, the leader segment. So we see this evolution, obviously we also, for the next additional again, raise our bar.
That's the other side of it. So we are clearly permanently challenging these vendors. Then we have the market perspective as usual, the big players being pretty much in front. This is sort of our perspective in natural and overview on this Ida IgM market. As I've said, you will get access to slides. You can use Casey plus to get access to all of our leadership compass in a very easy and affordable manner. And obviously we also can support you in all the tools, choice decisions you, you might need to make.
And that's part of our advisory services going into details, delivering our deep understanding of the vendors, helping you in selecting the appropriate journalists, supporting you and making your decisions on the vendors. So that is what we have here. And with that, I directly want to move to the Q and a session. So if you have any questions, please enter these questions.
Now, what I won't do in, in a public forum is sort of vendor pitching for sure, but everything which relates to where do I see this market heading the trends, the way to select vendors, all the stuff, which is more around methodology, don't hesitate to ask us. And so while, while you enter questions, as I said, I, I, I just wanna quickly come back to the way to do such a selection in a, in an appropriate manner. The most important thing to do from my perspective is understand your requirements.
So start with a rough requirements analysis.
What is it, what you need today and what is it, what you need in the future. That also means understanding your architecture, your bigger picture of identity management. And from there, you can then identify your key criteria. So as I've had this, for instance, top 10 criteria, you might use that to benchmark against the, the spider crafts and identify who are the ones which fit these requirements best. And then from there, you can create your shortlist. You can create your own questionnaire.
You need to do my perspective when the presentation study include as the beauty contest thing, where you best have vendors and the partners presenting because the system integrator or the one who do the, does the project that is highly important, you might have the best project, but if it doesn't work with the team, with the project team, you'll fail.
If your partner is perfect, even the, a product which appears not to be the super, super leading action best of breed product might be a clear win. So have all of them in, and then also do a POC, a proof of concept once you have made.
So short list, maybe five POC, two, once you're down to that, do it, and then make your final decision. And while I strongly believe that things like our leadership compass are very helpful, very important. Don't just rely on that, but look at our stuff. And we have also a lot of additional research around buyer Skype, but our key criteria, for instance, for iOS advisory notes on how we see this market, developing a lot of wide papers and leadership briefs, other documents available, work through that, roughly ask whenever you need to ask, that's what you should do. So let me quickly look okay.
I think that is basically what we have. Thank you very much for listen to this webinar and don't hesitate to come back to us when you have questions, when you need support or look at our new information and all the webinars, I wish you a very happy, relaxed holiday season, happy new year, and hope to have you soon back at one of our events or one of our upcoming webinars. Thank you.
