Sophos requires users to switch from Chrome to Firefox because of authentication issues.

Sophos, a security company, recommends that customers who use Sophos Authentication for Thin Clients, or SATC, delay updates to the latest versions of Google Chrome and Microsoft Edge because of authentication issues. In a technical support document released earlier this month and discovered by Gunther Born, Sophos said any Chromium-based browser could encounter the problem, so the company advised users to stick to the previous version or switch directly to Firefox.

Sophos advises customers not to update to Google Chrome or Microsoft Edge’s 84 version at this time. Sophos also recommends that customers consider using Firefox as an alternative because it still works with SATC agents. The security firm said an alternative to the agency is already in the pipeline and is expected to go live later this year. If you already have Google Chrome or Microsoft Edge updates installed, it is recommended to downgrade to version 83 or switch directly to Firefox.

In addition, Sophos says customers can enable the “Runs network service in-process” logo in the Chromium browser so that they can be certified by SATC after the update. Sophos explains that Win32 API code injection is how SATC works. When a third-party SSO firewall client hooks up to the Win32 API network stack to detect firewall authentication for each USER connected by TCP, TCP connection requests originating in their Chrome browser are no longer detected by the firewall SSO client. Since Chrome no longer uses the Win32 web stack, subsequent TCP connections cannot be properly authenticated and will not be able to cross the firewall.

Sophos requires users to switch from Chrome to Firefox because of authentication issues.