 Thank you so much. Well, listen, without any further delay, I am so privileged to welcome our keynote speaker who's going to be talking on the theme enterprise ready identity for SaaS apps. Please join me and warmly welcoming our Chief Product Officer for Workforce Identity Cloud, Arnaw Bose. Hi everyone, I'm super thrilled to be here today with you all on the second day of our Dev Day 23. As Michael introduced me, I'm the Chief Product Officer for Okta's Workforce Identity Cloud. And my session is going to be all about helping enterprise SaaS app builders figure out what does it mean to build applications that are enterprise ready and what are we seeing our workforce identity cloud customers expect from these SaaS applications. Thank you everybody for joining us here in person today at our San Francisco HQ and for all of those who are dialed in via our live webinar as well. So with that, we have to cover our famous safe harbor slide. There's going to be a couple of forward looking statements in my presentation. I'm going to talk about some features that are not yet generally available in production and all this legally says is please make purchasing decisions on generally available product. So with that, let's first take a step back and see what kind of trends are we seeing when we take a look at how our customers are leveraging SaaS applications in their workplace today. Okta publishes a businesses at work report based off of data we collect anonymized data we collect across our 17,000 plus customers. And this is available as a free download. There's going to be links and the Dev Day team is going to sort of send this out to you all so you can look at the data in more detail. But as the head of product for workforce identity, this report is always super interesting for me because it showcases things like what are the fastest growing app categories in use in the enterprises today. Where are we seeing enterprises invest in terms of choosing more SaaS applications or a diversity of SaaS applications, as well as if there are any business spending shifts. So places where we see a spike in investment after the pandemic or places where people are no longer investing in as as they look to modernize their businesses. So this is a good place for us to start as we sort of think a bit about what does it mean to build enterprise ready apps because we should take a look back at the data to see what enterprise apps are being used by our customers today. So if you look at the 2022 data, the standout category which is seen the maximum amount of growth in the last year is travel. So apps like Trip Actions, which is now called Navan are ones where we're seeing a massive growth in terms of total number of enterprises adopting them as well as number of users year over year. And this is probably not surprising to you all because post pandemic business travel has opened up. We're seeing more businesses sort of traveling to meet coworkers who might be remote as well as customers and partners. In fact, travel from our data is up to even higher than pre pandemic levels. It's not even going back to pandemic levels. It's even higher than that. Other than travel applications, our standout category last year was design software. So collaborative design software like Figma is a good example that had seen a lot of uptake that continues to grow at a massive rate year over year. I think it's to the tune of 36%. And that trend is continuing on in our customer base today. So really interesting data for everybody who's a SaaS app builder in the audience today, whether in person or live on the webinar. Good for all of you all to just take a look at this to get a sense for where our customers investing their budget today in terms of like spending on SaaS software applications. The other thing that's really interesting to take a look at is what is diversity of SaaS applications and use look like in market. We first started tracking this data as part of our businesses at work report in 2016. And compared to the 2016 numbers, you've seen the diversity of applications grow twofold. So it started out at about 100 apps in 2016. Now if you look at customers who have 2000 employees or more, it's gone up to 211 apps on average. So again, like good indication that even with the current macroeconomic headwinds, customers want to go ahead and buy off the shelf software to go solve real business needs. They're seeing value out of that and the diversity in terms of number of apps being used in the enterprise is only growing year over year. Another interesting thing to sort of double click on is like different categories. So I talked a little bit about travel apps being a category or design software being a category. Security tool adoption is another place where we're seeing significant increase in spending. So there was a 23% year over year increase in terms of number of customers looking at security tool adoption. And there's some really interesting stats in the data as well. It showcases that tools that help customers roll out new security training or help drive up the use of better security best practices. These are almost like training and tutorial products. That saw a massive increase in spending as well. So again, super interesting to take a look at this data to get a sense for across our customer segments for the various app categories, where are we seeing adoption rise, where are we seeing spend rise in the market. So that's great from the point of view of app builders. Like as an app builder, you're seeing that the diversity of apps being used in the enterprise today is increasing. You can get a sense for like where is the spend happening across the different categories. But if you now switch gears and look at this problem statement from the point of view of the economic buyer or the customer rolling it out. The customer's life is actually still pretty complicated. It's taking them about 30 days on average to roll out a new application and do it in a way that meets their security and compliance bar. Doing it in a way where their end users are able to easily adopt the application. And that's where we believe the opportunity lies. There's definitely a customer need and demand to go deploy SaaS apps, solve real problems. But there's a friction point here today where buying, deploying, rolling out and driving up adoption of that app is still not as good as it should be. It still kind of stuck in the 2010s. So just to kind of summarize this chapter of the keynote, we want you all to take away that SaaS app adoption is rising rapidly. You can again look at the data we have across our customers to get a sense for where do we see the adoption? What kind of organizations and what size are adopting? What kinds of applications? It's clear that buying applications is still the winner in the build versus buy debate. This is awesome. Like if you compare this trend to maybe like 15 or 20 years ago, most enterprise apps were homegrown. They were sort of built in-house. They were on-prem. It's changed to SaaS, which is awesome for all of us and for the end users and customers as well because they're getting an always-on, always up-to-date service. But there are higher expectations from IT teams who are deploying these applications. They want to ensure that their security and assurance levels from a sign-in and authentication point of view are met. They want to ensure that their compliance requirements in terms of not creating identity silos are met. They want to ensure that outcomes like automatic access, automatic provisioning is met so that they're not doing repetitive and manual work. These are some of the concepts that we'll dive a bit deeper into in the rest of the keynote and then through the rest of the day to day. The keynote's going to tee up. What does it really mean to build an enterprise-ready app? What does it mean to build an enterprise-ready app from an identity and security perspective? And then our follow-on sessions will cover things like, okay, what does Okta IT do internally in terms of app selection and rollout? And what do we recommend SaaS app developers look at when they're building applications so that they can be adopted by enterprises effectively? So with that, let's take a look at a tale of Bhavna and Arnab. So you met Bhavna yesterday. She's our CTO for our customer identity cloud. But in this story, she's going to be an up-and-coming SaaS app developer. She's got a cool new startup that's building a new application in the design software category, which was like a super-high-growth category last year as well as this year. And probably something that's been in the news for you all with Adobe's acquisition of Figma that's still kind of going through the regulatory process. And then I'm going to play the role because I'm on the workforce side. I'll play the role of an integrator admin working at a global systems integrator. So I'm working at a GSI and that GSI has a contract at Authco. Authco is a fictitious Fortune 500 company with a lot of complexity in their deployment. And what I'm doing is I'm helping them modernize their heavily on-prem deployment, figuring out how they can sort of increase their maturity on the zero trust curve, helping them adopt modern SaaS applications. So I'm the integrator and implementer and Bhavna is the app developer. And both of us are working for or trying to sell into a customer, which is a Fortune 500 company with hybrid architecture who wants to modernize their security posture. So with that set up, let's take a look at Authco's environment and the issues that Authco faces today. And again, like looking at our customer base of customers who would have like 2,000 or more employees, this is like very, very common. This is something that I see almost every day in my engagements with these customers. They tend to have complex hybrid identity deployments. They'll have some level of identities existing in on-prem sources like Active Directory that hasn't changed a whole lot over the years because you still need to maintain your AD instances for things like printers and devices and all sorts of other infrastructure. It's pretty hard to get rid of completely. Or they might actually have HR systems that are sources of record like Workday or SAP Success Factors. And that's what the standardized HR tool in use looks like at these companies. They have compliance officers and chief security officers who want to stay abreast and remain in compliance as identity standards and security outcomes change. So they're looking at things like the White House mandates on zero trust. They're looking at the NIST guidelines on AL assurance. Again, for some of the developers and folks in the audience, you guys might be like, hey, I want to stay focused on building a killer product in my category. I don't want to understand all of these random acronyms Arnab is throwing at me. And that's perfect because that's the outcome that we want. We want to ensure that developers and builders can stay focused on delivering value. And some of these complexities that are unique to enterprises are things that can be abstracted away and achieved automatically. And then finally, one other topic that I see very, very frequently is shrinking or static IT budgets while the number of employees and number of applications and number of tools is constantly growing. So overworked IT desks and help or support desks is very, very common. And so sometimes what happens is even if a particular product or SaaS application is extremely useful, extremely high value for the customer, they may not be able to actually roll it out because of the amount of support it's going to take and the support costs involved. So that's something to consider as an app builder as well as as an integrator as you're rolling out a change in a company. If you look at Bhavna's challenges as an app developer, again, I talked about some of these in my previous, on the previous slide. She wants to stay focused on building a killer experience that differentiates her design software product from others in market. But she's having to support these diverse personas where there's maybe an IT admin or an integrator rolling out her app versus an economic buyer who's choosing to buy the app. She needs to achieve things like single sign on and integration with identity providers. She needs to achieve things like a higher assurance security outcomes by supporting things like continuous authentication. But she's not an expert in those things and she wants to achieve these outcomes fast. From the point of view of Arnab as an integrator, you know, I'm helping the customer simplify their hybrid on-prem infrastructure. So I'm looking for options where I can move more workloads to the cloud in a fast efficient way while achieving all of the security outcomes that the customer was used to when they dealt with on-prem or legacy infrastructure. So how do I do that in a way which is consistent, which is repeatable, which is fast, and make my customer successful? So now that you've got the setup about the two sort of personas of the app developer as well as the integrator both working for Authco, here's our kind of way of thinking. There's Enterprise Readiness 101 for these applications, which are things like supporting single sign on and integrating your application with standard identity providers. And then ensuring that your application is available in enterprise app catalogs so that as an integrator or as an IT admin who's like quote-unquote installing the app for an enterprise, it's super straightforward. You can go ahead and get it from a catalog and hook it up to SSO and you're good to go. So these are two very basic steps. And then if you look at a slightly more advanced steps, there are things like ensuring that your application supports provisioning via standard protocol like SCIM and then supports advanced security outcomes like single logout. So SCIM will give you things like as and when a user joins a company or maybe they move within departments, it'll allow integrators and admins to automatically assign that application to the end user correctly and remove cumbersome manual processes like filing an IT ticket or calling into a help desk to get access to an application. So this is where maybe we can dive a bit deeper into like what does Okta provide in this space to sort of complete that end-to-end journey. Okta's workforce identity cloud focuses on customers who have employees, contractors and business partners and these customers need to connect those end user personas to the right tools and applications. So we provide a platform like the Okta integration network which is an app catalog that SAS applications can publish into and we make things like setting up single sign-on in a phishing resistant, secure manner, super straightforward, setting up things like these joiner mover, lever provisioning processes super straightforward with our life cycle management and workflows products, getting to governance outcomes around who has access to what and access requests super straightforward. But these are highly specialized identity and access management use cases which again like as an app developer you shouldn't have to go ahead and solve for yourself. You should have the tooling that available to you off the shelf that allows you to build an app that automatically plugs into all of these outcomes. And this is where Okta's customer identity cloud comes in and yesterday's sessions were probably focused a lot more on the first bucket here on consumer apps and digital experiences. But customer identity cloud is also focused on delivering amazing tooling for developers to build SAS apps. So they already provide tooling today where you can build a SAS app that plugs into SSO via SAML or OIDC correctly that supports things like pass keys correctly and then there's a few more things coming in the future. So this is a good place to kind of like go into the actual end to end journey and this is kind of like the meat of my presentation. I'm setting up what the enterprise readiness journey looks like across developers as well as integrators and whereas a developer you should focus on customer identity cloud and whereas an integrator you can sort of leverage the tools within workforce identity cloud to effectively roll out apps faster and in a more secure manner. So the first step is, you know, we have odd zero for startups. This means that as a startup, if you have 25 or fewer employees, you can get customer identity cloud for free and start building today. If you build your identity and authentication stack on customer identity cloud, there is already SDKs and tools available to ensure that your app can support single sign on via OIDC and SAML. And if you support one of those protocols, you're effectively automatically plugged in to the rest of the workforce identity cloud outcomes around password list and phishing resistance and so on and so forth. But the CIC team or the customer identity cloud team is not stopping just there. They're also going into some of the 201 level outcomes. So one of the things that they're working on this year that should be out by the end of this calendar year is support for single logout. What this means is you've got single sign on, but let's say there's a security change, right? Like the enterprise has some sort of endpoint protection tool on all of their company-issued laptops and R&OPS laptop that has malware on it. When some of these things happen, customers want those end users to be automatically logged out from every application and not rely on the session lifetime within that particular app. So this is a security use case that we've seen come up more and more often in enterprises. And if the application supports single logout or universal logout, it makes it super easy for a customer to go and configure workflows or other policies to go ahead and terminate that session. The second thing that the CIC team is working on is skim protocol-based provisioning. So again, like there'll be SDKs available later on this year where if you build your SaaS application using the Octa customer identity cloud stack, you will be able to support provisioning and it'll mean that when your application is installed or used by a customer who's also using workforce identity cloud or actually any other IDP in this case that supports skim, the customer or the integrator can go ahead and write automatic joiner mover lever processes to be able to reduce any manual tasks required to assign applications to the right people. So the goal standard here is as an enterprise application, as AUTCO, the way ARNUP, the GSI would set up their environment would be connecting AUTCO's identity provider to an HR system of record, like workday or success factors. It'll mean that whenever a new employee joins, that employee will automatically get an account created in the identity provider and then based on attributes like what department they're joining or what level or role they're joining, you would have automated processes that assign the right applications to them on day zero. So on day zero when that employee boots up their laptop and goes to the Octa dashboard, they'll start seeing your enterprise SaaS app if it's supporting provisioning correctly. After you've done those two steps, the next step is obviously publishing your SaaS app to the Octa integration network and from that point in time onwards you're kind of off to the journey of the integrator or the IT admin. The integrator gets to go ahead and install the app off of the OIN and then they can go ahead and build out policies that are advanced like, okay, what are all of these lifecycle automation use cases you want to deploy? What are some of the rules you want to use to go ahead and build out continuous authentication and trigger a single logout based on risk changes? And those are all kind of available today via our workforce identity cloud product with our LCM and workflow solution and workflows again, like we already have workflow templates that do things like help you do single sign out or single logout against Office 365, Google Workspace, Zoom and a bunch of other apps. So the macro takeaway here is as an app builder, you want to drive faster adoption by plugging into these standard processes and you want to increase your serviceable market. Like if you're trying to sell into an enterprise that's security conscious, that's compliance conscious, they're going to want things like standard SSO support, standard skim support and the CIC product helps you sort of build that natively into your application. So that was a lot of content but hopefully the journey made sense to you all. And what we want to do is ensure that everybody who is an app developer or a builder is well set up for this journey. So what we are doing right now is, you know, we've had the odd zero for startups program available for a while. We are doing a special promotion for everybody who's joined us here for Octa Dev Day, whether in person or online to ensure that not only can you get odd zero for startups, but you can also get Octa's workforce identity cloud solution as well. So if you sign up via this QR code, you'll get a registration and sign up page which will allow you to sign up not only for odd zero or CIC to build your applications identity stack, but it will also allow you to use workforce identity cloud for your own internal employees as well and it will help you sort of test out that entire end to end journey. Of what does it mean to go ahead and build your app using Octa's customer identity cloud? Go ahead and build some of the advanced capabilities like skim provisioning or single logout as they become available later this year. And then actually publish that app to the Octa integration network and use it yourself. You can use your own app yourself and see, okay, does this actually deliver differentiated outcomes in terms of easy provisioning, join or move or lever use cases? Does it actually deliver on the outcomes of continuous authentication? And you can see all of that live in action. And hopefully that will help you go ahead and build the business case for why is your app differentiated from others in your category when it comes to being enterprise ready? So that's the big call to action sign up today. And with that, I'm going to pause and end my keynote. That was the big message I had, which is build enterprise ready apps. Customers want more SaaS apps in their environment. There's a lot of diversity and there's a lot of growth in terms of utilization. And then if you look at tooling, you've got amazing tools with customer identity cloud to go ahead and build your application. And you've got amazing tools with workforce identity cloud to go ahead and leverage those differentiated enterprise ready features. All right, thank you so much for the time.