I think they removed the requirement to change passwords many years ago.
Everyone needs some sort of password manager. However passwords need to be removed. Using an email would be better. Until your email system gets hacked.
5 Verifiers and CSPs SHALL NOT impose other composition rules (e.g., requiring mixtures of different character types) for passwords.
6Verifiers and CSPs SHALL NOT require subscribers to change passwords periodically. However, verifiers SHALL force a change if there is evidence that the authenticator has been compromised.
I once had a provider, not that long ago, send me an unencrypted verification email with "Your Login:xxxxxxx Your New Password:yyyyyy". Note: it wasn't a temporary password -- it was the one I had just created and changed it to on the site itself.I think they removed the requirement to change passwords many years ago.
Everyone needs some sort of password manager. However passwords need to be removed. Using an email would be better. Until your email system gets hacked.
The only thing that should know your password is you or your password manager. It should not be stored by the other end. They should put the password though a complex one way encryption formula and store the result.I once had a provider, not that long ago, send me an unencrypted verification email with "Your Login:xxxxxxx Your New Password:yyyyyy". Note: it wasn't a temporary password -- it was the one I had just created and changed it to on the site itself.
It does not say when the quoted paragraphs were inserted into the guidelines.5 and 6
Verifiers SHALL NOT impose other composition rules (e.g., requiring mixtures of different character types or prohibiting consecutively repeated characters) for memorized secrets. Verifiers SHALL NOT require users to periodically change memorized secrets. However, verifiers SHALL force a change if there is evidence of compromise of the authenticator.
Damn! That's the combination on my luggage!I3QQa&1365_w77
The best password rules should say the password must be long and not certain combinations of letters. Any other rule will weaken the passwords.I used to log into one system, that was so nasty, you had to include at least two characters that weren't on the keyboard.
(i.e. you'd have to 'compose' them by using key combinations, or the Alt + (hex number) method.)
Blacklists for small sections of obvious passwords are still best practice, and indeed mandated in the NIST documentation I linked to.The best password rules should say the password must be long and not certain combinations of letters. Any other rule will weaken the passwords.
Here is a maths question for you all. If I use a password that is a random 10 characters using any valid character on the keyboard, how much longer must your password be if you only want to use lower case letters (a-z) and it to be even stronger than mine? The answer is not many.
We've tried showing this to the Nevada Gaming Control Board since NIST put it in, but no go. We enforce 16 character minimum passwords, but everyone has to change every 60 days because of the GCB mandates it.5 and 6
Likewise, but at least I can force password changes to keep mine alignedMy workplace requires us to change passwords every 90 days. That wouldn't be a problem in itself, but unfortunately the various applications and systems that are supposed to sync up with password changes...don't. Sometimes I go weeks with two passwords and having to try both with everything.