# Carry a stable source identity through AWS role sessions for investigation

> Connect assumed-role activity to an identity attribute that survives role chaining.

- Canonical URL: https://update.dsesecurity.com/updates/carry-a-stable-source-identity-through-aws-role-sessions-for-investigation/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-10-20T18:13:31+00:00
- Modified: 2026-10-20T18:34:28+00:00
- Last reviewed by DSE: 2026-10-20
- Resource type: Guide
- DSE priority: Information
- Topics: Cybersecurity, IT
- Reading time: 2 minutes

## What you need to know

Connect assumed-role activity to an identity attribute that survives role chaining.

## Potentially affected

This concerns AWS role-session attribution, not proof that any arbitrary caller-supplied label identifies a real person.

## DSE recommendation

DSE recommends selecting a stable, accountable attribute from the trusted identity workflow and documenting who can supply it.

## Article

Connect assumed-role activity to an identity attribute that survives role chaining.

## Source facts

AWS can record a configured source identity in CloudTrail for assumed-role activity. Once set, the value cannot change during the session and persists when the role assumes another role. Setting source identity requires the relevant permissions and trust configuration; AWS does not independently control the chosen identity value.

Source: [AWS Documentation](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_control-access_monitor.html).

## Applicability

This concerns AWS role-session attribution, not proof that any arbitrary caller-supplied label identifies a real person.

## DSE recommendation

DSE recommends selecting a stable, accountable attribute from the trusted identity workflow and documenting who can supply it. Review the complete role chain for the required permission before enforcing it in production. Avoid sensitive personal data in the value. Explain how investigators should correlate it with the identity provider and account records. Assign an owner to maintain the mapping when staff identities or federation settings change, and preserve the expected format in support documentation. Define the correlation record investigators should consult when a value is unfamiliar. Review that record’s ownership and retention alongside the role chain, and make a changed identity-provider mapping a reason to repeat the attribution test before relying on it.

## Verification

Proposed verification: assume approved test roles with the chosen source identity, follow the intended role chain and inspect the resulting CloudTrail fields. Check behavior when the attribute is missing or unauthorized. Record the evidence linking the supplied attribute to its trusted origin.

## Official reference

[AWS Documentation](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_control-access_monitor.html). Reviewed October 20, 2026.

## Primary reference

- Name: AWS Documentation
- Authority: docs.aws.amazon.com
- URL: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_control-access_monitor.html
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Carry a stable source identity through AWS role sessions for investigation,” DSE Security, https://update.dsesecurity.com/updates/carry-a-stable-source-identity-through-aws-role-sessions-for-investigation/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.