Set up multi-factor authentication and a password manager

Step-by-step: list your accounts, choose a method, turn on MFA, set up a password manager and keep recovery codes safe. Based on NIST and IRS guidance.

Country-neutral · Updated November 20, 2026

Country-neutral steps, with a US rule note on where multi-factor authentication is required. Sources are NIST small business guidance, IRS Publication 4557 and 16 CFR Part 314. The ordering and the set-up steps are working practice, not quotations of those sources. General information, not legal advice.

What multi-factor authentication is

Multi-factor authentication, or MFA, asks for two or more kinds of proof before an account opens. NIST names three kinds: something you know, such as a password or PIN; something you have, such as a security key; and something you are, such as a fingerprint or face scan. Its page says that if a password is compromised, MFA creates a second barrier, and that enabling MFA on all accounts that offer it is essential for reducing risk (NIST, multi-factor authentication guidance).

IRS Publication 4557 gives the same example: you enter your username and password plus a security code sent to your phone. It tells practitioners to use the most secure option available, not only for tax software but for email accounts and storage accounts, and to protect the password manager with a strong password.

Which kind to choose

NIST prefers phishing-resistant MFA, such as hardware security keys or authenticators built into a phone or laptop, and says one-time codes and text-message codes can be susceptible to phishing. For applications that protect sensitive information, and for administrator accounts, NIST says organizations should be enforcing, or at least offering, the phishing-resistant options. Use them where the service supports them. Where it does not, an authenticator app or a text code is still much better than a password alone.

Where the rules require it

US rule. The FTC Safeguards Rule requires multi-factor authentication for any individual accessing any information system, unless the firm's qualified individual approves in writing an equivalent or stronger method (16 CFR 314.4(c)(5)). Publication 4557 describes the rule as applying to covered companies regardless of size, and recommends MFA for anyone accessing customer information. Firms that fall under the rule may ask you for proof that you use it. Firms outside the rule may require it by contract anyway. Check your own regulator for local requirements.

Tutorial 1: turn on MFA

  1. List your accounts. Write down every account that holds or can reach client data: email, cloud storage, the firm's workspace, tax or accounting software, your password manager, your bank, your domain or website host and your phone account.
  2. Rank them. Start with email, because a password reset to your email can open every other account. Then the password manager, then storage and firm systems, then the rest.
  3. Open the security settings of each account and look for "two-step verification", "multi-factor" or "security key".
  4. Pick the strongest method offered, ranked as above.
  5. Enroll a second method if the service allows it, so a lost phone does not lock you out.
  6. Save the recovery codes the service gives you. Store them offline or in the password manager, not on the device that holds the codes.
  7. Test it. Sign out and in again from a clean browser.
  8. Record the date in your device and account list.

Tutorial 2: set up a password manager

A password manager creates and stores a unique password for each account, so you need to remember only one strong passphrase. Publication 4557 suggests using one, protected by a strong password, and NIST lists it among the ways to manage access to systems and data.

  1. Choose one from a supplier you trust, with advice from colleagues, a professional association or your insurer. Publication 4557 gives this advice for security software, and it fits here. Download it from the supplier's own site.
  2. Create a long passphrase for the vault: words you can remember, not personal details. Publication 4557 recommends phrases over personal information, and considering at least 16 characters for an administrator's password.
  3. Turn on MFA for the manager itself, using the strongest method it supports.
  4. Move accounts in one at a time. Start with email and storage. Change each password to a generated one as you go, and avoid reusing any.
  5. Retire browser-saved passwords. Publication 4557 advises disabling the stored-password feature some systems offer.
  6. Store the emergency recovery information offline: a printed sheet in a locked place.
  7. Plan for death or incapacity if clients depend on you: decide who could reach what, and write it down.

Common mistakes

  • Approving a prompt you did not start. If a sign-in request arrives that you did not initiate, deny it and change that account's password. It means someone has the password.
  • Sharing one login. Publication 4557 says each person with access should have a unique password. Do not share yours.
  • Keeping the recovery codes in the same place as the password.
  • Leaving old accounts open. Close accounts you no longer use.

Check your work

Once a quarter, open the account list and confirm three things: every account still has MFA, no unknown device or app is registered on any account, and the recovery codes are where you think they are. Remove devices you no longer own. NIST also suggests building a short policy and inventorying which systems support MFA, which this list does. If a firm gives you access to its workspace, ask whether it enforces MFA on its side, and use whatever method it requires.

Frequently asked questions

Is a text message code enough?

It is better than a password alone, and weaker than a security key. NIST says text codes and passcodes can be phished.

Do I need MFA on the password manager?

Yes. It holds the keys to everything else.

What if I lose my phone?

Use your second method or a recovery code. That is why you set both up.

Sources

Last verified November 20, 2026. Sources checked by the editorial team; not yet reviewed by a named professional. General information, not legal, tax or accounting advice.

Related pages

Join the CORAA CPA network waitlist

CORAA prepares audit files for US CPA firms. Network members are independent contractors who clear what the software flags, with evidence and a note, paid per file under a contractor agreement.

  • Files are offered to you; you accept or decline
  • No exclusivity: you can work for others
  • The firm reviews and signs; CORAA never does

* required