01Description
IAM users had long-lived access keys, some unrotated for long periods and attached to broad permissions such as AdministratorAccess.
02Impact
Access keys leak through source code, CI/CD logs and developer machines. A leaked long-lived key with broad permissions gives an attacker persistent control of cloud resources.
03Severity
Typically
High
Typically High. High where keys carry broad permissions. Medium for narrowly scoped keys that are rotated.
04How to verify
- 1Review the IAM credential report for key age and last use.
- 2Review policies attached to users with keys.
- 3Search code repositories and CI configuration for keys.
Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.
05Remediation
- 1Replace long-lived keys with roles and temporary credentials, such as IAM Identity Center and OIDC federation for CI/CD.
- 2Remove unused keys and rotate any that must remain.
- 3Apply least-privilege policies.
06References
Draft findings like this from your own evidence
Book a demo