The browser offers to save the bank password, the user clicks yes, and life gets easier — for the user, and for anyone who later sits at that unlocked PC or steals the browser's data files. This guide grades the risk honestly: not panic, not denial.
Let us be fair to the browser first. Passwords saved in Chrome or Edge are stored encrypted, not in a readable text file, and a saved password is better than the same password used on twelve sites or written on a sticky note. The problems are more specific than the usual scare stories. One: the encryption key is the Windows login, so anyone using that unlocked session — a colleague, a visitor, malware running as the user — is already past the lock. Two: infostealer malware specifically hunts browser password stores, because they are on every PC in a known place. Three: sync quietly copies the office passwords to the user's personal phone and home browser, where the office has no control at all. Browser Security Plus cannot fix human nature, but its data leakage policies can switch password saving off across the office — this guide is about deciding when that is right, and what must be ready before you do it.
A one-person office where the owner uses one PC has a different answer from a forty-PC office with shared desks. Ask three questions. Are PCs shared or left unlocked? Shared sessions make browser saving genuinely dangerous. Do staff sign into the browser with personal accounts? Then sync is exporting your passwords nightly. What is actually saved? If banking and admin portals are in the list, the browser store is a high-value target whatever its encryption. Two or more bad answers means it is time to manage this centrally instead of hoping.
Switching saving off without offering a replacement fails by Friday: users revert to sticky notes and one password everywhere. The sequence that works is: first roll out the office password manager (a proper one, with its own vault, sharing controls and a master password or SSO), then migrate the important logins, then apply the Browser Security Plus data leakage policy that disables the browser's own password saving and autofill on every managed PC, and finally wipe the already-saved browser passwords so the old store does not linger as a second, forgotten copy. The manager's browser extension goes on the allow list from the extensions guide — the two policies are designed to arrive together.
The data leakage prevention settings cover the cluster around credentials: password saving itself, autofill for payment cards and addresses (a saved office card in a browser is a purchase waiting for an unlocked PC), and the sync of this data to personal accounts. While you are there, look at cookies and browsing history settings with clear eyes — clearing history automatically sounds safe but also destroys the one record that helps after an incident. Grade each setting by its job: protect credentials strictly, be slower to punish convenience that harms no one.
Announce it as what it is: your passwords are moving to a safer vault the office provides free; the browser copy will be deleted on this date; here is a 10-minute help session. Expect two objections. "The manager is slower" — true for the first week, false by the second, once autofill from the vault becomes habit. "IT just wants to see our passwords" — a good manager is built so even admins cannot read staff vaults; say so, and pick one that can prove it. Staff who understand the infostealer point — that malware steals the browser store wholesale, in seconds, without touching the PC — usually become the policy's supporters.
If a full password-manager rollout is not possible this quarter, the minimum defensible position is smaller: disable browser sync with personal accounts on work PCs, keep banking and admin logins out of browsers by written rule, and lock PCs on a short idle timer. That does not make the browser store safe — say so plainly in the office note — but it removes the two worst multipliers (sync export and the unlocked shared desk) while the real fix is planned. Partial honesty beats a policy PDF nobody follows.
Password saving, autofill and sync — how these settings are controlled from the console is shown step by step in the video.
▶️ Watch Full VideoThey are encrypted, but the key is the user's own login session — so anything or anyone running as that user can read them, including the infostealer malware family that exists specifically to harvest browser stores. The honest verdict: acceptable on a private, single-user PC with a strong login; a poor place for shared office machines and banking credentials.
A proper password manager provided by the office — it keeps credentials in a separate vault, works across the user's devices under office control, lets you revoke access when someone leaves, and its browser extension can be pushed to every PC through the same allow-list policy that blocks rogue extensions.
They remain in the browser until cleared, which is why the rollout order matters: migrate the important logins to the manager first, confirm staff can sign in from the vault, then disable saving and clear the stored browser passwords centrally. Skipping the migration step is how people get locked out of the bank on a Monday morning.