UEM-02 Application and Service Approval
The organisation defines, records, enforces and evaluates a list of the services, applications and application sources, such as app stores, that endpoints may use when they access or hold organisation-managed data.
Source: CSA CCM v4.1, UEM-02. 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 device or endpoint management policy enforcing the list · Endpoint management (MDM / EDR)
periodic reviewEvidence produced at each review
- Reports of unapproved software detected on endpoints · Endpoint management (MDM / EDR)
- Review records of the approved list · Endpoint management (MDM / EDR)
governing documentDocuments that govern the control
- Approved applications and services list with approved stores · Policy repository / GRC workspace
First move
Common gaps auditors find
- List published but not enforced technically
- Browser extensions and SaaS services omitted
- No review of the list
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 sheetUEM-01 Endpoint Devices Policy and Procedures · UEM-03 Compatibility