UEM-07 Operating Systems
The organisation routes any change to an endpoint's operating system, its patch level or its applications through its change management process.
Source: CSA CCM v4.1, UEM-07. 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
- Change records for endpoint operating system and application rollouts · Endpoint management (MDM / EDR)
- Endpoint patch compliance report · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
- Patch deployment rings and approval records · Vulnerability scanner / patch tooling
governing documentDocuments that govern the control
- Change management policy section covering endpoints · Policy repository / GRC workspace
First move
Common gaps auditors find
- Endpoint updates pushed without change records
- No staged rollout or testing
- Patch levels not monitored after deployment
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