What evidence do auditors commonly ask for on AC.L2-3.1.7 Privileged Functions?

Configuration preventing privileged function execution by standard users; Audit log samples showing captured privileged function execution; Test results of an attempted privileged action by a non privileged account.

What is the most common gap auditors find on AC.L2-3.1.7?

Privileged functions blocked but execution not logged

CMMC 2.0 · Access Control

`AC.L2-3.1.7` Privileged Functions

Block non privileged users from executing privileged functions, and capture every execution of such functions in the audit log.

Source: CMMC 2.0, AC.L2-3.1.7. 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.

artefacts

held by a system

at each review

moderate

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

Configuration preventing privileged function execution by standard users · Identity provider / directory

periodic reviewEvidence produced at each review

Audit log samples showing captured privileged function execution · Identity provider / directory
Test results of an attempted privileged action by a non privileged account · Identity provider / directory

governing documentDocuments that govern the control

none for this control

First move

Start with the 1 of 3 artefacts that already live in a system (Identity provider / directory); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

Privileged functions blocked but execution not logged
Logging enabled without covering privileged function use
Local administrator rights on endpoints bypass the restriction

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

AC.L2-3.1.6 Non-Privileged Account Use · AC.L2-3.1.8 Unsuccessful Logon Attempts