Posted by:
admin
13 years, 7 months ago
Kudos to Google for putting more security around their authentication for Google Apps. Apparently, two-step authentication will be coming to Gmail as well once they feel comfortable.
Two-step authentication is clearly aimed at consumers that want more security and not Enterprises. In the installation instructions, it states:
Note: You can’t force your users to use two-step verification, they must opt-in themselves.
You also cannot use SAML for SSO and Two-step verification. This means that if you are an Enterprise that use Google Apps and Salesforce, for example, you will want to use SAML for SSO and two-factor authentication.
It looks like there is an option to "Remember verification for this computer". (I have not seen this option in my tests, but it there is something being set. If I sign out and close the browser, I am not prompted for the verification when I re-open the browser, just the username and password.) I believe that stronger authentication systems need to make things as easy as possible for the user. This option though should be in control of the enterprise for it to be an enterprise solution.
Enterprises may move a good bit of their infrastructure to the cloud, but they will still have a network and will still need a firewall and VPN. So most will still need a strong authentication system that works with VPNs, which means Radius, LDAP or TACACS support. While you can put your WiKID server "in the cloud", I still think it makes the most sense to keep the keys to the kingdom close to home.
So, it's not for Enterprises, but for consumers, Google Two-step authentication is definitely a step in the right direction. I admire the code release under open source licenses. I will point out what one privacy wag has said:
Nice, Google is rolling out "something you know" & "something we'd like to know" in their new auth scheme.
Share on Twitter Share on FacebookRecent Posts
- The latest WiKID version includes an SBOM
- WiKID 6 is released!
- Log4j CVE-2021-44228
- Questions about 2FA for AD admins
- WiKID Android tokens had their data deleted over the weekend by Google Chrome bug
Archive
2024
- January (1)
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)