GUIDE · IDENTITY AND ACCESS

Multi-factor authentication (MFA): how to introduce it without blocking people

This guide shows you how to bring multi-factor authentication into your business gradually. You will learn which accounts to protect first, which second-factor methods to choose, how to handle exceptions and how to demonstrate that the protection really works, without stopping everyday work.

Updated october 2026
8 min read
Altovar Technical Editorial Team

1. Why multi-factor authentication matters

A password on its own is a weak point. It can be stolen through a phishing message, reused from a compromised service or guessed if it is too simple. Multi-factor authentication, known as MFA, asks for a second proof of identity, usually something you have, such as an app on your phone or a physical key, in addition to something you know. Even if the password falls into the wrong hands, access stays blocked without the second element.

For a business it is often the control with the best balance between effort and risk reduction. It does not require changing every system at once and can be introduced first on the most sensitive access. The real work, however, is not technical: it consists of deciding which accounts to protect first, how to handle people who do not have a company phone and how to prevent people from finding shortcuts that cancel out the protection.

2. Prerequisites before you start

Before enabling any factor it is worth having some basics in order. You need a list of the systems that allow access with a password, distinguishing those that already support MFA from those that do not. You also need to know which accounts are privileged, meaning they can change configurations or read large amounts of data, because these are the ones to protect first.

You also need clear communication to people and a support channel. Someone who gets locked out without knowing whom to turn to tends to look for workarounds. Finally, decide which second-factor methods are allowed. Not all of them offer the same level of security, and some expose specific risks, such as the hijacking of a phone number.

  • Inventory of systems with access to business data
  • List of privileged accounts and critical roles
  • Second-factor methods approved by the business
  • A support contact and a recovery procedure
  • A clear message on what changes for people

3. The available factors and their limits

Factors fall into three families: something you know, such as a password or PIN; something you have, such as a phone or a key; something you are, such as a fingerprint. MFA combines at least two different families. Two passwords are not MFA, because they belong to the same family and can be stolen together.

Text messages are the simplest method to activate, but they are vulnerable to phone number hijacking and to codes being copied onto fake pages. Physical keys offer the strongest protection, but they have a purchase cost and a loss risk to manage. Ask suppliers which methods they support and which they recommend for the most sensitive accounts.

MethodMain strengthMain limit
Confirmation app on the phoneSimple and widespreadDepends on the device and how it is managed
One-time codes from an appWork even without a networkThe code can be entered on a fake page
Text messagesNo app to installVulnerable to phone number hijacking
Physical keyStrongest protectionCost and risk of loss

4. A phased rollout plan

Introducing MFA all at once rarely works. A phased approach reduces friction and lets you fix problems before they affect everyone. The order matters: start with privileged accounts and applications holding the most sensitive data, then extend to email and connected systems, and finally to external access and less critical services.

  1. Enable MFA for administrative accounts and for anyone with access to all data, with dedicated support in the first few days.
  2. Extend protection to email and collaboration tools, with advance communication and a trial period.
  3. Require the second factor for access from non-business networks and from outside.
  4. Check with a small group of users that the recovery procedure really works before extending it to everyone.
  5. Extend MFA to all remaining accounts and services, documenting the few approved exceptions.
  6. Plan a periodic review of exceptions and of the allowed methods.

5. Managing exceptions and special cases

There will be cases that do not fit the standard rule: employees without a company phone, shared workstations on the production floor, legacy systems that do not support a second factor, service accounts used by applications. For each case you need a documented solution, not an improvised shortcut. An exception should have a reason, an expiry date and an owner who approves it.

For people who cannot use a personal phone, alternatives such as physical keys or dedicated devices usually exist. For legacy systems, protection can come from an intermediary access point that supports MFA, or from restricting the network from which the system can be reached. For non-human accounts a second factor is not applicable: protection must be built with other controls, such as secrets kept safely and tightly restricted permissions.

6. Common mistakes to avoid

The first mistake is considering MFA complete when it is active on only part of the access. Attackers always look for the weakest system, and it is often an old mail protocol or a forgotten administration interface. The second is leaving recovery without a procedure. When someone loses their device, support must know what to verify before resetting the second factor, because this is one of the most exploited requests from people impersonating a colleague.

The third mistake is approving confirmation requests without reading them, that is, accepting sign-ins you do not remember starting. Train people never to approve an unexpected request and to report it straight away. The fourth is not measuring anything. Without data on lockouts and support requests you cannot tell whether the procedure is sustainable.

7. How to check that it works

Once active, MFA must be verified with concrete evidence. Test access from a test account, from a device that is not the usual one, and check that the second-factor request really appears. Verify that access without a second factor is impossible on the systems on the list, including through less commonly used protocols. Finally, check that the exceptions are still necessary.

  • Test access from an external network to every system on the list
  • Attempted sign-in using an alternative protocol, where available
  • Verification that second-factor recovery follows the written procedure
  • Review of approved exceptions and their expiry dates

8. Topics to explore and where to start

This guide covers MFA adoption as a project, and several topics need separate reading. It is best to read the overview of identity and access management first, which explains where MFA fits. Straight after, read the guide on passwordless access keys, the next step beyond the second factor for those who want to reduce phishing risk further.

Other topics to tackle later are single sign-on for applications, protection of privileged accounts, the user lifecycle with joining, changing and leaving, periodic review of permissions and choosing a business password manager. The recommended order is this: first the identity rules, then the second factor, then the advanced tools.

9. How to start

This week, do two things. First, list the administrative accounts and the applications holding the most sensitive data, and mark which ones already support MFA. Second, ask your supplier or security consultant which second-factor methods they recommend for that scope and how they handle recovery.

With these two elements you can decide the first phase without waiting for a full project.

Frequently Asked Questions

Does MFA make account theft impossible?

No, but it greatly reduces the chance that stealing a password is enough to get in. Some real-time phishing techniques can intercept even the code the user types in. For this reason physical keys and passwordless access keys are considered stronger. Protection should still be accompanied by training, monitoring of unusual sign-in attempts and response procedures.

Can I use text messages as a second factor?

They are better than nothing, but they are not the best choice for sensitive accounts. The number can be hijacked using known techniques. For administrative accounts and critical data, a confirmation app or a physical key is preferable. If you use text messages as a fallback, document it and set an expiry date.

Does every employee need a company phone?

No. Many methods work with a personal phone, provided the business sets clear rules on which apps and devices are allowed. For people who cannot or do not want to use a personal phone, alternatives such as physical keys or dedicated devices exist. The choice depends on the role, the type of data handled and how much the business policy is willing to support.

What happens if someone loses their device?

The procedure must be written before it happens. Usually support verifies the person's identity through a different channel, for example in person or through confirmation from the manager, before resetting the second factor. A reset on a simple request by email or chat should be avoided, because it is a typical target for people impersonating a colleague. After the reset, the new method must be registered straight away.

Is MFA enough to comply with GDPR or NIS2?

It is not enough on its own. Both regulations require security measures appropriate to the risk, and strong authentication is one of them. However, a set of controls is needed: access management, system updates, training and incident handling. What level is appropriate for your business should be checked with a consultant.

How long should the adoption process take?

It depends on the number of systems, the quality of the access inventory and the availability of those who must communicate and support the change. A phased approach allows the most critical accounts, which form the first part, to be completed in a reasonable time. Be wary of anyone who promises a complete result without having seen your environment.

About this content

General informational guide. Regulations and technical requirements change over time: always check the official sources and assess your specific case with a qualified technical or legal advisor.

GET IN TOUCH

Talk to our team.

We'll show how Altovar integrates into your infrastructure. No commitment, no sales pitch. Just a technical conversation.

BOOK A DEMO →