Implementing MFA and a password policy does not have to become a large IT project. This guide gives small businesses a practical deployment checklist, copy-ready policy language, a way to estimate implementation costs, a comparison framework for MFA providers and methods, and a quarterly access-audit workflow you can repeat after hiring, tool changes, or role changes.
Overview
Multi-factor authentication (MFA) requires a second proof of identity in addition to a password. That proof might be a passkey, security key, authenticator-app approval, or another method supported by the account provider. MFA is most valuable when it protects the accounts that can access email, financial systems, customer records, source code, documents, and administrative settings.
A password policy should support MFA rather than rely on password complexity alone. A practical small business policy usually covers:
- Use of a password manager for business credentials.
- Unique passwords for every account; never reuse a work password elsewhere.
- MFA on email, identity-provider, finance, payroll, file storage, and administrator accounts.
- Passkeys or hardware security keys where the service supports them, especially for administrators.
- No shared user accounts unless a system technically requires one and ownership is documented.
- Prompt removal of access when someone leaves or changes roles.
- Secure recovery procedures, including backup MFA methods controlled by the account owner or an approved administrator.
MFA is not a substitute for backups, endpoint protection, phishing training, or careful vendor review. For a broader starting point, use the Small Business Cybersecurity Checklist and connect access controls to your SaaS account security process.
How to estimate
Estimate both the recurring cost and the one-time effort. A simple planning formula is:
First-year access-security cost = subscription cost + hardware cost + implementation time + training time.
For subscription-based tools, calculate:
Annual subscription estimate = number of paid users × monthly price per user × 12.
Use the provider’s current quote or pricing page for the price input. Do not assume that every MFA feature is included in a basic plan. Check whether the selected tier includes administrative reporting, SSO, automated provisioning, audit logs, recovery controls, and the authentication methods you need.
For implementation effort, list the work rather than guessing a single number:
- Inventory users, applications, devices, and administrator accounts.
- Choose the MFA methods and recovery process.
- Configure the identity provider and priority SaaS applications.
- Enroll users and provide short instructions.
- Test sign-in, recovery, offboarding, and break-glass procedures.
- Document exceptions and schedule the first access review.
Multiply estimated hours by the internal or contracted hourly cost used for planning. Hardware security keys add a separate cost, including spare keys for approved recovery scenarios. If a password manager is part of the project, estimate it separately because its user count and licensing model may differ from the identity provider.
Inputs and assumptions
Deployment checklist
- Inventory: Export active users from email, file storage, finance, payroll, CRM, support, development, and other important systems.
- Prioritize: Start with administrators, email, identity-provider accounts, financial tools, and systems containing sensitive personal or customer data.
- Choose methods: Prefer phishing-resistant options such as passkeys or security keys when available. Use authenticator applications when they are the practical option. Treat SMS as a fallback only where stronger methods are unavailable and the risk is understood.
- Configure recovery: Require at least one documented recovery path without creating a universal bypass. Store emergency credentials securely and restrict access to named administrators.
- Disable legacy authentication: Identify older sign-in protocols that do not support MFA, test replacements, and disable them after confirming that business workflows still operate.
- Test: Verify a normal login, lost-device recovery, administrator recovery, new-hire provisioning, and immediate offboarding.
- Record: Keep an application list, owner, MFA status, exception reason, last review date, and remediation owner.
Compact comparison framework
| Option to evaluate | MFA methods to check | Price tier input | SSO and admin controls to verify |
|---|---|---|---|
| Existing identity provider, such as Microsoft Entra ID or Google Workspace | Passkeys, security keys, authenticator app, recovery options | Current edition and add-on requirements | Application coverage, enforcement rules, logs, groups, lifecycle controls |
| Dedicated identity provider, such as Okta | Passkeys, security keys, app-based methods, risk-based controls | User minimums, feature tier, implementation support | SSO catalog, provisioning, reporting, policy granularity |
| Business password manager with MFA features, such as 1Password Business | Passkeys, security keys, authenticator support, vault recovery | Per-user plan and administrative features | Vault permissions, reports, offboarding, directory integration |
| Hardware security keys | FIDO2 or other standards supported by the target services | Keys per user plus managed spares | Enrollment records, replacement process, administrator ownership |
This is a research framework, not a current pricing or feature ranking. Confirm supported standards, plan limits, integrations, and prices directly with each provider before purchasing. FIDO2 and passkey support can vary by application, device, browser, and account tier.
Copy-ready policy templates
MFA policy: “The business requires MFA for email, identity-provider accounts, administrator accounts, financial systems, file storage, and other systems designated as critical. Employees must enroll an approved method, protect recovery codes, report a lost device promptly, and never approve an unexpected sign-in request. Exceptions require a documented business reason, an owner, compensating controls, and an expiry date.”
Password policy: “Business passwords must be unique, stored in the approved password manager where practical, and never shared through email, chat, or documents. Employees must not reuse business passwords on personal services. Passwords are changed when compromise is suspected, during an approved recovery process, or when required by a system’s risk controls. Shared credentials are prohibited unless technically necessary and managed in an approved vault.”
Worked examples
Example one: a 12-person team. The owner lists 12 users, three administrators, nine priority SaaS applications, and two systems that still use older sign-in methods. The estimate includes 12 user licenses, any identity-provider upgrade, four security keys for administrators and controlled recovery, and implementation time for application testing. The first milestone is to protect email and administrator accounts, then migrate the two legacy systems or document temporary exceptions.
Example two: a 30-person team adding a password manager. The business estimates 30 password-manager seats, identity-provider costs for the users who need advanced controls, and a short training session. It also budgets time to identify shared credentials, move them into shared vaults with named owners, and rotate credentials after migration. The key outcome is not simply enrollment; it is a documented process for adding users, changing roles, and removing access.
In both examples, the calculation should show assumptions separately: user count, paid-seat count, hardware quantity, current plan, estimated hours, and unresolved exceptions. That makes the estimate easy to revise when the team or application list changes.
Quarterly access-audit workflow
- Export accounts: Collect active-user lists from the identity provider and important SaaS applications.
- Compare to employment records: Identify former employees, contractors, duplicate accounts, dormant accounts, and users with incorrect roles.
- Review privilege: Confirm that administrator, billing, export, API, and sensitive-document permissions are still necessary.
- Check MFA status: Confirm enrollment, review bypass or exemption logs, and close expired exceptions.
- Review shared credentials: Rotate credentials that were exposed, shared outside the approved vault, or owned by a departed employee.
- Test recovery: Confirm that recovery contacts, spare keys, emergency accounts, and documented procedures are current without weakening everyday controls.
- Record remediation: For each issue, note the application, finding, owner, due date, completed action, and evidence.
Use the same workflow after a new hire, departure, acquisition, major SaaS change, suspected compromise, or change in administrative responsibility. Pair this review with your vendor risk assessment and document-retention process when access changes affect customer or employee data.
When to recalculate
Recalculate the cost and revisit the policy at least quarterly alongside the access audit. Recalculate sooner when headcount changes, a new critical application is adopted, a provider changes pricing or plan features, hardware keys are lost or replaced, or a system requires a different authentication standard. Review authentication guidance and relevant privacy or security obligations annually, and after material legal or contractual changes. Keep the spreadsheet or decision record with the date, source of each price input, user count, assumptions, exceptions, and next review date.
A useful final action is to schedule a 60-minute implementation session: inventory accounts, protect the highest-risk systems, assign an owner for each exception, and book the first quarterly review before the project is considered complete.