Google is making G Suite accounts more secure by allowing administrators to remove phone-based 2-step verification (2-SV) from the available multi-factor verification options.
With the new policy in place, admins enforcing a second factor at login to improve the security of an account can prevent users from selecting 2-SV methods such as SMS and voice codes, which have been already deemed insecure.
“As awareness of the potential vulnerabilities associated with SMS and voice codes has increased, some admins asked us for more control over the ability to use phone-based 2-Step Verification methods within organizations,” Google says.
With additional control over the authentication methods used in their domain, administrators can now increase the security of user accounts and associated data, Google says.
To apply the new policy, G Suite admins need to access the Admin console and go to Security > Advanced security settings > Allowed two step verification methods.
Users enrolling in 2-step verification for the first time will have the option to set up Google Prompt or to ‘Choose another option,’ which lets them add a Security Key instead.
Users with phone 2-SV enabled won’t be able to log into their account when the change is made.
Thus, Google advises admins to inform all users of the planned changes in due time, so they are able to switch to a different 2SV method by the time the new policy is enforced.
Users who haven’t made the switch by the enforcement date can be added to an exception group where 2SV isn’t enforced until they can add a 2SV method. This, however, is only a workaround, to avoid having users locked out of their accounts, and is not recommended as standard practice.
“Before setting this policy, tell your users to add and start using another 2SV method. Also inform them that they won’t be able to get 2SV verification codes on their phones after a specified enforcement date,” Google notes.
The new policy is gradually rolling out and should become available to all G Suite admins in the next 15 days. The policy, however, is not enabled by default and admins need to explicitly choose to apply it.
Related: Google Helps G Suite Admins Enforce Strong Passwords
Related: Google Makes Secure LDAP Generally Available
Related: Google Turns on G Suite Alerts for State-Sponsored Attacks