Password security tips: 12 for employees

No items found.
Blog thumbnail image

NIST's current guidance dropped two rules that many workplaces still enforce: forced symbols and calendar-based password changes. For passwords used on their own, it sets a minimum length of 15 characters, and 8 when a password is used only as part of multi-factor authentication (NIST SP 800-63B-4). This guide gives 12 tips in 3 sets of 4, a list of habits to stop and a 10-minute session you can run with your team.

One caution first. NIST SP 800-63B-4 is written for the people who build and run login systems, which it calls verifiers, not for employees. The tips below take its findings and the advice of the UK National Cyber Security Centre (NCSC) and the US Cybersecurity and Infrastructure Security Agency (CISA), and turn them into things a person can do.

Why the old rules changed

The NCSC notes that people who swap letters for symbols, such as an "o" for a zero, gain little, because criminals know the trick (NCSC). NIST says systems must not impose other composition rules, such as requiring a mix of character types, and must not require people to change passwords on a schedule. A change is forced only if there is evidence that the password has been compromised (NIST SP 800-63B-4). The NCSC agrees that long-standing advice to fill passwords with random characters, symbols and numbers is not helpful (NCSC: Three random words).

If your own policy still demands a change every 90 days, raise it with IT: the policy may be set by a regulator or a client contract, so check before you act.

Set A: making a password (4 tips)

  1. Make it long, not clever. The NCSC suggests combining three random words, such as "applenemobiro", for a password that is long enough and strong enough (NCSC). NIST's 15-character minimum for a password used alone points the same way. CISA's own advice for individuals is at least 16 characters (CISA: Use strong passwords), so aim for 16 or more.
  2. Use a different password for every account. CISA says to use a different strong password for each account. One leaked password then opens one door, not all of them.
  3. Avoid common passwords. NIST says systems must check new passwords against a blocklist of commonly used, expected or compromised values, so "Password1!" gets rejected. The NCSC also says to avoid significant dates and pet or family names, because most of these details can be found on social media.
  4. Never share a password. A genuine IT request should never ask for yours. If a colleague needs access to something, ask IT to grant it to them.

Our pick: tip 1, make it long. Length is what NIST and the NCSC both lean on, and a few random words are easier to remember than a short string of symbols.

Set B: keeping and using it (4 tips)

  1. Use a password manager. NIST says login systems must allow password managers and autofill, and notes that managers help people choose stronger passwords (NIST SP 800-63B-4). Use the one your company approves.
  2. Do not reuse a work password anywhere else. A breach of a shopping or social site then cannot unlock your work accounts.
  3. Type the address yourself rather than following a login link in an email. NIST states that passwords are not phishing-resistant: a fake page that asks for one can collect it. Open the site from a bookmark or type the address.
  4. Change a password straight away if you think it leaked. This is the case NIST gives for a forced change, and the case where changing it is worth the effort. Tell IT at the same time.

Our pick: tip 7, type the address yourself. It sidesteps fake login pages and takes a few seconds.

Set C: more than a password (4 tips)

  1. Turn on multi-factor authentication (MFA). CISA's guide says to turn it on for each account or app that offers it, using a code from an authenticator app, a text or email code, or a fingerprint or face check (CISA: Turn on MFA).
  2. Do not approve a prompt you did not start. An unexpected approval request may mean someone else has your password. Decline it and tell IT.
  3. Lock your screen when you step away. On most laptops, the Windows key plus L or the Control, Command and Q keys on a Mac do it in one move.
  4. Tell IT when something looks wrong. A strange login alert, an odd email or a lost phone is better reported early than hidden. Make it easy to say so, and thank the person who did.

Our pick: tip 9, turn on MFA. It adds a second check, so a stolen password alone is not enough.

What to stop doing

  • Changing passwords on a calendar. NIST says verifiers must not require periodic changes, unless there is evidence of compromise.
  • Adding a symbol or capital letter because a rule says so. NIST bars systems from imposing composition rules.
  • Using hints and security questions. NIST says systems must not allow a hint that someone who is not logged in can read, and must not prompt people to use knowledge-based questions such as "What was the name of your first pet?".
  • Writing passwords on notes. A password manager does the remembering, so nothing needs to sit on a monitor or under a keyboard.

Run a 10-minute password session with AhaSlides

Use the 12 tips as the content and spend about 10 minutes on them in a team meeting or a security awareness session.

  1. Pick Answer: "Good or bad password habit?" Show a habit, such as "Change it every 90 days no matter what", and let people vote before you give NIST's position.
  2. Word Cloud: "How many accounts do you have?" The size of the numbers makes the case for a manager.
  3. Rating Scale: "How likely are you to use a password manager?" from 1 to 5, asked before and after the session.
  4. Open Ended and Q&A: an anonymous question box for IT, so people can ask what they would rather not say out loud.

For a ready-made course, start from the Security awareness essentials template, and add the Remote work and mobile device security template for teams who log in from outside the office. For more on security training, read about cybersecurity awareness training, phishing pulse checks in Slack and free online polling.

Frequently asked questions

How long should a password be?

At least 15 characters when it is the only factor, and at least 8 when it is used only with multi-factor authentication, according to NIST (NIST SP 800-63B-4). CISA advises individuals to use at least 16 characters, so a long passphrase can meet both.

Should employees change passwords every 90 days?

No. NIST says systems should not force periodic changes, and should force one only if there is evidence that the password is compromised. If your company still asks for it, ask IT whether a rule or contract requires it.

Are password managers safe to use at work?

Yes, and NIST says login systems must allow them. They help with unique, long passwords, so use the one your company approves rather than a tool you picked yourself.

What is a strong password?

A long, unique password or passphrase that is not used anywhere else. The NCSC suggests three random words, and CISA suggests a passphrase of 4 to 7 unrelated words (CISA).

Where to start

Pick Set B, tip 7, for your next team meeting: it takes one slide and a vote. Then ask IT to confirm your company's rules on password length and changes, so the advice you give matches the policy people have to follow.

Subscribe for tips, insights and strategies to boost audience engagement.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Check out other posts

AhaSlides is used by Forbes America's top 500 companies. Experience the power of engagement today.

Get started free
© 2026 AhaSlides Pte Ltd