By Vero SecurityBuilt and funded by Vero Security, the AI Security Engineering platform.Read the charter

Attribution and audit of agent actions

After an incident you need to know whether a person or an agent acted, under which identity, and from which session. Cloud source identity and session tags, verified commits from apps, and agent telemetry exported to your SIEM together form that trail. Decide the required fields before an incident rather than during one.

Read in this order

  1. OfficialAWS STS: Pass session tagsStart here: tag sessions so cloud logs show who or what acted.
  2. OfficialAWS IAM: Monitor and control actions taken with assumed rolesTrace actions taken with an assumed role back to their source.
  3. OfficialClaude Code: Monitoring with OpenTelemetryExport agent telemetry to your SIEM to cover the session side.

Save your progress

We email you a sign-in link. No password.

By signing in you agree to the terms. The privacy policy explains how we use your details.

Join the AI security engineering community

Free. Roadmap updates, chapters near you, and first word when credentials open.

We’ll email you community updates. Unsubscribe anytime. By sending this you agree to the terms. The privacy policy explains how we use your details.