Ensure hardware MFA is enabled for the root account
Hardware MFA provides better security than virtual MFA as it cannot be duplicated and is resistant to phishing attacks. The hardware device generates a time-based one-time password (TOTP) that is required in addition to the password.
Security Impact
Virtual MFA can be compromised through device theft, SIM swapping, or malware. Hardware MFA is resistant to these attacks.
How to Remediate
Configure a hardware MFA device (YubiKey, Gemalto) for the root account through the IAM console. Store backup codes securely offline.
Affected Resources
Compliance Frameworks
How TigerGate Helps
TigerGate continuously monitors your AWS environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:
- Continuous Scanning
Automatically scans all Identity and Access Management (IAM) resources across your AWS accounts every hour
- Instant Alerts
Get notified via Slack, email, or webhooks when this misconfiguration is detected
- One-Click Remediation
Fix this issue directly from the TigerGate dashboard with our guided remediation
- Compliance Evidence
Automatically collect audit evidence for CIS AWS v1.5.0, CIS AWS v2.0, PCI-DSS compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-iam-3
- Service
- Identity and Access Management (IAM)
- Category
- Identity Management
- Severity
- HIGH
- CIS Benchmark
- 1.3
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated Identity and Access Management (IAM) Checks
View all checksAvoid the use of root account
Ensure MFA is enabled for the root account
Ensure no root account access keys exist
Ensure IAM password policy requires at least one uppercase letter
Ensure IAM password policy requires at least one lowercase letter