UEM-07 Operating Systems
Put endpoint operating system changes, patch levels and application changes through the company's change management process.
4
artefacts
0
held by a system
1
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Change records covering endpoint operating system and application changes · Endpoint management (MDM / EDR)
governing documentDocuments that govern the control
- The patch deployment process and its link to change management · Policy repository / GRC workspace
- Patch level reporting across the estate · Policy repository / GRC workspace
- Emergency patch handling and its retrospective approval · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Endpoint patching run as a separate activity outside change management
- Patch compliance reported without any change record
- Emergency patches deployed with no retrospective record
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