Multi-factor authentication looks like a simple purchase: choose a provider, connect the applications, ask staff to install an app. In practice, the cost is driven by the applications that cannot use modern authentication, the people who lose a device and the helpdesk that has to recover access without weakening security.
This guide explains the scope drivers and a cost model for an SME rollout in Bangladesh. It also explains where passkeys fit, and why the cheapest per-user quote can be the most expensive rollout.
What counts as MFA
MFA requires two or more independent factors: something you know, something you have or something you are. A password plus a one-time code is MFA. A password plus a second password is not. A password plus a push notification is MFA, but it is weaker against real-time phishing than a passkey or a hardware security key.
For high-consequence accounts, the target should be phishing-resistant authentication: passkeys or FIDO2 security keys. NIST's digital identity guidance and the FIDO Alliance both describe the security benefits. The rollout can start with app-based MFA and move administrators to passkeys first.
The scope drivers
- Users: staff, contractors, partners, shared accounts and service accounts.
- Applications: email, cloud, VPN, finance, HR, admin panels and legacy software.
- Protocols: SAML, OIDC, RADIUS, LDAP, header-based SSO or no federation at all.
- Legacy bridge: applications that cannot speak modern protocols need a proxy or a password vault.
- Recovery: what happens when a phone is lost, replaced or stolen.
- Helpdesk: reset and recovery volume, identity proofing and audit.
- Change management: communication, training and a pilot group.
- Policy: conditional access, device trust, location and risk-based step-up.
A cost model
- Identity provider: per-user subscription or platform fee, including MFA and SSO.
- Application integration: the number of apps and the effort per app.
- Legacy bridge: proxy or vault for apps that cannot federate.
- Recovery: second device, recovery codes, identity proofing and helpdesk workflow.
- Support: the first 30 days of reset and recovery tickets, then steady state.
- Change management: communication, training and pilot support.
The per-user licence is usually the smallest line. The integration and recovery work is where budgets move.
Rollout sequence
- Inventory: list every application and identity source.
- Prioritise: administrators, finance, email, cloud and remote access first.
- Pilot: one team, two weeks, with a feedback channel.
- Recovery design: test lost-device and new-device scenarios before enforcement.
- Enforce: enable MFA in stages, with a break-glass account stored offline.
- Measure: enrolment, sign-in success, reset tickets and account-takeover attempts.
A worked rollout: 40 staff
A 40-person professional services firm starts with email, cloud storage, the finance system and the VPN. The pilot covers eight administrators and finance users. The first issue is a legacy accounting client that cannot use SAML; it gets a vaulted credential with MFA on the vault. The second issue is device replacement: two users lose phones in the first month. The recovery path is tested before enforcement, so the helpdesk does not fall back to disabling MFA.
By day 60, the firm has 100 percent coverage on the high-consequence accounts, a documented break-glass process and a monthly review of reset tickets. The remaining applications are scheduled for the next quarter. The rollout is not "finished", but the risk that matters is covered.
Passkeys and the next step
The FIDO Alliance reports roughly five billion passkeys in use in 2026, 90 percent consumer awareness and 68 percent of organisations deploying or actively deploying passkeys for employee sign-in. Passkeys are phishing-resistant and remove the shared secret. They are a strong target for administrators and high-value users.
Do not make passkeys a big-bang replacement. Start with the accounts that can end the business, keep a tested recovery path and measure sign-in success. A passkey that is hard to recover creates a new support problem.
Questions to ask a provider
- Which applications are covered natively, and which need a bridge?
- How is recovery handled, and who can approve it?
- Does the provider support passkeys and FIDO2 security keys?
- What happens if the identity provider is unavailable?
- How are service accounts and shared accounts handled?
- What logging and alerting is included?
- What is the migration and exit plan if we change providers?
A 90-day plan
- Inventory applications and classify by consequence.
- Choose the identity provider and the first 20 users.
- Pilot MFA with admins and finance; test recovery.
- Add conditional access for remote and privileged access.
- Move administrators to passkeys or security keys.
- Review enrolment, reset tickets and incidents at day 90.
Where this fits in our work
If you need help with an MFA or passkey rollout, start with Managed Technology & Cybersecurity. The pricing page explains scope. For the credential strategy, read the passkeys rollout plan.
Sources
- FIDO Alliance, "Five Billion Passkeys: State of Passkeys 2026", 2026.
- NIST SP 800-63B, Digital Identity Guidelines, accessed 17 November 2026.
- CISA, "More Than a Password" MFA guidance, accessed 17 November 2026.
- The Daily Star, "BB issues 17-point cybersecurity directive", accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.