Plenty of company password policies still read the same way they did years ago: at least eight characters, one capital, one number, one symbol, and a new password every 90 days. Current guidance has moved on. NIST Special Publication 800-63B-4, the United States National Institute of Standards and Technology's authentication guidance published in 2025, favours long passwords, checks against known breached passwords and multi-factor authentication. It discourages forced periodic changes and complicated character rules, because they push people towards predictable passwords and sticky notes.
Ten password policy best practices for 2027
1. Set minimum lengths by type of account
Length is what makes a password hard to guess. Our NIST-aligned template uses these minimums:
- Any account that relies on a password alone: 15 characters.
- Accounts protected by MFA: at least 8 characters, and we suggest 12.
- Admin accounts and the password manager main password: 15 characters, always with MFA.
- Service accounts and device admin logins: 25 random characters generated by the password manager.
Systems should accept long passwords (at least 64 characters), allow pasting and let password managers fill them in.
2. Encourage passphrases and drop composition rules
Four or more random words make a passphrase that is long and easy to remember. Staff can use any characters, including spaces, without being forced to add a capital, a number and a symbol.
3. Stop forced periodic changes
Change a password when there is a reason: you think someone knows it, you typed it into a page that may have been fake, a breach notice or password manager warns you, you reused it elsewhere, or someone who knew a shared password has left. Otherwise, leave it alone.
4. Block breached and common passwords
Criminals try leaked and common passwords first. Turn on checks that reject passwords found in breach lists, and add words guessers would try for your organization: your company name, your town or parish, or "Jamaica" with a year. Examples to ban include "Password1", "Welcome123" and keyboard patterns.
5. Require MFA on the accounts that matter most
Make multi-factor authentication mandatory for email, remote access, admin accounts, finance and banking systems, the password manager, and website and domain accounts. Use the strongest method each system offers: passkeys or hardware security keys first, then an authenticator app with number matching, and text message codes only when nothing better exists, because phone numbers can be stolen through SIM swaps.
6. Give everyone a password manager
You cannot ask people for a unique long password on every account without giving them somewhere to keep them. Roll out a password manager before the new rules take effect, and share logins only through its sharing feature, never by email, text or WhatsApp.
7. Control shared and service accounts
Keep a register of every shared login and service account with a named owner, change shared passwords when someone who knew them leaves, and never write service account passwords into scripts or configuration files.
8. Change default passwords on every device
Routers, Wi-Fi access points, firewalls, CCTV recorders, access control panels, printers and UPS network cards often ship with published default passwords. Change them before the device is used, and keep the admin login in the password manager rather than on a sticker.
9. Make resets safe
Confirm a person's identity before resetting a password or MFA, using a method you trust such as calling back on a number in the staff directory. Treat requests to register a new phone for MFA with extra care. Drop security questions and password hints, and lock or slow down sign-in after repeated failed attempts.
10. Separate admin accounts from everyday accounts
Anyone who needs admin rights gets a second account for admin work only. This is the core of privileged access management, covered in more detail below.
Privileged access management (PAM) basics
Privileged access management, or PAM, is the set of controls around admin accounts: the accounts that can change settings, create users, reset passwords or reach all the data on a system. Large organizations often buy PAM software that vaults admin passwords and records sessions. Smaller organizations can get most of the benefit with a few rules:
- Separate admin accounts, never used for email, browsing or opening attachments.
- Phishing-resistant MFA (a passkey or security key) on admin accounts wherever the system supports it.
- Admin rights only with approval, only for the systems a person needs, and a review of the admin list every three months.
- No admin rights for staff on their own computers unless approved.
- Named accounts for IT providers and vendors, removed when their work ends.
- One or two emergency "break glass" admin accounts, stored securely and changed after each use.
Our template's admin and privileged accounts section covers these core controls. It is not a full PAM policy for a large enterprise, but it is the right starting point for most small and mid-sized organizations.
Sample password policy clauses
If you are looking for a company password policy sample, here are three clauses from our template that show the modern approach:
When an auditor or insurer still asks for 90-day changes
Some older audit checklists, insurers or client contracts still ask for scheduled password changes or complexity rules. Rather than applying an outdated rule to everyone, record it as an exception for the systems it covers, with the reason and who approved it. Our template has an exceptions section for exactly this.
Rolling out a new password and authentication policy
- Choose and set up a password manager first.
- List your systems and record where MFA is on; fix email, remote access, admin and finance accounts first.
- Check what each system can enforce, such as minimum length and banned password lists, and record any gaps as exceptions.
- Train staff on the new rules and how to use the password manager and MFA.
- Collect signed acknowledgements and review the policy every year.
A password policy works best alongside an IT acceptable use policy, which covers devices, email, messaging and personal phones. Staff also need to recognize the phishing messages designed to steal passwords; our security awareness training covers passphrases, MFA and spotting fake sign-in pages, and our guide to running a phishing test shows how to check that the lessons stick.
Weak or stolen passwords are behind many data breaches. In Jamaica, a breach affecting personal data must be reported to the Information Commissioner within 72 hours of becoming aware of it, so a strong password and authentication policy is part of meeting your Data Protection Act duties too.