UEM-05 Endpoint Management
The organisation sets up, operates and evaluates processes, procedures and technical measures that enforce its policies and controls on every endpoint allowed to reach its systems or to store, transmit or process its data.
Source: CSA CCM v4.1, UEM-05. 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
- Compliance reports showing devices meeting or failing policy · Endpoint management (MDM / EDR)
- Conditional access rules blocking non-compliant devices · Endpoint management (MDM / EDR)
periodic reviewEvidence produced at each review
- Effectiveness review records · Endpoint management (MDM / EDR)
governing documentDocuments that govern the control
- Endpoint management configuration profiles and compliance policies · Policy repository / GRC workspace
First move
Common gaps auditors find
- Policies set but non-compliant devices still allowed access
- Coverage gaps on some device platforms
- Enforcement never evaluated
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