Azure Security Benchmark
Identity Management

Azure Security Benchmark ASBv3-IM-2: Protect identity and authentication systems

Treat the identity and authentication system as a high priority asset, restricting privileged roles, requiring strong authentication for privileged access and monitoring high risk activity.

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

What else in your programme already covers this

This control maps to 39 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.

NIST SP 800-53 Rev 5 · 3 controls

UK Cyber Essentials · 3 controls

  • CE-AC.4 Privileged Account Approval and Tracking
  • CE-AC.7 MFA for Administrative Accounts
  • CE-FW.3 Block Unauthenticated Inbound Connections
  • ASD37-20 Multi-factor authentication (Essential)
  • ASD37-23 Protect authentication credentials (Excellent)

C5 (Germany) · 2 controls

  • C5-IDM-08 Confidentiality of authentication information
  • C5-IDM-09 Authentication mechanisms

CIS Controls v8 · 2 controls

  • CIS-6.5 Require MFA for Administrative Access
  • CIS-6.6 Establish and Maintain an Inventory of Authentication and Authorization Systems

CMMC 2.0 · 2 controls

FedRAMP High · 2 controls

FedRAMP Moderate · 2 controls

ISO 27002:2022 · 2 controls

  • 5.17 Authentication information
  • 8.2 Privileged access rights
  • NIST-CSF-ID.AM-05 Assets are prioritized based on classification, criticality, resources, and impact on the mission
  • NIST-CSF-PR.AA-04 Identity assertions are protected, conveyed, and verified

NIST SP 800-171 Rev 3 · 2 controls

  • 03.01.06 Least Privilege - Privileged Accounts
  • 03.05.03 Multi-Factor Authentication
  • E8-MFA-ML2 Multi-Factor Authentication - Maturity Level 2

HIPAA Security Rule · 1 control

ISO 27001:2022 · 1 control

  • 8.2 Privileged access rights

ISO 27701:2019 · 1 control

  • 6.6.2 User access management

NIST SP 800-172 · 1 control

  • 3.5.3e Prohibit Connection of Unknown or Unverified System Components

PCI DSS 4.0 · 1 control

  • 8.3.2 8.3.2 Authentication factors unreadable with strong cryptography

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 Management

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

Azure Security Benchmark ASBv3-IM-2 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.

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 39 it maps to, and the evidence behind each claim, over MCP and REST.