Skip to content

Edge Browser | Harden System Security

Edge Browser configurations - Harden Windows Security GitHub repository










  • Rotating pink checkmark denoting registry or cmdlet Policy that automatically denies the window management permission to sites by default. This limits the ability of sites to see information about the device's screens and use that information to open and place windows or request fullscreen on specific screens.


  • Rotating pink checkmark denoting registry or cmdlet Policy that will keep support for Manifest V2 extensions enabled even after its depreciation. Manifest V2 extension support is vital for proper functioning of ublock origin (and similar extensions) which is beyond a simple adblocker and can provide lots of protection when browsing the web through its custom lists.

  • Note that this is something being pushed by Google through their controlling power of Chromium, not Microsoft.


  • Rotating pink checkmark denoting registry or cmdlet Policy that will prevent websites to even request access to the local connected USB devices.


  • Rotating pink checkmark denoting registry or cmdlet Policy that will disable dynamic code in Edge browser which is a security feature that prevents the browser process from creating dynamic code. The default value of this policy is not explicitly defined, it could be enable or could be disabled. Setting it explicitly to enabled via this policy ensures that no dynamic code is created by the browser process.


TLS_RSA_WITH_AES_256_CBC_SHA  Reason: NO Perfect Forward Secrecy, CBC, SHA1
TLS_RSA_WITH_AES_128_CBC_SHA  Reason: NO Perfect Forward Secrecy, CBC, SHA1
TLS_RSA_WITH_AES_128_GCM_SHA256  Reason: NO Perfect Forward Secrecy
TLS_RSA_WITH_AES_256_GCM_SHA384  Reason: NO Perfect Forward Secrecy
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA  Reason: CBC, SHA1
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA  Reason: CBC, SHA1


Due to security reasons, many policies cannot be used when you are signed into Edge browser using personal Microsoft account. This app does not use any of those policies. When those policies are applied, they are ignored by the browser and edge://policy/ shows an error for them.


  • You can view all of the policies being applied to your Edge browser by visiting this page: edge://policy/
  • You can find all of the available internal Edge pages in here: edge://about/