Tuesday, March 4, 2025
HomeGoogleGoogle to Auto-turn on 2-Factor Authentication For 150 Million Users by Default

Google to Auto-turn on 2-Factor Authentication For 150 Million Users by Default

Published on

SIEM as a Service

Follow Us on Google News

Google has announced recently that they are currently intending to auto-enroll 150 million users in the company`s “two-step verification” system by default and they are planning to do it by the end of this year. 

The main motive of planning this is to stop all unauthorized access to accounts and at the same time to increase security protection. While Google is also aiming to ask 2 million YouTube authors to switch on the setting that is known as 2-step verification (2SV).

Composing Password Sign-in Seamless and Safe

Google has a strong password manager, which has been built straight into Chrome, Android, and the Google App, not only this but it also uses the most advanced security technology that always keeps the users’ passwords safe and secure.

However, with the help of Google manager users can create a strong and reliable password. And the Google app enables the users to access all of the passwords that were being saved in Google Password Manager right from the Google app menu.

Making people enrolled in 2SV

Having 2-step verification doesn’t mean that it will perfectly protect you, what it means, it generally decreases the attack rate of cybercriminals. As 2SV has always been the heart of Google’s different security practices.

Therefore Google has decided to make it seamless for all the users with a Google prompt, that generally needs a simple click on your smartphone device to signify that it’s really you attempting to sign in.

Adding security keys into devices and sign-in enhancements

Google has started the invention of security keys, as it is another form of authentication which needed the users to click the key during questionable sign-in attempts.

Moreover, with Google Identity Services, the experts of Google have combined its advanced security along with easy sign-in to present a comfortable experience that tries to keep users safe. 

All these new services were mainly done for future authentication and guard the system from vulnerabilities like click-jacking, pixel tracking, and many other webs and app-based threats.

Currently, Google is mainly focusing on auto-enrolling Google accounts as it has the conventional backup mechanisms in position to make it quite a seamless transition to 2SV. 

But, all the iOS device owners can simply use Chrome to autofill saved passwords in their different apps, and not only this but Google has declared that very soon they will be able to use Chrome`s password generation tool for any type of iOS app.

Google always thinks of better options for their users, that’s why doing all this will help them to stay safe and secure from unwanted threat attacks that harm the users as well as Google in many ways.

You can follow us on Linkedin, Twitter, Facebook for daily Cybersecurity updates.

Balaji
Balaji
BALAJI is an Ex-Security Researcher (Threat Research Labs) at Comodo Cybersecurity. Editor-in-Chief & Co-Founder - Cyber Security News & GBHackers On Security.

Latest articles

Docusnap for Windows Flaw Exposes Sensitive Data to Attackers

A recently disclosed vulnerability in Docusnap's Windows client software (CVE-2025-26849) enables attackers to decrypt...

CISA Warns of Active Exploitation of Microsoft Windows Win32k Vulnerability

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has added CVE-2018-8639, a decade-old Microsoft Windows...

Update Alert: Google Warns of Critical Android Vulnerabilities Under Exploit

Google’s March 2025 Android Security Bulletin has unveiled two critical vulnerabilities—CVE-2024-43093 and CVE-2024-50302—currently under...

BigAnt Server 0-Day Vulnerability Lets Attackers Run Malicious Code Remotely

A critical vulnerability in BigAntSoft's enterprise chat server software has exposed ~50 internet-facing systems...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

Update Alert: Google Warns of Critical Android Vulnerabilities Under Exploit

Google’s March 2025 Android Security Bulletin has unveiled two critical vulnerabilities—CVE-2024-43093 and CVE-2024-50302—currently under...

Google Launches Shielded Email to Keep Your Address Hidden from Apps

Google is rolling out a new privacy-focused feature called Shielded Email, designed to prevent apps...

Hackers Abused Google and PayPal’s Infrastructure to Steal Users Personal Data

Cybersecurity researchers have uncovered a sophisticated phishing campaign leveraging Google Ads and PayPal’s infrastructure...