A glowing shield and padlock protect a computer chip in a browser window, while a yellow bird perches above.
Microsoft is testing an Edge Lockdown Mode that turns off the browser's graphics APIs. It's an opt-in experiment for people who expect to be targeted, and it isn't a feature most Edge users will want. The current version is limited to Edge Canary, the earliest and least stable release channel.

A glowing shield and padlock protect a computer chip in a browser window, while a yellow bird perches above. What Microsoft is testing​

The feature reduces Edge's attack surface by disabling the WebGL, WebGL2 and WebGPU APIs. It takes its name from Apple's Lockdown Mode and builds on Edge Enhanced Security Mode, internally called Super Duper Secure Mode, which disables JIT compilation in the V8 pipeline.

Microsoft's Browser Vulnerability Research team described the experiment in a post. The first version is available in Canary behind the #edge-sdsm-plus flag. It currently blocks WebGL and WebGPU, and Microsoft plans to add more capabilities over the coming releases. The company expects the full set of protections to take several releases.

The flag has been visible for a while. Windows Report earlier spotted it as "Enhanced Security Mode Plus", and at that point enabling it didn't activate any extra protections. That has now changed, because the flag now exposes real blocking toggles.

Why the GPU stack​

Microsoft's reasoning is that browser exploits often come in chains. An attacker first compromises the renderer, then needs a second bug in a more privileged process to escape the sandbox. Blocking a privileged component can break that chain.

Gareth Evans, Microsoft's Partner Security Group Manager, said the first mitigations target the GPU process. That process is a more privileged component that handles complex graphics workloads across browser code, third-party libraries and device drivers. Web content reaches it mainly through WebGL and WebGPU. WebNN can also use hardware acceleration for machine-learning workloads. Microsoft doesn't say the current experiment blocks WebNN.

The 60% claim​

Microsoft says its analysis of known exploited vulnerabilities since February 2022 shows the current Canary version would have mitigated roughly 60% of privilege-escalation exploits seen in the wild.

Treat this number with some care:

  • It is Microsoft's own retrospective estimate, not an independent test.
  • It covers privilege-escalation exploits only. It is not a claim that 60% of all browser attacks are blocked.
  • It describes the current experimental mitigations. It doesn't measure a live deployment.

Who it's for​

The mode is meant for users facing highly targeted attacks who will trade website compatibility for stronger defenses. Evans named journalists, executives, security researchers and administrators as the audience. Devices in highly restricted environments could also benefit.

The cost is compatibility. Evans warned that sites using the disabled APIs may not work properly, especially interactive graphics such as games and maps. Design tools and visualization sites are likely to be affected too. Microsoft says a manual bypass may be needed for some sites.

How to try it​

You need Edge Canary. Microsoft's steps are:

  1. Update Canary at edge://settings/help.
  2. Set edge://flags/#edge-sdsm-plus to Enabled and restart.
  3. Go to edge://settings/privacy/security, turn on "Enhance your security on the web" and choose Strict.
  4. The "Block WebGL graphics" and "Block WebGPU graphics" options appear below it. Make sure both are on.
  5. Reload your test pages.

If it's working, a "Lockdown Enabled" indicator appears in the address bar when WebGL or WebGPU is blocked for a page. Warnings in the console identify blocked WebGL or WebGPU requests. The edge://security-diagnostics page, under Enhanced Security Mode, shows blocking settings and past block decisions.

Microsoft's post says the two blocking toggles default to on for profiles that have never used Enhanced Security Mode. Profiles that already use it have to switch them on. Microsoft asks testers to report problems through Settings > Help and Support > Send feedback.

How it fits with Enhanced Security Mode​

Enhanced Security Mode already exists in stable Edge. Microsoft's documentation says it disables JIT compilation and turns on hardware-based protections. The Microsoft Learn page lists three settings:

  • Off: the default.
  • Balanced: applies the protections to unfamiliar sites. This is the recommended setting.
  • Strict: applies them to every site. The page says it isn't appropriate for most users because it may require some configuration to complete normal tasks.

Lockdown Mode piggybacks on Strict. Strict already carries a usability cost, and this adds a second one.

What admins should know​

Nothing here is ready for production. Microsoft says the finished design will include clearer descriptions of restricted capabilities and site-level exceptions that restore trusted sites without weakening protection elsewhere. Those are plans, not shipped features. Enterprise controls for the existing mode already exist as Group Policy settings, with allow and deny lists. Microsoft hasn't said whether Lockdown Mode will get its own policies.

If you manage high-risk users, a small pilot makes sense. Test on Canary, keep a list of the sites that break, and see whether the exception workflow works for your people. Given how often GPU bugs turn up in Chromium security updates, the idea is reasonable. Whether it's practical will depend on how well the exceptions work.

Bottom line​

  • Status: an experiment in Edge Canary behind a flag. It isn't generally available or on by default.
  • What it blocks today: WebGL, WebGL2 and WebGPU.
  • Trade-off: stronger protection against privilege escalation, but graphics-heavy sites may break.
  • Still unknown: a release timeline, enterprise policy controls, and the final exception experience.
 

References

  1. Microsoft tests new Edge Lockdown Mode that disables GPU APIs BleepingComputer 2026-11-19T06:46:00-05:00
  2. Reducing the Opportunity for Exploitation with Edge Lockdown Mode microsoftedge.github.io
  3. Super Duper Secure Mode microsoftedge.github.io