Microsoft Edge Security Baseline Update: Version 139 Enhancements
Microsoft has unveiled the latest security baseline for Edge browser version 139, which entails both the inclusion of a new setting and the removal of another. Security baselines serve a crucial function by enabling administrators to align their organization’s browser configurations with Microsoft’s current security recommendations.
Admins can download the updated security package directly from the Security Compliance Toolkit.
Disabling the EnableUnsafeSwiftShader Policy
One of the significant changes in this update is the default enforcement to disable the EnableUnsafeSwiftShader policy. This decision aims to reduce risks where malicious web content might exploit weaknesses within the renderer. SwiftShader is a fallback software renderer utilized in scenarios lacking GPU acceleration, such as in virtual machines. By disabling this feature, Microsoft appears to view it now as a potential security vulnerability rather than a necessary compatibility tool.
Impact on Enterprise Use of Virtual Machines
Given that SwiftShader has been particularly relevant in virtual machine environments, widely utilized in enterprise settings, this alteration could lead to operational disruptions for some organizations. While this security-enhancing step is commendable, organizations relying on SwiftShader may consider deviating from Microsoft’s recommended security setup to maintain functionality.
Introduction of Edge for Business Security Connectors
Additionally, this announcement introduces a new feature called Edge for Business security connectors. This functionality is designed to seamlessly integrate the Edge browser with security software focused on Data Loss Prevention (DLP) and authentication processes. Microsoft asserts that these connectors are essential for addressing critical gaps in enterprise security.
Proactive Security Measures
It’s important to note that Microsoft’s decision to disable SwiftShader does not stem from identified vulnerabilities; rather, it represents a proactive step towards strengthening security measures. Organizations utilizing it for their virtual machines should consider the implications of this change. If opting to deviate from Microsoft’s security baseline, it is essential to recognize that you step outside the bounds of the company’s security guidance.
For further information and images regarding these changes, please refer to the Source.
Related Articles:
Microsoft 365 Remains My Top Microsoft Product Despite Rising Costs
13:18
Why Clipboard History is an Essential Windows Feature
9:16
Microsoft outlines Windows 10 deprecation strategy for WHCP and HLK
9:12
Leave a Reply