[APPLAUSE] Well, good afternoon. So I was with you at this conference in December of last year. I stood on this stage in Barcelona. And I made a couple of comments. The first comment was that the unification of identity could transpire to be one of the most important security defense trends that we'll ever see.
The second thing I said was we're innovating at One Identity. We have all of the pieces of the jigsaw puzzle necessary to start integrations, but not integrations for integration's sake-- integrations based on real-world use cases, real-world problems that you, our customers, and our partners are having that cannot be solved by one identity vendor.
What we're going to do today is we're going to double down on some of those messages. I'm going to just do a quick reminder of what we mean by unified identity. Where are we going with this? What is the vision?
But very quickly, I want to get into some real-world example of this in action. True to my word, the team at One Identity over the past 10 months or so have been working with their partners and customers in the field. We now have many, many examples of the 1 plus 1 equals 3 that I mentioned last year.
We put product A together with product B. And now we can solve problems in identity that were not able to be solved before. So I'm going to give you an example of that. And I would encourage everybody in the audience to talk to our representatives this week about other examples. There are very, very many.
And then I want to get into the relative importance of all of this. Again, I made the statement, the unification of this stuff could turn out to be even more important than we think. I want to talk about some industry trends that we've been tracking very closely over the last year or so and that we're already seeing are having a material impact on the threat landscape and that can really only be solved-- we can only really start to resolve these issues when we think about a unified identity platform.
So let's get into this, the unified identity vision. Not going to spend too much time on this. I think pretty much everybody in the audience is familiar with this. But here's how I think about this.
The CISO and their team have a lot to think about. If you look at any of the industry standards, NIST, for example, there's a lot to think about in security. There are a lot of domains. We could be talking about data loss prevention. We can be talking about endpoint security, SIEM, threat intelligence, forensics. You name it. There's a lot of domains.
Identity is one of those domains. So maybe it's one of 30 things that a security team needs to think about. Given that that's the case-- it's one of 30 things-- how can we justify as software vendors, as producers of this, that actually, it's four things. It's five things. We have customers that have 50 data repositories all looking at identity.
As an architect, I think about that as unacceptable-- inefficiencies, gaps that create opportunities for cyber criminals, expense, not just in license costs but in support costs, and finger-pointing between vendors. No, no, no. This is not an access management problem. This is a privileged access management problem. Different vendor. Not my problem.
This is unacceptable. In the complex world of security, with a security team that have, again, 30 things to worry about, identity should at the very least be only one. So what we talked about last year was the fact that at One Identity, we've been collecting the tools for the toolbox. We believe we now have pretty much everything we need from a technology perspective to create a comprehensive identity solution.
We can think about who the user is, what the governance needs to look like. What policies and standards does this organization need to comply to? We can think about access management. How do we want people to access our systems? What forms of authority will they have? What kind of authorization will they have?
We can think about privileged access management. Who are the special users that really do have the keys to the kingdom that need that extra attention and governance? And we can protect our Active Directories.
So right now, these are products from One Identity. What we've been doing, as promised, over the past year is innovating to bring these things together and create that 1 plus 1 equals 3 that I mentioned. Now, I want to get to the main theme of the presentation today. So I've just got one example to show you here. But I think it's a good example of unification in action.
This is a real-world story-- in this case, a chain of restaurants, about 600 stores across 45 states in America, the challenge being we don't just have Microsoft. We have AD. And we have OneLogin. We also have Linux and Unix platforms. We also have robots. They have identities as well.
How do we unify the provisioning and, importantly, the deprovisioning of all of those identities in a cohesive way? And how do we do that within a governance framework that complies to the regulations that are important to our business. And how, at the same time, do we take all of the manually intensive labor that is traditionally associated with all of this and strip all of that back to save money as well?
Turns out, the answer was a combination of two of the products that I just mentioned. This is an integration between our OneLogin access management product and our Identity Manager IGA product-- two products tightly interfaced, one support contract, one vendor solving a problem that no other vendor in the industry can solve.
You want two vendors to solve it for you,
33:38