AWS Well-Architected Security Pillar
Identity & Access Management

AWS Well-Architected Security Pillar SEC02-BP01: Use strong sign-in mechanisms

Enforce MFA, strong password policies and phishing-resistant authentication factors for all human users accessing AWS, including IAM Identity Center and federated identities.

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

What else in your programme already covers this

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

CMMC 2.0 · 7 controls

NIST SP 800-171 Rev 3 · 5 controls

PCI DSS 4.0 · 5 controls

  • 8.3.1 8.3.1 Access authenticated with at least one factor
  • 8.3.6 8.3.6 Password minimum length 12 and complexity
  • 8.4.1 8.4.1 MFA for non-console administrative CDE access
  • 8.4.2 8.4.2 MFA for all non-console CDE access
  • 8.5.1 8.5.1 MFA system resistant to replay and bypass

C5 (Germany) · 4 controls

CIS Controls v8 · 4 controls

  • CIS-5.2 Use Unique Passwords
  • CIS-6.3 Require MFA for Externally-Exposed Applications
  • CIS-6.4 Require MFA for Remote Network Access
  • CIS-6.5 Require MFA for Administrative Access

FedRAMP High · 4 controls

  • IA-2(1) MFA to Privileged Accounts
  • IA-2(2) MFA to Non-Privileged Accounts
  • IA-2(6) Identification and Authentication (Organizational Users) | Access to Accounts: separate Device (IA-2(6))
  • IA-5(1) Password-Based Authentication

FedRAMP Moderate · 4 controls

  • IA-2(1) MFA to Privileged Accounts
  • IA-2(2) MFA to Non-Privileged Accounts
  • IA-2(6) Identification and Authentication (Organizational Users) | Access to Accounts: separate Device (IA-2(6))
  • IA-5(1) Password-Based Authentication

UK Cyber Essentials · 4 controls

  • CE-AC.7 MFA for Administrative Accounts
  • CE-AC.8 Passwordless Authentication
  • CE-SC.5 Password-Based Authentication Quality
  • CE-SC.6 Multi-Factor Authentication for Cloud Services

HIPAA Security Rule · 3 controls

NIST SP 800-66 Rev 2 · 3 controls

ACSC Essential Eight · 2 controls

  • E8-MFA-ML1 Multi-Factor Authentication - Maturity Level 1
  • E8-MFA-ML3 Multi-Factor Authentication - Maturity Level 3

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 2 controls

  • ANSSI-HYG-10 Define and Verify Password Selection and Sizing Rules
  • ANSSI-HYG-13 Prefer Strong Authentication Where Possible

Azure Security Benchmark · 2 controls

  • ASBv3-IM-2 Protect identity and authentication systems
  • IM-6 Use strong authentication controls

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 2 controls

ISO 27001:2022 · 2 controls

  • 5.17 Authentication information
  • 8.5 Secure authentication

ISO 27002:2022 · 2 controls

  • 5.17 Authentication information
  • 8.5 Secure authentication

NIST SP 800-53 Rev 5 · 2 controls

ASD Strategies to Mitigate Cyber Security Incidents · 1 control

  • ASD37-20 Multi-factor authentication (Essential)

Australia Consumer Data Right - Banking (CDR) · 1 control

  • AUCDR-IS-1 Limit risk of unauthorised access to the CDR data environment

ISO 27701:2019 · 1 control

  • 6.6.4 System and application access control

NIST Cybersecurity Framework 2.0 · 1 control

NIST SP 800-161 Rev 1 · 1 control

  • 161R1-IA-2 Identification and Authentication (Organizational Users)

SOC 2 · 1 control

  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets

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 Identity & Access Management

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

AWS Well-Architected Security Pillar SEC02-BP01 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.

If you hold NIST SP 800-53 Rev 582.5% covered · 11 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.174.6% covered · 16 gapsIf you hold ISO 27002:202273% covered · 17 gapsIf you hold FedRAMP Moderate69.8% covered · 19 gapsIf you hold Azure Security Benchmark65.1% covered · 22 gapsIf you hold PCI DSS 4.063.5% covered · 23 gaps

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.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

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

MCP endpointAll AWS Well-Architected Security Pillar controls