C5 (Germany)
C5: Identity and Access Management

C5 (Germany) C5-IDM-09: Authentication mechanisms

Authenticate every user and automated system component, require two-factor or multi-factor authentication to reach the production environment, permit only passwords, signed certificates or equally strong methods inside it, and enforce risk-derived password rules through configuration.

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

What else in your programme already covers this

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

PCI DSS 4.0 · 7 controls

  • 2.2.2 2.2.2 Vendor default accounts managed
  • 8.2.1 8.2.1 Unique ID assigned to every user
  • 8.2.2 8.2.2 Shared and generic IDs only by exception
  • 8.3.1 8.3.1 Access authenticated with at least one factor
  • 8.3.6 8.3.6 Password minimum length 12 and complexity
  • 8.4.1 8.4.1 MFA for non-console administrative CDE access
  • 8.4.2 8.4.2 MFA for all non-console CDE access

UK Cyber Essentials · 6 controls

  • CE-AC.2 Authenticate Users Before Granting Access
  • CE-AC.7 MFA for Administrative Accounts
  • CE-AC.8 Passwordless Authentication
  • CE-SC.4 Authenticate Users Before Access
  • CE-SC.5 Password-Based Authentication Quality
  • CE-SC.6 Multi-Factor Authentication for Cloud Services

CIS Controls v8 · 5 controls

  • CIS-4.7 Manage Default Accounts on Enterprise Assets and Software
  • CIS-5.2 Use Unique Passwords
  • CIS-6.3 Require MFA for Externally-Exposed Applications
  • CIS-6.4 Require MFA for Remote Network Access
  • CIS-6.5 Require MFA for Administrative Access

FedRAMP High · 5 controls

  • IA-2 Identification and Authentication (Organizational Users)
  • IA-2(1) MFA to Privileged Accounts
  • IA-2(2) MFA to Non-Privileged Accounts
  • IA-5 Authenticator Management
  • IA-5(1) Password-Based Authentication

FedRAMP Moderate · 5 controls

  • IA-2 Identification and Authentication (Organizational Users)
  • IA-2(1) MFA to Privileged Accounts
  • IA-2(2) MFA to Non-Privileged Accounts
  • IA-5 Authenticator Management
  • IA-5(1) Password-Based Authentication

ACSC Essential Eight · 3 controls

  • E8-MFA-ML1 Multi-Factor Authentication - Maturity Level 1
  • E8-MFA-ML2 Multi-Factor Authentication - Maturity Level 2
  • E8-MFA-ML3 Multi-Factor Authentication - Maturity Level 3
  • ASBv3-IM-2 Protect identity and authentication systems
  • IM-1 Use centralized identity and authentication system
  • IM-6 Use strong authentication controls

CMMC 2.0 · 3 controls

HIPAA Security Rule · 3 controls

NIST SP 800-171 Rev 3 · 3 controls

NIST SP 800-66 Rev 2 · 3 controls

  • ANSSI-HYG-10 Define and Verify Password Selection and Sizing Rules
  • ANSSI-HYG-13 Prefer Strong Authentication Where Possible
  • CBPR-06 Security Safeguards
  • CBPR-PR-27 Physical, technical and administrative safeguards
  • ASD37-20 Multi-factor authentication (Essential)
  • ASD37-23 Protect authentication credentials (Excellent)

ISO 27001:2022 · 2 controls

  • 5.17 Authentication information
  • 8.5 Secure authentication

ISO 27002:2022 · 2 controls

  • 5.17 Authentication information
  • 8.5 Secure authentication

NIST SP 800-161 Rev 1 · 2 controls

  • 161R1-IA-2 Identification and Authentication (Organizational Users)
  • 161R1-IA-3 Device Identification and Authentication

NIST SP 800-53 Rev 5 · 2 controls

SOC 2 · 2 controls

  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC6.6 CC6.6 Protection against threats from outside the system boundary

APPI · 1 control

  • AUCDR-IS-1 Limit risk of unauthorised access to the CDR data environment
  • MYHR-SEC-2 Access controls and user account management
  • APP-11 APP 11 - Security of personal information

ISO 27701:2019 · 1 control

  • 6.6.4 System and application access control

NIS2 Directive · 1 control

  • Art.21.2.j Multi-factor or continuous authentication, secured communications and secured emergency communications

NIST SP 800-172 · 1 control

  • 3.5.1e Identification of Systems, Components, and Devices

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

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.

Query this from an agent

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