Google Workspace has announced new password policies that will impact how users and third-party apps access Google services.
The changes, aimed at eliminating less secure sign-in methods, will be implemented in stages throughout 2024.
Here’s what you need to know about the upcoming changes and how they will affect users and administrators.
Google Workspace will no longer support the sign-in method for third-party apps or devices that require users to share their Google username and password.
This method, known as Less Secure Apps (LSAs), poses a security risk by requiring users to share their credentials with third-party apps, potentially allowing unauthorized access.
Instead, Google is encouraging the use of “Sign-In with Google,” which utilizes the more secure OAuth authentication method. The transition away from LSAs will occur in two stages:
Analyse Any Suspicious Links Using ANY.RUN’s New Safe Browsing Tool:
Organizations using Mobile Device Management (MDM) systems will also see changes. Starting June 15, 2024, MDM push configurations for password-based protocols like IMAP and CalDAV will no longer work for new connections.
By September 30, 2024, these configurations will cease functioning for existing users as well.
Administrators will need to push Google Accounts using OAuth through their MDM providers to ensure continued access on iOS devices.
Google Endpoint Management users should note that custom push configurations for CalDAV and CardDAV will become ineffective after these dates.
As part of this security overhaul, Google Sync is also being sunsetted:
Administrators can identify current Google Sync usage within their organization by navigating to Devices > Mobile & Endpoints > Devices in the Admin Console and filtering by Type: Google Sync.
For end-users relying on apps that access Google Accounts with only a username and password, action is required before September 30, 2024.
Users should switch to apps that support OAuth or configure app passwords where necessary. For example:
Developers must update their applications to use OAuth 2.0 to maintain compatibility with Google Workspace accounts. Detailed guides are available from Google to assist in this transition.
Google’s updated password policies represent a significant shift towards enhancing user security across its platform.
By phasing out less secure authentication methods and promoting the use of OAuth, Google aims to protect user data from potential breaches.
Administrators and end-users are encouraged to prepare for these changes well in advance of the deadlines to ensure a smooth transition.
Free Webinar on How to Protect Small Businesses Against Advanced Cyberthreats ->
Recent revelations about Google’s SafetyCore app have ignited a firestorm of privacy debates, echoing Apple’s…
Security researchers have uncovered a novel Bluetooth tracking vulnerability in Apple’s Find My network –…
Cybersecurity firm Group-IB, alongside the Royal Thai Police and Singapore Police Force, announced the arrest…
Cisco Systems has issued a critical security advisory for a newly disclosed command injection vulnerability…
A newly discovered Wi-Fi jamming technique enables attackers to selectively disconnect individual devices from networks…
GitLab has urgently released security updates to address multiple high-severity vulnerabilities in its platform that…