IA.L2-3.5.3 Multifactor Authentication
Require more than one authentication factor for privileged account access both locally and across the network, and for non privileged account access across the network.
Source: CMMC 2.0, IA.L2-3.5.3. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open CMMC 2.0 in the compliance library.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
- Multifactor configuration showing coverage of the required access cases · Identity provider / directory
- Evidence of enforcement for network access by non privileged users · Identity provider / directory
periodic reviewEvidence produced at each review
- Enrolment records for privileged account holders · Identity provider / directory
governing documentDocuments that govern the control
none for this control
First move
Common gaps auditors find
- Multifactor applied to remote access only, missing local privileged access
- Exemptions granted for service or legacy accounts without compensating control
- Second factor is another knowledge factor
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetIA.L2-3.5.2 Authentication · IA.L2-3.5.4 Replay-Resistant Authentication