Skip to content
AI Agent Access Control

Keep the agent's code from reading node, instance or other workloads' credentials

Check 18 of 30: Keep the agent's code from reading node, instance or other workloads' credentials. If agent code can read the host's metadata service, it can take the host's credentials, which are often broader than the agent's own. Isolating credentials keeps one compromised agent from becoming a compromised node.

The whole checklist ยท The map

Why it matters

If agent code can read the host's metadata service, it can take the host's credentials, which are often broader than the agent's own. Isolating credentials keeps one compromised agent from becoming a compromised node.

How, in each cloud

AWS
Restrict access to the EC2 Instance Metadata Service for pods so containers can only retrieve credentials for their own role.
Google Cloud
Use Workload Identity Federation for GKE, which protects the metadata that metadata concealment covered.
Azure
Run hosted agents in per-session VM-isolated sandboxes, which Microsoft documents as holding no blueprint credential.

What the documentation says

  • "A container never has access to credentials that are used by other containers in other Pods." (source)
  • "The sensitive metadata protected by metadata concealment is also protected by" (source)
  • "Each hosted-agent session runs in its own VM-isolated sandbox" (source)

Sources

  1. docs.aws.amazon.com/eks/latest/userguide/pod-identities.html, read 10 Nov 2026
  2. cloud.google.com/kubernetes-engine/docs/concepts/workload-identity, read 10 Nov 2026
  3. learn.microsoft.com/en-us/azure/ai-foundry/agents/concepts/agent-identity, read 10 Nov 2026

Last reviewed 16 Nov 2026.