We compete with Google because the health of the internet and online life depend on competition and choice. We compete with Google not because it's a good business opportunity. Please continue to give us feedback through the Security Baselines Discussion site or this post."From a social, civic and individual empowerment perspective ceding control of fundamental online infrastructure to a single company is terrible. We have included a spreadsheet listing the new settings in the release to make it easier for you to find them.Īs a friendly reminder, all available settings for Microsoft Edge are documented here, and all available settings for Microsoft Edge Update are documented here. Microsoft Edge version 104 introduced 12 new computer settings and 12 new user settings. Additional details on this setting can be found here. We highly encourage customers to begin compatibility testing with this setting to account for this upcoming change. Once that occurs the baseline will move to Enabled. By default, this setting is in Audit mode until such time as we have enough data to ensure the ecosystem is compatible. With this policy in place, it will now restrict the ability to load non-Microsoft signed binaries. However, there is 1 setting we would like to call out, Configure browser process code integrity guard setting.Ĭonfigure browser process code integrity guard setting (Consider Testing)įirst introduced with Edge in Windows 10 version 1511, code integrity guard requires DLLs to be Microsoft, Windows Store, or WHQL-signed. That baseline package can be downloaded from the Microsoft Security Compliance Toolkit. The Microsoft Edge version 98 package continues to be our recommended baseline. We have reviewed the new settings in Microsoft Edge version 104 and determined that there are no additional security settings that require enforcement. We are pleased to announce the enterprise-ready release of the security baseline for Microsoft Edge, version 104!
0 kommentar(er)
