ASD ISM 1837 Turn off password never expires and password not required
Rescinded in the March 2026 ISM
ISM-1837 is no longer part of the ISM. This page keeps it for reference, for organisations still working to an earlier version.
The existing control recommending that user accounts are not configured with password never expires or password not required was rescinded.
What it said
User accounts are not configured with password never expires or password not required.
Quoted as published. The guidance below is written by Control Stack.
In plain English
Under ISM editions that included it, no Microsoft AD DS user account, service accounts included, could have the password never expires or password not required option set.
The control said user accounts in Microsoft Active Directory Domain Services (AD DS) could not be configured with either of two account options:
- Password never expires: the password stays valid whatever maximum password age the password policy sets.
- Password not required: the account can be given a blank password, even where policy sets a minimum length.
User accounts include privileged and service accounts, but not computer accounts. The control set no expiry period. No current ISM control carries this requirement.
Why it matters
Malicious actors inside a domain can query AD DS for accounts with these options. A password not required account may have a blank password, and a never-expiring password keeps working long after it leaks, helping them move laterally and escalate privileges.
How to implement
Find every user account with either option set.
Query the userAccountControl attribute of all user accounts in every domain, enabled or disabled, for the DONT_EXPIRE_PASSWORD (65536) and PASSWD_NOTREQD (32) flags. Include service, privileged and built-in accounts; computer accounts are out of scope.
Agree each change with the account's owner first.
Clearing password never expires on an account whose password is older than the maximum password age expires it at once, which can stop a service that logs on with it. Plan the change and the new password together.
Clear both options and set new passwords where needed.
Set one on each account that had password not required, as its password may be blank, and on each service account whose password would expire at once. Use a randomly generated password (ISM-1227), at least 30 characters for service accounts (ISM-1795). Passwords expire only under a maximum password age above 0.
Move services to managed passwords where they support it.
A group managed service account has its password changed automatically by AD DS, so the service needs neither option. Where a service cannot use one, change its password before the maximum password age passes, rather than keeping either option as an exception.
Keep it running
Rerun the query after migrations, bulk imports and new provisioning tools, and alert on user account changes that set either option, since templates and scripts can set them. Recheck service accounts when the maximum password age changes.
Evidence and audit
- Check 1 of 2What an auditor asks for
Ask for
The assessor's own query of userAccountControl across every domain in every forest, with each domain's count of user accounts.
Look at
Whether the query covered every user account, enabled and disabled, and whether any has DONT_EXPIRE_PASSWORD or PASSWD_NOTREQD set.
Good evidence
The query covers every user account in every domain, and none has either option set, including service, privileged, built-in and disabled accounts.
- Check 2 of 2What an auditor asks for
Ask for
Accounts created since the last check, with the templates, scripts and provisioning tools used to create them.
Look at
Whether any new account has either option, and whether any tool sets them.
Good evidence
No account created since the last check has either option, and no template, script or provisioning tool sets them.




