UEM-06 Automatic Lock Screen
The organisation configures every relevant endpoint used interactively so that its screen locks automatically.
Source: CSA CCM v4.1, UEM-06. 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
- Configuration profile setting the screen lock timeout · Endpoint management (MDM / EDR)
- Compliance report showing lock settings applied · Endpoint management (MDM / EDR)
- Exceptions register for devices without automatic lock · Endpoint management (MDM / EDR)
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Definition of which endpoints count as interactive-use · Policy repository / GRC workspace
First move
Common gaps auditors find
- Timeout set by users rather than enforced centrally
- Mobile devices excluded
- No definition of interactive endpoints
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