C5 (Germany)
C5: Identity and Access Management

C5 (Germany) C5-IDM-06: Privileged access rights

Issue privileged access personally and for a risk-based limited period, tie each technical user to a named individual, log privileged activity, alert responsible personnel automatically on defined misuse indicators, and apply disciplinary measures where misuse is proven.

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

What else in your programme already covers this

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

NIST SP 800-161 Rev 1 · 6 controls

AWS Well-Architected Security Pillar · 5 controls

FedRAMP High · 5 controls

  • AC-17(4) Privileged Commands and Access
  • AC-2(7) Privileged User Accounts
  • AC-6 Least Privilege
  • AC-6(5) Privileged Accounts
  • AC-6(9) Log Use of Privileged Functions

FedRAMP Moderate · 5 controls

  • AC-17(4) Privileged Commands and Access
  • AC-2(7) Privileged User Accounts
  • AC-6 Least Privilege
  • AC-6(5) Privileged Accounts
  • AC-6(9) Log Use of Privileged Functions

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 4 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-13 Prefer Strong Authentication Where Possible
  • ANSSI-HYG-29 Limit Administration Rights on Workstations to Operational Need

Azure Security Benchmark · 4 controls

  • ASBv3-AM-4 Limit access to asset management
  • ASBv3-PA-7 Follow just enough administration (least privilege) principle
  • PA-1 Separate and limit highly privileged/administrative users
  • PA-2 Avoid standing access for user accounts and permissions

CMMC 2.0 · 4 controls

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

ASD Strategies to Mitigate Cyber Security Incidents · 3 controls

  • ASD37-18 Restrict administrative privileges (Essential)
  • ASD37-20 Multi-factor authentication (Essential)
  • ASD37-21 Disable local administrator accounts (Excellent)

CIS Controls v8 · 3 controls

  • CIS-5.4 Restrict Administrator Privileges to Dedicated Administrator Accounts
  • CIS-6.5 Require MFA for Administrative Access
  • CIS-6.8 Define and Maintain Role-Based Access Control

UK Cyber Essentials · 3 controls

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

ACSC Essential Eight · 2 controls

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

Australia My Health Records Act 2012 · 2 controls

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 Cybersecurity Framework 2.0 · 2 controls

  • NIST-CSF-DE.CM-03 Personnel activity and technology usage are monitored to find potentially adverse events
  • 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-171 Rev 3 · 2 controls

NIST SP 800-172 · 2 controls

  • 3.13.2e Introduce Unpredictability into System Operations
  • 3.9.2e Insider Threat Program

NIST SP 800-53 Rev 5 · 2 controls

PCI DSS 4.0 · 2 controls

  • 7.2.2 7.2.2 User access assigned by job function and least privilege
  • 8.4.1 8.4.1 MFA for non-console administrative CDE access

SOC 2 · 2 controls

  • SOC2-CC6.2 CC6.2 Registering and authorising users before issuing credentials
  • SOC2-CC6.3 CC6.3 Role-based access, least privilege and segregation of duties

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

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

HIPAA Security Rule · 1 control

ISO 27017:2015 · 1 control

ISO 27018:2019 · 1 control

  • 9.2.3 Management of privileged access rights

NIS2 Directive · 1 control

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

NIST SP 800-66 Rev 2 · 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 C5: Identity and Access Management

You are reading one control. How much of C5 (Germany) have you already done?

C5 (Germany) C5-IDM-06 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of C5 (Germany) your existing evidence covers. Hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 and 95 of 121 C5 (Germany) controls already carry evidence.

If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.178.5% covered · 26 gapsIf you hold NIST SP 800-53 Rev 572.7% covered · 33 gapsIf you hold FedRAMP Moderate71.1% covered · 35 gapsIf you hold ISO 27002:202267.8% covered · 39 gapsIf you hold ISO 27001:202257% covered · 52 gapsIf you hold NIST SP 800-171 Rev 350.4% covered · 60 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 Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 pair alone.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

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

MCP endpointAll C5 (Germany) controls