Lorixen.
EN

Hardware Security Keys for a Small Team: Who Needs One and How to Roll Them Out

Short answer: A hardware security key is a small USB or NFC device that proves you are present when you sign in, and it resists phishing because it only responds to the real website that registered it. For a small team, buy keys for the people who can change money, reset passwords or administer the business email and cloud storage. Enrol at least two keys per person, store the spare somewhere safe, and remove the weaker methods once the keys work. Authenticator apps and SMS codes are better than a password alone, but they can be tricked by a convincing fake login page, which a key will not fall for.

How the three main second factors compare

Second factors are not all equal. Here is how the options compare on the most important test, which is whether a phishing page can capture the code and reuse it.

Method What it protects against Main weakness
SMS code Stolen password alone Can be intercepted or redirected through SIM swaps, and codes can be typed into a fake page
Authenticator app code Stolen password alone Codes can be typed into a fake page within the short window
Hardware security key (FIDO2) Phishing and fake login pages Lost or broken key, which needs a backup

The key is phishing-resistant because the browser checks the website address before it releases the proof. A fake site with a similar name does not get a valid response. This is the reason regulators and security teams recommend keys for accounts with high privilege.

Who in a small team should get one

You do not need a key for everyone on day one. Start with people who can cause the most damage if their account is taken:

  1. The business owner or the person who controls the domain and the email admin console
  2. Anyone with administrator rights to cloud storage, accounting or the payment dashboard
  3. Finance staff who can approve or send payments
  4. An IT helper or outside provider who manages the systems

Take a fictional four-person accountancy called Northfield Books as an example. The partner who owns the domain and the admin console got two keys. The office manager who runs payroll and banking got two keys. The two junior staff members stayed on authenticator apps until the rest of the team had moved.

Choose the keys

Look for a key that supports FIDO2 and the standard your platforms use. Many keys offer USB-A and USB-C connectors, and some support NFC for phones. Pick a connector that matches your laptops and phones, and buy the same model for each person, so the backup process is the same for everyone.

Buy from a reputable retailer and check the packaging for signs of tampering. Do not buy keys from a marketplace seller with no return policy.

Enrol keys with Google and Microsoft

Both Google Workspace and Microsoft 365 let you add security keys to a user account. The steps are similar:

  1. Sign in to the account and open the security settings.
  2. Turn on two-step verification, if it is not already active.
  3. Choose the option to add a security key and follow the prompts.
  4. Insert the key, touch it when asked and give the key a name, such as "Office primary".
  5. Repeat the process for the backup key.
  6. Remove or disable SMS as a sign-in method, once the keys are working.

For Google accounts, the official Google Account help pages explain how to add a security key and how to manage the recovery options. Check the current wording on the page, because menu names change.

A roll-out plan that works

A staged roll-out avoids lockouts. Use this order:

  • Week one: Enrol keys for the owner and the admin. Test sign-in on a laptop and a phone.
  • Week two: Enrol keys for finance and other privileged staff. Test sign-in from each device they use.
  • Week three: Tell everyone else the date when SMS sign-in will stop, and give them a simple guide.
  • Week four: Remove SMS as a second factor for privileged accounts and enrol authenticator apps for the rest.

Keep a short log showing who received which key, the serial or name of each key and the date it was tested.

Lost keys and recovery

A lost key is the most common problem. Plan for it before it happens.

  1. Every privileged user has two keys, and the spare is stored in a separate location, such as the office safe or a locked drawer.
  2. The admin account has a second admin who can remove a lost key from the account.
  3. Recovery codes for each platform are stored in a shared password vault, with access limited to the admins.
  4. A staff member who loses a key reports it the same day. The admin removes that key and enrols a replacement.
  5. If both keys are lost, use the platform's recovery process, which may take time, so keep the admin accounts active and the recovery details up to date.

Common mistakes

  • Enrolling only one key, which leaves the account stuck if the key is lost
  • Keeping SMS as a fallback, which allows an attacker to bypass the key
  • Leaving old devices or shared phones signed in to the admin account
  • Storing the spare key in the same bag as the primary key
  • Forgetting to test the key after a software update

A short checklist

  • Privileged accounts identified
  • Two keys bought for each privileged user
  • Keys enrolled and named on each platform
  • SMS removed as a sign-in method for those accounts
  • Spare key stored in a separate, secure place
  • Recovery codes saved in the shared vault
  • Lost-key procedure written down and shared with the team

FAQ

Do I need a key if my team uses a password manager?

A password manager helps with unique passwords, but it does not stop a phishing page from tricking someone into typing a code. A key adds a layer that a fake login page cannot easily copy.

Can a security key work on a phone?

Many keys support NFC, which works with some phones. Check that your phone and the key are compatible before you rely on it, and keep a USB option available for laptops.

What if a staff member does not want a key?

Discuss the reason and the role. For people with admin or payment access, a key is usually a condition of the role. For others, authenticator apps are a strong alternative.

Where can I learn more about the standard?

The FIDO Alliance explains the standard that keys use, and the Google Account help page covers how to enrol keys and recovery options on Google accounts.

If you want help choosing keys and rolling them out across your team without lockouts, reach out through our enquiry page.

Sources

WhatsAppBook a call