Azure Security Benchmark
Privileged Access

Azure Security Benchmark ASBv3-PA-7: Follow just enough administration (least privilege) principle

Apply just enough administration by managing permissions at fine granularity, using role-based access control to grant only the access a role needs.

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

What else in your programme already covers this

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

PCI DSS 4.0 · 7 controls

  • 10.3.1 10.3.1 Audit log read access limited to job need
  • 3.5.1.2 3.5.1.2 Disk or partition encryption only on removable media
  • 7.2.1 7.2.1 Access control model defined
  • 7.2.2 7.2.2 User access assigned by job function and least privilege
  • 7.3.3 7.3.3 Access control default deny all
  • 7.2.5 7.2.5 Application and system accounts least privilege
  • 7.2.6 7.2.6 Query access to stored cardholder data restricted

FedRAMP High · 5 controls

  • AC-3 Access Enforcement
  • AC-6 Least Privilege
  • AC-6(1) Authorize Access to Security Functions
  • AU-9 Protection of Audit Information
  • CM-5(5) Access Restrictions for Change | Privilege Limitation for Production and Operation (CM-5(5))

FedRAMP Moderate · 5 controls

  • AC-3 Access Enforcement
  • AC-6 Least Privilege
  • AC-6(1) Authorize Access to Security Functions
  • AU-9 Protection of Audit Information
  • CM-5(5) Access Restrictions for Change | Privilege Limitation for Production and Operation (CM-5(5))

HIPAA Security Rule · 5 controls

NIST SP 800-66 Rev 2 · 5 controls

C5 (Germany) · 4 controls

CMMC 2.0 · 4 controls

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

ISO 27002:2022 · 4 controls

  • 5.15 Access control
  • 8.18 Use of privileged utility programs
  • 8.2 Privileged access rights
  • 8.3 Information access restriction

NIST SP 800-171 Rev 3 · 4 controls

CIS Controls v8 · 3 controls

  • CIS-3.3 Configure Data Access Control Lists
  • CIS-5.4 Restrict Administrator Privileges to Dedicated Administrator Accounts
  • CIS-6.8 Define and Maintain Role-Based Access Control

ISO 27001:2022 · 3 controls

  • 5.15 Access control
  • 8.18 Use of privileged utility programs
  • 8.2 Privileged access rights

ACSC Essential Eight · 2 controls

  • E8-ADMIN-ML1 Restrict Administrative Privileges (ML1)
  • E8-ADMIN-ML3 Restrict Administrative Privileges (ML3)

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 2 controls

  • ANSSI-HYG-09 Assign the Correct Rights on Sensitive Resources
  • ANSSI-HYG-29 Limit Administration Rights on Workstations to Operational Need

AWS Well-Architected Security Pillar · 2 controls

Australia My Health Records Act 2012 · 2 controls

NIST SP 800-161 Rev 1 · 2 controls

NIST SP 800-53 Rev 5 · 2 controls

SOC 2 · 2 controls

  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC6.3 CC6.3 Role-based access, least privilege and segregation of duties

UK Cyber Essentials · 2 controls

  • CE-AC.4 Privileged Account Approval and Tracking
  • CE-AC.5 Separate Admin Accounts for Administrative Activities

APEC Cross-Border Privacy Rules (CBPR) System · 1 control

  • CBPR-PR-27 Physical, technical and administrative safeguards

APPI · 1 control

ASD Strategies to Mitigate Cyber Security Incidents · 1 control

  • ASD37-18 Restrict administrative privileges (Essential)

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

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

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

ISO 27701:2019 · 1 control

  • 6.6.4 System and application access control

NIST Cybersecurity Framework 2.0 · 1 control

  • 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.13.2e Introduce Unpredictability into System Operations

NIST SP 800-218 · 1 control

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-7 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 gapsIf you hold FedRAMP Moderate78.8% covered · 18 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.172.9% covered · 23 gapsIf you hold ISO 27002:202269.4% covered · 26 gapsIf you hold C5 (Germany)65.9% covered · 29 gapsIf 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 eachBrowse the graph free

Query this from an agent

The graph holds this control, the 78 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll Azure Security Benchmark controls