EvidenceSheet
CMMC 2.0 · Identification and Authentication

IA.L2-3.5.2 Authentication

Authenticate or verify the identity of users, processes and devices as a precondition of granting access to organizational systems.

Source: CMMC 2.0, IA.L2-3.5.2. 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.

3
artefacts
2
held by a system
1
at each review
easy
to go live
Identity provider / directory
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

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

  • Authentication mechanism configuration per system · Identity provider / directory
  • Device and service authentication configuration · Endpoint management (MDM / EDR)

periodic reviewEvidence produced at each review

  • Evidence authentication precedes access in all paths · Identity provider / directory

governing documentDocuments that govern the control

none for this control

First move

Automate the pull from your Identity provider / directory. Scheduled export of users, roles and MFA state from the directory; access-review completion pulled from the IdP, not a spreadsheet.

Common gaps auditors find

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 sheet

IA.L2-3.5.1 Identification · IA.L2-3.5.3 Multifactor Authentication