NIST SP 800-53 Rev. 5 AC-19(5) — Full Device Or Container-Based Encryption

What this control requires

Employs full-device or container-based encryption to protect confidentiality and integrity of data on mobile devices, using fine-grained encryption for specific data structures. This control supports the Device Encryption Software capability within the Access Control family.

In plain English

Employs full-device or container-based encryption to protect confidentiality and integrity of data on mobile devices, using fine-grained encryption for specific data structures. In practice, this means you can prove you access access control-level controls on a defined cadence.

Why it matters

SP 800-53 is the catalogue every U.S. federal authorisation (FedRAMP, FISMA, CMMC) and most regulated industries point at. A missing control surfaces as a Plan of Action & Milestones (POA&M) item that an Authorizing Official must approve before the Authority To Operate is granted or renewed.

This control is rated critical in the source catalogue. Treat gaps here as production incidents in the risk register, not housekeeping.

What an auditor looks for

A 3PAO (FedRAMP) or Independent Assessor (NIST RMF) tests against NIST SP 800-53A assessment procedures. For each control they expect a documented implementation that addresses every assessment objective (Examine, Interview, Test) and an implementation summary in the System Security Plan.

Within Access Control, the assessor will trace your implementation back to the catalogue reference (Control AC-19(5)) and look for objective evidence on the latest two assessment cycles.

How to implement

Endpoint Protection

MDM. Make MDM enrollment a hard gate for device access (Intune compliance + Conditional Access, or Jamf + Okta device trust). Unmanaged devices simply don't get a session token.

EDR. Deploy CrowdStrike / SentinelOne / Defender for Endpoint to every server and laptop; alert on any host that stops sending telemetry for >24h.

Operational checklist

• Access. Document the trigger, the owner and the cadence.
• Security. Document the trigger, the owner and the cadence.
• Data. Document the trigger, the owner and the cadence.
• Device. Document the trigger, the owner and the cadence.
• Protection. Document the trigger, the owner and the cadence.
• Scope: access control, encryption, mobile devices, protection, software, capability, integrity, security.

Evidence to collect

• User Device Scan. MDM compliance state per user device (Intune / Jamf / Workspace ONE).

Endpoint compliance telemetry (Intune, Jamf) proves managed coverage. Focus: Full Device Or Container-Based Encryption.

Common pitfalls

• Pilot MDM rollouts that quietly exclude executives or engineers; carving out the highest-risk users is the most common audit failure.

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

• NIST SP 800-171 Rev. 3 3.1.18 — Access Control for Mobile Devices

Related controls in NIST SP 800-53 Rev. 5

• Control AC-19 — Access Control For Mobile Devices
• Control AC-19(4) — Restrictions For Classified Information
• Control AC-7(2) — Purge Or Wipe Mobile Device
• Control SC-8 — Transmission Confidentiality And Integrity
• Control AC-20(2) — Portable Storage Devices -- Restricted Use
• Control AC-11(1) — Pattern-Hiding Displays

References

• NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5
• Catalogue identifier: Control AC-19(5)

Topics: endpoint securitydata protectionendpoint protectionencryption at rest