See How Cross App Access (XAA) Works

AI has brought a new wave [music] of security issues as agents move between apps, often operating without the same identity governance and control as human users. >> [music] >> Enterprises are signaling that they need their vendors to help to solve this. They want the cross-app access protocol [music] integrated into their stack to provide the visibility and control necessary before purchasing or renewing their software. The time for B2B SaaS builders and AI platforms to [music] adopt cross-app access is now. So, let's talk about it. What it is, how it helps you win business, >> [music] >> how it works, and how to get started. AI is the biggest [music] opportunity in enterprise tech with AI agents driving companies' road maps. [music] But, with enterprises now asking their vendors for real enterprise grade security, [music] tapping into that market potential is a real hurdle. That's where cross-app access comes in. Cross-app access is the new open protocol, [music] also known as the identity assertion authorization grant. It's built as an extension of OAuth to secure [music] app-to-app and agent-to-app connections. As enterprises generate their own AI agents to automate [music] work, they operate without the same restrictions as human users, connecting to more data sources with less predictable patterns than traditional apps, [music] and no real oversight. This can cause real chaos like over-privilege risk, authorization gaps, and compliance challenges. >> [music] >> When agents and apps become more interconnected, the unsecured links between them become [music] a primary attack vector. Customers are asking for a solution, one that cross-app access provides. Cross-app access shifts access control [music] to the identity provider, so connections align with enterprise policies. When app builders and AI platforms [music] adopt it, it works across the entire ecosystem to make trusted connections possible. Cross-app access eliminates [music] critical security risks by replacing risky hard-coded tokens with robust identity-based controls. [music] It delivers better user experiences by removing frequent consent prompts that slows user adoption down, and it helps you scale faster. >> [music] >> You can build once to deploy across any customer environment to become a stickier [music] trusted part of the enterprise ecosystem. Let's look at how cross-app access [music] works. First, with a closer look at the problem. Today's consent model puts too much responsibility on users. >> [music] >> When Jane logs into her SaaS apps, every integration prompts for consent, and every yes can expose [music] data. The result is consent fatigue for users and blind spots for [music] IT. Even when enterprises use MCP to connect internal agents and systems, [music] authorization still happens at the user level, relying on user consent [music] and scattered app approvals. As an extension of the MCP spec, cross-app access shifts that control [music] back to IT. Instead of users granting access, the enterprise defines policies for which apps and agents can talk to [music] each other. No more redundant consent prompts. No hidden connections. Just simple, centrally managed, policy-driven control at the identity layer. The IDP [music] centrally governs agent-to-system interactions using centralized policies >> [music] >> and lifecycle management. IT can see and manage every connection from [music] agents to enterprise apps. Now, when an AI agent or app requests [music] access to another system, it follows a standard three-step handshake using the [music] identity assertion authorization grant or ID Jack. The requesting app takes the user's [music] ID token back to the IDP. The IDP issues a temporary ID Jack credential >> [music] >> based on enterprise policy. And then the app exchanges that ID Jack at the [music] resource apps authorization server for a final access token. Whether the connection is internal or external, this flow remains [music] the same ensuring every agent to app interaction is identity verified and policy governed. But what does this look [music] like in practice? Let's look at the four primary ways this protocol can secure the ecosystem. Starting with an external app connecting to an external resource. >> [music] >> Imagine an employee using a video conferencing app needs to create a task in a CRM. Through cross-app access, the video app seamlessly clears the ID Jack handshake to get an access token for the CRM. Enterprise IT gains full visibility into how these two third-party platforms are interacting. >> [music] >> Next, let's look at an internal resource to an external app, a capability available to Okta customers. >> [music] >> Here, a custom internal HR chatbot needs to fetch documents from an external [music] content management system. Even though the agent is homegrown, it uses the [music] same cross-app access flow to prove its identity to the external provider ensuring internal bots follow the same security rigor as human users. Now we can see this used for internal agents connecting to internal resources. >> [music] >> In this scenario, everything stays within the enterprise perimeter. That same [music] HR agent might need to pull data from a private employee directory. Cross-app access allows enterprises to build powerful [music] custom automation that connects enterprise agents to internal APIs securely [music] replacing hard-coded secrets with dynamic identity-based trust. Finally, >> [music] >> let's see an external app connect to an internal resource, another scenario available to Okta customers. This is a game-changer for legacy modernization. It allows a third-party [music] tool, like a messaging app, to securely push data into a protected internal CRM. >> [music] >> By bridging the gap between the SaaS tools your employees love and your private infrastructure, cross-app access secures your internal APIs from the [music] outside world. 95% of orgs [music] say cross-app access would improve their confidence in deploying AI. If you're building SaaS, cross-app access helps you win. [music] It shows enterprise customers you can meet their security and governance requirements from day one, accelerating deals and making your integrations easier to trust and adopt. [music] This is how you stand out in a world moving to AI-driven agentic [music] workflows. If you're an Auth0 customer, cross-app access is available out of the box with no [music] custom code required. You can act as a requesting app or a resource app and seamlessly integrate with any customer's identity provider that supports [music] the standard. Reach out to your Auth0 rep to learn about our early access program. [music] Cross-app access empowers your customers to unlock AI agents securely, bringing trust, control, and [music] confidence to every connection. Together, we can build an open, secure ecosystem [music] where innovation thrives safely and at scale. Contact us or visit us online to get started today. >> [music]