- Enforce full-device encryption through device management and treat an unencrypted device as failing posture, blocked from CUI-bearing services.
- Where CUI confidentiality rests on the encryption, FIPS-validated cryptographic modules become relevant — check the platform's validation status rather than assuming.
3.1.19OFFICIAL STATEMENT BELOWDERIVED REQUIREMENTPENDING NIST SME REVIEW
3.1.19 — CUI encryption on mobile
3.1 Access Control · NIST SP 800-171 Rev. 2 · The heading label is this site's navigational shorthand; the official language is the statement below.
Official requirement statement (verbatim)
Encrypt CUI on mobile devices and mobile computing platforms.
NIST SP 800-171 Rev. 2 — Protecting CUI in Nonfederal Systems ↗NIST SP 800-171A — Assessing Security Requirements for CUI ↗Independent interpretation
What this requirement is after
Any CUI that lands on a mobile device or mobile computing platform sits under encryption, so a lost phone or laptop bag is an inconvenience rather than an incident. Enforcement, not user diligence, is what makes this true.
Across revisions
Withdrawn as a standalone slot in Rev. 3 (03.01.19); mobile encryption is carried inside Access Control for Mobile Devices, 03.01.18.
Mapped practices
Brilliant at the Basics practices that support this requirement
No practice maps to this requirement — deliberately.
The campaign’s twenty practices are a priority list, not a control catalog, and none of them works this requirement’s substance directly. It still applies to you if it is in your contract’s scope: address it through your own implementation and the related artifacts below, and treat the absence of a mapping here as honesty, not permission to skip it.
Doing the work
Implementation considerations and evidence
- Device management posture reports showing encryption enforced across enrolled devices
- The policy configuration requiring encryption before access
Artifacts
Templates and worksheets with a mapped relationship
No artifact in the library names this requirement yet. The library index groups everything by category and practice.
The other revision
Where this lands in Rev. 3
Provenance
Sources and review status
| Primary sources | NIST SP 800-171 Rev. 2 — Protecting CUI in Nonfederal Systems · NIST SP 800-171A — Assessing Security Requirements for CUI |
|---|---|
| Review status | Pending NIST SME review |
| Content version | 1.0 |
| Updated |