Published February 2026 10 min read

Zero Trust for AI Agents

NANDA's Zero Trust Agentic Access (ZTAA) extends traditional Zero Trust to address the unique security challenges of autonomous AI agents — capability spoofing, impersonation attacks, and sensitive data leakage.

Technical Security

Why Traditional Zero Trust Falls Short

Zero Trust Network Access (ZTNA) revolutionized enterprise security by replacing the "castle and moat" perimeter model with continuous verification: never trust, always verify. But ZTNA was designed for a world where humans operate applications that access resources. The actors are identifiable, the sessions are bounded, and the access patterns are predictable.

Autonomous AI agents shatter every one of these assumptions:

  • Agents act without human supervision — they discover peers, delegate tasks, and make trust decisions autonomously, at machine speed
  • Agents can impersonate capabilities — a malicious agent can claim any skill, endpoint, or certification without cryptographic proof
  • Agents amplify blast radius — a compromised agent with delegation authority can spawn chains of compromised sub-agents
  • Agents create invisible data flows — sensitive information can be exfiltrated through multi-hop agent chains that bypass traditional DLP controls

The NANDA Enterprise paper identifies these gaps and introduces Zero Trust Agentic Access (ZTAA) — a framework purpose-built for the era of autonomous agents.

ZTAA: Four Pillars

ZTAA extends traditional Zero Trust with four agent-specific security pillars:

Cryptographic Identity

Every agent has an Ed25519-signed identity anchored in AgentFacts. No claim is accepted without cryptographic proof. Versioned key rotation prevents compromised keys from persisting.

Capability Verification

Before any interaction, capabilities are verified against signed attestations in the AgentFact — not just claimed in an unsigned metadata document. Third-party auditors can add their own signed evaluations.

Agent Visibility & Control

Enterprise AVC mechanisms provide continuous monitoring and governance over agent behavior — what agents can access, who they can communicate with, and what data they can process — while maintaining operational autonomy.

Instant Revocation

When an agent is compromised or misbehaves, its credentials and delegation chains are revoked in real-time — milliseconds, not the hours required by traditional CRL/OCSP mechanisms.

The Delegation Chain Problem

Perhaps the most dangerous security gap in multi-agent systems is uncontrolled delegation. Consider: Agent A delegates a financial analysis task to Agent B, which sub-delegates data collection to Agent C. If Agent C is compromised, it can exfiltrate the financial data — and traditional security has no visibility into this chain.

ZTAA addresses this through:

  • Delegation depth limits — enterprises can set maximum delegation depth (e.g., no more than 3 hops) enforced cryptographically
  • Scope narrowing — each delegation step can only narrow permissions, never widen them. Agent B cannot grant Agent C more access than Agent B itself has.
  • Chain auditing — every delegation event is logged with cryptographic proofs, creating an immutable audit trail for compliance
  • Cascade revocation — revoking Agent B's credentials automatically invalidates all downstream delegations to Agents C, D, E, etc.
ZTNA → ZTAA. Just as ZTNA extended traditional network security for cloud-native applications, ZTAA extends ZTNA for agent-native architectures. The principle is the same — never trust, always verify — but the threat model and verification mechanisms are fundamentally different.

Interactive · ZTAA Delegation Chain

Cryptographic Identity Initiates task delegation

Agent A needs financial analysis. Its Ed25519-signed identity is verified against its AgentFacts before any delegation begins. Identity is the root of all trust.

1 / 6

Enterprise Threat Model

The NANDA Enterprise paper identifies five categories of agent-specific threats that ZTAA is designed to counter:

  1. Capability spoofing — agents falsely claiming capabilities they don't possess, potentially leading to task failures or data corruption at scale
  2. Impersonation attacks — malicious agents masquerading as trusted agents to gain access to sensitive resources or delegation chains
  3. Sensitive data leakage — agents inadvertently or intentionally exfiltrating data through multi-hop communication chains that bypass traditional data loss prevention
  4. Shadow agent proliferation — unauthorized agents operating within enterprise environments without visibility or governance
  5. Trust exploitation — compromised agents leveraging established trust relationships to propagate laterally through agent networks

Each threat is addressed by specific ZTAA mechanisms: cryptographic identity prevents impersonation, signed capability attestations prevent spoofing, AVC provides visibility into shadow agents, and instant revocation with cascade propagation limits blast radius from trust exploitation.

Implementing ZTAA

For enterprises deploying AI agents today, ZTAA provides a practical security framework that builds on existing Zero Trust investments:

  1. Register agents in the NANDA Index — give every agent a cryptographic identity via AgentFacts
  2. Define delegation policies — set depth limits, scope constraints, and approved agent pools for each use case
  3. Deploy AVC monitoring — instrument agent communication channels for continuous visibility and compliance auditing
  4. Integrate with existing IdP — ZTAA works alongside enterprise identity providers, extending existing SSO and RBAC to agent identities
Further reading. The full ZTAA specification is detailed in Using the NANDA Index Architecture in Practice (Section 6). For a broader view of NANDA's security architecture, see the Security Blueprint installment of our Agentic Web series.

References

Continue Reading

Coming Soon

By Invitation Only