Every employee has dozens of work accounts: email, CRM, online banking, cloud services, supplier portals. The easiest option, offered by the browser itself, is “save password”. For a company it is the riskiest: passwords end up in personal profiles, nobody knows where they are, and when an employee leaves, the access leaves with them.
Here is why storing work passwords in the browser is a bad idea, what a business password manager gives you, and how to choose and roll one out.
Why browser-stored passwords are a risk for a company
- No central control. The company cannot see which work passwords are saved, by whom and on which devices. Browsers often sync them to the employee’s personal account — and to home devices.
- Employees leaving. Passwords saved in their browser cannot be revoked centrally; access has to be changed by hand, and some of it is forgotten.
- Information stealers. According to the review by Ukraine’s National Cybersecurity Coordination Center, account compromise became one of the dominant attack vectors in 2025, with infostealers collecting passwords, VPN configurations and session tokens from infected computers.
- Shared passwords travel through messengers. A password for a shared service is sent in a chat and stays there forever.
- No log. Nobody can see who used a shared account and when.
What a business password manager gives you
- Central management: password policies, mandatory multi-factor authentication to open the vault, device control.
- Role-based shared vaults: accounting sees online banking, marketing sees ad accounts, IT sees admin access. Nobody gets more than they need.
- Central revocation: when an employee leaves, their vault access is switched off centrally, and the shared passwords they saw are listed for change.
- An activity log: who opened, changed or shared entries.
- A password generator: long unique passwords for every service without having to remember them.
How to choose
| Criterion | What to check |
|---|---|
| Encryption | how data is encrypted and whether the provider can access vault contents — from the documentation and independent audit results |
| Vault sign-in | multi-factor authentication, integration with corporate sign-in (Active Directory, Microsoft Entra ID) |
| Roles and sharing | groups, shared vaults, view-only rights |
| Logging | which actions are logged, whether logs can be sent to a monitoring system |
| Hosting | a cloud service or self-hosted; for financial institutions — the NBU’s cloud requirements |
| Exit | data export if you change product |
| Emergency access | what happens if the administrator is unavailable |
Financial institutions using the cloud are subject to NBU Resolution No. 99 — see “NBU Resolution 99: cloud for banks and fintech”.
A modern password policy
NIST’s updated digital identity guidelines (SP 800-63B-4, 2025) changed the familiar rules:
- Length matters more than complexity. A password used as the only factor — at least 15 characters; as part of multi-factor authentication — at least 8.
- No forced composition rules such as “must contain a digit and a special character”.
- No scheduled changes. Change a password when there is evidence of compromise.
- Check against lists of common and compromised passwords when a password is created or changed.
- Password managers and autofill must be allowed.
Insurers, credit unions, finance companies and pawnshops are subject to NBU Resolution No. 143: passwords of at least 12 characters for users and 15 for privileged users, with digits, mixed-case letters and special characters, changed at least every 90 days, and multi-factor authentication for remote access. More in “NBU Resolution 143: cybersecurity rules for NBFIs”. A password manager helps meet these requirements too.
How to roll it out
- A pilot with the IT team. Vault structure, roles, sharing rules.
- Multi-factor authentication to sign in to the manager — no exceptions.
- Move passwords from browsers and spreadsheets into vaults, replacing weak and reused ones.
- Turn off password saving in browsers with a central policy. For example, in Microsoft Edge, disabling the PasswordManagerEnabled policy stops users saving new passwords, but already saved ones remain — move and delete them separately.
- Instructions for staff — how to use it, what to do if a device is lost.
- A leaver procedure: switching off manager access and changing the shared passwords the person saw.
- Emergency access: how to recover access to critical entries if the responsible person is unavailable.
Frequently asked questions
Isn’t it dangerous to keep all passwords in one place? The risk is concentrated, so the vault is protected more strongly than any single service: a long master password, mandatory multi-factor authentication, encryption, an activity log. The alternative — passwords scattered across browsers, spreadsheets and chats — is worse precisely because they can neither be protected nor revoked.
What if employees don’t want to use it? Start with services where the manager obviously saves time: a team’s shared accounts, online banking, ad accounts. Once browser saving is disabled by policy and the passwords people need are already in the vault, habits change quickly.
Does a password manager replace multi-factor authentication? No. It makes passwords long and unique, but a stolen password can still be used. Email, VPN, cloud services and admin access need a second factor.
Checklist
- A business password manager is chosen, its encryption and logging are checked
- Sign-in to the manager requires multi-factor authentication
- Vaults are split by role, with no excess rights
- Work passwords are moved out of browsers and spreadsheets
- Browser password saving is disabled by policy, old entries are deleted
- Passwords are long and unique and checked against compromised lists
- Shared passwords are not sent through messengers
- A leaver procedure with access revocation exists
- Emergency access to critical entries exists
- Manager logs are reviewed or sent to monitoring
How Bereg-IT can help
We review where and how work passwords are stored and help choose a solution that fits your requirements (consulting and audit). We set up multi-factor authentication and Active Directory group policies that turn off password saving in browsers (IT infrastructure, information security). Suspicious sign-ins and account changes can be sent to SOC as a Service monitoring.
The first consultation is free. Send a request and an information security specialist will get in touch.
Sources
- NIST SP 800-63B-4, Digital Identity Guidelines: Authentication and Authenticator Management (July 2025): https://csrc.nist.gov/pubs/sp/800/63/b/4/final
- National Cybersecurity Coordination Center at the NSDC of Ukraine, Review of the National Cybersecurity System of Ukraine 2025 (in Ukrainian) — account compromise and infostealers: https://www.rnbo.gov.ua/files/2026/NATIONAL_CYBER_SCC/kiber_2025.pdf
- Microsoft Learn, Microsoft Edge Browser Policy: PasswordManagerEnabled: https://learn.microsoft.com/en-us/deployedge/microsoft-edge-policies/passwordmanagerenabled
- Resolution of the Board of the National Bank of Ukraine of 09.12.2025 No. 143 — password and authentication requirements (in Ukrainian): https://bank.gov.ua/admin_uploads/law/09122025_143.pdf