4 ms·
I was confused on my first read through: this guidance seems to refer to federal enterprise applications, not necessarily customer-facing services. It seems re
by alwa 2y ago
I was confused on my first read through: this guidance seems to refer to federal enterprise applications, not necessarily customer-facing services.
It seems reasonable to me to require employees to use a physical authenticator. Heck, how many of the people here use them and require employees to use them? Often to secure access to applications and resources less consequential than Official Acts Of The Federal Government.
It would feel less reasonable (and a throwback to the ‘00s) to mail out hardware authenticators to customers/members of the public just to, say, buy stamps from the USPS or something.
But the employee needs to be responsible enough not to lose it, they definitely need to not be able to back it up to god-knows-what consumer-grade provider (or to duplicate it at all). And when they lose it, IT needs to know to invalidate the lost one and issue them a new one.
My impression is that physical authenticators (often in the form of smart cards that double as employee ID) are pretty much table stakes in serious federal environments anyway, is that mistaken?
- Ylpertnodi 2y ago>needs to be responsible enough not to lose it.... needs to know to invalidate the lost one and issue them a new one. Ah, the never-ending circle of life.
- 0xffff2 2y ago> My impression is that physical authenticators (often in the form of smart cards that double as employee ID) are pretty much table stakes in serious federal environments anyway, is that mistaken? I'm a Federal contractor. At least for my agency this is table stakes for any application period. I don't even have a password anymore. For the very small number of legacy applications that don't support smart card auth I have to log in to a different service to get a temporary password that expires after 24 hours.