IA-2 Identification and authentication (organizational users)

FedRAMP Moderate · Rev 5

What the standard requires

Uniquely identify and authenticate organizational users and associate that unique identification with processes acting on behalf of those users.

Quoted verbatim from NIST SP 800-53 Rev 5 (OSCAL catalog), which is in the public domain.

Maps to 3 controls in 3 other frameworks

Framework	Control
HITRUST CSF v11	01.g.02 Each user is uniquely identified before accessing operating systems
NIST Cybersecurity Framework (1.1, legacy)	PR.AC-7 Users, devices, and assets authenticated
TISAX (VDA ISA v6)	4.2.2 Strong authentication is used where risk requires

Mappings are CMDash’s own, seeded with the product and shown on both frameworks they connect. In the product they mean evidence you attach here also counts against the controls listed above.

Integrations that carry evidence for this family

Okta

MFA & identity coverage

These connectors produce data relevant to FedRAMP Moderate’s Identification & Authentication family, which is the granularity CMDash publishes — there is no pre-built per-control mapping, and claiming one would be inventing it. You decide which evidence answers which control.

Track IA-2 with evidence behind it

In CMDash this control is a row with an owner, a status, uploaded evidence kept with its full history, and an export an assessor can read.

Start free trial All FedRAMP Moderate controls