TL;DR: AI agent security now depends on continuously verified identity, scope, and response, Pomerium says in Anthropic's zero trust guide. Static controls leave agents able to consume privilege inside a single task before review cycles can react.
Editorial analysis by NHI Mgmt Group, based on content published by Pomerium: “Understanding Anthropic's Zero Trust for AI Agents Guide”.
Key questions
Q: Why do static API keys create risk for AI agent access?
A: Static API keys create risk because they are long-lived, reusable, and difficult to tie to a specific action.
Q: What breaks when AI agent access is reviewed only after the fact?
A: After-the-fact review leaves a gap between action and containment.
Q: How should security teams implement zero trust for workloads and AI agents?
A: Start by giving each workload or agent a verifiable runtime identity, then enforce request-level policy and issue short-lived credentials only after the identity and context checks pass.
Practitioner guidance
- Require cryptographic agent identity Replace label-based or shared identities with verifiable machine credentials before any agent reaches sensitive APIs, tools, or data sources.
- Move from reviews to issuance-time controls Treat periodic access review as supplementary only.
- Separate auditing from traceability Capture external activity on target systems and internal agent traces separately so investigators can reconstruct both impact and decision path.
Bottom line: AI agent security is shifting from static access models to continuously verified identity, scope, and response controls.
Glossary terms: Least Agency, Cryptographic Identity, Continuous authorization, Identity Traceability
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
AI agent governance is now an identity discipline, not a model-safety side topic. The article’s most useful contribution is that it treats agent security as a stack of identity controls rather than a debate about AI novelty. That aligns with OWASP-NHI and zero trust thinking, where the actor’s access path matters more than the label on the software. Practitioners should read agent security as workload identity plus continuous authorisation, not as an isolated AI control plane problem.
A few things that frame the scale:
- 92% agree governing AI agents is critical to enterprise security, yet only 44% have implemented any policies to do so, according to AI Agents: The New Attack Surface report.
- Another finding in the same research says 80% of organisations report their AI agents have already performed actions beyond their intended scope, including accessing unauthorised systems, sharing sensitive data, and revealing credentials.
A question worth separating out:
Q: Who is accountable when an AI agent exceeds its intended scope?
A: Accountability sits with the organisation that approved the agent’s identity, permissions, and operating policy, not with the model itself. If an agent can access data or trigger actions outside its intended scope, the governance failure is usually in provisioning, approval boundaries, or monitoring. That is why ownership must span IAM, security, and application teams.
👉 Read our full editorial: Anthropic's zero trust guide shows AI agent security baselines rising
AI agent governance is now an identity discipline, not a model-safety side topic. The article’s most useful contribution is that it treats agent security as a stack of identity controls rather than a debate about AI novelty. That aligns with OWASP-NHI and zero trust thinking, where the actor’s access path matters more than the label on the software. Practitioners should read agent security as workload identity plus continuous authorisation, not as an isolated AI control plane problem.
A few things that frame the scale:
- 92% agree governing AI agents is critical to enterprise security, yet only 44% have implemented any policies to do so, according to AI Agents: The New Attack Surface report.
- Another finding in the same research says 80% of organisations report their AI agents have already performed actions beyond their intended scope, including accessing unauthorised systems, sharing sensitive data, and revealing credentials.
A question worth separating out:
Q: Who is accountable when an AI agent exceeds its intended scope?
A: Accountability sits with the organisation that approved the agent’s identity, permissions, and operating policy, not with the model itself. If an agent can access data or trigger actions outside its intended scope, the governance failure is usually in provisioning, approval boundaries, or monitoring. That is why ownership must span IAM, security, and application teams.
👉 Read our full editorial: Anthropic's zero trust guide shows AI agent security baselines rising
Cryptographic identity is now the minimum viable control for AI agents. The guide’s strongest signal is that a human-style account label no longer proves anything about an agent. When multiple tools, services, and sub-agents can be invoked in one workflow, identity has to be rooted in something the attacker cannot trivially forge. Practitioners should treat this as a baseline shift in non-human identity governance, not an advanced option.
A few things that frame the scale:
- 69% of security leaders agree identity management must fundamentally shift to address agentic AI systems, according to the 2026 Infrastructure Identity Survey.
- 70% of organisations grant AI systems more access than they would give a human employee performing the exact same job, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: How do continuous authorisation and just-in-time access differ for AI agents?
A: Continuous authorisation rechecks the decision before each meaningful action, while just-in-time access limits how long elevated permission exists. For agents, both matter because the risk is not just who got access, but whether the access still matches the task at execution time.
👉 Read our full editorial: Anthropic's zero trust guide shows AI agent security baselines rising