Qvantor logo QvantorInfrastructure, explained plainly
Security

Hardware Security Keys for a Small Team and How to Start

A phished password plus a stolen six digit code is still enough to take over most team accounts, and small teams get hit because they look like easy targets.

Two small USB-C security keys with name labels lying next to a laptop keyboard on a wooden office desk

A phished password plus a stolen six digit code is still enough to take over most team accounts, and small teams get hit because they look like easy targets. Hardware security keys close that gap for roughly the price of a team lunch, yet most small teams never roll them out because the first step looks fiddly. This guide covers what to buy, which accounts to protect first, how to enroll a team of five to twenty people in one afternoon, and what to do when someone loses a key.

Why hardware security keys beat codes from an app

An authenticator app is far better than SMS, but it has one weakness that matters a lot: a person can type the code into the wrong website. Modern phishing kits act as a live relay. The victim enters their password and their code on a fake login page, and the attacker replays both to the real site within seconds.

A hardware key using FIDO2 or WebAuthn does not have a code to type. The browser tells the key which domain is asking, and the key signs a challenge only for the domain it was registered with. A fake page on a lookalike domain gets nothing useful. That is the whole point, and it is why large companies that moved staff to keys reported phishing takeovers dropping to near zero.

Keys also remove the friction of copying codes. Plug in or tap the key, touch the gold contact, done. Most people find it faster than an app after the first week.

What to buy and how many

For a small team you want keys that support FIDO2, work over USB-C, and ideally also support NFC so they tap against a phone. Expect to pay between 25 and 60 dollars per key depending on the model and features. The cheaper security-only keys handle FIDO2 and nothing else, which is all most teams need. The pricier models add smart card and one time password functions that you will probably never use.

Buy two keys per person. This is not optional. The second key is the backup that stops a lost key from becoming a support crisis.

Team sizeKeys to orderRough budget
5 people10 plus 2 spares300 to 700 dollars
10 people20 plus 3 spares575 to 1,400 dollars
20 people40 plus 4 spares1,100 to 2,650 dollars

The spares cover new hires and the inevitable key that goes through a washing machine. Keys usually survive that, by the way, but not always.

Which accounts to protect first

Do not try to put every account behind a key on day one. Start with the accounts where a takeover would hurt the whole company, then work outward.

  1. Your identity provider or main email. Google Workspace or Microsoft 365 is the master key to everything else, because password resets land in email.
  2. Your code host. GitHub and GitLab both support security keys, and an attacker with push access to your main branch can ship anything.
  3. Your cloud and DNS provider. Root accounts on AWS, a VPS host, or your domain registrar. Losing DNS means losing email and the website at once.
  4. Your password manager. If you followed our guide to a password manager for a small team, protect the vault with a key too.
  5. Finance and payroll. Banking portals vary, but many now accept keys.

Those five categories usually cover 80 percent of the real risk. Everything else can follow over the next month.

How to roll out hardware security keys in one afternoon

Block two hours, get everyone in the same room or on the same call, and hand out keys in labelled pairs. Label each pair with the person's name and mark one key "primary" and the other "backup" using a small sticker or a dab of nail polish.

Step by step enrollment

  1. Have each person sign in to their main email account and open the security settings.
  2. Add the primary key under "security key" or "passkey". Give it a clear name such as "Ana primary USB-C".
  3. Immediately add the backup key, named "Ana backup".
  4. Generate printed recovery codes and store them in a sealed envelope or in the team vault under an admin-only folder.
  5. Repeat for the code host, then for any cloud console where that person has admin rights.
  6. Sign out, sign back in with the key, and confirm it works before moving on.

The backup key should then leave the building. A home drawer, a locked desk at home, anywhere that will not burn down or get stolen at the same time as the laptop bag.

Enforce it, do not just encourage it

Once everyone has enrolled, turn on enforcement in the admin console. Google Workspace lets an admin require security keys for a group, and GitHub organizations can require two factor authentication for every member. Give people a one week grace period, then switch enforcement on. Optional security gets skipped by the one person who is most likely to be phished.

The advice to ignore: one key per person is enough

Plenty of quick guides say to buy a single key per person and keep recovery codes as the backup. That sounds cheaper and simpler, and in practice it causes the worst outcome. When someone loses their only key on a Friday evening, they reach for the recovery codes, discover they were saved in a downloads folder on the laptop that was also stolen, and lock themselves out of email for days.

A second registered key turns a lost key into a two minute problem. The person signs in with the backup, removes the lost key from every account, and orders a replacement. Recovery codes still matter, but as the third line of defence, not the second. The extra 25 to 60 dollars per person is the cheapest insurance in your entire security budget.

Handling lost keys and people leaving

Write a short runbook and pin it in your team chat. It only needs a handful of lines.

  • Lost key: sign in with the backup, remove the lost key from email, code host, cloud and vault within 24 hours, then issue a spare from the drawer.
  • Both keys lost: an admin verifies identity on a video call, resets the account, and the person enrolls two fresh keys before doing anything else.
  • Someone leaves: suspend their identity provider account first, which cuts off single sign on everywhere at once, then collect the keys or simply remove them from accounts. A key on its own is useless without the account.

Keys pair well with the rest of a sensible baseline. Servers should still use SSH key authentication rather than passwords, and you can store SSH keys on a FIDO2 key using the ed25519-sk key type in OpenSSH 8.2 or newer. For the broader move away from passwords, our explainer on how passkeys replace passwords covers the same technology from the account side.

Frequently asked questions

Do hardware security keys work on phones?

Yes. Keys with NFC tap against the back of most Android phones and iPhones, and USB-C keys plug straight into newer phones. Both iOS and Android support FIDO2 in their browsers and in apps from Google, Microsoft and GitHub.

What happens if a hardware security key is stolen?

The thief still needs the account password, and many keys also require a PIN for FIDO2 sign in, locking after eight wrong attempts. Remove the stolen key from your accounts using your backup key and the risk is closed. A stolen key without the password is close to worthless.

Are passkeys a replacement for hardware security keys?

Synced passkeys stored in a phone or password manager use the same phishing resistant protocol, so they are a big improvement over codes. Hardware keys go a step further by keeping the secret on a device that cannot be copied or synced to a compromised cloud account. For admin accounts, use hardware keys; for everyone else, either is a solid choice.

ON
Obi Nwachukwu

Obi works on account security and explains phishing, passwords and access in plain terms.

More posts by Obi

More in Security

01doorganico 084goad 3hot8 4465456 after5internprogram ahandfulofblessings ahmadpc ahomcybersecurity allodialresources annodex antiquesandperiodcollectibles aotc asianworldkashmir beedlectrics bloggertemplatefree bluefeatheragency bodyweightsolution campaign08blog carfixadvisor catstreetcollective cbstvsports cnfanspurchasing committeeof500yearsofdignityandresistance covertopsdjs cs-kaiyuangame cuestacomunicaciontotal cxoutlet dancebetgame deskgearhub destinyvillastay detectmagazine di33 diamondsteelbuildings donmo dyanadropship emarsysfinance emimattl escapechan eskitarih evautoplay everythingweddings-orlando farmzone feedviewerapp foxstudiosscratch gamevui123 gleasongrade greetingsday hacklabasu haskell iw-kaiyun jagoanproperti jilidskripsi joltbusinessfinance juegodepokergratis juegospucca kaeru-festival latestmehndidesigns lestanzediottaviano litemagazines localcommunityhero lustrsazan mariashebets menswheels newwebstechs1 nikkit ootheday oxigenvpn plurfitness prefetial probudgetcarpetcleaning psychicmrsmartin pyaten rejoignezlogis rexzbot riselayouts ruchin rwxqsgd5 sakaltime shibiaowang shop-bot skrtips spotlesshaven strcoding tetapatrium topselller uneplanteartificielle vipertechcr webtech1223411 wo-kygaming yamaha-mekar yeknava yoybuysheets zenunwa yamaha-mekar jilidskripsi ankertoto ankertoto ankertoto