NIST SP 800-53 Rev. 5 AC-7(2) — Purge Or Wipe Mobile Device

What this control requires

Purge or wipe data from mobile devices after a defined number of consecutive unsuccessful logon attempts, using organization-specified techniques to protect sensitive information. This control supports the Mobile Device Management System capability within the Access Control family.

In plain English

Purge or wipe data from mobile devices after a defined number of consecutive unsuccessful logon attempts, using organization-specified techniques to protect sensitive information. In practice, this means you can prove you access management-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 high. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation.

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-7(2)) 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.
• Information. 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.
• Unsuccessful. Document the trigger, the owner and the cadence.
• Scope: management, access control, information, organization, system, logon attempts, wipe mobile device, mobile devices.

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: Purge Or Wipe Mobile Device.

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-16(8) — Association Techniques And Technologies
• Control AC-11(1) — Pattern-Hiding Displays
• Control AC-9(4) — Additional Logon Information
• Control AC-17(1) — Monitoring And Control

References

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

Topics: endpoint securityendpoint protection