Course contentsShow
← Security
Lesson 1744 of 3,05235. Cloud Security - IAMFree lesson

Common Cross-Account Misconfigurations

Identifying overly permissive trust policies, wildcard principals, and privilege escalation risks in cross-account setups.

Common Cross-Account Misconfigurations

What you'll learn: How overly permissive trust policies and wildcard principals create dangerous backdoors in cross-account setups.

Cross-account access is powerful but error-prone. Even when you've set up AssumeRole and trust policies correctly, subtle misconfigurations can expose your resources to unintended principals or enable privilege escalation attacks.

The Wildcard Principal Trap

The most dangerous misconfiguration is using wildcards in trust policies:

{
  "Effect": "Allow",
  "Principal": {"AWS": "*"},
  "Action": "sts:AssumeRole"
}

This allows any AWS account in the world to assume your role—not just your trusted partners. It's like giving your house key to "anyone wearing a uniform" instead of specific delivery companies.

Overly Permissive Conditions

Trust policies without proper conditions can be exploited:

  • Missing External ID: Third-party accounts might impersonate legitimate users without the External ID check
  • Weak condition logic: Conditions that don't properly restrict source accounts or IP ranges
  • No MFA requirement: Allowing role assumption without multi-factor authentication

Privilege Escalation Chains

Cross-account roles with excessive permissions create escalation paths:

  1. Attacker compromises low-privilege account
  2. Uses overly permissive cross-account role to access high-value account
  3. Leverages broad permissions to escalate further

Think of it as leaving a ladder propped against your neighbor's fence—it creates an unintended path between properties.

Detection Strategies

Use Access Analyzer to identify external access patterns. Regularly audit trust policies for wildcards, review session logs for unusual cross-account activity, and implement Service Control Policies to prevent overly permissive trust policy creation.

Key Takeaway: Cross-account misconfigurations—especially wildcard principals and missing conditions—turn security boundaries into open doors; always validate trust policies with strict principal and condition constraints.