Browser Hardening in 2026: A Checklist and What Changed Since 2021
Archi4 min read
Contents
- The Browser Got Better. Your Settings Probably Did Not.
- 1. Check Which Engine You Are Actually Running
- 2. Audit Site Permissions and Set Them to Ask
- 3. Turn Off Autofill for Payment Data
- 4. Separate Profiles by Function, Not by Mood
- 5. Check Extension Count and Review Permissions
- 6. Enable DNS-over-HTTPS, Then Decide Who Sees It
- 7. Keep the Update Channel On and Restart
- What the Engine Fixed for You
- What It Did Not Fix
The Browser Got Better. Your Settings Probably Did Not.#
Five years ago, hardening a browser was mostly about blocking trackers and turning off Flash. Flash is gone. Third-party cookie deprecation has dragged on longer than anyone promised. What has changed is subtler: the rendering engine now ships security features that used to require extensions, and it also ships more ways for a site to reach into your machine.
Here is a checklist worth walking through, with notes on how each item compares to 2021.
1. Check Which Engine You Are Actually Running#
Chromium variants now account for a large majority of desktop and mobile browsing, and that concentration is the biggest shift of the past five years. In 2021 there were still four engines in serious contention. Today, for most people, there are two: Chromium and Gecko, with WebKit mostly confined to Apple devices.
What this means in practice: a single engine vulnerability has a wider blast radius than it did. If your work depends on one vendor's browsing, keep a second engine installed for anything sensitive, such as banking or admin consoles. This costs you ten minutes and buys real separation.
2. Audit Site Permissions and Set Them to Ask#
Permissions ask once, then rarely ask again. Cameras, microphones, location, notifications, clipboard reads, and now local network access all sit in a list most people never open.
Compare to 2021: the number of permission categories has grown, and the prompts have gotten quieter. Some engines now grant a permission for a session rather than persistently, which helps, but only if you notice. Open the permissions page for your browser, remove anything you do not recognize, and set defaults to "ask."
3. Turn Off Autofill for Payment Data#
Autofill is convenient and it is also a target. Stored card numbers and addresses are protected by the browser's own sandbox, not by your disk encryption alone. If you share a machine profile, or if you use a browser profile for both work and personal life, keep payment autofill off and use a password manager's separate vault instead.
Five years ago this advice was mostly about form-filling quirks. Now it is about attack surface: several recent exploit chains started with a compromised renderer reading autofill data.
4. Separate Profiles by Function, Not by Mood#
Profile separation is the cheapest isolation available. One profile for logged-in work accounts, one for personal browsing, one for anything you would rather not see correlated. Modern browsers made this easier: profile switching is one click, and some engines isolate each profile's storage and cache.
In 2021, profile isolation existed but was clunky. The improvement is real, and it is underused.
5. Check Extension Count and Review Permissions#
Every extension runs inside your browser with the access it requests. Count yours. If the number is above five, justify each one. Look for "read and change all your data on all websites," which is broad access that most utilities do not need.
One thing that changed for the better: extension stores now require more disclosure and review, and manifest changes pushed many older extensions to declare their access more precisely. One thing that changed for the worse: abandoned extensions linger, and a sale of a popular extension to a new owner is a common path to abuse. Remove what you do not actively use.
6. Enable DNS-over-HTTPS, Then Decide Who Sees It#
Encrypted DNS is now a default in several major browsers. That is a real privacy gain compared with 2021, when it was an optional toggle most people never touched. The tradeoff moved rather than disappeared: your DNS queries are now visible to whichever resolver the browser selected, which may not be your network operator or your company's filtering service.
Check which resolver you are using. On a managed work device, follow the organization's policy. On a personal device, choose deliberately rather than accepting whatever the browser picked at setup.
7. Keep the Update Channel On and Restart#
Browser updates ship silently and often, and many of them patch actively exploited flaws. The failure mode is not a missed update; it is a pending update that never applies because the browser stays open for weeks.
Set a habit: close and reopen the browser at least once a day, or enable automatic restart. Five years ago, browser update cadence was measured in weeks. Now it is measured in days, sometimes hours for zero-days, and the gap between patch availability and exploitation has narrowed.
What the Engine Fixed for You#
Site isolation, now standard in major engines, means a malicious page in one tab has a harder time reading another. Memory safety work in the rendering pipeline has cut a category of bugs that used to dominate exploit reports. Sandboxing is stricter. These are genuine improvements over 2021, and they are why the checklist above is shorter than it once was.
What It Did Not Fix#
The browser still cannot tell you whether the site you reached is the site you meant. Phishing pages now load faster and look more convincing than the originals. Password managers that match on domain are your best defense, and they only work if you let them fill rather than typing credentials yourself.
And the browser still trusts too much by default. Every permission you granted in 2021 and forgot about is still granted unless a policy revoked it. That is the core of this checklist: the features improved, the defaults drifted, and the review is still yours to do.
More articles