Dell Identity Manager 7.0: Why Things Have Changed

Good afternoon, ladies. I'm transman. Welcome to our equipping a call webinar, Dell identity manager, 7.0, why things have changed? Flexibility is key to success in identity and access management. This webinar is supported by Dell software. The speakers today, army Martin equipping around the CEO, founder, and principal Analyst of cooking a call and Alexei bento, who is senior product manager at Dell software. Before we start with our webinar content, I want to just give you some background information.

I'm clip a call and some housekeeping information, and then we'll dive directly into the topic of today's webinar. Coping our call as an Analyst company, we are providing enterprise it research advisory, decision support, networking for it professionals in particular around information security and digital transformation, including the area of identity access management. As one of our core research areas, we have research services, advisory services and events amongst ROS.

You will find the European identity and cloud conference, which will be held next time May 10th to thirteens in Munich and the digital finance world, which will be held next year, September in Frankfurt, the letter focusing on the changes in the final industries, for instance, through blockchain and a lot of other evolution we are facing today regarding the webinar. Some guidelines you are muted centrally, so you don't have to mute around with yourself. We are controlling these features.

We will record the webinar and the podcast recording will be available latest tomorrow at our website, there will be a Q and a session at the end. You can answer questions at any time using the questions, featuring the go to webinar control panel. The go to webinar control panel usually is at the right side of your screen, and there's an area questions. And there you can. The questions which we don't will pick in the Q and a session. So let's have a look at the agenda. The agenda is split into three parts. In the first part, I will talk about approaches solving IM I and IHG.

So identity and access management and identity access governance challenges, and the increasing convergence and how such integrated solutions can support the flexibility requirements we are facing today. So we are in a situation where we on the one hand have to do far more than for identity access management and governance. Never. Before we see solutions conversion, I think there's some logic. And on the other hand, on the other hand, we also have to face the situation that it's, that we have new challenges, et cetera. Okay.

Then the second part we are facing is, or in second part of the webinar will be done around Dell identity manager, seven oh Alexei OV Dell will do this. He will talk about what has changed, why it has changed and how this helps customers addressing their real world challenges in identity and access management. As I've said on the third part will be the Q and a session. So this will be then the third element of our webinar. I'll right now jump into the topics of our webinar. So the next slide I will talk about is very simple.

It's sort of the big picture of our identity and access management identity and access management. When we look at it, this is not a, not just a, how should you phrase it? It's not just one technical element. It's a complete set of different technology. So we have identity provisioning here. We have directory virtualization, we have directory services. On one hand, we have the authentication part with single sign on versatile authentication, risk and context based authentication authorization. We have the authorization part and we have the audit area.

So we have a number of different areas we are facing. And we have to understand that identity and access management is a more complex, more complete area. We have to look at. It's not only one tool, it's a set of tools, but on the other hand, this will be one of the major topics for today at the center of this is the, at the center of, this is what, what we call identity, access management, access governance as provisioning and access governance. And this is right now situation. So we are talking about identity, access management governance for a pretty long time.

But what we are facing today are a number of changes. And I have two slides on that. One is the one you currently see, which is the computing. Troy cut computing. Troy cut is about two days' scope and changing scope of information security. So we have three major elements here. One are element we are seeing here is cloud computing. So we have new types of deployment models. We have social computing, which is about the change of more users.

And we have mobile computing, which is about more types of devices and what we need to do right now in this identity, access management world, and all other areas of it. We have to support all these areas. We have to support everything here. And as you can see in the current slide, everything and everyone are right now becoming connected. So we have a far more complex world with not only the organizations and some people accessing the computer systems, but a variety of the Wises and the connected things. And all these things are sort of tightly related and go hand in hand.

And what we are doing in identity access management on one hand has to support what we already have in our organizations, but it also has to support the everchanging complexity we are facing here. When you remember back, the first slide I had, these four pillars was administration, various technologies, authentication, authorization, and auditing.

And in the context of the changes we are facing, it's very important to understand that these four A's we have here just administration authentication, authorization and auditing must work for all types of users, all devices and all deployment models. So what we are doing in identity and access management has to change in the sense of, we have to do it for more uses than ever before, more devices and more deployment models, but we also have to do it for our traditional scope. So we have to do it here. So maybe trust the technical hint. We have some delays partially with the slides.

And so it might be that the slides are a little be ahead or a little behind me. Please apologize for that. I try to keep it as synchronized as possible. So let's look at the future identity management in the future of identity management, we have to cover all identities. So what we have to do is we have to deal with not only the employees, but we have to deal with business partners, customers, consumers, services, devices, and things. So we have to extend the scope of our identity and access management and manage more than we ever did before more. So our employees still are here.

Business partners is something we did partially for a while, but we have to do it for everything else. And we have to do it for a growing number of applications. So when we look at the who, what, where and how we have a cruise from sort of an traditional perspective, where we looked at our applications and internal web applications. So this is one of the part of the, the entire story where we right now are seeing more and more types of other applications we have to deal with. So we have business partner, web applications.

We have also different ways of access to these applications technically, but any way we need to define the users, we need to manage the use for all these scenarios. We need to manage all these use cases, and this is what, what we currently have to, to solve. So we have a situation where we, on one hand have our sort of existing, real world environment. On the other hand, we also have to deal with the sort of ever increasing complexity of our target environments. And this is something which is important.

And I think one thing also the mobile app part, and one thing we shouldn't under underestimate is while there are new ways to, for instance, manage access to that types of applications, such as cloud servers is we still have to manage the users. And from a user perspective, the cloud service and all the other services still are silos. So we have to, in fact, sort of more silos, not less silos, we have to solve problems for sort of ever increasing complexity here with a growing number of silos, et cetera.

So moving ahead, it's, I think also interesting to understand how our identity and access management style scenario is changing. And when we look at this and we hear a lot of talk about, okay, there's on one hand, there's the consumer identity management on the other hand, their sort of the enterprise identity management. What I personally see is when we look at it from various perspective, and I just picked the administration identity and access and the authentication part as two examples, these scenarios, they are not that different.

So they are not as identical, but they are to a high degree. They are similar. So when we look at, for instance, the administration of identity and access, we have the complexity of processes. So from low to high, we have the scale consumer identity management has a higher scale employee identity management has probably a little bit more complex processes, but we shouldn't ignore the fact that even for our consumers, we must have a lifecycle management, not as complex, maybe as for the employee, whereas for partners, it might be very similar from a complexity perspective.

When you're on the other hand, look at the indication part. We have the area of strong and adaptive authentication, where we have high requirements and strengths and adaptiveness adaptiveness. In the sense of, if someone has a weak authentication, he might not access everything. And we have the flexibility in the sense of how many different types of authenticates are supported. And when we look at this, we have a situation where booths have a very high requirement on strengths and adaptiveness. Also for consumer identity management, we need to be adaptive.

If this a higher volume business transaction, it must be support. On the other hand, we have clearly even more demand for flexibility in consumer identity management, but also high demand in the employee identity management. So what I wanna point out is it's not that with all these changes, we are facing connected devices and things and whatever cloud and mobile and social that everything is changing, changing, and we can just do another identity management.

No, what we need to do is we need to do still have a strong for the foundation. This is the point, which is very important. We need to balance this needs. We need to balance the need of security compliance versus agility and cloud.

So we need a strong foundation on this foundational sort of the core identity management and identity access governance with identity provisioning and governance, where we then can add extended services, such as privilege management and data governance, where we then can add first services, such as app force indication and where we then can add additional services such as access and Federation. And then we can use this foundation to scale out, to support new requirements, cloud mobile, social, but clearly without a strong requirement, a strong foundation, we will fail in that.

Okay, let's move ahead to the next slide. One other thing we should keep in mind. And I think this is also important. It's not only about managing the identity and the access. So we have access governance and we have identity provisioning. But what we also need is we also need layer where we can then start managing the underlying systems. So we have all these systems and what we need to do here is we need to support also this sort of lower level environment, the entitlement and access governance or data governance layer.

We need to understand what is really happening at the level of the particular system. So the thing we really need to add is we need to add the level of entitlement and the access governance or some call it data governance. So our cold term Analyst tend to create their own terms with the entitlement and access governance term. This helps us then to manage all the various layers of security. So this is the situation we are facing.

And, and this situation, we have sort of two sets of requirements. We have traditional requirements and we have modern requirements and together they make the requirements for a modern and robust, robust identity and access management. So these traditional requirements, there are, we need to support connectors, connect to systems, still a challenge. It always will be one of the major challenges we need to support processes in a very well sought out in a very flexible way, creating new processes, cetera. We need to support self-service interfaces for the users.

We need to support access governance capabilities. And with the modern requirements, we need to also support it for the cloud. We need to be more scalable because there might be far more users right now. We need to be modular. We need to integrate, we need to move to data governance as well.

So we, we have to extend what we are doing. And we have to sort of look at not only the traditional, we think people, but we understand what is happening and we have to do it for all users. So going very quickly above. So the next part, we have to move to a concept which I call prevent, detect, respond beyond sort of just sinking people, managing people towards detecting and responding. So we are in situation where we have to support a changing environment on one hand.

And we, on the other hand, we have to support this in a way which is more flexible than ever before. I won't go into detail trust for, for the reasons, for the sake of time into the seven fundamentals for future identity and access management. But clearly it's a situation where we need a strong foundation to scale out, to support more types of identities, more types of a indications, etcetera. You will find all the details on the seven fundamentals in my blog. So if you look at blocks, could call.com.

You can search for my blog around the seven fundamentals for future identity access management. So start with your foundation, but look at that, you can scale it out and start in Westing now because identity and access management, it's an investment.

Yes, but it helps you mitigating major risks. And this is what we really needed to do here. So trust us very quickly to my last slide. In my last slide, I'm looking at the, the fact that we never will be able to solve every security problem, but with some decent investment we can solve a lot. And the most important part is we don't need to become perfect in security, but we need to do create a good baseline and a major element of this advance, the access management identity access governance. We need to create a baseline to mitigate our risk to cover.

So the cost must not be higher than the cost of risk medication must not be higher than the cost of incident, but we need to move forward in that thinking. So this is the reason why we need still a strong foundation for identity access management, identity provisioning, access governance. When we are moving to our sort of future challenges right now, I will hand over to Alexei who will do the second part of the presentation and dive into the details of Dell identity manager, seven Dell Alexei. I'll make you the moderator right now. It's your turn. All right. Thank you very much, Martin.

Good morning or good afternoon, everyone. Once again, Alexei bono. I'm one of the product managers within the Dell security group. More specifically around the identity dais management product portfolio. Just wanna make sure here the slides are, are, are everything Go ahead. All right. So we get started well, Martin bar, some really, really, really good points around the, the whole concept of connected, connected technologies, connected roles. So if you see it today, more and more worlds, it's more connected than ever. And the opportunities for business are becoming extremely unprecedented.

And in connections that create opportunities for your organizations, you know, that allows you to perhaps entire new markets be able to perhaps adopt new technologies and that would make your company even more efficient, you know, more productive, the reduced costs every day. You know, every customers that we speak on, on a regular basis, regardless of what kind of identity and access management projects that they have, there's always an end goal. The end goal is that to increase efficiency or, or productivity obviously reduce costs.

And some of the comp complexities that, that they have had in the past, you know, when you see it, you know, how do they become innovated in, in, and get these new up and running technologies and be able to adopt this and often enough, you know, it becomes the core of any business ability to take advantage of these opportunities, right? So the it infrastructure or the folks that there the, he normally are, are the ones that have to have to deal with it.

In fact, it becomes their daily job in order to do that, cuz you may have a, a department of sorts that want to be creative and initiate a a and start utilizing technology that once upon a time wasn't part of the it infrastructure. And therefore now they have to be able to adapt. They have to be able to nimble and be able to be able to manage that new infrastructure in the same way that they have managed the, you know, more specific on-prem solutions. They in the past with the same type of compliance initiatives that they had in place.

So that's obviously become becoming a prevalent and then, you know, what do you have? So how do you help business to take advantage of those opportunities in a very secure and compliant way?

And, and I think Martin brought up a really good point to the fact that you still need to have a foundation in place regardless. What kind of technologies that you bringing in-house or any of these opportunities that are, that are pertaining to, to, to your organization. Right. You're trying to introduce cloud cloud is prevalent mobility, virtualization, big data. The concept of, of non-human identities is becoming prevalent as well. So how do you take that from a business standpoint, those opportunities and you bring it in from a very securing compliant way.

Well, you still need to have that foundation in place, regardless if there's a, a regular identity or nonhuman identity. The concept of being able to provision to be able to auto create these remains the same.

I mean, there is, you know, the difference is, is the type of the identity that you're managing and how you going to approach and who individuals. But at the end of the day, you still need to be able to automatically create these accounts and, and give them the proper access that's required.

And, and obviously you need to meet the ongoing challenges that, that you have from, from your organization standpoint, which is the never ending, you know, drum beat of threats. You know, we have threats on an ongoing basis. Compliance is number one in everyone's list.

You know, no company wants to have their name on the front of, of, of the, of the newspaper because of lacking compliance. But at the same time, there is definitely that need to be able to take on and adopt new technologies in a way that you haven't done before and things have to change. And because if you think of it, you know, on the right hand side here, have those kind of building blocks of kind of looking like security styles that create risk well that could potentially impede your business.

Innovation is because things have to change, you know, in the olden days from a security before even cloud or bring your own devices or any other type of the motivations. You often enough had to lock down parts of the enterprise, right?

If, if individual users requested access to certain type of application, you basically lock down that application and only provided that type of level of access that was needed. Sometimes from a compliance standpoint, you held, let you have to lock down those that the, that application to the point that it almost became unusable and, and it didn't have that business factor that the end users really wanted to take on that.

And, and you had that, that balancing as I think Martin mentioned the whole balance of security and compliance is what you have to deal on a regular basis. Right? Do I fully secure and become less compliant or do I become fully compliant? And I lock down to the point that I can't really be, you know, provide my end user community was something that is, is, is valuable for them. And how do I, you know, reduce the complexity and so on.

So from a Dell one identity manager perspective, we've spent the last 18 months really looking at this and looking from an identity management challenge, what are some of the challenges that our customers had faced in the last few years, not just using our own technology, but what other technologies that we, that they already had in the past the past, right?

And then obviously complexity and cumbersome of, of these tools became really prevalent as, as we spoke with these customers, the fact that it was difficult just to, to merely being able to onboard, you know, active directory or, or a one or two applications became a very complex and cumbersome job that at times it didn't scale. Right?

And with now with all these other different applications, you know, the, the concept of, of consumer identities coming into place, where you're now having to trust the identities from, from other sources and, and provide that flexibility for them to come in to your identity management system or to your self-service mechanism to gain access to certain type of, of, of tasks or application, it became prevalent that we had to change. And one of the things we were extremely proud of is with the release of version seven, is that we truly now offer a very modular and integrated platform.

So it's, it's a platform where that we deliver extremely scalable approach how identity and access management, but not just from a pure identity and access management sort, the ability is to enable organizations to currently leverage, leverage what they have and expand from that. So going back to the roots, not really, you know, not, not going away to the fact that, you know, provisioning still tends to be a stronghold from an identity user lifecycle standpoint, but how do, how do you have that initial basis and then grow from there so that you can start adopting cloud applications?

So you can start adopting, you know, the whole essence of these non-human identities, whereas these, you know, number of devices that are growing exponentially out there and requires the need for you to be able to manage in a way that you did from, you know, olden ways from an identity and access manager standpoint, the whole lessons of how do you unify and secure entitlement accents and, and, and external accounts privilege. Another area that is becoming extremely prevalent now is the fact that how do you provide that layer of privilege account governance, right?

There's lots of those applications already out there that deals with the concept of past we're voting, where you take a, a privileged account and you put in a vault, and then you provide certain access to the individual users on a request basis. And you obviously audit and, and you also have the flexibility of even, you know, auto log to the individual servers and things so that people perform certain tasks, but where that, where does that governance come to place? Where does the, where can you actually fully validate, discover?

Where are those, you know, where do you actually have to be able to put in a risk factor for that particular privilege account so that you can, and, you know, take that, that governance to the next level and say, listen, do you really need to have, does that individual really need to have access to this? And so on in order to perform their task, you know, how do you extend the functionality of the product as well?

You know, often enough you have identity management systems are there that are kind of dispersed. If you look at, from that, from a broader perspective, some products are specific to just the user provisioning or the user administration side of the house. And others are more, you know, take a step towards more of a governance to be able to just manage, you know, certification campaigns, role management, and so on.

How do you incorporate all those, all that functionality into one, one platform that allows you to expand, not just from an identity standpoint, but as Martin mentioned, how do you, how do you bring in the entitlements and how do you have have that whole, you know, be able to provide that governance that layered of, of compliance over your structured data over SharePoint, other over perhaps now the more, the higher growth of, you know, more and more customers are using cloud as, as a method of storage, their unstructured data. Well, so how do you take it to the next level?

How do you know be able to manage that functionality? And, and, and that's kind of an area that we're really spent with seven, oh, to provide this really modular, integrated platform to move forward, to really help the business from a responsiveness and, and full agility. I'm gonna spend the next kind of two slides here, just kind of walking through some of the, what has changed. I'm not sure what the, the, the audience is. If you have any knowledge of our product set in the past, but for those that have some sort of intimacy with the product, I just wanted to highlight next two slides.

Some of the changes that occur that really is gonna help us get to that next stage. And as customers embarked in this identity and access management project, they can feel that they have the, the, the right product and platform to be able to grow with their needs and, and, and so on. So one area that is kind of a core that we actually know. So what has changed into the product? The database scheduler is kind of the core it's, it's one of the, it's an engine that really processes the jobs within the identity management product or Dell one identity manager.

The product itself its task is to process the, the large number of jobs that gets created on a regular basis. For example, you know, if, if I'm bringing in an HR feed from an authoritative source, that HR feed comes either automated or via flat file import, whatever process that may be, it has to come into the identity management system. The identity management system has to kind of parse that job and it has to process. And that's one of the things about agility, right? About how do you pro process data faster?

How do you be able to then incorporate or bring in other applications at a faster pace into your identity management environment? And we've spent a lot of time and with the help of a lot of our customer base to change the way things so that, you know, so that we can start, we can be able to better scale as new items became prevalent part of the identity management cycle. So we changed the concept of being a multi-threaded.

So it's, the database schedule is a fully multi-threaded has full multi support. It has the smart within the itself to determine the available resources on that server on the database server.

So he, it can allocate the necessary number of threads that is required to process the jobs at hand. So it's not just being able to say, okay, it's a multi-threaded capability, but often enough, if you have a multi-threaded, you know, application, it, it tends to consume the resources on a particular server.

So we took that next level of steps to say, we need to figure out here what, what best suits, you know, and really get the smarts and working conjunctions with, with the database out there so that we can better utilize those resources so that we can process data much faster and realize enough fast to deliver any type of deployment standpoint. Another area that I think Martin kind of alluded in the fact that now more and more cloud applications, new applications are popping there every, every day. There's kind of new.

And how do you become nimble in a way that you be able to connect to these target systems?

We kind of re standardize the way we do our connectors in, in, from a connector module framework standpoint, so that we have have a standard method that is adhered by our obviously development team, our professional services in our partner ecosystem, so that if they create, if there is a need, if, for example, we don't have a native connector for a particular application out of the box, we provide the, the, the tools and mechanisms to help us internally to quickly create and have that connection, establish that connection point with that target system, or perhaps a partner or even, you know, part of an engagement standpoint.

The idea behind this is that we have this unified connector framework that allows us to kind of have a repeatable process in the sense that if it's created, it's created based on the standards that we have provided, it can be reutilized on a different project.

It, it can then become productized in a much faster ways, and therefore allows that the whole, you know, the whole modularity of the product and that, that allows to scale with the needs of, of new applications that are coming out, or perhaps the concept of how do you tie in with new devices and so on that is gonna become more and more prevalent as the time progressed.

Another key area that we've we've, we kind of looked at this as well, is how desynchronized data, you know, most more provisioning and deprovisioning standpoint, you know, as Martin mentioned is still core, any type of identity, the access management project, regardless if you're trying to do governance, or if you're trying to do other things that perhaps are more prevalent to you, you still need from a pure identity identity, life cycle management.

You need to have that if you're not able to provision, if you're not able to synchronize with that target system in a, in a very easy and, and intuitive way that you can potentially browse that and, and, and make the, the necessary changes in what kind of attributes that is relevant for the synchronization. Well, everything else is, is going to fail.

And we, you know, that's an area that from a lot of vendors, it gets overlooked because often enough, it's pushed.

It's an area where you push that from a professional service standpoint that, you know, folks, you know, hands on, on a keyboard type of thing, hammering away, we kind of, you know, we kind of took a step back in this and trying to analyze and said, well, how can we, you know, with the growing needs of new applications and the fact that more and more we're trying to empower the, the user, the end user to do more, what they have, how do we make changes to the product that allows this to be an area which in the past has been kind of a trouble scenario, right?

Any, if, if you look at, from any identity management products or, or projects in the past an area that is that adds complexity is the, is when you're trying to connect to a target system and having to synchronize those, those target systems into identity management repository, and then the ongoing synchronization of those attributes as they fluctuate from one environment to another.

And as you starting to do, you know, as you manage, start managing those target systems from an identity and access management standpoint, so really look at how, how do we make, first of all, how do we make things a bit easier in the sense that, you know, so we've created a wizard driven approach, which is a centralized client that, that incorporates the connectors, the native connectors, the, the flexible connectors that I call.

I mean, like the types of connector, like ado or, or a database type of connectors that has the flexibility of connecting to various flavors of different databases, you know, create that mapping browse the ability to simulate changes prior of actually a synchronization job.

You may think that it's kind of like cool and so on, but it, it is, it's incredible the amount of time and effort that folks on the field that are deploying technology, that when they're, you know, trying to configure these, these connect, connecting, or connecting to these target systems and not having the ability to test or simulate what the outcome is going to be prior of actually running a synchronization job.

And often enough, when these synchronization jobs fail, then almost becomes a troubleshoot nightmare for you to be able to type, diagnose exactly what has failed and, and why a certain attributes are not coming across as expected. And so with that in mind, we really spent time, not only trying to make things easy, but putting more infrastructure in place that it helps expedite and then have the ability to actually, you know, simulate some of these changes.

So you can actually visualize from a report standpoint, well, how exactly those that synchronization take place and indeed those attributes so that we can actually grow and then have that a successful synchronization job in a much effective way, another key area, as well, as you can see, as from a growth standpoint, as you know, we talked about Martin talk and I briefly talked about the connected world as new business need to, you know, take opportunities. You need to be able like your identity management system no longer can be just that, that silo.

As you mentioned, that silo there that manages your infrastructure, you have to be able to open the doors so that if you already have other processes, if you already have other business processes in place, then you need to take advantage of that. There's need, there's need to be a collaboration between the identity management system and these other business processes that you already have in place. And in the past, it was very cumbersome to do that because it was kind of the isolation.

There was no method of being able to actually lay in, tap into particular or specific functionality that, that an identity and access management product provided. An example that I give you is, is the simple as a risk, right? Most identity and access governance technologies have a concept of a risk where they have built in risk analysis. And as you create a role or as the user, the, the identity starts fluxing or through the identity access management repository, the risk index that that person can grow, right.

If I give him access to a sensitive document, the risk of that individual user has increased. If that individual user perhaps is a CIO of, of a company, of, of a financial institution.

Well, and he's accessing certain types of data, well, his risk obviously's gonna be higher than every day, Joe, that is not accessing a sense of information. Well, how do we take that information that is being established via the identity and access governance management tool and utilize that externally, right. I may already have some other process. May we have some, some multiple, some other compliance initiatives that I need to be able to obtain the report on those? How do you do that?

Well, it's difficult now with version seven, we really, we really wanted to open the architecture, the product. So we fully built upon rest API architecture where you can't, you know, not only increase the security between the components within the product, but also enables customers to author their own applications or, or utilize particular tasks from the product for the business process. Right?

Another core area is UI web, UI extensibility, more and more, you know, you know, as, as you're, you you're, you are introducing new applications could be cloud, could be big data, could be maybe human identity into your identity management practice. There has to be an easy way for you to be able to empower the business users, to perform certain tasks. If governments and compliance is, is a driven initiative within your organization.

Well, you are gonna have to need to identify those business owners. You're gonna have to, there's gonna be a need for you to create these certification campaigns where those, those business owners or applications owners would then have to validate the individuals that have access to those applications on a regular basis. A task that often enough, when you see in, in many different customers is still very much driven via a spreadsheet.

You know, you know, how do you incorporate that into a, in a very unified web phase that is kind of persona based that basically as an end user, if I'm coming into the Porwal to the self-service Porwal Porwal to request specific items, it is a nice and intuitive way for me to be able to go in and get that information. But if I am more of a, you know, if I am a application owner, or if I am a business owner that I require to do some sort of certification campaign, well, the, the, the web interface itself needs to be, has to have that look and feel in, in an easier way as well.

So that I come in here and I can quickly perform my tasks and, and, and move on to what's next. So that I increase agility, a business agility, you know, overall, and the whole idea of being able to then even if more and more companies are allowing individual users to bring their own devices as well.

Well, we need to have that flexibility within the product to allow for, for, for the mass number of different devices that everyday users have, they're disposable and still be able to access and, and perform the specific tasks.

So if I am that application owner, and I'm on a tablet running from one from one business meeting to another, actually have the flexibility, obviously, you know, from a, from a, within regards, from a security standpoint, but have the flexibility be able to access the self service or the certification Porwal in this case and perform the task, regardless of the actual form factor that I have in place, right? And the last but not least here is the, the whole idea of componentization of core components.

This is huge from an architecture standpoint, it extremely differentiates us from, from any, any other vendor in the space is that we've taken the approach, that we are providing a flexible way to install core and unco components in the product. It simplifies installation. It's a very marginal approach, the sense that we can easily introduce new modules within the product without having to reinvent the wheel, have to rev the product. Right? So for example, I can say is the data governance portion of it.

We're basically the only vendor of there that has a tightly integrated data governance offering, which basically is a module, is a specific, is a module that is built specific for unstructured data that gets embedded into the Dell one identity manager of version seven. And it utilizes the governance layer within the Dell one identity management pro product to provide that governance layer. So there's, you know, two aspects. I think one is that we're doing the, the full analysis, the access control analysis to identify where users have access and how they've gained the access.

But then because of that type module integration, we leverage the governance layer that comes from Dell one identity manager, and then we can then create those certification campaigns. We can create those adaptations and also then incorporate segregation of duty rules.

So that as a user, from a self-service standpoint, if I'm asked and require access to a certain type of data, or which perhaps is, you know, access to a share, that gives me ultimately access to a bunch of content for a particular project, we could have these rules and policies in place and say, well, if I have access to this, I should not have access to these this other shares. Well, because there's some conflict or compliance conflicts in place. So that becomes a very easy and methodic way of approach.

And the same thing goes from a priv privilege account governance standpoint is that we can correlate and tie in with not only our own privilege user access management product set, but be able to then manage these privilege accounts from any external source and still provide that governance layer O over that and to my last slides here. So I just really just kind of reiterate more of the fact of our execution principles.

You know, we've really made some significant changes, not on the core product to be able to have that more modular approach, to be able to be able to grow with new needs the market needs.

And then, you know, as you starting to, you know, if, if, if you start from a simple, as, you know, having that flexibility to a customer base, or to say, if I want to start with a certain aspect and then grow from there that opens up the door now, because you can easily start from as, as simple as mainly managing, you know, active directory, doing user and group provisioning of active directory and doing some sort of governance or compliance of groups and distribution lists to grow into other cloud applications, or perhaps privilege or bringing in unstructured data in a flexible way.

You don't have to bite everything at once. It can be easily done in, in, in chunks in the way that you can't execute in a proper way.

And right, so the path of kind of governance is it's is we provide you that ability to, to look at from my identity access data. And so on the lockdown of those privilege and accounts, it is the whole goal is, you know, business driven approach provide business the line of business with the ability to, to do the things unified way of, you know, compliance, really providing visibility to the company in every step of the way.

And as, as already mentioned before, and a very modular approach that you can start anywhere and build from there, and not only connect from other Dell hardware or software applications, but then start connecting to these other opportunities that you may encounter as your needs grow. And with that, I'm going to, I thank you very much for the time. I'm gonna turn this to Martin for the Q and a, Okay, thank you. Alexei. We have already a number of questions here, and I'll directly start with these questions.

So if you have questions, just enter these questions into the go to webinar control panel, and then we pick it kind of pick up the questions. So the first question I have here is when do you plan to publish the SDK for Dell one identity seven oh, and when will be the SDK connector framework be available? Very good question.

So, so, you know, as, as I already mentioned, I, as I mentioned, the whole lessons of the connected module framework was our initial way to actually starting standardizing the way that new connectors are created internally. And then as we exposed externally, we do have the midst of a NDK already available for the connectors. We have a internal project right now that we're actually kind of testing the waters within.

Whereas the first time we've been able to provide a different team within the, the, the company, a total team that was not part of the Dell, wanted any management development team to actually go in, create a set, a new set of, of connectors based on a new standard policy. Our, our, so there are some documentations in place. Our goal is to round out and have a, a much better process. So I would encourage you to reach out directly to me if you, if you have any more specific questions around that, and we'll be more than happy to walk you through what we have and what our plans in the future.

Okay. Then there's, there's sort of more, more, I would call it housekeeping question. You will sort of the copies of both slide X will be available later by tomorrow at the could call life website where you have registered for the event. So could call.com/events. When you go to our, this, when you will find copies of both Slidex question I have here from various attendees is what about a migration pass from version six to version seven? Very good question.

So keeping that in mind, knowing that as, as I kind of mentioned through the fact that there's some really core architecture changes between version six X and version seven, we have taken that initiative and we have actually created a migration module. And going back to the whole modular nature of version seven is that with, that allows us to create modules that are sometimes external to the, the product processes. Now let's keep that in mind.

It is a, it is not, I'm not gonna say is that push button and, and voila and things are done, you know, step 1, 2, 3, it is a migration module that is available, the migration module. It, it helps you with the overall migration process, but it also helps you identify customizations that have to be taken in consideration prior to the entire migration process. We have lots of customers in, as far as version five is still active and, and therefore, you know, a lot of things have changed from one version to another. And especially now from six X to version seven.

So I would encourage really to kind of look at the things, you know, from what has been customized and understand the customization points and how that has been translated to version seven, to, to make those necessary changes and mitigate risk during the migration process. Okay. When talking about migration, another question which came up from various attend is, are there migration tools or any other type of support to move out of other I identity access management systems.

So migrating from some other systems to Dell, one identity manager, We per se don't have anything, no specific tools per se. We have a good partner ecosystem in place. So we have various certified Dell, one identity management partners that have done several of these kind of migration from, from different identity management platforms into Dell, one identity manager. So I would, I would encourage you just to maybe reach, reach out to me externally, be more than happy to put, to explain and, and put perhaps in contact with the right necessary folks. Okay.

Can you say a bit more about the governance of privilege to access in one, tell one identity manager, do you certify the access to the target systems the user has, or do you work with Wal? Sorry, what was the question again?

Martin, Can you say a bit more about governance of privileged access and one identity manager? Right.

So, so that's the whole essence of this modular approach is that we can go in and start creating specific modules specific to, to different the needs, right? So we have, so the data governance is one actually is the best showcase when it comes to that. We're implementing that and it's highly integrated.

Next step, we have what's called a solution accelerating in place, which brings in which predominantly has been a work that we have done predominantly with our own privilege user access product, where we, we integrate these products together in a way that the privilege accounts are, are in the Dell, wanted identity manager.

In the sense that if you're asking a, from a self-service standpoint request of, let's say, I need to access a certain server or route account of a certain server to change a print queue, being able to actually have that account from a self-service standpoint, have the individual request go to an approval process. And then at the same time, have the, the actually application or a server owner where that individual would then either understand who has access to that, to be able to run some sort of certification campaigns, either remove or, or maintain those users, maintain access to that.

So that we already have in place. We actually, there's a, what we are in the midst of making some changes in enhancements as well. And it will be a dedicated module, is that I'm not sure if you're aware, but we also, we just release our, the latest version of our privilege user management platform as well, called safeguard. And with that, we are now also creating a dedicated we'll be creating a dedicated module specific to the safeguard platform. Okay. Next question is that's Dell one identity manager still work seven versus work in contraction with active roles server. Yes. Correct.

So, OK. Active role server is the Dell's Okta directory delegation and administrative tool. And it's still look at Dell one identity manager. One it's connector is a active role server connector. That's available out of the box. OK. Is data governance part of the product From a off? So data governance is a tightly integrated offering.

So from, from a, a license standpoint, it is not part of the Dell one identity manager license. It's kind of an add-on, but the add-on itself, it's, it's one product it's part of the framework. It's it ships with the actual product itself is the simple ability for you to enable that specific portion of the product and incorporate unstructured data management and governance with your identities. Okay. Identity though one identity used as a service catalog.

Yes, there's lots of, we have lots of different scenarios that we have integrated Dell, one identity manager in the past. Once, you know, a lot of folks have used ServiceNow, other types of service catalog, where we've actually done an integration at that level.

And, and Dell one becomes the, the fulfillment mechanism in, in the back end or customers that don't have any third party tool as well. They can easily utilize Dell. One's it shop concept to create a service catalog for self-service request, Okay. Reaching the top of the hour and the end of our webinar.

So we still have a number of questions left and Alexei bono will follow up on these questions that individually with the person who have asked these questions time right now to thank you for attending this script call webinar, thank you, Alexei for your presentation and the answers to the great number of questions we have. So thank you to you all. And hopefully we have you soon again, as a participant in equipping a cold webinar or in one of our upcoming events. Thank you.