# Agent Security & Identity (Part 1): Who Are You, Who's Your Agent, And What Should They Be Allowed?

DevFeed: [Agent Security & Identity (Part 1): Who Are You, Who's Your Agent, And What Should They Be Allowed?](<https://devfeed.tech/articles/agent-security-identity-part-1-who-are-you-who-s-your-agent-and-what-should-they-be-allowed-93920.md>)

Original publisher: [Read original article](<https://hackernoon.com/agent-security-and-identity-part-1-who-are-you-whos-your-agent-and-what-should-they-be-allowed?source=rss>)

Author: Alejandro Saucedo

Published: 2026-10-21T20:24:35Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [LLM security](<https://devfeed.tech/topics/llm-security.md>), [Security](<https://devfeed.tech/topics/security.md>), [Open Policy Agent](<https://devfeed.tech/topics/open-policy-agent.md>), [Keycloak](<https://devfeed.tech/topics/keycloak.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [service-mesh](<https://devfeed.tech/topics/service-mesh.md>)

Tags: [access-tokens](<https://devfeed.tech/tags/access-tokens.md>), [actor](<https://devfeed.tech/tags/actor.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-identities](<https://devfeed.tech/tags/agent-identities.md>), [agent-identity](<https://devfeed.tech/tags/agent-identity.md>), [agent-memory](<https://devfeed.tech/tags/agent-memory.md>), [agent-orchestration](<https://devfeed.tech/tags/agent-orchestration.md>), [agentgateway](<https://devfeed.tech/tags/agentgateway.md>), [agentic-identity](<https://devfeed.tech/tags/agentic-identity.md>), [agentic-identity-broker](<https://devfeed.tech/tags/agentic-identity-broker.md>), [agentic-security](<https://devfeed.tech/tags/agentic-security.md>), [agentic-systems](<https://devfeed.tech/tags/agentic-systems.md>), [agents](<https://devfeed.tech/tags/agents.md>), [agntcon](<https://devfeed.tech/tags/agntcon.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-ethics](<https://devfeed.tech/tags/ai-ethics.md>), [ai-identity](<https://devfeed.tech/tags/ai-identity.md>), [ai-security](<https://devfeed.tech/tags/ai-security.md>), [api](<https://devfeed.tech/tags/api.md>), [arcade](<https://devfeed.tech/tags/arcade.md>), [hackernoon-top-story](<https://devfeed.tech/tags/hackernoon-top-story.md>), [identity](<https://devfeed.tech/tags/identity.md>), [security](<https://devfeed.tech/tags/security.md>)

## AI overview

The article argues that agent security needs distinct user (subject) and agent (actor) identities, plus separate controls for in-cluster access and user-delegated third-party access. A shared bot token obscures attribution, requires broad permissions, and makes individual revocation difficult. Zalando's open-source Agentic Identity Broker addresses delegated access by storing users' encrypted provider tokens, recording scoped, revocable grants, and exchanging credentials through a trusted gateway; it does not provide human login, agent identity, or gateway enforcement. In the described KAOS design, Keycloak supplies user and agent identity, a gateway and Open Policy Agent enforce resource access, and a network policy blocks routes that bypass the gateway. The author emphasizes fail-closed decisions, the availability cost of a required policy service, and that authorization does not prevent poisoned tool output or prompt injection. Agent-specific identity standards remain unsettled, and the broker's documented production use is limited to Zalando's internal platform.

## Source excerpt

Part 1 of a 2-part series on agent identity and security