Does your institution force password changes every so often?

We do, every 180 days (used to be every 90), but it is still a huge pain point, and one of the more frustrating things we deal with. I'm seeing more and more that forcing password changes doesn't actually improve security though. Examples of articles that say this:

https://www.extremetech.com/computing/292534-microsoft-says-forced-password-resets-dont-improve-security

https://www.sans.org/security-awareness-training/blog/time-password-expiration-die

https://www.sans.org/security-awareness-training/blog/time-password-expiration-die

https://www.wired.com/2016/03/want-safer-passwords-dont-change-often/

I've been thinking about trying to push getting rid of password changes, or at least offer an alternative, which would be we won't force you to change your password, IF, you turn on two factor authentication.

What does your university do in this area?

Posted Jan 29, 2020, 2:12 PM UTC

811
TaviRider•

I suggest referring to and following NIST Special Publication 800-63B Digital Identity Guidelines. From Section 5.1.1.2 Memorized Secret Verifiers:

Verifiers SHOULD NOT require memorized secrets to be changed arbitrarily (e.g., periodically). However, verifiers SHALL force a change if there is evidence of compromise of the authenticator.

Forcing password changes is known to worsen security rather than improve it. Appendix A covers the justifications for the standard related to passwords.

5
ra4oasisOP•

5.1.1.2

Thank you, this is very helpful.

2
Briancanfixit•

Does your org have good practices for offboarding and account review?

If not, password expiration is the cheep way of achieving account expiration “security”.

3
ra4oasisOP•

Thankfully for the most part, when someone leave the university, their account is turned off almost immediately. Vendor accounts are sort of another animal, but we don't have a lot of those, so it's not a big concern.

1
beejandhispjs•

At the university I used to work at, password changes were required every 90 days and you couldn't use any of your last 10 passwords that were used.  

It felt like it just led to people either only slightly modifying accepted passwords or creating gibberish that they would forget, increasing the volume of password reset requests.

2
phantomtofu•

Our general AD environment does not require password changes. Employees are encouraged to change the password annually. Most services require 2FA (Duo) for employees, though.

Our PCI-scope environment has a separate AD and does require regular password changes, with strict complexity and re-use requirements.

1
iblowuupDesktop Support, ConfigMgr, Jamf, etc...•

Every 180 days and it can't be the last 5.

So many just change it 5 times then set it back to the original :)

1
TaviRider•

That’s why password systems also have a minimum password age. But it’s better to have no password history or age.

1
iisdmitch•

Ours is yearly and cannot reuse last 5

1
juskom95•

You NEED some way to secure you accounts from compromise. While many see password changes as arbitrary, remember that an account can be compromised without your knowledge.

If you don't want passwords (or want long running password times) you can go with MFA like tokens, CAC or apps.

1
xXNorthXx•

Every 180 days with no reuse for the past 24 passwords.

We’ve found the password changed last value on the AD objects to find abandoned accounts.

Users still get the accounts compromised, currently in the process of rolling out MFA for all users to direct that.

1