Posted by:
admin
13 years, 5 months ago
In the past, we've commented on the 'Vendor-in-the-middle' issues in the past, in particular we've pointed out this weakness when using SMS as a one-time passcode delivery mechanism. As always, such reliance may be ok based on your risk tolerance. Another example of this risk occurred to me today when someone on twitter mentioned pointed to this Wordpress plugin that add two-factor authentication to Wordpress using Google's authenticator. There is also one for SSH via a PAM module.
I have always lauded Google and Facebook for adding two-factor authentication to their products. At WiKID, our competition is static passwords and there is plenty of room for improvement there. But do you want to use it for other products?
We like to point our risks, especially where they are created by diverse incentives. Because Google is not in the two-factor authentication business. They are in the advertising business. And they will make decisions based on what they see as best for their advertising business. It was difficult to point my finger on a good example though, until today: Google has been suspending accounts for violation of their Google+ terms of service. And apparently Google is, at least sometimes, suspending all services, not just G+.
So my question is: what happens to your Google Authenticator account when Google suspends your account?
UPDATE:
The answer is nothing, according to Mike Smith. We have a real focus on Enterprise two-factor authentication, so I pre-maturely assumed that Google Authenticator included communication with a server in the middle. Turns out, it doesn't. What this means is that it is a fine solution for two-factor authentication for personal sites and servers, but without a server in the middle to manage users, it is not an enterprise worthy solution.
Kudos to Google, shame on me for jumping the gun.
Share on Twitter Share on FacebookRecent Posts
- Blast-RADIUS attack
- The latest WiKID version includes an SBOM
- WiKID 6 is released!
- Log4j CVE-2021-44228
- Questions about 2FA for AD admins
Archive
2024
2022
- December (1)
2021
2019
2018
2017
2016
2015
2014
- December (2)
- November (3)
- October (3)
- September (5)
- August (4)
- July (5)
- June (5)
- May (2)
- April (2)
- March (2)
- February (3)
- January (1)
2013
2012
- December (1)
- November (1)
- October (5)
- September (1)
- August (1)
- June (2)
- May (2)
- April (1)
- March (2)
- February (3)
- January (1)
2011
2010
- December (2)
- November (3)
- October (3)
- September (4)
- August (1)
- July (1)
- June (3)
- May (3)
- April (1)
- March (1)
- February (6)
- January (3)
2009
- December (4)
- November (1)
- October (3)
- September (3)
- August (2)
- July (5)
- June (6)
- May (8)
- April (7)
- March (6)
- February (4)
- January (427)
2008
- December (1)
Categories
- PCI-DSS (2)
- Two-factor authentication (3)
Tags
- wireless-cellular-mobile-devices (7)
- Two-factor authentication (10)
- Wireless, cellular, mobile devices (6)
- NPS (1)
- Phishing and Fraud (111)
- Active Directory (1)
- pam-radius (3)
- privileged access (2)
- Cloud Security (10)
- Mutual Authentication (60)
- Web Application Authentication (1)
- Authentication Attacks (99)
- pci (50)
- Security and Economics (97)
- WiKID (133)
- pam (2)
- VPN (1)
- Installation (2)
- RADIUS Server (1)
- Open Source (64)
- Tutorial (2)
- Strong Authentication (35)
- Information Security (137)
- Transaction Authentication (13)
- Miscellaneous (100)
- Linux (2)
- transaction-authentication (6)
- Two Factor Authentication (254)