4.3 Configure Automatic Session Locking on Enterprise Assets
Make enterprise assets lock the session automatically after a set idle period: no more than 15 minutes on general-purpose operating systems and no more than 2 minutes on mobile end-user devices. Implementation Groups: IG1, IG2 and IG3 (part of the IG1 essential cyber hygiene baseline, so every enterprise applies it). Asset type: Devices. Security function: Protect.
Source: CIS Controls v8.1, 4.3. 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 CIS Controls v8.1 in the compliance library.
Each safeguard shows its Implementation Groups. IG1 is the essential baseline for every enterprise, IG2 adds to it, IG3 is all 153. Version 8.1 adds the Govern security function and asks for more processes to be documented; numbering is unchanged from v8.
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
- Group policy or MDM profile showing screen lock timeouts of 15 minutes or less (2 minutes or less for mobile) · Endpoint management (MDM / EDR)
periodic reviewEvidence produced at each review
- Compliance report of devices meeting the setting · Endpoint management (MDM / EDR)
governing documentDocuments that govern the control
- Exception list · Policy repository / GRC workspace
First move
Common gaps auditors find
- Timeouts set to 30 minutes or disabled for some groups
- Mobile devices without enforced lock
- Servers with interactive sessions left unlocked
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 sheet4.2 Establish and Maintain a Secure Configuration Process for Network Infrastructure · 4.4 Implement and Manage a Firewall on Servers