Lockdown Lab #5 CRITICAL AWS

Enable MFA on root account

Enable MFA on root account

Let’s talk about the keys to the kingdom. Your AWS root account is exactly that – unrestricted access to everything, including billing. I’ve seen organizations get completely wiped out because this account was compromised.

This isn’t just “important”; it’s foundational. If your root account doesn’t have hardware MFA enabled, you’re leaving the front door wide open for an attacker to delete resources, exfiltrate data, and run up astronomical bills. IAM policies cannot limit the root account.

This is a basic, non-negotiable step. Use a physical hardware MFA device. Never use SMS or virtual MFA for root. You can check your current status with:

aws iam get-account-summary –query ‘SummaryMap.AccountMFAEnabled’

Enable it, secure it, then lock it away and never touch it for daily operations.

The fix

# Check root MFA status

aws iam get-account-summary --query ''SummaryMap.AccountMFAEnabled'

Reference: CIS AWS Foundations Benchmark 1.5

Mark this as done

Open the interactive hardening checklist and tick this off in your environment.

Open interactive checklist →

Related Posts

Enable MFA for all users

If I had a nickel for every breach that started with a single compromised password, I'd have retired years ago. It's the oldest trick in...

lockdown-labhardeningazureidentity
/Shimi Cohen

Rename and disable built-in Administrator

If you’re still running default Administrator accounts on your Windows Servers, you’re practically handing attackers a key. This isn't theoretical; tools like Mimikatz and CrackMapExec...

lockdown-labhardeningwindowsidentity
/Shimi Cohen

Restrict who can create and publish Copilot Studio agents

Shadow IT is bad enough. Add generative AI, and you’ve got a recipe for serious data exfiltration. I’ve seen organizations completely miss this control. Any...

lockdown-labhardeningcopilot-studioservices
/Shimi Cohen