Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 CCM-IAM-10: Management of Privileged Access Roles

What else in your programme already covers this

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

AWS Well-Architected Security Pillar · 7 controls

SEC01-BP02 Secure account root user and properties
SEC02-BP02 Use temporary credentials
SEC03-BP03 Establish emergency access process
SEC03-BP04 Reduce permissions continuously
SEC03-BP09 Share resources securely with a third party
SEC06-BP03 Reduce manual management and interactive access
SEC10-BP05 Pre-provision access

FedRAMP High · 5 controls

AC-17(4) Privileged Commands and Access
AC-2(7) Privileged User Accounts
AC-6(1) Authorize Access to Security Functions
AC-6(10) Prohibit Non-Privileged Users from Executing Privileged Functions
AC-6(5) Privileged Accounts

FedRAMP Moderate · 5 controls

AC-17(4) Privileged Commands and Access
AC-2(7) Privileged User Accounts
AC-6(1) Authorize Access to Security Functions
AC-6(10) Prohibit Non-Privileged Users from Executing Privileged Functions
AC-6(5) Privileged Accounts

Azure Security Benchmark · 3 controls

ASBv3-PA-5 Set up emergency access
PA-1 Separate and limit highly privileged/administrative users
PA-2 Avoid standing access for user accounts and permissions

CIS Controls v8 · 3 controls

CIS-12.8 Establish and Maintain Dedicated Computing Resources for All Administrative Work
CIS-5.4 Restrict Administrator Privileges to Dedicated Administrator Accounts
CIS-6.5 Require MFA for Administrative Access

CMMC 2.0 · 3 controls

AC.L2-3.1.15 Privileged Remote Access
AC.L2-3.1.6 Non-Privileged Account Use
AC.L2-3.1.7 Privileged Functions

PCI DSS 4.0 · 3 controls

9.2.3 9.2.3 Physical protection of network hardware and lines
9.4.4 9.4.4 Management approval for media leaving facility
8.6.1 8.6.1 Interactive use of system accounts controlled

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-05 Maintain an Exhaustive Inventory of Privileged Accounts
ANSSI-HYG-29 Limit Administration Rights on Workstations to Operational Need

ISO 27001:2022 · 2 controls

8.18 Use of privileged utility programs
8.2 Privileged access rights

ISO 27002:2022 · 2 controls

8.18 Use of privileged utility programs
8.2 Privileged access rights

NIST SP 800-171 Rev 3 · 2 controls

03.01.06 Least Privilege - Privileged Accounts
03.01.07 Least Privilege - Privileged Functions

UK Cyber Essentials · 2 controls

CE-AC.4 Privileged Account Approval and Tracking
CE-AC.6 Periodic Review of Privileged Access

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

Australia My Health Records Act 2012 · 1 control

MYHR-SEC-6 Emergency access controls

C5 (Germany) · 1 control

C5-IDM-06 Privileged access rights

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.1 · 1 control

IAM-10 Management of Privileged Access Roles

HIPAA Security Rule · 1 control

164.308(a)(4)(ii)(C) Access Establishment and Modification (Addressable)

NIS2 Directive · 1 control

Art.21.2.g Basic cyber hygiene practices and cybersecurity training

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

NIST800-AC-6 AC-6 Least Privilege

NIST SP 800-66 Rev 2 · 1 control

164.308(a)(4)(ii)(C) Access Establishment and Modification (Addressable)

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 Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 have you already done?

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 CCM-IAM-10 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 140 of 197 Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 controls already carry evidence.

If you hold NIST SP 800-53 Rev 571.1% covered · 57 gaps If you hold FedRAMP Moderate60.4% covered · 78 gaps If you hold PCI DSS 4.060.4% covered · 78 gaps If you hold C5 (Germany)58.4% covered · 82 gaps If you hold ISO 27001:202256.3% covered · 86 gaps If you hold ISO 27002:202256.3% covered · 86 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. 12 were rejected on the NIST SP 800-53 Rev 5 pair alone.

See the released pairs, $299 each Browse the graph free