DEV Community

Olli Junes
Olli Junes

Posted on

Rolling out a password manager in a small company: the order matters

Installing a password manager takes an afternoon. The benefit arrives only when the shared logins are inside it and no longer sit in chat threads, spreadsheets and one person's browser. This is a rollout order for a small company, with the reasoning behind each step.

We provide managed hosting and website maintenance at ResaHost, and we set up and manage 1Password Business for customers, so we have a commercial interest in this subject. The steps below are not specific to one product, and where we describe product behaviour we link the vendor's own documentation.

Why reuse is the problem to solve

The attack to design against is credential stuffing: the OWASP Credential Stuffing Prevention Cheat Sheet defines it as testing username and password pairs obtained from the breach of another site. If an employee uses the same password for a supplier portal and for the company mailbox, the portal's breach becomes your incident. OWASP names multi-factor authentication as by far the best defence against password attacks of this kind, so a password manager and MFA belong together.

The UK NCSC gives the same reasoning for a unique password per account, notes that nobody can remember that many, and recommends turning on two-step verification on the password manager account as well. NIST's authentication guideline, SP 800-63B, goes further for service owners: verifiers shall allow password managers and autofill, and should permit pasting into password fields. If you run a login form for your own product, blocking paste works against your users' security.

1. Inventory where the logins live today

List the services your team signs in to, and for each one note where the login is kept and who uses it. Developers and site owners should include the less obvious ones: domain registrar, DNS provider, hosting control panel, SSH and database credentials, payment and analytics accounts, and the shared inbox that receives password resets. Mark the email accounts used to reset other passwords. Whoever controls those can usually reach everything else.

2. Decide on vaults and two administrators

Keep the vault structure small. A shared vault for logins everyone uses, one for finance, and one for website, domain and infrastructure access is enough for a small company. Vaults should follow who needs to see what, not mirror a list of services.

Name at least two administrators. If the only administrator is away or leaves, nobody can add users or recover a locked-out account. Check how recovery works in the product you pick before you rely on it.

3. Understand what protects the vault

With 1Password, for example, the data is encrypted with a key derived from two things: the account password and a Secret Key. According to 1Password's documentation, the Secret Key has 128 bits of entropy and is stored on the user's devices and in the Emergency Kit rather than with the vendor, and the account password, which has to be memorised, has about 40 bits of entropy on average. Those two figures explain why the account password still has to be long and unique, and why losing the Secret Key without a saved Emergency Kit can lock you out. Other products design this differently, so read the vendor's security model before you decide.

4. Move the logins, then delete the old copies

Import from browsers or spreadsheets, check the result, and then remove the originals. If you skip the deletion step, the logins live in two places again, which is worse than before because nobody knows which copy is current. A browser export is an unencrypted file, so delete it, including from the trash, as soon as the import is verified.

5. Replace the reused and weak passwords

Moving a weak password into a vault only stores it neatly. Work through the manager's warnings for reused, weak and breached passwords in order of importance: email first, then the domain registrar, bank, accounting, cloud storage and the website admin. Generate random replacements and turn on MFA at the same time where the service supports it. The NCSC also recommends passkeys as the first choice wherever a service offers them, with a unique password plus two-step verification elsewhere.

This step does not have to happen in one day. Agree who handles the list and by when.

6. Share with outsiders through the manager

Accountants, freelancers and stand-in staff sometimes need a login. Sending it by email or text puts a secret in two mailboxes with no expiry. Many business password managers can share an item with a time limit or give a guest access to a single vault. Use that and review it when the engagement ends.

7. Write the leaver checklist

Removing a departing employee's account is not enough, because they may have seen or copied shared passwords. Because the logins now sit in vaults, you can list which vaults they could open and rotate the most important credentials in those vaults. Without a password manager that list usually does not exist, which is why old shared passwords stay in use for years.

When to ask for help

A ten-person company can do all of this itself if someone has the time. We describe the same rollout, step by step, in our guide to rolling out a password manager in a small business. It is written around 1Password Business because that is the product we deliver, and we say so there as well.

Sources

  1. OWASP: Credential Stuffing Prevention Cheat Sheet
  2. UK NCSC: Password managers
  3. NIST SP 800-63B: Authentication and Authenticator Management
  4. 1Password Support: About your Secret Key
  5. ResaHost guide: Rolling out a password manager in a small business (commercial source)

Top comments (0)