Privacy and Security

Multi-Factor Authentication and Password Policies

A law firm MFA and password policy staff will follow: current NIST password rules, which MFA methods to choose, a sample policy and a rollout plan.

AssistCall research teamPublished Reviewed by Faruque Amin, VP of Sales and Marketing7 min read

On this page
  1. Why this policy comes first
  2. What current password guidance actually says
  3. Choosing MFA methods
  4. Setting up the password manager
  5. A sample policy
  6. Rolling it out without a revolt
  7. Remote work and shared devices
  8. Example: an exception that should not have been
  9. How this fits the rest of your security program
  10. Frequently asked questions
  11. References
Privacy and Security: Multi-Factor Authentication and Password PoliciesArticle coverPRIVACY AND SECURITYMulti-FactorAuthentication andPassword PoliciesAva for LawyersInsightsPrivacy and Security: Multi-Factor Authentication and Password PoliciesArticle coverPRIVACY AND SECURITYMulti-FactorAuthentication andPassword PoliciesAva for Lawyers

Key takeaways

  • Only 54% of lawyers in the 2023 ABA survey said two-factor authentication was available at their firm, and only 33% used a password manager.
  • Current NIST guidance favors long passwords over complex ones and says not to force periodic changes without evidence of compromise.
  • Phishing-resistant MFA, such as security keys and passkeys, is the strongest option; any MFA is better than none.
  • Roll out MFA to partners and anyone who handles money first, with a written policy and a short exceptions process.

Why this policy comes first

Most account takeovers at law firms begin with a password that was guessed, reused or typed into a fake login page. Once inside a mailbox, an attacker can read privileged communications, redirect payments and reach every system that sends password resets to that address. A second sign-in factor makes the stolen password far less useful on its own.

Adoption is still patchy. In the ABA's 2023 Legal Technology Survey, 70% of respondents said their firm used mandatory passwords, but only 54% said two-factor authentication was available and only 33% used a password management tool[1]. The ABA report pointed out that MFA rarely costs anything to turn on, and called the low numbers a mystery[1].

Account security tools at law firms (2023)Share of ABA Legal Technology Survey respondents
Account security tools at law firms (2023)Column chart. Mandatory passwords: 70%; Two-factor authentication available: 54%; Password manager used: 33%.0%20%40%60%80%Mandatory passwords: 70%70%Mandatory passwordsTwo-factor authentication available: 54%54%Two-factor authenticationavailablePassword manager used: 33%33%Password manager usedAccount security tools at law firms (2023)Column chart. Mandatory passwords: 70%; Two-factor authentication available: 54%; Password manager used: 33%.Mandatory passwordsMandatory passwords: 70%70%Two-factor authentication availableTwo-factor authentication available: 54%54%Password manager usedPassword manager used: 33%33%

Source: American Bar Association, Law Practice Division, 2023[1]

Show the data
ItemValue
Mandatory passwords70%
Two-factor authentication available54%
Password manager used33%

Small firms have the most to gain. With 71.8% of US law offices employing fewer than five people[2], one compromised account is often a partner's, and it often holds everything.

What current password guidance actually says

Many firm password rules still date from guidance that has since been reversed. The National Institute of Standards and Technology's current digital identity guidelines, SP 800-63B-4, set out a different approach[3]:

  • Length over complexity. Passwords used as the only factor must be at least 15 characters; passwords used as part of multi-factor sign-in must be at least 8[3].
  • Allow long passwords. Systems should permit a maximum of at least 64 characters, including spaces, so people can use passphrases[3].
  • No composition rules. Systems should not require mixtures of character types, such as one capital, one number and one symbol[3].
  • No forced periodic changes. Systems should not require users to change passwords on a schedule, but must force a change when there is evidence of compromise[3].
  • Block the obvious. Systems should reject passwords that appear on lists of commonly used, expected or compromised values[3].

The reasoning is practical. Composition rules and forced changes push people toward predictable patterns, like a season and a year with an exclamation mark, and toward writing passwords down. A long, unique passphrase stored in a password manager is both stronger and easier to live with.

Choosing MFA methods

CISA lists the common forms of MFA as text or voice messages, app-based codes or prompts, phishing-resistant methods, and fingerprint or face scans[4]. It is blunt that not all methods give the same protection: phishing-resistant MFA is the standard to aim for, but any MFA is better than none[4]. It names FIDO/WebAuthn as the only widely available phishing-resistant method, because it blocks the login when a user is tricked into visiting a fake site[4].

MFA methods compared. The ranking follows CISA's guidance that FIDO/WebAuthn is the only widely available phishing-resistant method.
MethodStrengthWhere it fits at a firm
Security key or passkey (FIDO/WebAuthn)Strongest; resists phishingPartners, administrators, anyone who approves payments
Authenticator app with number matchingStrong; can be phished by a convincing fake pageDefault for all staff
Authenticator app with simple approve promptModerate; vulnerable to repeated-prompt fatigue attacksAcceptable while moving to number matching
Text or voice codeWeakest MFA; exposed to SIM swaps and interceptionFallback only, and never for admin accounts

Turn off text-message fallback once stronger methods are enrolled. An attacker will always pick the weakest option an account still allows.

Setting up the password manager

A password manager is what makes the NIST approach workable. Nobody can remember dozens of long, unique passwords, and the alternative is reuse. For a firm, a few setup choices matter more than the brand:

  • Choose a business plan with an admin console, so the firm can see who is enrolled, recover access and remove a departing user's vault access in one step.
  • Create shared vaults by role, such as billing, IT and court e-filing, rather than sharing individual passwords by email or chat.
  • Protect each vault with a long master passphrase and MFA. The master passphrase is the one password people must memorize, so make it a sentence they will not forget.
  • Turn on breach and reuse alerts, and have each person fix flagged passwords for firm systems in their first week.
  • Keep personal and firm vaults separate where the product allows it, so staff do not mix their own accounts with client systems.

Budget an hour per person for setup in the first month. Most of that time goes into finding old logins people forgot they had, which is itself a useful cleanup.

A sample policy

Keep the written policy to one page. People follow rules they can remember. A version a small firm can adapt:

  1. Every firm account that can reach client information, firm money or email must use multi-factor sign-in. No exceptions without written approval from the managing partner.
  2. Administrators, partners and anyone who sends or approves payments must use a security key or passkey where the service supports it.
  3. Each person uses the firm password manager. Passwords for firm systems must be unique and at least 15 characters, or at least 8 if the account uses MFA.
  4. Passwords are not changed on a schedule. Change one immediately if you suspect it was exposed, typed into a suspicious page or shared.
  5. Never approve a sign-in prompt you did not start. Report unexpected prompts to the office manager the same day.
  6. Shared logins are not allowed. If a service has only one login, record who holds it and store it in a shared vault in the password manager.
  7. When someone leaves, the office manager removes their access to every system on their last day.

Rolling it out without a revolt

  1. Inventory accounts

    List every system with a login: email, practice management, document storage, banking, court e-filing, the phone system, the website host and social media. Note which support MFA and which support security keys.

  2. Start with the riskiest accounts

    Enroll partners, the bookkeeper and administrators first. Their accounts can move money and reset everyone else's.

  3. Issue the password manager

    Set it up for each person in a short one-on-one session, migrate their firm passwords, and protect the vault itself with MFA.

  4. Enroll staff in one sitting

    Block an hour, have phones ready and enroll everyone together, with the IT contact in the room. Register a backup method for each person so a lost phone is not a lockout.

  5. Enforce at the admin level

    Once enrolled, switch the setting from optional to required in each admin console, and turn off weaker fallbacks.

  6. Check monthly

    Review the enrollment report and the list of active users each month. Remove anyone who has left.

Explain the reason in a single sentence when you announce it: a stolen password can no longer open client files or redirect a settlement. People accept extra steps when they understand what they protect.

Remote work and shared devices

Home working raises the stakes. In 2025, 35% of employed Americans did some or all of their work at home on the days they worked[5]. Home computers may be shared with family members, and home networks are rarely managed. Require MFA for every remote connection to firm systems, never let browsers on shared devices save firm passwords, and sign out of web sessions at the end of each day. CISA's own list of where to turn on MFA starts with email accounts and financial services[4], which are exactly the systems a remote worker reaches from home.

Example: an exception that should not have been

Example (fictional): a six-person firm turns on MFA for everyone except a senior partner who travels and finds the prompts annoying. Months later, that partner's password, reused on a shopping site, appears in a breach. An attacker signs in to the partner's mailbox, which has no second factor, and sends a client new wiring instructions. The firm catches it only because the client calls to check. Afterward, the firm issues the partner a security key that works with a tap, removes the exception and rewrites the policy so exceptions expire after 30 days unless renewed in writing.

How this fits the rest of your security program

Account security is the base layer. It supports the reasonable-efforts duty discussed in our cloud computing ethics guide, reduces the odds of the incidents covered by the data breach response plan, and is one of the first things a cyber insurer asks about, as explained in cyber insurance for law firms. It also limits how far ransomware can spread, covered in ransomware protection and backups.

Frequently asked questions

Should law firms still require password changes every 90 days?

Current NIST guidance says not to force periodic changes. Require a change when there is evidence a password was compromised, and focus instead on length, uniqueness and MFA.

Is text-message MFA good enough for a law firm?

It is better than no MFA but is the weakest option. Use an authenticator app for most staff and security keys or passkeys for partners, administrators and anyone who handles payments.

What if a vendor does not support MFA?

Record it as a risk, use a long unique password stored in the password manager, limit what data the service holds, and press the vendor or plan to replace it.

How do we handle a lost phone used for MFA?

Register a backup method for each person during enrollment, such as a second key or recovery codes stored securely, so the office manager can restore access without disabling MFA.

References

  1. American Bar Association, Law Practice Division (2023). 2023 Cybersecurity TechReport (archived copy) (opens in a new tab) โ†‘

  2. U.S. Census Bureau (2023). County Business Patterns 2023: U.S. detail file (cbp23us) (opens in a new tab) โ†‘

  3. National Institute of Standards and Technology (2025). NIST Special Publication 800-63B-4: Digital Identity Guidelines, Authentication and Authenticator Management (opens in a new tab) โ†‘

  4. Cybersecurity and Infrastructure Security Agency (2026). More than a Password (opens in a new tab) โ†‘

  5. U.S. Bureau of Labor Statistics (2025). American Time Use Survey - 2025 Results (opens in a new tab) โ†‘

Book a demo

See Ava handle your calls.

Book a short demo. Weโ€™ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo