Docker Rethinks AI Agent Security: The Confused Deputy Problem in a Multi-Model World

Docker·2 Sept 2026·2 min read
#docker

In a recent blog post, Docker lays out a vision for the future of AI development: a multi-model, multi-harness world where developers use various AI models and tools, not just one. But with this flexibility comes a critical security challenge: the confused deputy problem, a term coined by Norm Hardy in 1988. In essence, an AI agent, acting as a deputy, might use its own broad permissions instead of the user's limited ones, leading to unintended or malicious actions. Docker argues that current governance models are inadequate for this new reality, where every AI agent could become a confused deputy.

The solution Docker proposes is a new trust model that focuses on the interaction between the user, the agent, and external tools. Instead of giving agents blanket permissions, the model introduces fine-grained, context-aware authorization. Here are the concrete changes highlighted:

  • Granular permissions: Agents should have permissions scoped to the specific task, not the user's full access. This might involve using OAuth scopes or other fine-grained access control mechanisms.

  • Contextual decisions: The authorization should consider the context, such as the user's intent, the tool's purpose, and the data involved, to make real-time decisions.

  • New infrastructure: This requires a new layer of infrastructure that can mediate between the user, the agent, and the tools. Docker is positioning itself as a key player in providing this infrastructure, given its role in standardizing development environments.

  • Trust boundaries: Clear trust boundaries must be defined, ensuring that agents from different sources (e.g., Hugging Face, OpenAI) are properly vetted and isolated.

For developers, this shift is crucial. If you're building with AI agents, you're likely already facing issues where an agent has more access than it should, or you're hesitant to give it needed access due to security risks. This new model could enable more powerful automations without the fear of data leaks or system compromise. Docker's emphasis on a standardized runtime for these trust boundaries could mean that your Dockerfile or similar configurations will soon include security policies for AI agents, making secure (and innovative) development easier and more universal.

Source: https://www.docker.com/blog/below-the-harness-governing-a-multi-model-multi-harness-world/

Related

auto-curated · source linked above← all news