AWS Well-Architected Security Pillar SEC02-BP04: Rely on a centralized identity provider

What else in your programme already covers this

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

FedRAMP High · 5 controls

AC-2 Account Management
AC-2(1) Automated System Account Management
IA-2 Identification and Authentication (Organizational Users)
IA-4 Identifier Management
IA-8 Identification and Authentication (Non-Organizational Users)

FedRAMP Moderate · 5 controls

AC-2 Account Management
AC-2(1) Automated System Account Management
IA-2 Identification and Authentication (Organizational Users)
IA-4 Identifier Management
IA-8 Identification and Authentication (Non-Organizational Users)

NIST SP 800-171 Rev 3 · 5 controls

03.01.01 Account Management
03.01.12 Remote Access
03.05.01 User Identification and Authentication
03.05.03 Multi-Factor Authentication
03.05.05 Identifier Management

NIST SP 800-53 Rev 5 · 5 controls

NIST800-AC-2 AC-2 Account Management
NIST800-IA-13 IA-13 Identity Providers and Authorization Servers
NIST800-IA-2 IA-2 Identification and Authentication (Organizational Users)
NIST800-IA-4 IA-4 Identifier Management
NIST800-IA-8 IA-8 Identification and Authentication (Non-organizational Users)

CIS Controls v8 · 4 controls

CIS-12.5 Centralize Network Authentication, Authorization, and Auditing (AAA)
CIS-5.6 Centralize Account Management
CIS-6.6 Establish and Maintain an Inventory of Authentication and Authorization Systems
CIS-6.7 Centralize Access Control

CMMC 2.0 · 4 controls

AC.L2-3.1.1 Authorized Access Control
AU.L2-3.3.2 User Accountability
IA.L2-3.5.1 Identification
IA.L2-3.5.2 Authentication

Azure Security Benchmark · 3 controls

ASBv3-GS-6 Define and implement identity and privileged access strategy
ASBv3-IM-5 Use single sign-on (SSO) for application access
IM-1 Use centralized identity and authentication system

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

CCM-IAM-03 Identity Inventory
CCM-IAM-06 User Access Provisioning
CCM-IAM-13 Uniquely Identifiable Users

NIST Cybersecurity Framework 2.0 · 3 controls

NIST-CSF-PR.AA-01 Identities and credentials for authorized users, services, and hardware are managed by the organization
NIST-CSF-PR.AA-02 Identities are proofed and bound to credentials based on the context of interactions
NIST-CSF-PR.AA-04 Identity assertions are protected, conveyed, and verified

NIST SP 800-161 Rev 1 · 3 controls

161R1-AC-2 Account Management
161R1-IA-2 Identification and Authentication (Organizational Users)
161R1-IA-8 Identification and Authentication (Non-Organizational Users)

PCI DSS 4.0 · 3 controls

8.2.1 8.2.1 Unique ID assigned to every user
8.2.2 8.2.2 Shared and generic IDs only by exception
8.4.3 8.4.3 MFA for remote access that could reach CDE

HIPAA Security Rule · 2 controls

164.308(a)(3)(i) Workforce Security (Standard)
164.312(a)(2)(i) Unique User Identification (Required)

ISO 27001:2022 · 2 controls

5.16 Identity management
8.5 Secure authentication

NIST SP 800-66 Rev 2 · 2 controls

164.308(a)(3)(i) Workforce Security (Standard)
164.312(a)(2)(i) Unique User Identification (Required)

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

ANSSI-HYG-08 Identify Each Person by Name and Separate User and Administrator Roles

C5 (Germany) · 1 control

C5-IDM-01 Policy for user accounts and access rights

SOC 2 · 1 control

SOC2-CC6.2 CC6.2 Registering and authorising users before issuing credentials

UK Cyber Essentials · 1 control

CE-AC.2 Authenticate Users Before Granting Access

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.

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

AWS Well-Architected Security Pillar SEC02-BP04 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 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.174.6% covered · 16 gaps If you hold ISO 27002:202273% covered · 17 gaps If you hold FedRAMP Moderate69.8% covered · 19 gaps If you hold Azure Security Benchmark65.1% covered · 22 gaps If 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 each Browse the graph free