CMMC 2.0 IA.L2-3.5.6: Identifier Handling

What else in your programme already covers this

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

SOC 2 · 4 controls

SOC2-CC6.1 CC6.1 Logical access security over protected information assets
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
SOC2-P5.1 P5.1 Data subject access

AWS Well-Architected Security Pillar · 3 controls

SEC02-BP05 Audit and rotate credentials periodically
SEC03-BP04 Reduce permissions continuously
SEC03-BP06 Manage access based on lifecycle

FedRAMP High · 3 controls

AC-2(3) Disable Accounts
IA-4 Identifier Management
IA-4(4) Identifier Management | Identify User Status (IA-4(4))

FedRAMP Moderate · 3 controls

AC-2(3) Disable Accounts
IA-4 Identifier Management
IA-4(4) Identifier Management | Identify User Status (IA-4(4))

Azure Security Benchmark · 2 controls

ASBv3-PA-4 Review and reconcile user access regularly
PA-3 Manage lifecycle of identities and entitlements

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

CCM-IAM-07 User Access Changes and Revocation
CCM-IAM-08 User Access Review

HIPAA Security Rule · 2 controls

164.308(a)(4)(ii)(C) Access Establishment and Modification (Addressable)
164.312(a)(2)(i) Unique User Identification (Required)

ISO 27001:2022 · 2 controls

5.16 Identity management
5.18 Access rights

ISO 27002:2022 · 2 controls

5.16 Identity management
8.5 Secure authentication

ISO 27701:2019 · 2 controls

6.6.2 User access management
7.4.5 PII de-identification and deletion at the end of processing

NIST SP 800-66 Rev 2 · 2 controls

164.308(a)(4)(ii)(C) Access Establishment and Modification (Addressable)
164.312(a)(2)(i) Unique User Identification (Required)

PCI DSS 4.0 · 2 controls

8.2.4 8.2.4 User ID lifecycle changes authorized
8.2.6 8.2.6 Inactive accounts removed within 90 days

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

ANSSI-HYG-06 Organise Joiner, Leaver and Role Change Procedures

C5 (Germany) · 1 control

C5-IDM-03 Locking and withdrawal of user accounts in the event of inactivity or multiple failed logins

NIST Cybersecurity Framework 2.0 · 1 control

NIST-CSF-PR.AA-01 Identities and credentials for authorized users, services, and hardware are managed by the organization

NIST SP 800-161 Rev 1 · 1 control

161R1-IA-4 Identifier Management

NIST SP 800-171 Rev 3 · 1 control

03.05.05 Identifier Management

NIST SP 800-53 Rev 5 · 1 control

NIST800-IA-4 IA-4 Identifier Management

UK Cyber Essentials · 1 control

CE-AC.3 Remove or Disable Accounts When No Longer Required

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 CMMC 2.0 have you already done?

CMMC 2.0 IA.L2-3.5.6 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CMMC 2.0 your existing evidence covers. Hold FedRAMP Moderate and 108 of 110 CMMC 2.0 controls already carry evidence.

If you hold FedRAMP Moderate98.2% covered · 2 gaps If you hold NIST SP 800-171 Rev 394.5% covered · 6 gaps If you hold NIST SP 800-53 Rev 585.5% covered · 16 gaps If you hold ISO 27001:202279.1% covered · 23 gaps If you hold ISO 27002:202267.3% covered · 36 gaps If you hold CIS Controls v864.5% covered · 39 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. 1 were rejected on the FedRAMP Moderate pair alone.

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