Lockdown Mode is a Firefox feature that lets your organization apply stronger security protections to specific websites. When you visit one of these sites, Firefox shows an icon in the address bar and some website features are limited. Sites your organization hasn't selected work as usual.
Organizations use Lockdown Mode to replace virtual desktops (VDI) and remote browser isolation (RBI) for web apps. Instead of streaming a remote desktop or browser to your device, Firefox isolates sensitive sites on your device: each protected site runs with fewer features an attacker could exploit, and its data is kept apart from the rest of your browsing.
Table of Contents
How to tell if Lockdown Mode is on
When protections apply to the page you're viewing, Firefox shows a restrictions icon on the right side of the address bar.
Click the icon to see the message Viewing with restrictions applied:
You can't turn these protections off yourself. They're set by your organization's IT or security team.
What changes on a protected site
Your organization chooses which protections apply to each site, so you may see some or all of these changes:
- Script optimizations turned off: pages that rely heavily on JavaScript, such as web apps, maps, and document editors, may load or respond more slowly.
- Service workers blocked: the site can't work offline, send push notifications, or sync in the background. You may not be able to install it as an app.
- Secure connections only (HTTPS): Firefox only loads the site over a secure connection. If the site doesn't support HTTPS, you'll see an error page instead of the site.
- Separate container: the site keeps its cookies and sign-ins apart from your other tabs, so you may need to sign in again. If your organization also makes the container temporary, Firefox doesn't keep the site's data between sessions and you'll need to sign in each time.
Most browsing works normally. These limits are expected: each one removes a way an attacker could exploit the browser.
If a protected site doesn't work
- Check the address bar for the restrictions icon. If it isn't there, Lockdown Mode isn't affecting the page.
- Reload the page.
- If the site asks you to sign in again, sign in. This is expected when the site opens in a separate container.
- If the site still doesn't work, contact your IT or help desk team. Tell them the site address, what you were trying to do, and what happened.
For help desk staff and administrators
Lockdown Mode is configured with the SitePolicies enterprise policy. Each entry lists the sites to protect (Match), any sites to leave out (Exceptions), and the protections to apply (Policies). You may turn off JavaScript just-in-time compilation (JIT), block service workers, prevent downgrades to insecure HTTP connections, and open sites in their own containers.
When a user reports a broken site, these symptoms may match each protection:
| Symptom | Likely protection |
|---|---|
| Site is slow or unresponsive | DisableJit |
| Offline mode, notifications, or app install don't work | DisableServiceWorkers |
| Error page instead of the site | HttpsOnly |
| User is signed out or asked to sign in repeatedly | Container (especially when ephemeral is set) |
If the site is required for work, the narrowest fix is usually to add the specific address to Exceptions or to change which protections apply to that Match entry. Check with your security team before relaxing protections, and review exceptions periodically.
For configuration steps, policy values, defaults, and limitations, see SitePolicies on Firefox Admin Docs.