AC.L2-3.1.6 Non-Privileged Account Use
Require staff holding privileged accounts to use a non privileged account or role when performing work that does not need elevated rights.
Source: CMMC 2.0, AC.L2-3.1.6. 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
- Logs showing routine activity performed under non privileged accounts · Identity provider / directory
periodic reviewEvidence produced at each review
- Evidence that administrators hold distinct day-to-day accounts · Identity provider / directory
governing documentDocuments that govern the control
- Policy requiring separate privileged and non privileged accounts · Policy repository / GRC workspace
First move
Common gaps auditors find
- Administrators use privileged accounts for email and browsing
- Dual accounts issued but daily use not enforced or monitored
- No detection of privileged account use for nonsecurity tasks
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 sheetAC.L2-3.1.5 Least Privilege · AC.L2-3.1.7 Privileged Functions