Notifications
Clear all
Topic starter
22/07/2026 4:34 pm
TL;DR: AWS IAM Identity Center now lets a server-side application exchange a user’s OIDC token for that user’s AWS access, which breaks non-repudiation because actions are logged as the human even when an app initiated them, according to Clutch Security. This is not a short-lived credential win if the app inherits human identity instead of acting as itself; lineage, scope, and accountability all collapse at once.
NHIMG editorial — based on content published by Clutch Security: On Behalf of Whom? How AWS Broke Non-Repudiation and Shipped It as a Feature
By the numbers:
- Only 44% of organisations have implemented any policies to manage their AI agents, despite 92% agreeing that governing AI agents is critical to enterprise security.
- 70% of organisations grant AI systems more access than they would give a human employee performing the exact same job.
Questions worth separating out
Q: What breaks when applications can act as human users in AWS?
A: Non-repudiation breaks first, followed by clean attribution and workload-level least privilege.
Q: Why is user-borrowed access risky for cloud workloads?
A: Because the service’s effective permissions become whichever entitlements the user already has, rather than the permissions the task actually needs.
Q: How do security teams know whether delegated access is actually governable?
A: Look for a distinct workload identity, a separate role, and a durable event trail that preserves which application initiated the action.
Practitioner guidance
- Preserve separate service principals Require applications to authenticate as distinct workloads with scoped roles, even when they are invoked by users.
- Treat on-behalf-of sessions as high-blast-radius events Flag every session where an application can act under a human identity as a privileged delegation path.
- Correlate action lineage outside CloudTrail alone Join identity events with application telemetry, user-agent signals, and application ownership data so investigators can reconstruct which service drove the session when platform logs stay ambiguous.
What's in the full article
Clutch Security's full blog post covers the operational detail this post intentionally leaves for the source:
- CloudTrail event sequencing and how the credentialId can be used to join related actions.
- The exact places where the application disappears from the log trail and where attribution breaks down.
- Practical alerting ideas for CreateTokenWithIAM and follow-on userIdentity events.
- The missing controls AWS would need to restore application-level scope and auditability.
👉 Read Clutch Security's analysis of AWS impersonation and non-repudiation →
AWS impersonation in identity center: what it means for IAM teams?
Explore further
22/07/2026 4:40 pm
Human impersonation is a governance anti-pattern, not a federation feature. The core problem is that AWS is allowing an application to execute under a user principal, which breaks the identity boundary that IAM programmes rely on. Auditability depends on the actor remaining visible as itself, and that is lost here. For practitioners, the lesson is that delegation must preserve actor separation if non-repudiation is to survive.
A few things that frame the scale:
- Only 44% of organisations have implemented any policies to manage their AI agents, despite 92% agreeing that governing AI agents is critical to enterprise security, according to The 2026 Infrastructure Identity Survey.
- 69% of security leaders agree identity management must fundamentally shift to address agentic AI systems, which aligns with the growing pressure to separate human and non-human principals.
A question worth separating out:
Q: Who is accountable when an application acts on behalf of a user?
A: The organisation is accountable for the access design, but operational accountability becomes unclear if the platform suppresses the application’s identity. That is why cloud identity models must preserve actor separation: without it, accountability shifts from evidence to inference.
👉 Read our full editorial: AWS identity center impersonation breaks non-repudiation and auditability
