Guide

Moving Beyond Passwords: A Step-by-Step Guide to Passkeys and Advanced MFA in 2026

The password is dead. Or at least, it should be. Despite decades of warnings about complexity, frequent rotations, and password managers, human error remains the primary vector for data breaches. Why? Because any…

By SecureBusinessHub Editorial, International cybersecurity desk — 2026-02-26 · 9 min read

Passwords have been the primary attack vector for decades. Complexity requirements, forced rotations, password managers: none of it solved the core problem. Any shared secret, something you type or a code sent by SMS, can be phished, intercepted, or stolen from a server.

In 2026, the industry has moved to passkeys and hardware security keys built on the FIDO2 standard. These offer authentication that genuinely can't be phished. Here's how to migrate your critical accounts away from legacy passwords.

What are passkeys?

Passkeys replace passwords with cryptographic key pairs. When you register with a website, a public key gets stored on the server. The private key stays locked inside your device's hardware: your phone's secure enclave or your laptop's TPM chip.

To log in, the server sends a mathematical challenge. Your device solves it locally using the private key, confirmed by a biometric check or device PIN. The private key never leaves the device. If the server gets breached, attackers only find public keys, which are useless without the matching private key.

Implementing passkeys: practical steps

Passkeys have some cross-platform friction that's still being resolved. A hybrid rollout makes sense for now:

Pair with a password manager: Use an enterprise password manager like Bitwarden or 1Password as your central vault. The good ones now sync both legacy passwords and passkeys across devices.
Secure the root accounts first: Convert your Google/Microsoft Workspace admin accounts, your Apple ID, and your password manager itself before anything else.
Plan for recovery: The real risk with passkeys is losing the device that holds the private key. Set up a recovery option before you need it, whether that's backup codes or a secondary registered device.

Hardware security keys: the higher tier

For anyone accessing highly sensitive intellectual property or managing financial infrastructure, cloud-synced passkeys may not be strict enough. Hardware security keys like the YubiKey 5 series are physically isolated on a USB drive. You have to plug it in or tap it via NFC to authenticate.

The two-key rule

Never set up hardware authentication with only one key. Drop it and you're locked out of your accounts indefinitely. Register at least two physical keys for every critical account:

Primary key: On your keychain (a YubiKey 5C NFC works well for this).
Backup key: Stored somewhere secure offline, like a fireproof safe or safe deposit box.

Removing weak MFA

Moving to passkeys or hardware keys is only half the job. If an attacker can click "I forgot my passkey, send me a text" and bypass everything, your security is gone.

Once your passkeys or hardware keys are registered and verified, go into each service's security settings and remove your phone number as a recovery option. SMS-based 2FA is vulnerable to SIM swapping and shouldn't be trusted in 2026.

Summary: the 2026 authentication tier list

Tier 1 (maximum security): Two hardware security keys (FIDO2/WebAuthn), SMS disabled. Use for admin, financial, and email accounts.
Tier 2 (strong): Device-bound or cloud-synced passkeys. Use for standard employee accounts, CRMs, and SaaS tools.
Tier 3 (acceptable): Complex, unique passwords from a manager plus an authenticator app (TOTP).
Tier 4 (unacceptable): Reused passwords plus SMS codes.

Start with your highest-privileged users. That's where breaches do the most damage, and where the migration pays off fastest.

NIS2 requirements: the second regime to know about

Data protection law is not the only European regime a business gets asked about. The NIS2 directive sets baseline cybersecurity and incident-reporting obligations for organisations in a defined list of sectors, and it is the source of most of the security questions that now arrive attached to contracts. The two regimes cover different ground: data protection law governs personal data and what people can ask you to do with it, while the NIS2 requirements govern the security and resilience of network and information systems, whether or not personal data is involved. A single incident can engage both, on separate clocks, to separate authorities.

The directive applies to organisations in its listed sectors that are at least medium-sized, meaning broadly fifty or more employees or turnover and balance sheet above ten million euros. That size rule puts most small businesses outside its direct scope, and the honest answer for a ten-person company is usually that the directive does not regulate it. What the size rule does not do is keep the requirements away, because one of them is supply chain security: organisations inside scope are expected to consider the security practices of their direct suppliers, and the way that expectation shows up in the world is as a questionnaire in your inbox.

The measures the directive names are a reasonable checklist for any business, which is why they are worth knowing even when they do not apply to you directly. They cover risk analysis and written security policies, incident handling, business continuity and backups, supply chain security, secure development and vulnerability handling, basic cyber hygiene and training including for management, encryption and access control policies, and multi-factor authentication. Reporting is staged and fast for the organisations it covers: an early warning within twenty-four hours of becoming aware of a significant incident, a fuller notification within seventy-two hours, and a final report within one month.

Because the directive is national law in each member state rather than a single rulebook, the details of scope, thresholds and reporting differ by country. For a fuller explanation of the instrument itself, see our guide to what the NIS2 directive is, and for the supplier side of the supply chain obligation, our walkthrough of vendor risk assessment. The reporting clocks that run alongside data protection deadlines are covered in data breach notification requirements.

Frequently asked questions

Does NIS2 apply to a small business?

NIS2 generally applies to organisations in its listed sectors that are at least medium-sized, meaning broadly fifty or more employees or turnover and balance sheet total above ten million euros. Most smaller businesses fall outside its direct scope, unless a member state has specifically designated them or they sit in one of the size-independent categories such as DNS service providers or trust service providers. Being outside scope does not stop the directive reaching you through customers who are inside it.

What is the difference between GDPR and NIS2?

GDPR governs personal data: what you may collect, why you may hold it, and what rights people have over it. NIS2 governs the security and resilience of network and information systems in specific sectors, whether or not personal data is involved. One incident can engage both regimes at once, on separate reporting clocks and to separate authorities.

How long do you have to report a data breach?

Under the European model, a personal data breach is reported to the supervisory authority without undue delay and, where feasible, within seventy-two hours of becoming aware of it, and affected individuals are told without undue delay where the risk to them is high. Organisations in scope of NIS2 carry a separate obligation: an early warning within twenty-four hours, a fuller notification within seventy-two hours, and a final report within one month.

Does a small business need a data protection officer?

Under GDPR a data protection officer is required where the organisation is a public authority, where its core activities involve regular and systematic monitoring of people on a large scale, or where its core activities involve large-scale processing of special category or criminal offence data. Most small businesses meet none of those tests and are not required to appoint one, though naming someone internally as the contact for privacy questions is worth doing regardless.

What should a small business do when a client's security questionnaire asks about NIS2?

Answer what you actually do rather than what you think the client wants to hear. The questions usually cover written security policies, incident handling and how fast you would notify them, multi-factor authentication, access control when staff join and leave, backup and recovery arrangements, and which of your own subprocessors touch their data. Gaps are common, and disclosing one with a date for closing it lands far better than an answer that does not survive the follow-up question.

Do these rules reach a business based outside the EU?

They can. GDPR reaches organisations outside the EU that offer goods or services to people in the EU or monitor their behaviour, and other regions have their own regimes with their own triggers. NIS2 obligations follow the sectors and the member states that transpose it, but its supply chain expectations travel through contracts, which is how they reach suppliers anywhere in the world.