CRITICAL

Ensure IAM role does not allow assume from any AWS account

IAM roles should never allow Principal: * or Principal: AWS: * in trust policies as this allows any AWS account to assume the role.

Security Impact

Any AWS account worldwide could assume the role and access your resources with the role's permissions.

How to Remediate

Update role trust policies immediately to specify exact AWS account IDs. Never use wildcards for Principal in trust policies.

Affected Resources

AWS::IAM::Role

Compliance Frameworks

SOC 2PCI-DSSNIST 800-53HIPAA

How TigerGate Helps

TigerGate continuously monitors your AWS environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:

  • Continuous Scanning

    Automatically scans all Identity and Access Management (IAM) resources across your AWS accounts every hour

  • Instant Alerts

    Get notified via Slack, email, or webhooks when this misconfiguration is detected

  • One-Click Remediation

    Fix this issue directly from the TigerGate dashboard with our guided remediation

  • Compliance Evidence

    Automatically collect audit evidence for SOC 2, PCI-DSS, NIST 800-53 compliance

  • Drift Detection

    Get alerted if this configuration drifts back to an insecure state after remediation

Check Details

Check ID
aws-iam-22
Service
Identity and Access Management (IAM)
Category
Cross-Account Access
Severity
CRITICAL

Automate This Check

TigerGate automatically scans your AWS environment for this and 575+ other security checks.

Start Free Trial

Related Identity and Access Management (IAM) Checks

View all checks
aws-iam-1high

Avoid the use of root account

aws-iam-2critical

Ensure MFA is enabled for the root account

aws-iam-3high

Ensure hardware MFA is enabled for the root account

aws-iam-4critical

Ensure no root account access keys exist

aws-iam-5medium

Ensure IAM password policy requires at least one uppercase letter