Yes. First of all, thanks for the invitation to be here today. It's great to be talking to you. We -- at Okta -- I see we have a slide up here. So our mission is to enable everyone to safely use any technology. And our core business historically has been the business of authentication, of making sure that when a human is logging into a piece of technology that, that person is properly authenticated and it is who they say they are. And over the years, that mission has gotten more and more important and also more and more sophisticated.
So what used to be basic login has gotten into advanced step-up capabilities like multifactor authentication, 2-factor authentication you're familiar. And then as multifactor starts getting compromised through threat actors and cyber-attacks, we get into nonphishable multifactor, which is if you send someone an e-mail for a token or an SMS as a token, someone can intercept that and then use that and log in on their behalf. So how do you provide nonphishable things like biometrics? So how do you do a face ID or a thumbprint scan for your multifactor?
So our business has gotten -- has advanced to get more sophisticated on those fronts. But really, what we've seen overall and really in the past 2 years is a shift from the industry and our customers viewing identity as primarily a functional tool to identity being, first and foremost, a security tool. So today, depending upon whatever source you read, north of 80% of cyber-attacks start with some form of compromised identity. And so the problem of securing identity has never been more important. As threat actors are busier than ever, state-sponsored threat actors are busier than ever, our business has become more important than ever.
And then in addition to that core workflow I described in securing identity and authentication, the introduction of nonhuman identities is becoming increasingly important. So in addition to people that are authenticating, most systems that are out there, most technologies that are out there are deployed with something called service accounts. These are machine-to-machine accounts that APIs use to log into applications and log into technologies. And historically, customers, companies have not been great about securing the credentials for those accounts. And so service accounts can and are frequently used as a threat vector for actors to get into systems and create trouble within those systems.
So our customers are being increasingly mindful of how they secure their nonhuman identities. And that includes things like, for example, knowing where they are. So we've added a product to our portfolio this year called Security Posture Management -- Identity Security Posture Management. This tool scans customers' networks and identifies all the systems that they have deployed in their networks and identifies which machine accounts, which nonhuman accounts are configured in those networks to make them aware of where those credentials lie.
We then have a product called Okta Privileged Access, which allows them to take the credentials for those service accounts and manage them in a vaulted fashion where they're securely managed and they can be rotated. So we can cause them to make sure they're changing those credentials over time. Historically, once these service accounts were created, they were typically hardcoded into config files and hardcoded into APIs and never changed. And so they were really significant threat vectors.
And then we have an Identity Governance product, which also allows customers to provision and deprovision those machine accounts only when they're needed. So you shouldn't have a machine account that can be used or taken any time. It's when you're in a workflow and then you need to take action with that account, you want to have it turned on and then turned off immediately after it's completed. So our space has evolved in those areas with new product offerings that have helped customers solve related problems.
And then on the developer side, as people are developing custom applications, they need to manage identity for their users. They also need to manage authorizations. So it's one thing to know who an individual is. It's another thing to know what that individual is allowed to do and what data they're allowed to access.
You can think about this as your Google Workspace login. If you log into Google Workspace, when you log in with your username and password and multifactor or your passkey, you're coming in and you're authenticated. But then once you're into that account, we look at the problem of what you should have access to, what documents do you have privilege to read to edit, to comment. That's authorization, having fine-grained authorization.
Our Auth0 platform allows developers to build both authentication and fine-grained authorization for the systems that they're building and to manage their assets. That is increasingly important to your question about how does AI impact all of this. As people are developing new agents and developing agents in AI, it's very important that they can secure those agents from the get-go. So as they're developing in the beginning, they can use Auth0 with our new product that's in preview right now called Auth for GenAI, which allows them to build credentials for those agents that are properly vaulted and stored and to call APIs -- having the agents call APIs in a protected way as well.