AWS root account without MFA
The root user owns the entire AWS account and can't be restricted by IAM policies. Without multi-factor authentication, a single leaked or phished password is a complete account takeover.
Why it matters
Root can close the account, change billing, delete every resource and remove other admins. No IAM guardrail applies to it.
Password reuse and phishing are the most common ways accounts are taken over. MFA on root turns a stolen password into a non-event.
How to check for it
- IAM console → the dashboard shows a security recommendation if root has no MFA.
- aws iam get-account-summary and check AccountMFAEnabled equals 1.
- While you're there, confirm there are no root access keys (AccountAccessKeysPresent should be 0).
How to fix it
- Sign in as root once and add a hardware or virtual MFA device (IAM → root user → Security credentials).
- Delete any root access keys and create IAM roles/users for day-to-day work.
- Lock the root credentials away and use it only for the handful of tasks that truly require it.
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
- Can I just delete the root user instead?
- No — the root user can't be deleted. The right approach is MFA on root, no root access keys, and doing everyday work through IAM roles.