Azure Security Benchmark
Governance and Strategy

Azure Security Benchmark ASBv3-GS-6: Define and implement identity and privileged access strategy

Define and implement an identity and privileged access strategy with documented guidance, policy and standards for the identity system, authentication strength, privileged access and entitlement lifecycle.

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

What else in your programme already covers this

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

  • ANSSI-HYG-05 Maintain an Exhaustive Inventory of Privileged Accounts
  • ANSSI-HYG-08 Identify Each Person by Name and Separate User and Administrator Roles
  • ANSSI-HYG-10 Define and Verify Password Selection and Sizing Rules

CIS Controls v8 · 3 controls

  • CIS-5.4 Restrict Administrator Privileges to Dedicated Administrator Accounts
  • CIS-6.1 Establish an Access Granting Process
  • CIS-6.2 Establish an Access Revoking Process

ISO 27002:2022 · 3 controls

  • 5.1 Policies for information security
  • 5.15 Access control
  • 8.2 Privileged access rights

PCI DSS 4.0 · 3 controls

  • 7.1.1 7.1.1 Requirement 7 policies and procedures maintained
  • 7.2.1 7.2.1 Access control model defined
  • 8.1.1 8.1.1 Requirement 8 policies and procedures maintained

FedRAMP High · 2 controls

  • AC-1 Policy and Procedures
  • IA-1 Policy and Procedures

FedRAMP Moderate · 2 controls

  • AC-1 Policy and Procedures
  • IA-1 Policy and Procedures

ISO 27001:2022 · 2 controls

  • 5.1 Policies for information security
  • 5.15 Access control

NIST SP 800-53 Rev 5 · 2 controls

UK Cyber Essentials · 2 controls

  • CE-AC.1 User Account Approval Process
  • CE-SC.5 Password-Based Authentication Quality

APRA CPS 234 · 1 control

  • CPS234-19 Information Security Policy Framework
  • AUCDR-IS-1 Limit risk of unauthorised access to the CDR data environment

C5 (Germany) · 1 control

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

CMMC 2.0 · 1 control

  • CCM-IAM-01 Identity and Access Management Policy and Procedures

HIPAA Security Rule · 1 control

ISO 27701:2019 · 1 control

  • 6.6.1 Business requirements of access control
  • NIST-CSF-GV.PO-01 Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced

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 Governance and Strategy

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

Azure Security Benchmark ASBv3-GS-6 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 38 it maps to, and the evidence behind each claim, over MCP and REST.