4.11 Enforce Remote Wipe Capability on Portable End-User Devices
Be able to wipe enterprise data remotely from enterprise-owned portable devices when appropriate, for example after loss or theft or when the user leaves. Implementation Groups: IG2 and IG3 (not in the IG1 baseline; applies from IG2 upward). Asset type: Data. Security function: Protect.
Source: CIS Controls v8.1, 4.11. 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 CIS Controls v8.1 in the compliance library.
Each safeguard shows its Implementation Groups. IG1 is the essential baseline for every enterprise, IG2 adds to it, IG3 is all 153. Version 8.1 adds the Govern security function and asks for more processes to be documented; numbering is unchanged from v8.
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
- Wipe action logs for lost devices and leavers · Endpoint management (MDM / EDR)
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- MDM remote wipe capability enabled for enrolled devices · Policy repository / GRC workspace
- Lost device procedure · Policy repository / GRC workspace
First move
Common gaps auditors find
- Devices not enrolled cannot be wiped
- Leaver process omits wipe
- Wipe initiated but completion not confirmed
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 sheet4.10 Enforce Automatic Device Lockout on Portable End-User Devices · 4.12 Separate Enterprise Workspaces on Mobile End-User Devices