Avoiding mistakes with AWS OIDC integration conditions

This report reviews insecure AWS OIDC integrations across many vendors, highlighting that omitting or misconfiguring IAM trust policy conditions (especially "sub" and "aud", though some vendors use other keys) can enable attackers to assume IAM roles and potentially take over accounts; it catalogs vendor behaviours, provides correct policy examples, and recommends adding both aud and sub (or vendor-specific) conditions and detection checks.