[Company name]
Password and Multi-Factor Authentication Policy
| Organization | [Company name] |
|---|---|
| Document | Password and Multi-Factor Authentication Policy |
| Document owner | [Owner name], [Owner title] |
| Approved by | [Approver name], [Approver title] |
| Effective date | [Effective date] |
| Version | [Version] |
| Review frequency | Reviewed [Review frequency] and after any significant change |
| Classification | Internal use |
1. Purpose
This Policy sets the requirements for creating, protecting, and managing passwords and for using multi-factor authentication (MFA) at [Company name]. Its purpose is to prevent unauthorized access to company and client information by making accounts difficult to guess, steal, or misuse, while keeping sign-in practical for employees.
These requirements are aligned with the recommendations in NIST Special Publication 800-63B-4, Digital Identity Guidelines: Authentication and Authenticator Management (2025), published by the U.S. National Institute of Standards and Technology. Where this Policy and a system's technical capabilities differ, [IT contact] will apply the strongest setting the system supports and record any gap in the exceptions register.
2. Scope
This Policy applies to all employees, contractors, and other users with access to [Company name] systems, and to all accounts used for company business, including:
- Computer and network sign-ins (Windows, macOS, domain or directory accounts)
- [Email / productivity platform] and other cloud services
- [Main line-of-business application], accounting, banking, and payroll systems
- Remote access (VPN, remote desktop, remote support tools)
- Administrator accounts on servers, firewalls, Wi-Fi, and cloud consoles
- Vendor portals, social media, and domain registrar accounts used on behalf of the company
- Mobile devices that access company data
3. Password Requirements
Length is the most important factor in password strength. All passwords for company accounts must meet the following requirements:
| Requirement | Standard |
|---|---|
| Minimum length | At least [Minimum password length] characters. Longer is better. |
| Maximum length | Systems must allow at least 64 characters where supported. |
| Allowed characters | All printable characters, including spaces, are allowed. Passphrases of several unrelated words are encouraged. |
| Composition rules | None. Users are not required to include uppercase letters, numbers, or symbols. |
| Uniqueness | Every company account must have its own password. Never reuse a password across accounts or between work and personal accounts. |
| Breached and common passwords | Passwords must not appear on lists of known breached, commonly used, or easily guessed passwords. Systems should check this automatically. |
| Context-specific words | Do not use the company name, your name or username, the name of the service, or simple variations of them. |
| Hints and security questions | Password hints and knowledge-based questions (for example, "What was your first car?") must not be used for account recovery where alternatives exist. |
| Expiration | No scheduled expiration. Passwords are changed only when there is evidence or suspicion of compromise (see Section 5). |
Creating a strong passphrase
A good approach is to combine four or more random, unrelated words, for example "canal pepper orbit lantern". Do not use song lyrics, famous quotes, or personal information. For accounts that do not need to be memorized, let [Company password manager] generate a long random password.
Drafting note: NIST SP 800-63B sets a lower minimum when a password is used together with MFA than when it is the only factor. Many small businesses simply adopt one minimum of 15 characters for everything, which is easy to explain and meets the stricter case. Adjust the minimum if a critical system cannot support it and record that in the exceptions register.
4. System Configuration Requirements
[IT contact] is responsible for configuring company systems so that they enforce this Policy wherever technically possible:
- Enforce the minimum length and remove legacy complexity and expiration settings
- Enable screening against breached and banned password lists (for example, the built-in password protection features of [Email / productivity platform] or the password manager's breach monitoring)
- Limit failed sign-in attempts: accounts or sign-ins must be locked, delayed, or challenged after [Failed attempts before lockout] consecutive failures, with alerts sent to IT for repeated lockouts
- Store passwords only in hashed form using an industry-standard, salted algorithm; never in plain text or reversible encryption
- Allow paste into password fields so users can use the password manager
- Show a "show password" option so users can check long passphrases as they type, where the system supports it
- Disable legacy authentication protocols that cannot enforce MFA
- Change all default passwords on new devices and software before they are put into use
5. When Passwords Must Be Changed
Passwords are not changed on a fixed schedule. A password must be changed immediately, and IT notified, when:
- The user suspects the password was seen, guessed, or entered on a phishing site
- The password manager, a breach-monitoring service, or IT reports the password in a known data breach
- The account shows signs of unauthorized access (unfamiliar sign-ins, new mail rules, unexpected MFA prompts)
- The password was shared with anyone, including by accident
- A device on which the password was stored or typed is lost, stolen, or found to be infected with malware
- An employee or contractor who knew a shared or service account password leaves the company
When a password is changed because of suspected compromise, IT will also sign the user out of all active sessions, review recent account activity, and confirm MFA methods have not been altered by an attacker.
6. Password Manager
[Company name] provides [Company password manager] to all employees. It is the only approved place to store company passwords.
- Use the password manager to generate and store unique passwords for every company account
- Protect the password manager with a strong master passphrase of at least [Minimum password length] characters that is not used anywhere else, and with MFA
- Never store company passwords in browsers, spreadsheets, documents, sticky notes, email, or chat messages
- Share credentials with coworkers only through the password manager's sharing feature, and only when there is a business need
- Do not store company passwords in a personal password manager account, and do not store personal passwords in the company vault
- Company vault contents remain company property and access is removed when employment ends
7. Multi-Factor Authentication Requirements
MFA requires something beyond a password, such as a passkey, security key, or authenticator app approval. MFA must be enabled for:
- Email and the [Email / productivity platform] account, on every device
- All remote access: VPN, remote desktop gateways, and remote support tools
- All administrator and privileged accounts, including cloud consoles, firewalls, and backup systems
- Banking, payroll, accounting, and payment systems
- [Main line-of-business application] and any cloud application holding client or employee data
- The company password manager
- Domain registrar, DNS hosting, website administration, and company social media accounts
- Vendor portals that can change company services or payment details
If a system that holds Confidential or Restricted data does not support MFA, it must be recorded in the exceptions register with compensating controls (for example, access only from the company network or through a VPN protected by MFA).
8. Approved MFA Methods
Not all MFA methods offer the same protection. Phishing-resistant methods cannot be captured by a fake login page and are preferred wherever supported.
| Method | Strength | Use at [Company name] |
|---|---|---|
| Passkeys (device-bound or synced) and FIDO2 security keys | Phishing-resistant | Preferred for all users; required for administrators where supported |
| Windows Hello for Business or platform authenticators | Phishing-resistant | Preferred on company computers |
| Authenticator app push with number matching ([Approved authenticator app]) | Strong | Approved default for most users |
| Authenticator app one-time code (TOTP) | Moderate | Approved when push or passkeys are not supported |
| SMS text or voice call codes | Weaker (vulnerable to SIM swapping and phishing) | Last resort only; recorded as an exception |
| Email codes | Weak | Not approved for company accounts |
MFA devices (phones, security keys) must be protected with a screen lock. Users must register at least two methods, or keep a backup security key, so that losing one device does not lock them out. Backup recovery codes must be stored in [Company password manager].
9. MFA Fatigue and Suspicious Prompts
Attackers who already have a password may send repeated MFA prompts hoping a user will approve one to make them stop, or may call pretending to be IT and ask for a code. Users must:
- Approve an MFA prompt only when they personally just started a sign-in
- Deny any unexpected prompt, and report it immediately to [IT contact] at [IT contact phone] or [Security reporting email]; an unexpected prompt means someone else likely has your password
- Never read an MFA code or approve a prompt for anyone on the phone, by text, or by email, including someone claiming to be IT, a bank, or a vendor. Legitimate IT staff will never ask for your code
- Change the account password right away after reporting an unexpected prompt
IT will investigate reports of unexpected prompts as potential security incidents under the Incident Response Plan.
11. Account Recovery and Help Desk Verification
Attackers frequently target password resets by impersonating employees. Before resetting a password or MFA method, the help desk or [IT provider / MSP] must verify the requester's identity using a method that does not rely on information an attacker could easily find, such as:
- A call back to the phone number already on file (not a number provided during the request)
- Confirmation by the employee's manager through a separate channel
- In-person verification with photo ID
Resets of administrator accounts or MFA methods for executives and finance staff require verification by two of the methods above. All resets are logged.
12. Onboarding and Offboarding
New users receive a temporary password delivered through a secure channel, must change it at first sign-in, and must register MFA before accessing company data. When a user leaves, [IT contact] will on or before their final day:
- Disable the user's accounts and revoke active sessions and MFA methods
- Remove the user from [Company password manager] and transfer any company vault items
- Change the passwords of any shared or service accounts the user knew
- Remove the user from administrator groups, vendor portals, and bank or payment systems
- Recover security keys and company devices
- Confirm mail forwarding and delegated access are set up according to management instructions
13. Exceptions
Any system or user that cannot meet this Policy must be recorded in the exceptions register below, approved by [Owner name], and reviewed at least [Review frequency].
| System / account | Requirement not met | Reason | Compensating control | Approved by | Review date |
|---|---|---|---|---|---|
14. Enforcement
Failure to follow this Policy may result in suspension of access and disciplinary action up to and including termination. Users are encouraged to report mistakes, such as entering a password on a suspicious site, immediately; prompt good-faith reporting will be treated as the right thing to do, not as a violation.
15. Revision History
| Version | Date | Description of change | Author |
|---|---|---|---|
| [Version] | [Effective date] | Initial adoption of this Password and Multi-Factor Authentication Policy | [Owner name] |
16. Approval
This Password and Multi-Factor Authentication Policy has been reviewed and approved by the undersigned and is effective as of [Effective date]. It will be reviewed [Review frequency], after any significant incident, and whenever there is a material change to our systems, staff, or legal obligations.
| Signature: | Name / title: [Approver name], [Approver title] | Date: |
| Signature: | Name / title: [Owner name], [Owner title] | Date: |
Template adapted from the free Password and Multi-Factor Authentication Policy template by PinellasIT (pinellasit.com/templates). Review with your legal counsel and insurer before adoption.
