Azure Security Benchmark
Privileged Access

Azure Security Benchmark ASBv3-PA-6: Use privileged access workstations

Provide secured, isolated workstations for sensitive roles such as administrators, developers and critical service operators, so administrative sessions do not originate from general-purpose endpoints.

What else in your programme already covers this

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

FedRAMP High · 5 controls

  • AC-17 Remote Access
  • AC-17(4) Privileged Commands and Access
  • AC-6(2) Non-Privileged Access for Nonsecurity Functions
  • MA-4 Nonlocal Maintenance
  • SC-2 Separation of System and User Functionality

FedRAMP Moderate · 5 controls

  • AC-17 Remote Access
  • AC-17(4) Privileged Commands and Access
  • AC-6(2) Non-Privileged Access for Nonsecurity Functions
  • MA-4 Nonlocal Maintenance
  • SC-2 Separation of System and User Functionality
  • AC-17 Remote Access
  • AC-17(4) Privileged Commands and Access
  • AC-6(2) Non-Privileged Access for Nonsecurity Functions
  • MA-4 Nonlocal Maintenance
  • SC-2 Separation of System and User Functionality
  • AC-17 Remote Access
  • AC-17(4) Privileged Commands and Access
  • AC-6(2) Non-Privileged Access for Nonsecurity Functions
  • MA-4 Nonlocal Maintenance
  • SC-2 Separation of System and User Functionality

CMMC 2.0 · 4 controls

NIST SP 800-53 Rev 5 · 4 controls

  • ANSSI-HYG-08 Identify Each Person by Name and Separate User and Administrator Roles
  • ANSSI-HYG-27 Prohibit Internet Access from Administration Workstations and Servers
  • ANSSI-HYG-28 Use a Dedicated and Partitioned Network for Administration

ISO 27001:2022 · 3 controls

  • 6.7 Remote working
  • 8.1 User end point devices
  • 8.18 Use of privileged utility programs

ISO 27002:2022 · 3 controls

  • 6.7 Remote working
  • 8.1 User endpoint devices
  • 8.2 Privileged access rights

ACSC Essential Eight · 2 controls

CIS Controls v8 · 2 controls

  • CIS-12.8 Establish and Maintain Dedicated Computing Resources for All Administrative Work
  • CIS-4.6 Securely Manage Enterprise Assets and Software

NIST SP 800-171 Rev 3 · 2 controls

  • ASD37-18 Restrict administrative privileges (Essential)
  • SEC06-BP03 Reduce manual management and interactive access

C5 (Germany) · 1 control

HIPAA Security Rule · 1 control

NIST SP 800-172 · 1 control

  • 3.1.2e Restrict Access to Organization-Owned, Provisioned, or Issued Information Resources

NIST SP 800-218 · 1 control

PCI DSS 4.0 · 1 control

  • 2.2.7 Non-console administrative access encrypted

UK Cyber Essentials · 1 control

  • CE-AC.5 Separate Admin Accounts for Administrative Activities

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