What problem does it solve? When a cloud credential surfaces during an external engagement — an AWS access key in a JS bundle, a GCP service account JSON in an APK, an Azure token via SSRF — testers need a fast, structured way to determine what the credential grants and how to escalate privileges without guesswork or destructive mistakes. ## Core Features & Use Cases - Credential Identification & Validation: Recognize AWS key prefixes (AKIA/ASIA), Azure storage keys, GCP service account JSON, and K8s SA tokens, then validate with safe read-only calls like aws sts get-caller-identity. - Privilege Escalation Playbooks: Lookup tables mapping 24+ AWS, 8+ Azure, and 6+ GCP IAM permissions to concrete escalation techniques (PassRole chains, login profile resets, service account key creation). - IMDS & Managed Identity Abuse: Step-by-step SSRF-to-metadata chains for AWS IMDSv1/v2, Azure Managed Identity tokens, and GCP metadata endpoints. - Cognito Identity Pool Attack Chain: Full unauthenticated-role workflow from IdentityPoolId discovery through GetId, GetCredentialsForIdentity, and permission enumeration with severity rubric. - Use Case: An SSRF finding reaches the EC2 metadata endpoint and returns temporary credentials. Use this Skill to identify the assumed role, enumerate attached policies, map a PassRole-to-Lambda escalation path, and document the finding with severity scoring and cleanup notes. ## Quick Start Use the cloud-iam-deep skill to analyze this leaked AWS access key and tell me what privileges it grants and how the role could be escalated.