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.
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.
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
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.