Plan your migrations so that your users can access critical webpages during this transition.

Enabling this policy is only a temporary solution to give you more time to transition to a permanent solution.

If your users are running the Chrome Browser on an OS that no longer supports Symantec certificates, enabling this policy will have no effect and the certificates will not be trusted. However, other OS’s such as Windows, Linux, or macOS could remove support for Symantec certificates before Chrome 73 is released.

Chrome OS will support this policy until version 73.

Click below for steps, depending on how and where you use certificates. Chrome versionĭistrust Symantec-issued certificates issued after 1 and before 1, but allow all certificates issued between these dates.ĭistrust all Symantec-issued certificates.Īssess your deployment to determine the best solution for your enterprise. Which certificates are blocked depends on the Chrome version and the date the certificates were created. Also, sites that use resources (such as Javascript or CSS stylesheets) served by a host that uses a Symantec certificate, may no longer work correctly.

Visitors to websites that use a Symantec certificate no longer trusted may see an error message. All certificates issued under Symantec brands such as GeoTrust ®, Equifax ®, Thawte ®, RapidSSL ®, and VeriSign ®, and those from Symantec resellers are impacted by this change.

In Chrome version 70 and later, Chrome Browser and Chrome OS will stop supporting Symantec certificates. Symantec ® certificates issued before December 2017 are being phased out of support starting with Chrome version 66 (applies to Chrome Browser and Chrome OS). Applies to managed Chrome browsers and ChromeOS devices.

Symantec version