Zero trust AI agents demand a different kind of security
Teleport's Chris Webber argues zero trust must extend to AI agents through trusted runtimes with zero initial privileges and continuous per-action enforcement.
In an interview, Teleport VP of Product Marketing Chris Webber says point-in-time authentication and static least privilege fail for agents that act fast, unpredictably, and continuously, sometimes spawning dozens of clones with the credentials of the human who invoked them. Teleport Trusted Runtimes give each agent a unique attestable identity, zero starting privileges, and expiration after task completion to eliminate standing privilege and stored data. Teleport Identity Security monitors agent actions against declared objectives in real time, intervening up to termination and runtime destruction, replacing anomaly-based ITDR detection with continuous enforcement.
Zero trust has a big AI agent problem ahead
Experts argue agentic AI undermines zero trust: chained authorized actions create exfiltration paths, unregistered agents evade identity controls, and agent-to-agent messages stay opaque.
Security practitioners including Nik Kale (CoSAI), Krti Tallam (Kamiwaza.ai), and Mike Wilkes (Aikido Security) argue that agentic AI breaks zero trust assumptions because individually authorized actions can compose into unauthorized outcomes, such as chained reads and writes creating an exfiltration path. Most enterprise agents are unregistered shadow IT or third-party launched, subagents inherit privileges without recognized identity, and agent-to-agent communication, sometimes embedding instructions in media files, remains invisible to security teams. Proposed mitigations include short-lived delegated credentials modeled on OpenPGP subkeys, rate limits, sandboxing, approval gates, and immutable activity trails.
Google’s $10,000 refund test shows why AI agents need zero trust
Google released an open-source zero-trust reference architecture for AI agents defending against prompt injection via signed database writes, gVisor sandboxing, and deterministic gating.
Google's demonstration, built on the Agent Development Kit (ADK) and Gemini, shows a customer support agent that could be manipulated into issuing a $10,000 refund on a $149 order and exposing environment variables via AI-generated Python. The architecture adds three security layers outside the model: cryptographic signatures on database writes verified via Cloud KMS backed by Cloud HSM, gVisor sandboxing of generated code with network egress disabled, and a Semantic Gateway applying deterministic checks to prompts and tool calls. It treats system prompts as insufficient boundaries because prompt injection, prompt tuning, or model updates can change agent behavior.