Skip to content
AI Agent Access Control

Make every logged action traceable to the specific agent identity

Check 29 of 30: Make every logged action traceable to the specific agent identity. If logs only show a shared role or a generic account, you cannot tell which agent did what. Per-agent attribution turns a log line into a decision about one agent.

The whole checklist ยท The map

Why it matters

If logs only show a shared role or a generic account, you cannot tell which agent did what. Per-agent attribution turns a log line into a decision about one agent.

How, in each cloud

AWS
CloudTrail records the type of IAM identity that made each request in the userIdentity element.
Google Cloud
Agent identity appears in logs across Google Cloud services, and for user-delegated flows logs show both the user and the agent.
Azure
Entra sign-in logs show which agent identity obtained a token for which resource, including on behalf of which user.

What the documentation says

  • "element contains details about the type of IAM identity that made the request, and which" (source)
  • "show both the user identity and the agent identity." (source)
  • "These logs show which agent identity obtained a token for which resource" (source)

Sources

  1. docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-event-reference-us, read 10 Nov 2026
  2. docs.cloud.google.com/gemini-enterprise-agent-platform/scale/runtime/agent-ident, 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.