# Make every logged action traceable to the specific agent identity

Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.

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.

## 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](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-event-reference-user-identity.html))
- "show both the user identity and the agent identity." ([source](https://docs.cloud.google.com/gemini-enterprise-agent-platform/scale/runtime/agent-identity))
- "These logs show which agent identity obtained a token for which resource" ([source](https://learn.microsoft.com/en-us/azure/ai-foundry/agents/concepts/agent-identity))

- [Previous: Log reads and writes to the data the agent touches](/checklist/log-data-access/)
- [Next: Alert on denied calls and on changes to the agent's role or policies](/checklist/alert-on-denied-and-role-changes/)

## Related pages

- [Alert on denied calls and on changes to the agent's role or policies: the check, and how in AWS, Google Cloud and Azure](/checklist/alert-on-denied-and-role-changes/)
- [Give each agent its own role or service account, not a shared one: the check, and how in AWS, Google Cloud and Azure](/checklist/own-identity-per-agent/)
- [Use short-lived role credentials and no long-lived access keys for the agent: the check, and how in AWS, Google Cloud and Azure](/checklist/short-lived-credentials/)

## Sources

- docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-event-reference-us: https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-event-reference-user-identity.html (read 10 Nov 2026)
- docs.cloud.google.com/gemini-enterprise-agent-platform/scale/runtime/agent-ident: https://docs.cloud.google.com/gemini-enterprise-agent-platform/scale/runtime/agent-identity (read 10 Nov 2026)
- learn.microsoft.com/en-us/azure/ai-foundry/agents/concepts/agent-identity: https://learn.microsoft.com/en-us/azure/ai-foundry/agents/concepts/agent-identity (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://aiagentaccesscontrol.com/checklist/attribute-actions-to-the-agent/
