Details

DEPRECATED: This policy is deprecated. It is currently supported but will become obsolete in a future release.

When this setting is enabled Microsoft Edge allows connections secured by SHA-1 signed certificates so long as the the certificate chains to a locally-installed root certificate and is otherwise valid.

Note that this policy depends on the operating system (OS) certificate verification stack allowing SHA-1 signatures. If an OS update changes the OS handling of SHA-1 certificates this policy might no longer have effect. Further this policy is intended as a temporary workaround to give enterprises more time to move away from SHA-1. This policy will be removed in Microsoft Edge 92 releasing in mid 2021.If you don’t set this policy or set it to false or the SHA-1 certificate chains to a publicly trusted certificate root then Microsoft Edge won’t allow certificates signed by SHA-1.This policy is available only on Windows instances that are joined to a Microsoft Active Directory domain Windows 10 Pro or Enterprise instances that enrolled for device management or macOS instances that are that are managed via MDM or joined to a domain via MCX.

Solution

Policy Path: Microsoft Edge
Policy Setting Name: Allow certificates signed using SHA-1 when issued by local trust anchors (deprecated)

Supportive Information

The following resource is also helpful.

• https://techcommunity.microsoft.com/t5/microsoft-security-baselines/security-baseline-for-microsoft-edge-version-89/ba-p/2186265

This security hardening control applies to the following category of controls within NIST 800-53: Configuration Management.This control applies to the following type of system Windows.

References

• 800-53|CM-5(3)

Source

• Tenable.com/audits