Plenty of small-business password policies were written years ago and say the same three things: eight characters, a capital letter and a symbol, change it every 90 days. Cyber Essentials asks for more than the first and neither of the other two. The NCSC says regular expiry does harm. Furthermore, Microsoft has not applied it to new tenants since 2021. A policy written to the 2026 requirements is shorter than the one it replaces. Much of it is already switched on in Microsoft 365.

What Cyber Essentials requires of a password policy

The Requirements for IT Infrastructure v3.3, published in April 2026, sets out password-based authentication as a short list of choices.

ControlWhat the requirement says
Protection against guessingAt least one of: multi-factor authentication; throttling, with no more than 10 guesses in 5 minutes; or locking the device after no more than 10 failed attempts
Password qualityAt least one of: multi-factor authentication; a minimum of 12 characters; or a minimum of 8 characters with a deny list that blocks common passwords
Maximum lengthNone allowed
Regular expiryNot enforced
Complexity rulesNot enforced
Guidance to staffAvoid common passwords, keyboard patterns and passwords used elsewhere; use three or more words
StorageUsable secure storage, such as a password manager
CompromiseA process to change a password promptly when you know or suspect it has been compromised
Cloud servicesMulti-factor authentication wherever the service offers it, and always on administrator accounts

Two things stand out. The first is that MFA satisfies both of the first two rows on its own. This is why a tenant with phishing-resistant MFA in place has done most of the work before anyone writes a policy. However, the password behind the MFA still has to be at least 8 characters. The second is that regular expiry and complexity rules appear in the requirement as things a policy should not do.

The password expiry rule to drop

The NCSC’s guidance for system owners puts it bluntly: regular password changing harms security. People asked to change a password every 90 days choose a minor variation of the last one. A stolen password is used at once, so expiry closes nothing. The guidance says to ask for a change only on indication or suspicion of compromise. It also says to monitor sign-ins and lock out inactive accounts instead.

Microsoft’s position is the same. Its password recommendations for Microsoft 365 say the recommended setting for cloud accounts is for passwords never to expire. Microsoft’s password policy notes for Entra add that tenants created from around spring 2021 have that as the default, while older tenants were set to 90 days and may still be. If your firm has been on Microsoft 365 since before then, the expiry setting is worth a look in the admin centre. This is important because it may be enforcing a rule nobody chose.

What replaces expiry is a compromise process. If a password turns up in a breach, if a phishing email was answered, if a leaver’s account was shared, the password changes that day. That is a line in the policy and a job for whoever runs the tenant.

What Microsoft 365 already does

For accounts in Microsoft 365, three of the controls in the table are on before anyone opens a policy document.

  • Guessing protection. Microsoft’s documentation says smart lockout is always on for every tenant, with a default of 10 failed attempts and a one-minute lock that lengthens on each repeat. Customising the values needs Entra ID P1, which Business Premium includes.
  • Deny list. Microsoft’s global banned password list applies to every account, cannot be switched off, and is built from the weak and compromised passwords Microsoft sees in its own security telemetry. A custom list of your own terms, such as the company name, is an Entra ID P1 feature.
  • MFA. The requirement is MFA on every cloud service that offers it, and Microsoft 365 does. The phishing-resistant methods matter more than the password underneath, and from 1 February 2027 Microsoft’s passkey prompt will move staff whose only second factor is a text-message code.

Microsoft recommends a 14-character minimum, above the scheme’s 12, and it is a reasonable number to put in the policy. With MFA enforced, the length rule is belt and braces for the cloud account. It earns its keep on the accounts that MFA does not cover.

Where a password policy falls short on assessment day

The accounts that cause trouble are the ones outside Microsoft 365. This is because the requirement applies to every device and service in scope, and the controls above protect only the tenant.

  1. The laptop sign-in. A local or domain account on a Windows laptop has no MFA unless Windows Hello for Business or a passkey is set up, so it needs 12 characters or 8 plus a deny list, and a lockout after 10 attempts. An old group policy that still says 8 characters, complexity on and 90-day expiry disagrees with the requirement on at least two counts, and a third unless a deny list is in place.
  2. Router and firewall admin accounts. Easily left on a default or shared password, with no lockout, and in scope.
  3. Line-of-business applications. The accounts package, the CRM, the practice management system. Each either offers MFA, which must then be on, or does not, and then the password rules and a lockout apply.
  4. Shared accounts. The requirement is unique credentials per user. A reception login three people know is a finding in its own right.
  5. Nowhere to keep them. The requirement asks for usable secure storage. Without a password manager, staff keep passwords in a notebook, a spreadsheet or the browser, and the assessor will ask.

The one-page policy

A policy that meets the requirement fits on a page and says, in order:

  1. Every user has their own account; nothing is shared.
  2. MFA is on for every cloud service that offers it, and for every administrator.
  3. Passwords are at least 14 characters, with no maximum and no complexity rules; three random words, long enough between them to reach 14, is the way to make one.
  4. Passwords do not expire. They are changed on suspicion of compromise, and the policy names the person who runs that process.
  5. The company password manager is where passwords live.
  6. Where MFA is not in place, accounts lock after 10 failed attempts.

That is the whole document. If you are preparing for Cyber Essentials, The Unite Group, as an authorised certificate issuing body, reviews your application before submission and runs the process from initial audit to certificate. The expiry setting is the quickest place to start on your own, because it may be enforcing a rule the scheme tells you not to enforce.