Cloud environments
Cloud workloads constantly handle credentials: role sessions from metadata services, secrets for databases, tokens for SaaS. Every workload is therefore a potential credential source.
TA0006Tactic 9 of 15
How do attackers steal credentials in AWS?
Credential Access covers techniques for stealing account names, passwords, keys and tokens. Stolen credentials let the adversary act as a legitimate identity, which makes later steps harder to distinguish from normal work and often survives the remediation of the original foothold.
The adversary is trying to steal account names and passwords.
Credential Access consists of techniques for stealing credentials like account names and passwords. Techniques used to get credentials include keylogging or credential dumping. Using legitimate credentials can give adversaries access to systems, make them harder to detect, and provide the opportunity to create more accounts to help achieve their goals.
Cloud workloads constantly handle credentials: role sessions from metadata services, secrets for databases, tokens for SaaS. Every workload is therefore a potential credential source.
Typical sources: EC2 instance metadata (IMDS), ECS/EKS credential endpoints, Secrets Manager and Parameter Store, credentials in code or environment variables, CI/CD variables, and Kubernetes service account tokens.
Agents often hold API keys for tools; credentials in agent configuration, prompts or logs are new harvesting targets (ATLAS tracks AI agent tool credential harvesting).
secretsmanager:GetSecretValueRead a secret value.ssm:GetParameter (WithDecryption)Read SecureString parameters.Instance metadata exposes role credentials to SSRF and local code.
Read the Securitain guideSecrets Manager / Parameter Store reads with over-broad permissions.
Read the Securitain guideApplication and workload tokens.
Credentials in files, images and repositories.
View on MITRE ATT&CKForged web credentials (for example SAML tokens) bypass normal sign-in.
GetSecretValue by new principals or in bulk
Instance credentials used outside AWS
For leadership
Assume any compromised workload yields its credentials. The investment that matters is limiting what those credentials can do.
Myth
“IMDSv2 stops credential theft.”
Reality
IMDSv2 defeats many SSRF patterns, but code executing on the instance can still obtain role credentials.
0 of 3 done
Saved only in this browser. Nothing is sent to Securitain.
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