# CIS 4.10 — Enforce Automatic Device Lockout on Portable End-User Devices

- Source: https://support.icompaas.com/support/solutions/articles/a_gen_cis_410_bccb017291-cis-410-enforce-automatic-device-lockout-on-portable-end-user-devices
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [AWS Checks New Version](https://support.icompaas.com/support/solutions/62000112673) › [Respond](https://support.icompaas.com/support/solutions/folders/f_gen_62000112673_respond)
- Last updated: 2026-05-30
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

CIS · Control 4.10 · Priority: high · Component: Respond

### What this control covers

Enforce automatic device lockout following a predetermined threshold of local failed authentication attempts on portable end-user devices, where supported. For laptops, do not allow more than 20 failed authentication attempts; for tablets and smartphones, no more than 10 failed authentication attempts. Example implementations include Microsoft® InTune Device Lock and Apple® Configuration Profile maxFailedAttempts.

### Why it matters

Endpoint posture (encryption, EDR, OS patch state) is also the most common evidence customers ask for in their vendor reviews.

### How to implement

#### AWS

Bake hardening into **EC2 Image Builder** + **AMI accounts**; use **Systems Manager Fleet Manager** for inventory and patch state.

#### Azure

**Intune** enrolment for laptops + phones; Conditional Access requires "compliant device" before any corporate app loads. EDR via **Defender for Endpoint**.

#### GCP

**Org Policy Service** for guardrails and **Config Validator** in CI to pre-check Terraform plans against policy as code (Rego).

#### Google Workspace

**Endpoint Management** (basic/advanced) for BYOD/COPE; require screen lock, disk encryption and OS minimum; block sign-in on jailbroken devices.

#### GitHub

Require **SSO + SCIM** from your IdP on the organisation; enforce **2FA** org-wide and use **fine-grained PATs** (or, better, GitHub Apps) instead of classic tokens. Restrict **outside collaborators**, require signed commits on protected branches, and use **OIDC** from Actions to short-lived AWS/GCP/Azure credentials rather than stored secrets.

#### Zoho Mail

Make **two-factor authentication** mandatory for all users (TOTP, OneAuth, or YubiKey) in _Admin Console → Security_. Configure **SAML SSO** against your IdP and disable password-based logins for admins. Use **role-based privileges** (Admin / Spam Moderator / Mail Account Admin) and review the _Login history_ report monthly for anomalies.

### Evidence to collect

-   `user_device_scan` — Output from your MDM/EDR (Intune, Jamf, Kandji) showing managed-device count, posture and last-check-in.

Endpoint compliance telemetry (Intune, Jamf) proves managed coverage. Focus: Enforce Automatic Device Lockout on Portable End-User Devices.

### Quick checklist

-   Enforce — End User / Portable

### Related articles on this site

-   [1.4 Ensure that 'Allow users to remember multi-factor authentication on devices they trust' is 'Disabled](https://support.icompaas.com/support/solutions/articles/62000219682-1-4-ensure-that-allow-users-to-remember-multi-factor-authentication-on-devices-they-trust-is-disab)
-   [EFS Access Points Should Enforce a User Identity](https://support.icompaas.com/support/solutions/articles/62000233320-efs-access-points-should-enforce-a-user-identity)
-   [Ensure that 'Allow users to remember multifactor authentication on devices they trust' is Disabled (Manual)](https://support.icompaas.com/support/solutions/articles/62000233929-ensure-that-allow-users-to-remember-multifactor-authentication-on-devices-they-trust-is-disabled-m)
-   [Enable Microsoft Entra Authentication for Azure SQL Servers to Centralize Identity and Access Management](https://support.icompaas.com/support/solutions/articles/62000234769-enable-microsoft-entra-authentication-for-azure-sql-servers-to-centralize-identity-and-access-managem)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.