Padlock and a phone with a check mark, titled Account Security about strong passwords and two-factor login
Cybersecurity and network guides

Business Password Policy and MFA: A Simple Guide Employees Actually Follow

Key takeaways

  • An effective password policy is simple enough that everyone follows it.
  • Length matters more than complexity, and passwords must never be reused.
  • A company password manager solves storage and safe sharing.
  • Enable MFA first on email, finance systems and manager accounts.
  • Close accounts and change shared passwords as soon as anyone leaves.

Many account compromises require no advanced skill at all: a password reused on another site that leaked, or a password shared by five employees and unchanged for years. A business password policy does not need to be complicated to work. Exhausting rules push people to write passwords on sticky notes or reuse them everywhere. The goal is a simple policy that everyone actually follows.

What modern guidance recommends

The NIST digital identity guidelines emphasize password length and screening against leaked passwords rather than complex symbols and forced periodic changes. In practice:

  • Length beats complexity: a memorable passphrase of several words is stronger than a short string of symbols.
  • No routine rotation without a reason: change a password when there is a sign of compromise, not every month by default.
  • Block common and leaked passwords: such as the company name plus a year, or 123456.
  • A unique password for every service: which is practically impossible without a password manager.

A company password manager

A password manager stores strong, unique passwords for every account and lets teams share access without sending credentials over chat or email. Choose one that supports:

  • Shared vaults per department with clear permissions.
  • Instant access removal when someone leaves.
  • Multi-factor authentication on the manager itself.

Multi-factor authentication: start with critical accounts

Multi-factor authentication (MFA) means a password alone is not enough to sign in. CISA guidance describes it as one of the most effective steps to protect accounts. Do not try to roll it out everywhere in one day; follow this order:

  1. Company email, because it is used to reset passwords for everything else.
  2. Domain registrar, hosting and website admin panels.
  3. Banking and accounting systems.
  4. Social media pages and advertising accounts.
  5. Internal systems such as CRM and ERP.

Prefer authenticator apps or security keys over SMS codes where possible, and store recovery codes somewhere secure that the company controls.

Shared accounts and staff departures

Shared accounts such as “sales@” or a Facebook page login need a clear owner inside the company. When anyone leaves, follow a fixed checklist: disable their account, change shared passwords they knew, remove their devices from MFA, and transfer ownership of their files and pages.

Signs an account may be compromised

  • A sign-in alert from an unknown device or city.
  • New mail forwarding rules the owner did not create.
  • Customers asking about strange messages sent from a company address.
  • Repeated MFA prompts the employee did not trigger.

When any of these appear, change the password immediately, sign out all active sessions, review forwarding rules and connected apps, and inform whoever handles IT.

A Short Sample Password Policy

  1. Passwords are at least 12 characters; a memorable passphrase is preferred.
  2. No password is reused across accounts, especially between work and personal accounts.
  3. All passwords are stored only in the company-approved password manager.
  4. MFA is mandatory for email, finance systems and manager accounts.
  5. Passwords are never sent by WhatsApp, email or paper.
  6. Staff report suspicious messages or unknown sign-ins immediately.
  7. Accounts are closed and shared passwords changed on an employee's last day.

Rolling Out the Policy Without Resistance

Policies fail when imposed suddenly without explanation. Start with a short session explaining why protection matters to staff and how a password manager makes life easier. Then enable MFA in phases, starting with management as an example, with support available in the first days. Review adoption after a month and fix the obstacles rather than blaming people. Our guide to business backups covers the next layer if an account is compromised anyway, and our network infrastructure service helps secure the network itself.

Choosing and Rolling Out a Password Manager

Choose a manager that supports team accounts, shared folders with permissions, desktop and mobile apps, and lets administrators remove access when someone leaves. Start by moving shared and critical service passwords, such as domain, hosting, social media and banking, then ask each employee to move their work accounts. Name at least two administrators so access never depends on one person.

Admin and Finance Accounts First

Attackers look for the account that opens the most doors: the email administrator, hosting, banking and payment gateways, and admin accounts in ERP and CRM. Apply stricter rules there: MFA with an app or security key, no everyday use, and a monthly review of sign-in logs.

On an employee's last day, close or redirect their email, remove password-manager and system access, change shared passwords they knew and recover company devices.

Keep the policy to one page

Write the policy on a single page in plain language, explain it in a short session with real examples, and pair it with awareness training on phishing emails. The strongest password does not help if someone types it into a fake login page.

The AISMISR cybersecurity and business protection team can review your current accounts, identify the ones at highest risk, and help you roll out MFA and a password manager.

Frequently asked questions

Should passwords be changed every 90 days?

Modern guidance does not recommend forced periodic changes without reason, because they push people towards predictable passwords. Change a password when a leak is suspected or someone who knew it leaves.

Which type of MFA is best?

Authenticator apps and security keys are stronger than SMS, but any MFA is far better than none. Start with email, manager accounts and financial systems.

How should shared accounts be handled?

Reduce them as much as possible, share them through a password manager with permissions, and change them as soon as anyone who used them leaves.

Articles you may like