> Nowadays, newly-onboarded Discord corporate users receive a laptop and at least one Yubikey alongside that laptop. IT onboards users to Okta and instructs them to register at least two WebAuthn authenticators; typically, this is their Macbook’s TouchID/Windows Hello sensor and also their Security Key C NFC.
> We also instruct corporate users to set up Okta Verify for use only as a fallback MFA in the event that all their authenticators fail at once. This way, we never have user accounts lacking at least one strong form of multi-factor authentication.
So OS level keys, a yubikey for roaming, and Okta Verify for fallback
When we deployed we banned Verify (didn't want any OTP), but encouraged TouchID, and the Yubi. If someone was locked out we could temporarily enable Verify, or reset their Macbook or Okta access so they could reregister into either.
But,in deploying 1500 or so yubikeys over a 5+ year period we never saw one actually break. Employees would often say they'd broken, but troubleshooting normally was user error.
The worst we saw were a few cases where Yubis needed unplugging and replugging (sometimes being left out for an hour or so).
If a Yubikey gets lost: on all our internal systems, an administrator will remove that Yubikey from the user's account and a new Yubikey is deployed. For a remote employee, we can usually switch to OTP until the new key arrives. For external systems, it is the responsibility of the employees to securely store their recovery keys. If these are gone, well then it depends on the service how tedious it will be to reset the 2FA for that account... it usually (and hopefully) involves some kind of manual identity verification process.
Some people in critical positions simply get two Yubikeys.
That really seems like the way to go for everyone, because of course when you lose access to the yubikey, it's suddenly far more challenging to get support via systems you may no longer be able to access. Google insists on two hardware MFA tokens for their elevated account protection program, most likely for this reason.
It's possible to break, but it's not trivial.
Also you just keep a bucket of non signed up ones at the office. Enrolling them is pretty easy.
It’s been my understanding that for corporate use, only a single one should be issued because:
1: There’s an establish support team in your org that can always issue a new one (except for a few edge cases, super critical things) 2: You can’t trust users with 2 devices
For private use, nr. 1 would not be true so the recommendation rightly is to issue 2.
If you're their number two, possibly you hold theirs.
You keep both your keys, one securely and one at-the-ready.
Yes, safety deposit boxes. Yes, family, yes friends. Yes, attorneys.
But also what I said initially.
https://krebsonsecurity.com/2018/07/google-security-keys-neu...
I’ve supported users who would eBay the second one, if they were smart enough to do that.
I’ve got one of the original ones (15 years old?) the must have been through the wash a dozen times and it still works.
9 years later I'm still procrastinating and after reading these comments I'm convinced I'm good for another couple years LOL
I did have a nano though, it broke on me, but it was my company's key. I don't think the same holds for those ones.
https://www.zdnet.com/article/yubico-to-replace-vulnerable-y...