Passkeys are built on the FIDO2 standard (CTAP2 + WebAuthn standards). They remove the shared secret, stop phishing at the source, and make credential-stuffing useless.
But adoption is still low, and interoperability between Apple, Google, and Microsoft isn’t seamless.
I broke down how passkeys work, their strengths, and what’s still missing
How do you use it then if you need to share access in the whole team?
You don’t share your personal password across the whole team now, do you? At least for your teams sake I hope you don’t.
You know that not every account is only used by a single user, right?
I think that’s the problem right there… If you share accounts across multiple people you have far greater problems than how passkeys work…
Or they’re using it as intended. I’ve had more than one account I’ve gotten by cost sharing with friends. That’s not a problem, that’s a solution.
And it only takes one person with a grudge to cause a problem. I have seen it. I have shared accounts but very carefully and if someone abuses it then they permanently lose access to my stuff even if they are family.
Obviously not the personal password, but sometimes you need to share a password. Think about the password for a remote desktop your team may need to connect to for troubleshooting a problem for example.
We share a password. Then we don’t call it a personal password anymore. Was that your question?
That’s an IAM no-no.
So? Read my question above.
You create unique accounts for every team member so that access can appropriately be logged.
Or you implement a PAM tool that logs access and vaults the password and rotates it after use.
So do you think passkeys are not useful at all for me?
That’s not what I said
Then you said useless things only.