窪蹋勛圖厙

Skip to main content
keyboard-feat

窪蹋勛圖厙 to change login requirements to use passphrases

窪蹋勛圖厙 TO CHANGE LOGIN REQUIREMENTS TO USE PASSPHRASES | June 3, 2020
STORY BY: EDITORIAL STAFF

On June 15, 窪蹋勛圖厙 changed user login requirements to promote stronger security and improved usability. This change will require users to convert passwords associated with their network ID (abc123) to passphrases. Passphrases are an improvement over passwords, because they are more difficult to brute-force guess while also remaining easy to remember.

Whats happening?

  • The minimum required character length will increase from eight characters to 12.
  • Passphrases can contain words and spaces (e.g. correct horse battery staple).
  • Complexity of a passphrase will be calculated by a meter while the user creates it.
  • To ensure strong passphrases, minimum complexity is required, indicated by a green score on the passphrase meter.
  • Users enrolled in 窪蹋勛圖厙 Duo Security two-factor authentication system will no longer need to change their login passphrases annually.

When is it happening? 

  • This passphrase change will be implemented on June 15
  • All passwords must be converted to passphrases by Dec. 31
  • anytime during this time window.

How does this affect me?

  • Anytime 窪蹋勛圖厙 account credentials need to be changed, they will be required to meet the updated passphrase criteria.
  • All users, faculty, staff, students, alumni and affiliate users are affected.

What should I do?

  • Be aware and prepared to create a passphrase when its time to reset your 窪蹋勛圖厙 credentials in the future.
  • Learn more about passphrases from the following references:
    •  

Other recommendations

  • Passphrases should be long enough to be difficult to guess and unique to you.
  • A passphrase cannot contain your name or network ID.
  • The passphrase should be hard to guess by intuition, even by someone who knows the user well.
  • It also should be easy to remember and type accurately
  • The passphrase a user selects must not be reused between sites, applications, systems and other different sources