Google gets tougher on suspicious Google Apps logins

Google has fortified the security protocol for Google Apps through the addition of a dual-layered verification process aimed at deterring unauthorized access attempts. In scenarios where irregular login activity is recognized, this security functionality sends a verification code via text message to the user’s registered mobile phone.

This advanced security arrangement, a form of two-factor authentication, is now fundamental for all online services irrespective of whether users have availed of this feature. Like notable platforms including Microsoft, Twitter, Dropbox, and LastPass, this innovative system demands a password and a one-of-a-kind code, typically produced via a smartphone application or text message.

To elaborate, upon detection of unconventional login attempts, a security verification mechanism is triggered. Users are then sent an authentication code to their mobile phones via text message, which they need to enter to gain admittance to their accounts. This mechanism significantly bolsters defenses against unauthorized infiltrations as any unlawful entities would necessitate access to not only the user’s login details but their physical phone as well.

Subscribers to Google Apps, a service providing key functionalities such as Gmail, Google Calendar, and Google Docs to businesses, are charged an annual fee of $50 per user. This subscription encompasses formidable protection against threats like government monitoring, industrial espionage, and identity fraud.

The introduction of Google’s new security measure highlights the escalating significance of having a fully functioning phone as an exclusive identifier. This feature also necessitates that users register their phone numbers in case of sighting any suspicious login activity across Google’s suite of services.

In cases where users are unable to access the sent verification messages, an alternative ‘fallback challenge’ is available. Furthermore, organizational administrators have the capacity to temporarily disable the login verification, although this deactivation only persists for a brief period of ten minutes.

One potential issue arises if users lack phone service to receive the authentication messages or are unable to retrieve their emails to contact IT support, which may cause substantial obstacles.

The content of this article is drawn from the original version on http://www.cnet.com/.

Minor enhancements were applied in 2025 for readability.