IAM user without MFA
An IAM user who can sign in with just a password is a standing risk. MFA is the single most effective control against credential theft.
Why it matters
Passwords leak into code, logs, laptops and phishing pages. Without a second factor, a leaked password is immediate access.
Attackers specifically look for IAM users without MFA because they're the easiest foothold in an otherwise well-run account.
How to check for it
- IAM → Users → the Credentials report (aws iam generate-credential-report) lists mfa_active per user.
- Look for any user with console access (password enabled) and mfa_active = false.
How to fix it
- Assign an MFA device to each human user (IAM → Users → the user → Security credentials → Assign MFA device).
- Enforce it with an IAM policy that denies actions unless aws:MultiFactorAuthPresent is true.
- Prefer federation/SSO with MFA at the identity provider over long-lived IAM users where you can.
SkyShield checks this automatically
Connect your AWS, Cloudflare, GitHub, GitLab, Hetzner or DigitalOcean account read-only and SkyShield flags this across every account and region, with the fix in plain words — alongside the agent that watches your servers. Start free.
FAQ
- Do service accounts need MFA?
- Machine identities should use roles and temporary credentials, not a password, so MFA doesn't apply. MFA is for humans who sign in to the console.