Uber’s Secure AI Framework for Autonomous Agents
Summary
Pixel’s announcement explores Uber’s Secure AI framework for governing autonomous agents across provisioning, runtime enforcement, and continuous assurance. It highlights risks such as prompt injection and goal hijacking, and explains why organizations need visibility into agent actions to improve security and accountability.
DEV Community
Secure AI Framework: How Uber Governs Autonomous Agents Across Their Lifecycle
Agentic AI could sit inside 33% of enterprise software applications by 2028, up from roughly 1% today (Source: Gartner via AI Business, 2024). In the Philippines, the National Privacy Commission already holds organizations accountable for the outcomes of AI processing and requires mechanisms for people to contest automated decisions (Source: National Privacy Commission, 2024). The gap between those two facts is architectural: plenty of teams can deploy an agent, and few can prove which agent acted, on whose behalf, and under what scope. Authorization Answers Who, Not Whether Uber's security team states the problem plainly: identity and authorization systems can determine whether a user or service has permission to access a resource, but they cannot determine whether an agent's proposed action is appropriate in context (Source: Uber, 2026). The failure modes that follow are semantic rather than credential-based: prompt injection, tool and memory poisoning, goal hijacking, behavioral drift, and hallucination-driven actions (Source: Uber, 2026). Gartner describes the same shift: with agents, the threat surface expands to the chain of events the agent initiates, which by default are not visible to and cannot be stopped by human or system operators (Source: Gartner via AI Business, 2024). A control you cannot see is a control you cannot pull. Gartner now expects 25% of enterprise generative AI applications to hit at least five minor security incidents a year by 2028 (Source: Gartner, 2026). Three Layers Spanning the Whole Lifecycle Uber's Secure AI framework covers the agent lifecycle in three layers: provisioning-time validation, runtime enforcement, and continuous assurance (Source: Uber, 2026). At provisioning, the Uber AI Registry stores an agent's identity, ownership, persona, permitted intents, constraints, dependencies, and risk tier. Argus reads source code, prompts, configurations, dependencies, exposed endpoints, and tool-invocation paths to derive intents that the declared contract can be checked against (Source: Uber, 2026). At runtime the registry is the policy administration point, AI Guard the decision point, and Agent Guard hooks the enforcement points. An agent can hold valid credentials and the user legitimate access, and the action can still be denied as outside the agent's defined intent (Source: Uber, 2026). The third layer closes the loop: a unified execution trace links actions, tool calls, and guardrail decisions, recorded interactions replay against candidate guardrails before enforcement, and automated threat modeling with red teaming feeds findings back into risk scores (Source: Uber, 2026). Identity That Survives Every Hop The identity layer is where most stacks fail. Uber's engineers found that identity models are built around humans and workloads, while the originating user and intermediate agents are dropped across hops, leaving downstream systems to see only that some service called an API (Source: Uber, 2026). Their fix: each workload fetches a SPIFFE-verifiable ID from SPIRE, then a Security Token Service mints a single-hop JWT with a specific audience and a time-to-live in the order of minutes (Source: Uber, 2026). The exchange follows OAuth 2.0 Token Exchange (RFC 8693) and embeds the full actor chain, so a gateway sees the engineer, the on-call agent, and every step between (Source: Uber, 2026). P99 latency for that exchange sits below 40 milliseconds in production, and the system is adopted by thousands of internal agents (Source: Uber, 2026). Scoped Spending Shows the Same Shape The pattern is not confined to infrastructure. OpenAI's ChatGPT Wallet, launched on 13 November 2026, lets an agent complete a purchase only after the user reviews the items, the total, and the card, then approves with Face ID or a fingerprint, which creates a record of the transaction (Source: TechCrunch, 2026). The wallet charges through a payment token that stands in for the card details, so neither the agent no...

Powered by Readybot.io