Azure Security Benchmark IM-1: Use centralized identity and authentication system

What else in your programme already covers this

This control maps to 50 controls across 25 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 · 5 controls

CIS-12.5 Centralize Network Authentication, Authorization, and Auditing (AAA)
CIS-5.1 Establish and Maintain an Inventory of Accounts
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

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

CCM-IAM-01 Identity and Access Management Policy and Procedures
CCM-IAM-03 Identity Inventory
CCM-IAM-13 Uniquely Identifiable Users

FedRAMP High · 3 controls

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

FedRAMP Moderate · 3 controls

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

NIST SP 800-53 Rev 5 · 3 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)

PCI DSS 4.0 · 3 controls

8.2.1 8.2.1 Unique ID assigned to every user
8.3.1 8.3.1 Access authenticated with at least one factor
7.3.1 7.3.1 Need-to-know access control system covers all components

ACSC Essential Eight · 2 controls

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

ASD Strategies to Mitigate Cyber Security Incidents · 2 controls

ASD37-21 Disable local administrator accounts (Excellent)
ASD37-23 Protect authentication credentials (Excellent)

C5 (Germany) · 2 controls

C5-IDM-01 Policy for user accounts and access rights
C5-IDM-09 Authentication mechanisms

HIPAA Security Rule · 2 controls

164.312(a)(1) Access Control (Standard)
164.312(a)(2)(i) Unique User Identification (Required)

NIST SP 800-161 Rev 1 · 2 controls

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

NIST SP 800-171 Rev 3 · 2 controls

03.01.01 Account Management
03.05.01 User Identification and Authentication

NIST SP 800-66 Rev 2 · 2 controls

164.312(a)(1) Access Control (Standard)
164.312(a)(2)(i) Unique User Identification (Required)

UK Cyber Essentials · 2 controls

CE-AC.2 Authenticate Users Before Granting Access
CE-SC.4 Authenticate Users Before Access

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

AWS Well-Architected Security Pillar · 1 control

SEC02-BP04 Rely on a centralized identity provider

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

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

Australia My Health Records Act 2012 · 1 control

MYHR-SEC-2 Access controls and user account management

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

CFTC-SS-3 Information Security Category

NIST Cybersecurity Framework 2.0 · 1 control

NIST-CSF-PR.AA-01 Identities and credentials for authorized users, services, and hardware are managed by the organization

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.

You are reading one control. How much of Azure Security Benchmark have you already done?

Azure Security Benchmark IM-1 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of Azure Security Benchmark your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 71 of 85 Azure Security Benchmark controls already carry evidence.

If you hold NIST SP 800-53 Rev 583.5% covered · 14 gaps If you hold FedRAMP Moderate78.8% covered · 18 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.172.9% covered · 23 gaps If you hold ISO 27002:202269.4% covered · 26 gaps If you hold C5 (Germany)65.9% covered · 29 gaps If you hold ISO 27001:202261.2% covered · 33 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