Attack scenario · AWS identity & access

Dangerous cross-account role trust

What is AWS cross-account role abuse and how does it happen? A role trusts an entire external account without conditions. When that account is compromised, the adversary walks straight into yours.

Fictional, educational scenarioData exposurePrivilege takeoverLast updated · ATT&CK v20.1

Attack path · 4 stages

  1. 1

    Control a principal in the trusted account

    T1199

  2. 2

    Assume the trusting role

    T1078.004

  3. 3

    Map what the role can reach

    T1580T1619

  4. 4

    Collect data

    T1530

For leadership

Executive summary

Cross-account roles are how AWS accounts, vendors and internal platforms legitimately work together. They also mean your security depends partly on someone else’s. If a role in your account trusts "anyone in account 1111…" and that account is breached, or a vendor’s platform is abused, the attacker inherits whatever the role can do — without stealing anything from you. These relationships are easy to create, rarely revisited and often outlive the project that needed them. Leaders should expect a current inventory of who can enter each production account from outside, what they can do once inside, and the business owner of each relationship.

For engineers

Technical summary

A role trust policy with Principal {"AWS": "arn:aws:iam::<external>:root"} lets any principal in that account with sts:AssumeRole permission obtain a session. Without sts:ExternalId (for third parties) or organization conditions, compromise of the trusted account, or a confused-deputy scenario at a vendor, yields access in the trusting account.

Environment and assumptions

Fictional company: production data lives in account "prod-data". Two years ago a monitoring vendor was onboarded with a role "vendor-readonly" whose trust policy names the vendor’s whole AWS account and has no ExternalId. The role was later given s3:GetObject on all buckets "to troubleshoot an integration". The vendor relationship has since ended.

  • The trusted external account (or a tenant inside the vendor’s platform) is under adversary control.
  • The trust policy has no ExternalId, aws:PrincipalArn or organization conditions.
  • The relationship is no longer actively owned by anyone in the business.
  • Fictional and simplified for education.

Interactive

Attack sequence

Select a stage, or use the arrow keys, to see preconditions, evidence and controls.

Stage 1

Control a principal in the trusted account

The adversary compromises the vendor account, or abuses the vendor’s platform to make it assume roles on their behalf.

Preconditions
  • Your role trusts the external account broadly
Required access
  • Any principal in the trusted account permitted to call sts:AssumeRole.
Potential evidence
  • Not visible to you until a role in your account is assumed
Defensive controls
  • Third-party access inventory with business owners
  • ExternalId unique per customer for vendor roles
Text version of the attack sequence
  1. Control a principal in the trusted account (T1199). The adversary compromises the vendor account, or abuses the vendor’s platform to make it assume roles on their behalf. Preconditions: Your role trusts the external account broadly. Evidence: Not visible to you until a role in your account is assumed. Controls: Third-party access inventory with business owners; ExternalId unique per customer for vendor roles.
  2. Assume the trusting role (T1078.004). The adversary calls sts:AssumeRole on your role and receives temporary credentials for your account. Preconditions: No ExternalId or principal-specific conditions in the trust policy. Evidence: CloudTrail (your account): AssumeRole with a caller account outside your organization; Unusual role session names or source IPs. Controls: Trust specific principal ARNs, not the account root; Require sts:ExternalId for third parties.
  3. Map what the role can reach (T1580, T1619). The adversary lists buckets and objects available to the role. Preconditions: Role has list permissions. Evidence: CloudTrail: ListBuckets / ListObjects calls by the vendor role at unusual times. Controls: Least-privilege permissions for third-party roles.
  4. Collect data (T1530). Objects are downloaded using the role’s s3:GetObject permission. Preconditions: s3:GetObject on sensitive buckets. Evidence: S3 data events showing GetObject by the vendor role. Controls: Bucket policies restricting sensitive data to internal principals; Data perimeter (aws:PrincipalOrgID) on sensitive buckets.

Technique mapping

MITRE ATT&CK and ATLAS techniques referenced in this scenario
IDTechniqueTactics (official)Stages
T1199Trusted RelationshipInitial Access1
T1078.004Valid Accounts: Cloud AccountsInitial Access, Persistence, Privilege Escalation, Stealth2
T1580Cloud Infrastructure DiscoveryDiscovery3
T1619Cloud Storage Object DiscoveryDiscovery3
T1530Data from Cloud StorageCollection4

Technique names and tactic assignments come from the imported MITRE data. Mapping a stage to a technique is Securitain’s analysis.

Why the attack can succeed

  • Trusting the account root delegates the decision of "who may assume this role" entirely to the other account.
  • No ExternalId means any customer of a vendor platform might be able to direct the platform at your role (confused deputy).
  • Permissions grew over time without review, and the business relationship ended without decommissioning.

What prevents or limits the attack

What may detect the attack

Detection signals and telemetry sources
SignalTelemetry sourceNotes
AssumeRole where the caller account is outside your organization and not on an allow-listCloudTrail management events—
First AssumeRole in N days for a dormant external roleCloudTrail management eventsDormant roles suddenly becoming active are high-signal.
GetObject by third-party rolesS3 data events—

Telemetry only helps if it is enabled before the incident and someone acts on it. Listing a signal here does not mean it is collected or monitored in your environment.

What Securitain may assess

  • Securitain can assess todayRisky trust relationship analysis, including roles trusted by external accounts and missing or unscoped ExternalId. Learn more
  • Securitain can assess todayEffective-permission view that considers managed, inline, group, boundary and SCP policies together. Learn more
  • Securitain can assess todayPublic and cross-account exposure checks on S3, KMS, SQS, SNS and Secrets Manager resource policies. Learn more
  • Outside Securitain’s current scopeReal-time detection of attacker activity in CloudTrail is not part of Securitain’s current assessment — use GuardDuty, a SIEM or your SOC for that.

For leadership

Executive implications

confidentiality
Data reachable by the role can be read by whoever controls the trusted account.
compliance
Third-party access without documented need or ownership is a common audit finding (vendor management, access review).
operations
Removing trust in an emergency can break integrations if ownership was never documented.

No financial loss estimates are given; impact depends on the data, contracts and regulation involved.

Next steps

  1. Inventory every role whose trust policy names an account outside your organization.
  2. For each, record the business owner; remove any without one.
  3. Add ExternalId and principal-specific trust for vendors; organization conditions for internal trust.
  4. Reduce permissions to documented needs and review last-accessed data.
  5. Alert on AssumeRole from unknown external accounts.

References

MITRE ATT&CK® and ATT&CK® are registered trademarks of The MITRE Corporation. ATT&CK data © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation (ATT&CK v20.1). Securitain is not affiliated with or endorsed by MITRE. Explanations, scenarios and control mappings on this page are Securitain’s own analysis. Sources and licensing

Stay in the loop

Cloud security insights, early access & compliance updates

Weekly InsightsEarly AccessExpert Content
No spam, everUnsubscribe anytimeWeekly updates
Chat with Securitain