FedRAMP Moderate IA-4: Identifier Management

What else in your programme already covers this

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

CIS Controls v8 · 5 controls

CIS-5.1 Establish and Maintain an Inventory of Accounts
CIS-5.3 Disable Dormant Accounts
CIS-5.5 Establish and Maintain an Inventory of Service Accounts
CIS-6.6 Establish and Maintain an Inventory of Authentication and Authorization Systems
CIS-6.7 Centralize Access Control

Australia Consumer Data Right - Banking (CDR) · 2 controls

AUCDR-IS-1 Limit risk of unauthorised access to the CDR data environment
AUCDR-PS-9 Privacy Safeguard 9 - Adoption or disclosure of government related identifiers

CMMC 2.0 · 2 controls

IA.L2-3.5.5 Identifier Reuse
IA.L2-3.5.6 Identifier Handling

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

CCM-IAM-03 Identity Inventory
CCM-IAM-13 Uniquely Identifiable Users

PCI DSS 4.0 · 2 controls

8.2.1 All users are assigned a unique ID before access to system components or cardholder data is allowed
8.2.4 Addition, deletion, and modification of user IDs, authentication factors, and other identifier objects are managed as follows: • Authorized with the appropriate approval. • Implemented with only the privileges specified on the documented approval

SOC 2 · 2 controls

SOC2-CC6.2 Prior to granting access, registration and authorization processes are established
SOC2-CC6.3 Role-based access and least privilege are enforced

UK Cyber Essentials · 2 controls

CE-AC.1 User Account Approval Process
CE-AC.2 Authenticate Users Before Granting Access

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

ANSSI-HYG-05 Maintain an Exhaustive Inventory of Privileged Accounts

AWS Well-Architected Security Pillar · 1 control

SEC02-BP04 Rely on a centralized identity provider

Australia My Health Records Act 2012 · 1 control

MYHR-REG-11 Ensuring required information is given to the System Operator

Azure Security Benchmark · 1 control

PA-3 Manage lifecycle of identities and entitlements

C5 (Germany) · 1 control

C5-IDM-02 Granting and change of user accounts and 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.312(a)(2)(i) Unique User Identification (Required)

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 Identifier management

NIST SP 800-66 Rev 2 · 1 control

164.312(a)(2)(i) Unique User Identification (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 FedRAMP Moderate have you already done?

FedRAMP Moderate IA-4 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of FedRAMP Moderate your existing evidence covers. Hold ISO 27002:2022 and 182 of 323 FedRAMP Moderate controls already carry evidence.

If you hold ISO 27002:202256.3% covered · 141 gaps If you hold PCI DSS 4.051.1% covered · 158 gaps If you hold ISO 27001:202249.8% covered · 162 gaps If you hold NIST SP 800-171 Rev 345.5% covered · 176 gaps If you hold C5 (Germany)37.2% covered · 203 gaps If you hold CMMC 2.035% covered · 210 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. 348 were rejected on the ISO 27002:2022 pair alone.

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