Chrome misconfigurations in MEDC + Endpoint Protection (vulnerability scanning) need to be updated

Chrome misconfigurations in MEDC + Endpoint Protection (vulnerability scanning) need to be updated

After finding more Chrome misconfiguration errors it's pretty clear these rules are based on an outdated version of the Unified Compliance Framework Google Chrome configuration guide (by Network Frontiers). There is an updated version of that guide here (July 2021):


Customers who are paying for the Endpoint Protection add-on for MEDC are expecting these security notifications to be up-to-date and relevant. ManageEngine should definitely be updating all misconfiguration policies on a regular basis to add current security guidelines and remove outdated information.

Please update the MEDC Endpoint Protection Chrome misconfigurations to reflect current best practices.


P.S.
I'm posting this because I also found the "Safe Browsing is not enabled" security misconfiguration is looking at a Chrome policy that is no longer valid (deprecated since v83). This policy was replaced with a new policy called "SafeBrowsingProtectionLevel".

See official Chrome policy documentation:

                New to ADManager Plus?

                  New to ADSelfService Plus?