Azure Security Benchmark
Privileged Access

Azure Security Benchmark PA-2: Avoid standing access for user accounts and permissions

Use Privileged Identity Management (PIM) for just-in-time access elevation with approval workflows and time-bound activation.

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

What else in your programme already covers this

This control maps to 41 controls across 22 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 · 4 controls

  • AC-17(4) Privileged Commands and Access
  • AC-2(2) Automated Temporary and Emergency Account Management
  • AC-6 Least Privilege
  • AC-6(2) Non-Privileged Access for Nonsecurity Functions

FedRAMP Moderate · 4 controls

  • AC-17(4) Privileged Commands and Access
  • AC-2(2) Automated Temporary and Emergency Account Management
  • AC-6 Least Privilege
  • AC-6(2) Non-Privileged Access for Nonsecurity Functions

CMMC 2.0 · 3 controls

C5 (Germany) · 2 controls

CIS Controls v8 · 2 controls

  • CIS-6.1 Establish an Access Granting Process
  • CIS-6.5 Require MFA for Administrative Access

HIPAA Security Rule · 2 controls

ISO 27001:2022 · 2 controls

  • 5.18 Access rights
  • 8.2 Privileged access rights

ISO 27002:2022 · 2 controls

  • 5.18 Access rights
  • 8.2 Privileged access rights

NIST SP 800-171 Rev 3 · 2 controls

NIST SP 800-53 Rev 5 · 2 controls

NIST SP 800-66 Rev 2 · 2 controls

PCI DSS 4.0 · 2 controls

  • 7.2.3 7.2.3 Privileges approved by authorized personnel
  • 8.2.7 8.2.7 Third-party remote access accounts controlled
  • E8-ADMIN-ML3 Restrict Administrative Privileges (ML3)
  • ASD37-21 Disable local administrator accounts (Excellent)
  • NIST-CSF-PR.AA-05 Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties

NIST SP 800-172 · 1 control

  • 3.1.1e Dual Authorization for Sensitive System Operations

SOC 2 · 1 control

  • SOC2-CC6.3 CC6.3 Role-based access, least privilege and segregation of duties

UK Cyber Essentials · 1 control

  • CE-AC.4 Privileged Account Approval and Tracking

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 Privileged Access

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

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