Anthropic just announced "Agent Identity" for Claude Tag.

Anthropic just announced "Agent Identity" for Claude Tag, allowing enterprises to give AI agents direct, independent permissions to internal systems like GitHub, CRMs, and Data Warehouses. The industry is cheering. Security teams should be terrified.

Applying legacy Identity & Access Management (IAM) to autonomous AI agents is a fundamental architectural mismatch. An API token only verifies who is asking. It cannot verify what they are actually trying to do.

If your Claude agent is given write-access to your engineering repo, and it suffers a prompt injection attack or simply hallucinates a destructive command, your standard security policies will wave it right through. Why? Because the agent's "Identity" is valid. The token clears.

You cannot secure synthetic workers with access tokens. You have to secure their execution paths. This is exactly why we built Sevorix. We don't rely on identity tokens to stop rogue agents. We deploy a Rust/eBPF sidecar that intercepts the agent's outbound system calls at Ring-0 (the Linux kernel). We evaluate the actual semantic intent of the payload in <20ms. If a permitted agent goes rogue, we physically sever the TCP connection before the data ever leaves the host.

Trusting an AI with a badge is not security. Containment is security.

Source article:
Read the report on Help Net Security →