AWS Well-Architected Security Pillar
Security Foundations

AWS Well-Architected Security Pillar SEC01-BP02: Secure account root user and properties

Protect the root user of every AWS account with strong MFA, no programmatic access keys, monitored email and contact details, and use root only for tasks that explicitly require it.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 37 controls across 21 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

CIS Controls v8 · 3 controls

  • CIS-4.7 Manage Default Accounts on Enterprise Assets and Software
  • CIS-5.4 Restrict Administrator Privileges to Dedicated Administrator Accounts
  • CIS-6.5 Require MFA for Administrative Access

CMMC 2.0 · 3 controls

FedRAMP High · 3 controls

  • AC-2(9) Restrictions on Use of Shared and Group Accounts
  • AC-6(5) Privileged Accounts
  • IA-2(1) MFA to Privileged Accounts

FedRAMP Moderate · 3 controls

  • AC-2(9) Restrictions on Use of Shared and Group Accounts
  • AC-6(5) Privileged Accounts
  • IA-2(1) MFA to Privileged Accounts
  • ANSSI-HYG-12 Change Default Authentication Elements on Equipment and Services
  • ANSSI-HYG-13 Prefer Strong Authentication Where Possible
  • ASBv3-IM-2 Protect identity and authentication systems
  • PA-1 Separate and limit highly privileged/administrative users

C5 (Germany) · 2 controls

ISO 27001:2022 · 2 controls

  • 8.2 Privileged access rights
  • 8.5 Secure authentication

NIST SP 800-171 Rev 3 · 2 controls

  • 03.01.06 Least Privilege - Privileged Accounts
  • 03.05.03 Multi-Factor Authentication

NIST SP 800-53 Rev 5 · 2 controls

UK Cyber Essentials · 2 controls

  • CE-AC.7 MFA for Administrative Accounts
  • CE-SC.6 Multi-Factor Authentication for Cloud Services
  • E8-MFA-ML2 Multi-Factor Authentication - Maturity Level 2
  • ASD37-21 Disable local administrator accounts (Excellent)

HIPAA Security Rule · 1 control

ISO 27002:2022 · 1 control

  • 8.2 Privileged access rights
  • NIST-CSF-PR.AA-05 Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties

PCI DSS 4.0 · 1 control

  • 2.2.2 2.2.2 Vendor default accounts managed

SOC 2 · 1 control

  • SOC2-CC6.3 CC6.3 Role-based access, least privilege and segregation of duties

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Security Foundations

You are reading one control. How much of AWS Well-Architected Security Pillar have you already done?

AWS Well-Architected Security Pillar SEC01-BP02 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of AWS Well-Architected Security Pillar your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 52 of 63 AWS Well-Architected Security Pillar controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.

Query this from an agent

The graph holds this control, the 37 it maps to, and the evidence behind each claim, over MCP and REST.