AC.L2-3.1.19 Encrypt CUI on Mobile
Encrypt CUI held on mobile devices and mobile computing platforms so the data stays protected if a device is lost or stolen.
Source: CMMC 2.0, AC.L2-3.1.19. 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
- Device encryption configuration and compliance reporting · Endpoint management (MDM / EDR)
- Evidence of encryption status per enrolled device · Endpoint management (MDM / EDR)
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Policy identifying which mobile platforms may hold CUI · Policy repository / GRC workspace
First move
Common gaps auditors find
- Encryption assumed by default without verification
- Removable storage in mobile devices left unencrypted
- Devices holding CUI outside the managed estate
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.18 Mobile Device Connection · AC.L2-3.1.20 External Connections