Microsoft Edge “Super Duper Secure Mode” How much speed can security cost?
Company on the subject
The test of the Microsoft Vulnerability Research Team on the “Super Duper Secure Mode” makes sense at first glance. Almost half of the vulnerabilities and vulnerabilities (CVE) known for V8 relate to the JIT compiler and more than half of all “in-the-wild” exploits for Chrome exploit errors in JIT. (Modern versions of Edge are based on the same Chromium code as Google’s Chrome browser, so Chrome exploits also affect Edge). So Microsoft speculates whether it would not be the simplest thing to simply deactivate the problematic sub-system and see what happens then.
Only half as fast
The team compared the last official version of Edge (version 92.0.902.67) with the last available Microsoft Edge beta (version 93.0.961.11) with Super Duper Secure Mode activated and deactivated. During testing, Malwarebytes found that the speed differences between the last official version and the beta version were minimal, so we did not include them in the results. The tests were performed in a virtual machine (VM) with a slow connection. We used Sunspider 1.0.2 as a benchmark.
Notes on the test:
- The test was repeated several times and, although there were differences, they were generally minimal. (The results varied between 1.87 times and 1.90 times the speed when JIT was activated).
A permanent solution?
If you want to try the Super Duper Secure Mode yourself, you need one of the Microsoft Edge pre-release versions (Beta, Dev or Canary). If one of the above is used, simply enter edge: // flags / # edge-enable-super-duper-secure-mode in the address line of the browser and set the new function to “Enabled”.