IA-2(1) Multi-factor authentication to privileged accounts
What the standard requires
Implement multi-factor authentication for access to privileged accounts.
Quoted verbatim from NIST SP 800-53 Rev 5 (OSCAL catalog), which is in the public domain.
Maps to 2 controls in 2 other frameworks
| Framework | Control |
|---|---|
| HITRUST CSF v11 | 01.c.03 Privileged accounts use strong authentication |
| NIST Cybersecurity Framework (1.1, legacy) | PR.AC-7 Users, devices, and assets authenticated |
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
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.
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.