UEM-12 Remote Locate
The organisation turns on the ability to locate every managed mobile endpoint remotely, in line with every law and regulation that applies.
Source: CSA CCM v4.1, UEM-12. 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 CSA CCM v4.1 in the compliance library.
Version 4.1 adds 11 controls (among them API security, log sanitisation and a service bill of materials) and renumbers several domains. CSA accepts v4.0.x during its transition; if your STAR assessment is still on v4.0.1, check the numbering against it.
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
- Mobile management configuration enabling device location · Endpoint management (MDM / EDR)
periodic reviewEvidence produced at each review
- Legal or privacy review confirming location tracking is lawful per jurisdiction · Endpoint management (MDM / EDR)
- Employee notice or consent records · Endpoint management (MDM / EDR)
- Records of location use for lost devices · Endpoint management (MDM / EDR)
governing documentDocuments that govern the control
none for this control
First move
Common gaps auditors find
- Location enabled without a privacy review
- Some mobile platforms not enrolled
- No rule on who may look up device location
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 sheet