Summer!2017. Summer!2017a. Fall#2017. If your office has a rule that everyone changes their password every 90 days and it must contain a capital letter, a number and a symbol, there is a very good chance a few of your employees' passwords look something like that. People are practical. When you force them to invent a new complicated password four times a year, they find the easiest pattern that satisfies the rules.
This month, the National Institute of Standards and Technology (NIST) published a major update to its digital identity guidelines, Special Publication 800-63B. NIST's guidance is written for federal agencies, but it is widely treated as the reference point for everyone else. And the new version tosses out several rules most of us have been following for over a decade.
What NIST is and why it matters
NIST is the federal agency that publishes technical standards, including a lot of the security guidance that auditors, insurers and IT departments lean on. When a regulator or a client asks whether your password policy follows "best practice," NIST is often what they mean.
That is why this update is a big deal. It is not one blogger's opinion; it is the standards body saying, in effect, that the old rules were making passwords easier to guess, not harder, because of how real people respond to them.
The big changes, in plain English
1. Length beats complexity
The new guidance says passwords should be at least 8 characters, and that systems should allow much longer ones — at least 64 characters. The emphasis shifts toward length. A passphrase like "pelican coffee sunset bridge" is far harder for a computer to guess than "P@ssw0rd1", and it is much easier for a human to remember.
2. Stop the forced composition rules
NIST now recommends against requiring a specific mix of uppercase, lowercase, numbers and symbols. Those rules did not produce random passwords; they produced predictable ones. Everyone capitalizes the first letter and puts the number and the exclamation point at the end, and attackers know it.
3. No more scheduled password changes
This is the one that surprises people most. NIST says organizations should not require passwords to be changed on a fixed schedule. Instead, a password should be changed when there is a reason to — for example, evidence it was stolen or exposed. Forced 60- or 90-day changes just lead to "Password1," "Password2," "Password3."
4. Check new passwords against known bad ones
Instead of complexity rules, NIST wants systems to compare new passwords against lists of passwords that are commonly used, that are dictionary words, or that have already shown up in previous data breaches. If someone tries to set their password to "letmein" or to one sitting in a leaked database, the system should reject it.
5. Drop the password hints and security questions
Hints and "what was the name of your first pet?" questions are out. The answers are often guessable or findable on social media.
6. Let people paste passwords
NIST also recommends allowing paste into password fields. That sounds minor, but it matters: it makes password managers work smoothly, and password managers are how people actually end up with long, unique passwords for every account.
The old rules asked people to remember complicated passwords and change them constantly. The new rules ask for long passwords that are changed when there is a real reason.
What this looks like in a small office
You do not have to adopt every line of a long federal document. But the direction is clear, and several changes are easy to make:
- Raise the minimum length and encourage passphrases. Twelve characters or more is a comfortable target for most offices, and it is easy to hit with three or four ordinary words.
- Relax the expiration rule. If your Windows domain or Office 365 tenant forces a change every 90 days, consider turning that off, as long as you have a way to force a reset when an account may be compromised.
- Block the obvious ones. Company name, the season and year, "Welcome1" — make sure people cannot use them.
- Introduce a password manager for staff who juggle lots of logins. One strong master passphrase beats a sticky note under the keyboard.
Passwords alone still are not enough
Better passwords help, but a password can still be phished, reused on a site that gets breached, or captured by malware. That is why the other half of the story is two-factor authentication — a second step, like a code from an app on your phone, before anyone gets in. It is available for Office 365, for most online banking, and for many of the web apps small businesses rely on. For email in particular, it is the single biggest improvement most offices can make.
NIST's new guidance does address text-message codes, flagging them as a weaker option than an authenticator app because phone numbers can be hijacked. Text codes are still far better than nothing; an app is better still.
Updating your password policy: a checklist
- Review your current policy (written or just "how the server is set up"). Note the length, complexity and expiration settings.
- Set a longer minimum length and tell staff that passphrases are welcome.
- Remove scheduled forced changes, but keep the ability to force a reset when needed.
- Stop using security questions where you have a choice.
- Roll out a business password manager to the people who need it.
- Turn on two-factor authentication for email and remote access first, then other critical accounts.
- Explain the change to staff. People are relieved to hear they do not have to invent a new password every quarter.
It is not often that security advice gets both stronger and easier to live with at the same time, so this is worth taking advantage of. If you would like help rewriting your password policy or setting up two-factor authentication across the office, it is part of the cybersecurity work we do every day. Drop us a line at info@pinellasit.com.
