Azure Security Benchmark PA-1: Separate and limit highly privileged/administrative users

What else in your programme already covers this

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

CMMC 2.0 · 4 controls

AC.L2-3.1.4 Separation of Duties
AC.L2-3.1.5 Least Privilege
AC.L2-3.1.6 Non-Privileged Account Use
AC.L2-3.1.7 Privileged Functions

FedRAMP High · 4 controls

AC-2 Account Management
AC-2(7) Privileged User Accounts
AC-5 Separation of Duties
AC-6(5) Privileged Accounts

FedRAMP Moderate · 4 controls

AC-2 Account Management
AC-2(7) Privileged User Accounts
AC-5 Separation of Duties
AC-6(5) Privileged Accounts

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

ANSSI-HYG-05 Maintain an Exhaustive Inventory of Privileged Accounts
ANSSI-HYG-08 Identify Each Person by Name and Separate User and Administrator Roles
ANSSI-HYG-29 Limit Administration Rights on Workstations to Operational Need

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

CCM-IAM-04 Separation of Duties
CCM-IAM-09 Segregation of Privileged Access Roles
CCM-IAM-10 Management of Privileged Access Roles

NIST SP 800-171 Rev 3 · 3 controls

03.01.04 Separation of Duties
03.01.06 Least Privilege - Privileged Accounts
03.01.07 Least Privilege - Privileged Functions

NIST SP 800-53 Rev 5 · 3 controls

NIST800-AC-2 AC-2 Account Management
NIST800-AC-5 AC-5 Separation of Duties
NIST800-AC-6 AC-6 Least Privilege

PCI DSS 4.0 · 3 controls

2.2.2 2.2.2 Vendor default accounts managed
7.2.2 7.2.2 User access assigned by job function and least privilege
7.2.3 7.2.3 Privileges approved by authorized personnel

ACSC Essential Eight · 2 controls

E8-ADMIN-ML1 Restrict Administrative Privileges (ML1)
E8-MFA-ML2 Multi-Factor Authentication - Maturity Level 2

ASD Strategies to Mitigate Cyber Security Incidents · 2 controls

ASD37-18 Restrict administrative privileges (Essential)
ASD37-21 Disable local administrator accounts (Excellent)

AWS Well-Architected Security Pillar · 2 controls

SEC01-BP02 Secure account root user and properties
SEC03-BP03 Establish emergency access process

CIS Controls v8 · 2 controls

CIS-4.7 Manage Default Accounts on Enterprise Assets and Software
CIS-5.4 Restrict Administrator Privileges to Dedicated Administrator Accounts

ISO 27001:2022 · 2 controls

5.3 Segregation of duties
8.2 Privileged access rights

ISO 27002:2022 · 2 controls

5.3 Segregation of duties
8.2 Privileged access rights

UK Cyber Essentials · 2 controls

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

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

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

Australia My Health Records Act 2012 · 1 control

MYHR-SEC-2 Access controls and user account management

C5 (Germany) · 1 control

C5-IDM-06 Privileged access rights

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

CFTC-SS-3 Information Security Category

HIPAA Security Rule · 1 control

164.308(a)(3)(ii)(A) Authorization and Supervision (Addressable)

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-161 Rev 1 · 1 control

161R1-AC-6 Least Privilege

NIST SP 800-172 · 1 control

3.13.2e Introduce Unpredictability into System Operations

NIST SP 800-66 Rev 2 · 1 control

164.308(a)(3)(ii)(A) Authorization and Supervision (Addressable)

SOC 2 · 1 control

SOC2-CC6.3 CC6.3 Role-based access, least privilege and segregation 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.

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

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