Password Security for Businesses: MFA, Zero Trust and Password Policies
How organizations protect accounts: strong password policies, password managers, multi-factor authentication and zero-trust security, explained in plain English.
Weak, reused and stolen passwords are among the most common ways attackers get into business systems. The good news is that the most effective defences are well understood and don't require a huge budget. This guide explains them in plain English: sensible password policies, password managers, multi-factor authentication (MFA) and the zero-trust approach.
How Attackers Get In
- Credential stuffing: attackers take usernames and passwords leaked from one website and try them on others. Anyone who reuses a password is at risk.
- Phishing: a convincing email or text tricks someone into typing their password into a fake login page.
- Password spraying: trying a few very common passwords, such as "Summer2024!", against many accounts at once, avoiding lockouts.
- Brute force: guessing every combination. It only works against short or simple passwords, or stolen password databases that weren't stored securely.
- Social engineering: phoning the help desk while pretending to be an employee who's locked out.
Most of these attacks rely on human habits, not clever hacking, which is why policy and tools make such a difference.
A Modern Password Policy
Older rules ("change your password every 90 days, include a symbol") often made security worse, because people responded with predictable tweaks like Password1!, Password2!. Current guidance from the US National Institute of Standards and Technology (NIST SP 800-63B) recommends:
- Length over complexity. Require at least 8 characters, preferably 15 or more, and allow long passphrases (at least 64 characters).
- No forced periodic changes. Only require a new password when there's evidence it has been compromised.
- Block known-bad passwords. Check new passwords against lists of breached and common passwords, and reject them.
- Allow all characters, including spaces, so passphrases work.
- No password hints or security questions ("What was your first pet's name?"). The answers are often easy to find online.
- Rate-limit login attempts to stop guessing, without permanent lockouts that attackers can abuse.
Passphrases
A passphrase is several random words strung together, such as copper-lantern-orbit-mango. It is long, hard to guess and easier to remember than T7#qL!2x. The words must be chosen at random (the "Diceware" method uses dice for this), not a famous quote or song lyric.
Password Managers
The only practical way for people to have a unique, strong password for every account is a password manager. It generates and stores passwords, fills them in automatically, and only requires the user to remember one strong master password.
For businesses, look for:
- Zero-knowledge, end-to-end encryption, so the provider can't read your vault.
- Secure sharing of team passwords without pasting them into chat or email.
- Admin controls: enforcing policies, removing access when someone leaves, and recovery options.
- Single sign-on (SSO) integration if you already use a service such as Microsoft Entra ID, Google Workspace or Okta.
Well-known business options include 1Password, Bitwarden, Keeper and Dashlane. Check each provider's security history and audits before choosing.
Multi-Factor Authentication (MFA)
MFA requires two or more kinds of proof to log in:
- Something you know: a password or PIN
- Something you have: a phone, hardware security key or smart card
- Something you are: a fingerprint or face scan
Even if a password is stolen, an attacker without the second factor can't get in. Turning on MFA is one of the single most effective security steps an organisation can take.
Not all MFA is equal. From strongest to weakest:
- Phishing-resistant MFA: hardware security keys and passkeys using the FIDO2/WebAuthn standard. They only work on the genuine website, so a fake login page can't capture them.
- Authenticator app codes or push approvals: much better than nothing. Use "number matching" for push approvals, so users can't simply tap "approve" on a request they didn't start.
- SMS codes: better than a password alone, but vulnerable to SIM-swap fraud and interception.
Prioritise the strongest options for administrators, finance staff and anyone with access to sensitive data.
Zero Trust in Plain English
Traditional security treated the office network like a castle: once you were inside the walls, you were trusted. Zero trust assumes there is no safe "inside", because people work from home, apps live in the cloud and attackers may already be in.
The core ideas:
- Verify every request: check who the user is, what device they're on and whether the request makes sense, every time, not just at the front door.
- Least privilege: give people access only to what they need for their job, and remove it when they no longer need it.
- Assume breach: design systems so that one compromised account or laptop can't reach everything. This is often done by segmenting networks and data.
Zero trust is a direction of travel, not a product you buy. Most organisations get there step by step: MFA everywhere, device management, then tighter, role-based access.
Protecting Admin and Service Accounts
- Separate admin accounts: administrators use a normal account for email and browsing, and a separate one only for admin tasks.
- Time-limited access: grant elevated rights only when needed, and remove them automatically afterwards.
- Service accounts and API keys: store them in a secrets manager, rotate them regularly and never hard-code them in scripts.
- Break-glass accounts: keep one or two emergency accounts with very strong credentials, stored securely and monitored closely.
Detecting Problems Early
- Alert on unusual logins: new countries, impossible travel (London and Sydney within an hour) or many failed attempts.
- Monitor for leaked credentials: services such as Have I Been Pwned can alert you when company email addresses appear in breaches.
- Have a plan: know who resets passwords, revokes sessions and investigates when an account is compromised.
Compliance
Regulations rarely dictate exact password rules, but many require "appropriate" access controls. Examples include GDPR for personal data in Europe, HIPAA for US health information and PCI DSS for card payments. PCI DSS version 4.0, for example, requires MFA for access to cardholder data environments. Check the specific requirements for your industry and region.
A Practical Rollout Plan
- Turn on MFA for email, admin accounts and remote access first, then everything else.
- Roll out a password manager with short training, and help people move their passwords into it.
- Update your password policy in line with NIST guidance: longer passwords, breached-password checks, no forced expiry.
- Review who has access to what, and remove old accounts and unnecessary admin rights.
- Train staff to spot phishing, and make it easy and blame-free to report a suspicious email.
- Move towards phishing-resistant MFA, such as passkeys or security keys, starting with high-risk roles.
Conclusion
Strong business password security comes down to a few habits: unique, long passwords stored in a password manager, MFA on every important account, and access limited to what each person needs. These steps stop the vast majority of everyday attacks, and they form the foundation for a zero-trust approach as your organisation grows.
Need a strong password right now? Our free Password Generator creates random passwords in your browser, and nothing is sent to our server.