Azure Security Benchmark
Privileged Access

Azure Security Benchmark ASBv3-PA-4: Review and reconcile user access regularly

Review privileged account entitlements on a regular cycle and confirm the access granted remains valid for control plane, management plane and workload administration.

What else in your programme already covers this

This control maps to 55 controls across 27 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-2 Account Management
  • AC-2(7) Privileged User Accounts
  • AC-6(7) Review of User Privileges
  • PS-5 Personnel Transfer

FedRAMP Moderate · 4 controls

  • AC-2 Account Management
  • AC-2(7) Privileged User Accounts
  • AC-6(7) Review of User Privileges
  • PS-5 Personnel Transfer
  • ANSSI-HYG-05 Maintain an Exhaustive Inventory of Privileged Accounts
  • ANSSI-HYG-06 Organise Joiner, Leaver and Role Change Procedures
  • ANSSI-HYG-09 Assign the Correct Rights on Sensitive Resources

CIS Controls v8 · 3 controls

  • CIS-5.1 Establish and Maintain an Inventory of Accounts
  • CIS-5.3 Disable Dormant Accounts
  • CIS-6.2 Establish an Access Revoking Process
  • AC-2 Account Management
  • AC-6(7) Review of User Privileges
  • PS-5 Personnel Transfer
  • AC-2 Account Management
  • AC-6(7) Review of User Privileges
  • PS-5 Personnel Transfer

PCI DSS 4.0 · 3 controls

  • 7.2.5.1 App and system account review cadence
  • 8.2.6 Inactive user accounts are removed or disabled within 90 days of inactivity
  • 7.2.4 All user accounts and related access privileges, including third-party/vendor accounts, are reviewed as follows: • At least once every six months. • To ensure user accounts and access remain appropriate based on job function.

C5 (Germany) · 2 controls

  • C5-IDM-04 Withdraw or adjust access rights as the task area changes
  • C5-IDM-05 Regular review of access rights

CMMC 2.0 · 2 controls

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

  • AC-2 Account Management
  • PS-5 Personnel Transfer

NIST SP 800-66 Rev 2 · 2 controls

SOC 2 · 2 controls

  • SOC2-CC6.2 Prior to granting access, registration and authorization processes are established
  • SOC2-CC6.3 Role-based access and least privilege are enforced

UK Cyber Essentials · 2 controls

  • CE-AC.3 Remove or Disable Accounts When No Longer Required
  • CE-AC.6 Periodic Review of Privileged Access

APPI · 1 control

  • ASD37-18 Restrict administrative privileges (Essential)

ISO 27701:2019 · 1 control

  • 6.6.2 User access management
  • 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

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