Cyberpediaby Brain

Changing your password every 90 days

Why forcing a password change every 90 days weakens security, and when an employee should change theirs.

On this page
  1. 1In 30 seconds
  2. 2What it is
  3. 3Straight answers
  4. 4How it works
  5. 5What you do
  6. 6Pitfalls
  7. 7Sources
  8. 8Cite this article

In 30 seconds

Where it happens
In the password policy of an organization that requires a change every 30, 60 or 90 days[1].
What it produces
According to the CNIL[2], most participants in the studies use a slightly modified version of the old password, for example by adding a digit at the end.
The reflex
Change your password immediately if you know or suspect it is compromised, and not only because a deadline is coming[1].
If it's already done
When a data breach affects a password, the data controller must force a change at the next login and recommend that the user also change the passwords of other services if the same one was used[2].

What it is

Many systems force users to change their password at regular intervals, typically every 30, 60 or 90 days[1]. The NCSC (UK) writes that this regular change harms security rather than improving it[1].

The CNIL[2] has dropped the renewal requirement for standard user accounts. In its guidelines, the NIST[3] prohibits requiring a periodic change. There are still cases where a password must be changed right away: when it is known or suspected to be compromised[1].

Straight answers

Why does changing a password on a fixed schedule weaken security?

The NCSC (UK)[1] gives five reasons. The user is likely to choose a new password that is only a minor variation of the old one. Stolen passwords are generally exploited immediately. Resetting the password reveals nothing about a possible compromise. An attacker who has access to the account will probably receive the reset request too. Finally, if the password was compromised through insecure storage, the attacker will find the new one in the same place[1].

The CNIL[2] speaks of generally predictable coping strategies, which lower the effective level of security. In its view, the security benefits are minor and largely outweighed by the negative user experience[2]. Microsoft[4] writes that, according to research, almost every rule imposed on users weakens password quality: requirements on length, special characters and changes lead to password standardization, which makes passwords easier to guess or crack[4].

What does the NIST say?

In Special Publication 800-63B, verifiers and providers of authentication services must not require subscribers to change their passwords periodically. The verifier, meaning the service that checks the password, must however force a change if there is evidence that the authenticator is compromised[3]. The same text prohibits imposing other composition rules, such as the requirement to mix several types of characters[3]. These guidelines concern authentication to government information systems[3].

What does the CNIL say?

Its password recommendation, adopted by deliberation no. 2022-100 of 21 July 2022, drops the renewal requirement for standard user accounts. Renewal remains required for privileged accounts, meaning administrator-type accounts or accounts with extended rights[2]. The CNIL specifies that this recommendation is not a standard: it reflects the state of the art on which a data controller can rely for its obligations under the GDPR[2].

And the ANSSI?

The ANSSI published a guide on multifactor authentication and passwords in October 2021, intended in particular for end users[5]. According to the CNIL[2], the ANSSI adopted in 2021 the position of no longer recommending periodic changes for standard users, and the CNIL co-signed this guide[2]. The main recommendations the ANSSI[5] summarizes are: carry out a risk analysis, favor multifactor authentication, favor a possession factor, adapt password strength to its context and use a password vault[5].

What does Microsoft say?

For cloud-only Microsoft 365 accounts, Microsoft's latest recommendations discourage password expiration policies. The recommended setting is that passwords never expire[4].

What replaces periodic changes?

The NCSC (UK)[1] recommends countering the illicit use of compromised passwords with four measures: an effective process for joiners and leavers, automatic locking of inactive accounts, monitoring of suspicious logins (unusual hours, new devices) and encouraging users to report anything that looks suspicious[1]. It adds that two-factor authentication makes a compromised password less useful to the attacker[1].

Another safeguard is the ban list. The NIST[3] asks that any new password be compared against a list of common, expected or compromised values, for example passwords from previous leaks[3]. Microsoft[4] also recommends banning easy-to-guess passwords and requiring registration for two-factor authentication[4].

For employees, Cybermalveillance.gouv.fr[6] advises a different password for each service, a password manager and two-factor authentication when available[6].

How long should a password be?

The texts give different thresholds. The NIST[3] sets at least 15 characters for a password used alone, and at least 8 if it is used only in multifactor authentication[3]. Microsoft[4] recommends at least 14 characters[4]. Cybermalveillance.gouv.fr[6] accepts that a good password has at least 12 characters mixing upper case, lower case, digits and special characters[6].

How it works

The NCSC (UK)[1] explains that the multiplication of passwords and complexity requirements places an unrealistic demand on users. They then invent workarounds: reusing the same password, adopting simple and predictable creation methods, or writing passwords down in a place where they are easy to find. Attackers exploit these known workarounds[1].

The CNIL[2] describes dictionary attacks: instead of testing every combination, they try a limited number of dictionary words or first names with their classic derivations. From the word « kangourou », for example, they test « k4ng0urou », « kangourou01 » or « KaNgOuRoU »[2]. In this CNIL example, « kangourou01 » is a derivation that adds a digit to the starting word[2].

What you do

  • Change the password concerned immediately at the slightest suspicion about an account, or if you learn that an organization or company where you have an account has been hacked. Cybermalveillance.gouv.fr[6] advises not waiting to find out whether it is true[6].
  • If you used a shared computer, change all the passwords entered on it as soon as possible, once you are back on a trusted computer[6].
  • Use a different password for each service: if one password is stolen, only the service concerned is vulnerable[6].
  • Entrust your passwords to a password manager rather than a sticky note or an unprotected file[6]. The NCSC (UK)[1] also recommends password managers where they are suitable.
  • Turn on two-factor authentication when the service offers it[6].
  • Report a two-factor authentication code you did not request. The NCSC (UK)[1] notes that some methods, such as SMS or email notifications, can warn the user of a compromise, since they receive a code they did not ask for[1].
  • Never give your password to a third party: no serious company or organization asks for it by email or phone, even for maintenance or IT support[6].
  • Choose a particularly strong password for your email, because it receives the reset links for your other accounts[6].

Pitfalls

  • The predictable modification. Adding a digit to the old password does not protect you: this is the behavior the CNIL[2] observes in studies on expiration.
  • Believing that the end of rotation applies to every account. According to the CNIL[2], renewal remains required for privileged accounts.
  • Changing the password without changing your situation. If the password is stored insecurely, the attacker will find the new one in the same place[1].
  • Sharing an account. The NCSC (UK)[1] states that, when an account must remain shared, the password should be changed as soon as someone no longer has the right to access it[1].
  • Reusing your work password elsewhere. Microsoft[4] lists this message among the most important to get across, because using an organization password on external sites greatly increases the probability of its compromise[4].
  • Keeping a default password. Cybermalveillance.gouv.fr[6] points out that cybercriminals often know them and advises replacing them as soon as possible[6].

Sources

  1. NCSC (UK), “Password policy: updating your approach”. https://www.ncsc.gov.uk/collection/passwords/updating-your-approach (accessed 14 November 2026)
  2. CNIL, “Mots de passe : recommandations pour maîtriser sa sécurité”, 14 October 2022. https://www.cnil.fr/fr/mots-de-passe-recommandations-pour-maitriser-sa-securite (accessed 14 November 2026)
  3. NIST, “NIST Special Publication 800-63B”. https://pages.nist.gov/800-63-4/sp800-63b.html (accessed 14 November 2026)
  4. Microsoft, “Password policy recommendations for Microsoft 365 passwords”. https://learn.microsoft.com/en-us/microsoft-365/admin/misc/password-policy-recommendations?view=o365-worldwide (accessed 14 November 2026)
  5. ANSSI, “Recommandations relatives à l’authentification multifacteur et aux mots de passe”, 8 October 2021. https://messervices.cyber.gouv.fr/guides/recommandations-relatives-lauthentification-multifacteur-et-aux-mots-de-passe (accessed 14 November 2026)
  6. Cybermalveillance.gouv.fr, “Pourquoi et comment bien gérer ses mots de passe ?”, 23 November 2019. https://www.cybermalveillance.gouv.fr/tous-nos-contenus/bonnes-pratiques/mots-de-passe (accessed 14 November 2026)