Good afternoon, ladies and gentlemen, welcome to our webinar. The fast direct to regulatory compliance, lean efficient, and user-centric access governance. This webinar supported by ware I E. The speakers today are Laurel BES who runs the international business development of ware and me Martin equipping around principle Analyst at, before we start with our webinar, I just want give you some quick background information about cooking a coal.
Some housekeeping information could call is an independent mutual focused and globally active Analyst company, where offices in the us, in the AP region and, and Europe, we are focused on identity and access management, information, cybersecurity, risk, and compliance, and other topics concerning the digital transformation. We support our customers with three types of services, which are around content communities and change.
So we do research such as our clinical leadership documents, where we compare vendors in the products and certain market segments, such our executive view reports, our leadership briefs, and many others.
We do events such as conferences, webinars, and other stuff, which I'll touch in a minute. And we deliver advisory to our customers, particularly on the strategic angle, the choice of tools and related areas, advisory support, benchmarking, strategy, support, architecture, support, technology, selection, and project guidance.
All strictly went on neutral, assisting you in defining your strategy, roadmap, picking the right products, policies, guidelines, related stuff. We have also a series of upcoming events with our flagship event, European identity conference taking place May 14th to 17th in Munich. You should not miss that event. And then we have the autumn, a couple of other events, such as our blockchain enterprise days, the digital finance world, our cybersecurity events and the consumer identity world. We'll find more information at our website and hope to see you at one of these events in person.
Then for the webinar itself, some housekeeping information, you are muted centrally, so you don't have to mute our yourself.
We are controlling these features. We are recording the webinar and the podcast recording will be available by tomorrow. And there's a Q and a session at the end.
However, you already can start entering questions. The more questions we have that more likely the Q and a will be. So don't hesitate to enter your questions now that we have an interesting lively Q a with a lot of questions for the agenda of today. This webinar is most called webinars to three parts. The first part, I will talk about the current state of IHA and specifically access governance. So focus a little bit on lessons, learned of what works, what causes problems in projects, and also look a little bit at potential alternatives for architecture.
Then the second part, all current of level, where we'll talk about and approach and demonstrated showed us approach for a fast for access governance that works standalone integration with existing IGA and identity provision tools, and also service.
Now, part three, I already managed to be the Q a session looking forward to that. So as an intro, so I'll touch five, five topics. As you can see at the bottom of the slide, I'll, I'll touch the compliance. I'll talk about that. All is about access I'll talk symptoms of IMD is about an IM blueprint and architectural options.
So at the beginning, I, I wanna quickly touch the, the difference between compliance, audit security, and these are fellow different things, but from a business perspective, at the end, it's important to obviously be compliant to pass the audits, but what really counts at the end taking the right actions. So compliance in that sense means that you meet laws and regulations. And this is a must, but just meeting loss and regulations might not be enough audit on the means that you're doing what you say, you are doing it, that you can historically prove it.
But it's about historically proving.
It's start about meeting what is happening right now. Action is what you actually do, which might be the same. You tell the auditor, which might be more than utility. The auditor even might be something different than you tell the auditor audit compliance, as you all know are tightly related, but post don't really make you secure. It is something which helps you because it helps you identifying challenges, identifying risks, working on mitigating these risk, but what really helps is taking the right actions.
And so you always should think beyond trust meeting and passing, audit, meeting regulatory compliance requirements, try to get better and do what your business really needs. And when we talk about access and access is our topic for today, then we are talking about access first access.
First, I think, as we all know, today are business risks.
We need to have control about these. We need to understand these risks. And the challenge we we are facing is that inappropriate access directly can lead to sometimes free business risks. If you look at some of the larger incidents at financial institutions, then we had the situation of inappropriate access, sometimes putting an entire bank at risk, which really resulted not only in reputational risk, but in severe operational damage and factually in strategic risks. So this is that. And I think it's the other side of this thing.
It's not an it thing. So it's also about, so it helps, but we need more than that. So policies need to be followed. They need to be there first. And when we do part of our business is doing benchmarking of for instance, identity management or cyber security or whatever else in organizations that when we do such benchmarks, we look at posterior organizational and the technical aspects.
And in that organizational side, we, we very frequently observe that policies are either more or less non-existent maybe aside of one high level, outdated it security policy, and they are not complete.
They are not comprehensive. And if you don't have the policies, it's hard to follow the policy. So obviously the first thing is free to have the policies that are followed and to execute changes. So this goes beyond it, but there's the need for an, it are tools. We are lost.
We anyway, spend far too much time in all this audit related stuff. So we need to make it efficient to understand what are our risks, how to heal those things and how to get better, how to learn from that, and for recertification termination of accounts, they require business expertise, but they also need the right tooling behind. But that business expertise is very obvious.
Only business understands, oh, this person still has that. Or this person still is here. It without business, can't solve that. So having said this at the end access, to some extent, that core.
So when you look at how manager is involved in all these things, then access is really what affects the manager most, yes, he has his own daily authentication to do. He might manually authorize a few things, but more at the business end of things. So authorized, authorizing certain types of transactions, less authorizing access, but access. That is where he's really in. He needs to define who has access. He needs to access for his own daily work, and he has to review access, which then goes into the audit governance and protection thing.
And that is also important for a manager in the sense of did I do my stuff, right? I am I safe?
Did I fulfill my obligations? But access really is what, from this entire identity management thing affects him most because also part of access, review of approvals, access approvals, he's very regularly confronted, confronted with this part of it. Unfortunately, when we look at, at how identity measurement and, and I should identity access governance and, and it identity governance of precision, whichever term we use there are around the same work today. Then we very frequently can serve.
So to speak some common symptoms of harshly that I am, and I G diseases. And at the core of these things, the access reviews role models are. So there are other things in there as well. So obviously there's challenge of users complaining, cause they have too many different interfaces for access request. They have too many, or they don't have a well working sort of performance is lousy. The usability is tough because they just don't understand what they need to order, et cetera.
So that, that is one element. This is a sort of a symptom we observe below that obviously there's the need to, to get better in access requests, performance, usability, translating stuff, translating technical title and into something. The business can understand. There's the symptom of many projects start big and say, okay, right now we have this whatever, take a bank, 400, 700 whatever systems we will connect them. And then we automate everything, etcetera.
And then if you look at this three years later than whatever eight or 12 systems are connected, maybe more, but at the end, a large number of systems is not connected. And I think this is just the reality. So too big of a promise to, to really fulfill. And also that understanding fully understanding what are the systems I really should connect or so for automated provision, which are the ones I don't connect.
This are the most important thing automation, or is the most important thing to better serve the user to improve access requests, to mitigate risks.
Cetera, onboarding of users might be lengthy frequently, something which is based on the fact that we have too many of approvals in and the more you need to approve the ball length processes, but also it's a, and that's really modern automation issue. There are other aspects in what we also frequently observe missing awareness processes for movers leaders. So the onboarding process is the one which commonly works still best revoking entitlements, managing levers. So this users still here, that's where we things really become cumbersome.
So what else customers externals, etcetera, externals very, very common right now. Nowadays we are more and more confronted with this topics around, for instance, robotic process automation, etcetera. These are other challenges, there's this. And that's where we really end up with access review and grow models. I think the, the most hated thing is how a lot of the access review process of the ertification processes work today. So they are bumpy uses, are confronted with a big metrics where they need to look at a lot of things. It takes a lot of time.
It's not well supported managers, which have a lot of other stuff to do really are not big friends of these approaches. So we need to look at it and think about how can we make it smarter, more efficient, implemented, faster, make it lean as, as much as we can, et cetera. And then there's the other thing as talk, I don't know how many companies really AMA a mass of companies, many, many, many, and the ones we truly have a well working role model implemented and running and always up to date.
It's probably significantly less than a handful.
So some are half something which is okay, but in most cases, this is really complex because the models are inconsistent. They are incomplete. They are not sort of resilient against organizational change. So it is a challenge. And we need to also think about how can we make things simpler than they are. So I think it's time really to rethink. There's not a simple solution on that because we need to still need to pass the audit. We need to ensure that we meet the least privileged principle, cetera, but I think there are options that we need to just think about how can we do it better?
And even while identity and access management as a whole is, is, is pretty big and consists of a lot of technol technical elements. So when we look at our call IM reference architecture, you see, there are many, many things from directory services to privileged access management, to web access Federation.
So all the authentication authorization pieces, obviously various administration audit analytics pieces, but at the end of the chorus, what today frequently is referred as IHA. So identity governance administration, or actually combination of identity provisioning and access governance.
And there we have the identity provisioning piece, which is one. So how can I create the accounts if a new comes in, how can I grant the title lines? And we have this access governance piece, which in fact, or to some extent includes access, request, access, review auditing, and all the other things around it. And from an architectural perspective, we can integrate them or we can split these two areas. So from an audit perspective, this is a very essential focus. We see a lot of momentum also around authentication authorization.
So the entire access, so based on policies that are there's as well on privilege management, but if you don't manage the IGA portion, well, then you will be pretty much challenged by fulfilling the regulatory compliance requirements.
When you right now, take a look at, at how this architectures look like I split it up a little into four larger blocks. One of them is RA unknown. One of them is a little outside of the IGA piece. So when we look at a center of this picture, we have the access governance and we have provisioning in there, which commonly formed this, this it thing.
But actually there's a little more. So there's the management of IDs and provisioning data connectors to target systems, which might go through systems such as actually directory or directly connector systems, or which might integrate into it service management as well for, for manual provisioning.
And we have this workflow portion, which to some extent, overlaps with what we commonly find in the access governance piece, where it's about access requests, user self service requests, about access review about managing roles and entitlements, or maybe only entitlements and groups and other stuff, no roles we have to reporting piece.
And then we have on top, we have some it service management, which exists to most organizations. So most organizations have some, some piece of, of it service management endeavor. They have a Porwal. And the very important question is how do we integrate it?
How do you go from there? Which is usually more a cost grain service request, define grain requests of access. Specific applications can be a very lengthy discussion. Very interesting discussion, a little bit beyond the core topic, but this integration frequently missing.
And on the other hand, on the left hand side, we have this, what I call the ETL layer, excuse me, if we're not translating shift into layer here, ETL layer effect is something which is frequently part of provisioning at a decent level at some capabilities, which is about, you know, you got data from a variety of sources, HR out data sources, and you need first to, so to speak, normalize the data, to know which data maps to which account etcetera.
So this is an influencing, usually it's integrated, but if you have more complex environments, it might be even something where you go for really more ETL extract from low tools, stronger capabilities. There's little focus on that, but it's some of, one of these aspects in our architectural decision for today's webinar. I think the main question is, should you integrate provisioning access governance, or are there meaningful areas where you better split it?
And I think a couple of approaches where it makes sense, you should really roughly think about what to do, which way there, if you take this, there are encounters, there are many options for, for, for architecture, how you can build it. And there are some better in some worse way, but it depends very much on what you have, what you want, what you can do. So think about this very roughly. So you can go for one IHA tool, which combines ETL and provisioning access governance, or you leave access governance separately.
Particularly if you want to E two to roll out quickly or to make it sometimes also slightly more user friendly, you could use three different tools. You could try to do ITSM.
Why I am, should say, should say ITSM, why I am, which is not a smart approach. The other way around also that don't try to do identity management. That's the full extent to your it service management, but think about where to really integrate. There are a couple of criteria for such architecture decision. So the more components you have, the more operations, those integration efforts, you have the architectural complexity increasing. You might have data redundancies. On the other hand, if you have smaller blocks, you can deploy them fast or you might replace them so less lock and risk.
If you have a bump mono thing, it's harder to replace, it might be more adequate users to have more or less depending on which you either use. So there are different aspects to look at, and there's clearly that one approach, which says, why not going for particularly when it's about lean thing, you have a challenge. You need to fix it.
Now, why not go for something? Start with the access governance piece, do the lead way and move from there. With that. I want to hand over to locals from ware who will talk about an approach for fast track solution for access governance that works standalone in integration of existing IGA and identity provision tools. And with ServiceNow Laura, what's your term?
I would like to introduce myself. I am so on. As Martin said, I am in charge of the international development at ware Martin presentation actually focus on some point, which seems very important to, to us.
The first one is neither compliance on audit, make you secure taking the right action. Does the second one is access risk equals to business risk and business risk require business expertise. And the third one is we are often facing incomplete and inconsistent world model.
Yeah, basically today we are in an ever open and interconnected world. The digital transformation is changing people mind on people. Relationship. We are in a, in a world where business and it are in a fast on, I would say Peral movement. The business needs to be more reactive need to answer to the market. The information system is becoming complex on most of the time is composed of application that are in the cloud.
We have new access. So we are also in a, in a, in a perpetual movement on the it infrastructure.
On the other side, we have, we are also in a world where regulation are trying to protect people and we are facing a multiplication of this regulation. So us at clever, we, based on that, we decided to focus only on the identity on access governments, because for us to face this challenge is really complex on, I think it's, it require a dedicated solution AutonoMe solution, which as Martin said, you know, is going to be more lean efficient on really user centric.
So our mission as it's written on the screen is really to map or maintain under control it, access to mitigate risk on, on improved compliance. Our key driver actually are basically involving all the actors of the organization. It means business. It means security.
It means it, it means also to be easy, to use, easy to use for the business, easy to implement for the, it, it means also quick to implement because the key point is for an organization because we are organization are in interpret movement is really to have a visibility. So it's need to be quick to implement on, on that's.
One of the reason was why we decided to go on a stone alone solution on that. And then also to be able to facilitate all the process to meet, to meet the regulation. So let's talk a little bit about ware. So is a in I don't, the company was created in 2005 by BEJ Fisher on when they created the company, they wanted to be fully innovative in the way they develop the product was developed, but also in the approach of the IgM market. And we have been supported by different organization, which are BP excellence for security that help us in that process of, of innovation.
But more importantly is now we are one of the leader in France, and we have many customer that trust ware in which we have large company like AXA, postal, just some names. But the key point is they have been with us for a long time and they, you know, complex architecture. They have already some IM tools. They have a lot of tools, but they really needed to have a tool that was easy to use, easy to implement on satisfied their requirement in terms of visibility on access governments.
The other point in our relationship with, with our customer is every year we are organizing some user meeting, which we call clever days on the next one is going to happen in EMBO in on June 4th on one in Paris. So will happen on June nine, sorry, 18th. And we intend to create soon, some clever days in Switzerland and Germany. The objective of the clever days is really to understand the requirement of our user. And I'm not talking only about the evolution of the it and the evolution of the it integration the infrastructure, but also the behavior of people and organization.
Because as I said earlier, we have more, you know, we are really in an ongoing evolution. So it means people are really key in, in the way they want to access to the information system. So we must understand how they want to access on what are their requirement.
So it's, it means to have discussion with business is very important for us, want it to help us to anticipate, you know, to work on our, on our roadmap. And for the reason that also our major customer are, are, are staying with us is, is because we are with them to anticipate what's going to, what's going to happen. And now we have, so we have started our European development and in France, we are saying direct with the support of, of our channel outside front, we decided to sell through channels.
And currently we are, we are building up this network and of, of course we'll be part of the EIC in may. So that's, that's going to be our first big German event.
So just to, to, to start the presentation on, I think it's it's numbers on its it's. But just to give an idea is I, I took three example of survey that has been made in the last year to, to, to show how important is, is access.
Access governance is one was an with Verizon 2014, said that more than 50% of the secret incidents are Perri while the employee R and the office, the second one is, is from PWC and 26% of the incidents of security incidents are attributed to former employees on the, the last 20 is from on the recent one, say that 63% of security incidents are rate to an error or malicious section of an insider.
That shows how important is to, to have a good understanding of who has access to the information stand on to which application the other point that we faced, as you know, as a challenge for ware is digital transformation.
As I said earlier, digital transformation is, is changing the profile of the organization on also the behavior of the staff member, even in the way they're working together on, on that's implied a real reorganization of, of, of the company. And it's really global.
So because we are digital transformation brings some hyper mobility, digital transformation implies a change of work methodology, and we have a lot of task force that are created to bring value to the company, which means that they need to have specific access to specific tools for specific time on, on. So it's, it's real challenge, I would say now, but many in the future, because I think we are only at the beginning of, of beer change in, in, in the way of doing things.
And of course, that digital info in transformation as impact on the, on the it, on it is really in a fast, the non control and perpetual movement in term of infrastructure, you know, application, you know, on premise infrastructure, cloud infrastructure in term of application, it means as a service, it means application is told by the business.
It means, you know, internal development. So it's managing, managing the users is becoming more and more complex on the same thing regarding as a staff member. It's we have a lot of movement within the organization.
We have, of course at the onboarding on the departure, but we have also old internal mobility on more and more to, to, to keep people, people are changing very often of, of responsibility within, within the organization. So we can say it's really an ongoing reorganization. And then at last, as I said earlier, we have the regulation on the new regulation coming up and we, we, the company needs to, to comply, comply to that.
So it means simply that I don't see on access control as become vital for the company.
And, you know, staff member are the key factor for the company success, but they are also there also the key risk. And we it's really important to, to identify there is a life cycle governance to, to, to, to manage with, with the, with the employees. It means that yeah, there will be an evolution of the people within, within the company with the onboarding, with the transfer. And then we just be sure that when, when things are changing, there is an access of debt. And that's really key. If there is no access, an access update, we have a real, a real big operational risk.
So on that, why, you know, we, we created clever actually it's really, to, to be able to, to manage that, to manage the onboarding. It means to control the legitimacy of the newly created entities example is a registered provider, really under value contract with the organization in term of transfer, because we have a same employees going to evolve within the company. We must be sure that he's not accumulated rights when he's changing function within, within the organization, because that of course is part of the personal risk that can happen during the transfer process.
And then of course at the departure is, is to be sure that, you know, the, the, the rights of the individual living the company are going to be the activity. And we, we monitor all that, all that right on again, the key point is, is going to be, is going to be that all the actors are involved business it security because on, on the must work together on, on, on, on the way we built up our solution, help that, and that collaboration between the different department in business, it and security, to be sure that we are not missing on that.
Everybody is really proactive in, in that challenge.
So if you're looking the, you know, the, the point of, of our solution is, as I said, is it's, it's really to be easy to use for it on business. And, and we have in, in the different experiences that we had with our customer, we had a lot of support from, from develop from business, from it, from security, because they realize that our solution is helping everybody to, to reach on, to have that visibility on the, on the access governance. The other it is, is really to give, to be able to fit in the it with no change on no constraints. And we have a, we have a bottom approach.
We are going to get information from the application, and then we are going to build on that. I will show use that later on this slide, then, then of course we have to, from the function linked to, to a, which is compliance to the access review, the rectification on to be able to do so, we have to, to have really some appropriated dashboard to ensure on efficient tracking of all the government process of the identities on accesses.
So the idea is that we report are designed to answer the needs regarding the process of the different review campaign on, on provide oversight on, on, on staff movement, you know, as, as you, as I showed you earlier that the onboarding of new employees, the outgoing staff and all the transfer, so to, to, to be able to be able to do, to do so, we, we need to, to really map the identity on the access. It has to be fully comprehensive. So it means it's not coming only from the, the IM infrastructure. It's really bottom of approach. We're going to get the data from the different application on.
Then we built on the top of that. It, it, it has to be focused. So we focus on, on, on, on the risk situation.
We, we, we have to target the campaign on the change in the previous one to have to have really it's, it's, it's an ongoing process.
We have also to be agile. It means we, we must define valuable business context for the reviewer, and it has to be another very important point is, is we must have a view not only per organization, but also per resources. So per program, per application on we are able to provide.
So on, on the key points is we have now, you know, a large experience of that, of million of entertainment that are regularly re certified. We were.
So it's, we have now a very strong feedback from our, how we must do that rectification campaign to, to, to help to the business, to end the it, to have this situ to manage that on, on, on, when that is done is the key point is really to keep the control with, with collaborative tools. So it's ified the gap between the access request on the actual entertainment.
It's, it's also to ensure that access has been removed when an employee years left company check for the remain remaining undetermined after employee departure. It it's really a cycle it's to verify granted access on the, it coming to the job function it's to measure gap with business role it's to identify the SOG high, the policy regulation.
So it's, it's, I would say a sort of circle of, of application that, that we, we have to, to achieve.
So if you're looking very quickly in terms of functional architecture, so we are, as I said, it's a bottom approach. So we are going to get information from the application on, from the HR flow, from the access metrics on that, in that all that info are going to, to make the correlation on, to build up, you know, our identity on access repository.
So we are going to build up that ID, I on access repository with the help of the business, with the help of the security on the, it, it's going to be an overall process. So by getting from HR, all the mutation detection, by getting from the business, all the access model, and then we'll be able to do the access review on be able to do the remediation based on that.
So it's, it it's really an ongoing process just to just, just to, to finalize that short presentation.
And again, my intent was not to do a product demonstration, but Tru to show, to show you that the way that we built ware ERJ is, is the standalone solution that can be added on existing infrastructure with existing tool, because our target is really to give, to give benefits for the end user, which for the business to gain time, to do the access certification, to have a dedicated interface, to have a global view users on their resources for the, it is easy to modelize the organization.
And that's really a key point. It's, it's quick to integrate business application. We can start by the most critical application, and then we can in stem because it's, it's a step by step approach. So we can say, okay, that 10 application are critical for my business. So I want to be sure that I monitor the access to that application.
It has also to be data driven and then for security it's, it's also flexibility is to be able to do it's to have a global view on resources on the authorized users on for, for the partners that we're working with.
I'm talking internationally is really to, to, to, to develop a relationship with ware that help us to, to bring that benefits to the partner locally, either in Switzerland, Germany, or other countries. So, yeah, in quick, quite quick, but that's the way we have, we have big Ji. So thank you very much.
And, you know, I'm, I'm open to any question that we could have.
Okay. Thank you very much, LA, and so let's directly move to the Q and a, as I said, we will do a Q and a session right now, walking through the, the various questions the audience might have. So if you haven't entered your questions yet, then please do.
So now, so the, the one, the one question I see here is, is, is this what you're delivered on premise solution? And, and how would you position that also in that market, you have intentions around SaaS and how would you compare it to, to SA approach? Do I go for your specific approach?
And we, we, we can, you know, we can adapt in term of sense at the moment we are, you know, the customer is hosting the solution on premise, but we have the ability if we want to manage that by ourself, if it's needed.
Okay. So customers currently doing it on premise. I think also when you look at them, look at some of the targets you support, including and other systems, it's a hybrid world, but you could do, you could do it on premises.
So the other other question is what frequently observed to the market is that while larger organizations have some IHA tool in place, on the other end, the other number of larger organizations on your customer list, the impression is that many mid last businesses, despite some regulatory challenges are not, not very good in, in supporting this part by tooling. So, so do you, do you see your solution more as something targeted at the large businesses or is something which serves well also medium size businesses?
Actually, no, actually, actually it's both, it's, you know, what we are bringing is really visibility on quick visibility. So the request, if we're looking the request of our customers, it could be from different angle on, on, on, on the, we can, we can, you know, for the reason we are also addressing some medium size companies, because we are quick to implement, we are flexible. So it means for a company that are in, you know, that's something on, on, but really not are starting some IM project.
But at, at that point, the business is saying, I need to have a visibility on what's going on, on, on. So on for the reason often we are asked to, to start because we are going to be quick to implement on a specific number of applications.
So, so, so the common buyers are these more the CS or the business people, or more the it people in your case. So
If you, if you are looking today, most of the time, it's, it's starting from it, but very quickly we are connected to the business.
You know, it's like, if you're looking in the process, we, you have the RFI that will start coming from the it, but then we are very quickly implement, sorry. We are very quickly in connection with the business.
So, and when you say also quickly implemented, so what's the average time for setting up your solution?
I would say in, in three months, we can have, we can have a, our solution upon running.
Someone needs a real fast track.
Oh, it, it can be, you know, when I'm talking to that, it's going to be, it's going to depend on the number of application that we want to start with, you know, so if it can be even quicker, I was giving you an average approach, but if we have a specific need and we have to be quicker, we can be quicker.
Okay. Yes. So I think these were already a couple of questions.
We, we, we have here, so I, I trust, let me quickly look up. So there are additional questions, so, okay. Basically I think these are most of the questions we already had. So if there are any more questions, please enter these questions.
Now, maybe one point to touch. I mean, I touch it quickly. Maybe you can also elaborate a little on that.
So, so how do you, do you deal with this most entitlements or entitlements currently are described in a very technical way. They, how to understand for business use. So how do you deal with that, that a business user needs sort of a different translation of different terminology in your tool?
What do just be sure I understand the question is, is, you know, that we can have a, it view of on the business view on how we reconciliate.
So yes. Can you translate, can you transform?
So, so to speak from, from a technical entitlement, which is called XYs to a business entitlement, which means financial master data, blah, blah, blah,
That, that, that's basically, that's basically going to be done through, through the different report that we are going to work on that the business on the it.
So the business always has a business perspective while so map sort of covering the it perspective that they really can use it efficiently. Correct? Yeah. Yeah. Okay. Perfect. I think we are, as I said, we are done right now with the questions we have. So thank you very much.
All thank you for taking the time. Thank you very much to all the attendance of this call webinar. I hope to see you soon in another webinar at one of our onsite events. Thank you for clever aware for supporting this. Have a nice day. Bye. Thank you. Bye.
