ASD ISM 1888 Ensure mobile devices have secure lock screens
What it says
Mobile devices are configured with secure password-based lock screens.
Quoted as published. Everything else on this page is written by Control Stack.
In plain English
Configure mobile devices with a secure lock screen that unlocks with a password, which can be a PIN, rather than a swipe or pattern.
Mobile devices must be configured with secure lock screens that are password-based: a PIN counts, but a swipe or pattern does not. Biometric unlock can sit alongside the password, which must stay set. Other controls set minimum lengths: 15 characters up to PROTECTED, 17 at SECRET and 20 at TOP SECRET for single-factor authentication (ISM-0421, ISM-1557, ISM-0422), or 6, 8 and 10 respectively for multi-factor authentication as ISM-1401 defines it (ISM-1559, ISM-1560, ISM-1561). ISM-2078 bars common or compromised passwords, and ISM-2012 requires locking within 15 minutes of inactivity.
Free. Save your status, tasks and notes.
Why it matters
A lost or stolen device with a weak or missing lock opens straight to organisational data and whatever applications are signed in. A password-based lock stands in the way, and on many devices the password also helps protect the encryption of stored data.
How to implement
List every mobile device and its current lock settings.
Cover every device on a mobile operating system; on those on a desktop one, ISM-2012's screen lock still applies. Compare the device management console with the asset register and sign-in logs, so devices with no enforced lock show up.
Set the password rules for each platform.
The control sets no length, so set the minimum from the data held and the configuration guide or instruction ISM-1867 and ISM-0687 require. ISM-1559, ISM-1560 and ISM-1561 set minimums where the password is one of several factors, and ISM-0421, ISM-1557 and ISM-0422 where it is the only one. Record which applies and why.
Enforce the rules through device management.
Require a password on the whole device, not only on a work area. Block swipe and pattern unlocks, and turn on the setting that rejects repeated or sequential characters, to help keep out common passwords (ISM-2078). Do not impose complexity rules or limit passwords to digits (ISM-2080, ISM-2081). Stop users weakening these settings (ISM-0864).
Set how the lock behaves.
Lock the screen automatically after inactivity: ISM-2012 sets a maximum of 15 minutes for screen locks on systems and requires content to be concealed, so hide notification content too. The control sets no failed-attempt limit. If one is set, many phones erase themselves on reaching it, and ISM-1403 caps user accounts at five failed logons.
Decide on biometric unlock, then test as a user.
Allow biometrics only alongside a set password, where any applicable guide or instruction permits them and unlocking still uses all authentication factors (ISM-2012). On a test device, try a swipe, a pattern, 1234 and a password below the minimum. A device that cannot refuse them stays off organisational systems.
Keep it running
Recheck after operating system upgrades and changes to the password controls, because available settings differ by version. A new model, a lost device or a request to relax the rules should trigger another look.
Evidence and audit
- Check 1 of 3What an auditor asks for
Ask for
Lock settings in the device management console for all devices, and an independent list of devices on a mobile operating system, from sources such as the asset register, carrier bills or sign-in logs.
Look at
Whether every device on the independent list has the lock policy applied, whether it covers the whole device, and what minimum length and automatic lock time it sets.
Good evidence
Every device on the independent list has a whole-device, password-based lock policy applied, with a stated minimum length and an automatic lock time within the 15 minutes in ISM-2012, including any privately owned devices allowed to connect. A recorded exception does not pass.
- Check 2 of 3What an auditor asks for
Ask for
A live test as an ordinary user on a device of each platform sampled from the independent list: setting a swipe, a pattern, 1234 and a password below the minimum, turning the lock off, and leaving the device idle.
Look at
Which settings the device accepts, whether it locks by itself within the set time, and what the lock screen shows.
Good evidence
Each device refuses every weak setting and the attempt to turn the lock off, locks by itself within the set time, and shows no organisational content while locked.
- Check 3 of 3What an auditor asks for
Look at
Whether the rule is at least as strong as those sources where they apply, and whether complexity rules are imposed.
Good evidence
The minimum is no weaker than the guide or instruction, than ISM-1559, ISM-1560 or ISM-1561 where the password is one of several factors, or than ISM-0421, ISM-1557 or ISM-0422 where it is the only one. The organisation has recorded which case applies to each platform and why, and no complexity rule is imposed (ISM-2080).
Mappings
Closest match in ISO/IEC 27001: A.5.15, Access control, which this control partially meets.
ISO/IEC 27001: 6 mappings
This control partially meets A.5.15.
ISM-1888 requires mobile devices to have secure password-based lock screens to prevent unauthorised access. ISO/IEC 27001:2022 Annex A 5.15 requires organisations to establish and implement rules for logical access control based on business and security requirements. While Annex A 5.15 encompasses a wider range of access control measures, mobile device lock screens are a typical implementation of such controls.
This control partially meets A.5.17.
Annex A 5.17 covers the management process for allocating and handling authentication information across the organisation, including the advice given to personnel. ISM-1888 is one specific case within that scope, requiring mobile devices to be configured with secure password-based lock screens, which applies the wider requirement of Annex A 5.17 to the credentials that unlock a mobile device.
This control partially meets A.7.7.
Annex A 7.7 mandates clear screen policies to ensure unattended information processing facilities do not display sensitive information. ISM-1888 requires mobile devices to have secure lock screens, which is an element of a clear screen policy by blocking unauthorised viewings when a device is idle. Annex A 7.7 has a broader enforcement scope across all workstations and facilities.
This control partially meets A.8.1.
ISM-1888 focuses on one specific endpoint protection measure: enforcing secure lock screens on mobile devices. Annex A 8.1 requires protection of information stored on, processed by, or accessible via user endpoint devices, which commonly includes screen lock, authentication and other endpoint hardening measures. ISM-1888 is therefore a specific implementation detail that contributes to satisfying the broader endpoint protection intent of Annex A 8.1.
This control partially meets A.8.3.
ISM-1888 requires secure password-based lock screens to prevent unauthorised access to mobile devices. ISO/IEC 27001:2022 Annex A 8.3 encompasses broader access restrictions for information assets, within which mobile lock screens provide a fundamental layer of security.
This control partially meets A.8.9.
Annex A 8.9 covers establishing, documenting, implementing, monitoring and reviewing configurations across hardware, software, services and networks. ISM-1888 sits inside that scope as one specific configuration requirement, namely that mobile devices carry secure password-based lock screens. Mobile lock screen settings such as timeout and PIN complexity are among the many configurations Annex A 8.9 governs.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




