Data protection and cyber security

Multi-factor authentication and password policy

Rolling out multi-factor authentication and a sensible password policy at a law firm without disrupting fee earners: methods, phasing and exceptions.

Ava research teamPublished 7 min read

On this page
  1. Why this comes before almost everything else
  2. Choosing the second factor
  3. What to protect, in order
  4. A rollout that does not stop the fee earning
  5. Answering the objections
  6. Measuring whether it worked
  7. A password policy people will follow
  8. Access control: who can get in, and to what
  9. Leavers, absences and lost phones
  10. A worked example
  11. Frequently asked questions
  12. References

Key takeaways

  • Only 47% of businesses use any form of two-factor authentication, though the share of micro businesses requiring it rose from 35% to 43% in a year[1].
  • Protect email first, then remote access, case management, banking and every administrator account.
  • Use authenticator apps with number matching or passkeys where possible; text message codes are better than nothing but weaker.
  • For passwords, the NCSC recommends three random words or a password manager[2]; ban reuse and shared logins.
  • Plan for court days, lost phones and help desk resets, or fee earners will find workarounds.

Why this comes before almost everything else

Most successful attacks on law firms begin with a password the attacker should never have been able to use: typed into a fake sign-in page, reused from a breached website or guessed because it was the firm's name and the year. Phishing featured in 88% of cases where businesses identified a breach[1], and its aim is usually exactly that password. Multi-factor authentication makes the stolen password useless on its own.

Adoption is still patchy. The Cyber Security Breaches Survey 2025/2026 found that 47% of businesses had any two-factor authentication for networks or applications, although the share of micro businesses requiring it rose from 35% to 43% in a year[1]. In the SRA's thematic review, 25 of the 40 firms visited confirmed that two-factor authentication was required for many day-to-day activities[3], which means a substantial minority were not using it. In a sector where 78% of enterprises employ four people or fewer[4], one compromised mailbox can be a large share of the firm.

Micro businesses requiring two-factor authenticationCyber Security Breaches Survey 2025/2026.
Micro businesses requiring two-factor authenticationComparison. 2024/25: 35%; 2025/26: 43%.35%2024/252024/25: 35%43%2025/262025/26: 43%Micro businesses requiring two-factor authenticationComparison. 2024/25: 35%; 2025/26: 43%.35%2024/252024/25: 35%43%2025/262025/26: 43%

Source: GOV.UK (DSIT and Home Office), 2026[1]

Show the data
ItemValue
2024/2535%
2025/2643%

Choosing the second factor

Common second factors, from weakest to strongest.
MethodStrengthNotes for a law firm
Text message codeBasicBetter than nothing; vulnerable to SIM swap and to users typing the code into fake pages
Authenticator app push without number matchingModerateEasy to use, but users can be tricked into approving a prompt they did not start
Authenticator app with number matchingGoodUser must type the number shown on screen, which defeats most prompt fatigue attacks
Authenticator app codeGoodWorks offline; still phishable if typed into a fake page
Passkeys or hardware security keysStrongestResistant to phishing because they only work on the genuine site; ideal for partners, accounts and IT admins

A practical mix for most firms is an authenticator app with number matching for everyone, and passkeys or hardware keys for the accounts that can move money or change systems: the COFA, the accounts team, partners with banking authority and anyone with administrator rights.

What to protect, in order

  1. Email, including shared mailboxes and the accounts of people on long-term leave.
  2. Remote access to the office network and any remote desktop service.
  3. Online banking and client account payment systems.
  4. Case and document management, especially if accessible from outside the office.
  5. Administrator accounts, and your IT provider's own access to your systems.
  6. Cloud storage, e-signature and identity verification portals.
  7. HM Land Registry, court and other professional portals that support it.
  8. Payroll, HR and the firm's website and social media accounts.

A rollout that does not stop the fee earning

  1. Announce the why

    A short message from the managing partner explaining that stolen passwords are the main route into law firms, and that the change protects clients and the firm's insurance.

  2. Pilot with a willing team

    Start with a small group, including a partner and a secretary, for a week. Fix the friction they find before rolling out.

  3. Enrol in person

    Book short slots for each person to set up the app with IT on hand. Register a backup method at the same time.

  4. Enforce in stages

    Turn on enforcement for email first, then remote access and other systems over the following weeks, avoiding month end and known busy periods.

  5. Handle exceptions deliberately

    Staff without a suitable phone get a hardware key. Shared devices in reception get individual sign-ins. Nobody is exempt by seniority.

  6. Review after a month

    Check enrolment reports for gaps, ask for feedback, and tighten settings such as number matching once everyone is comfortable.

Conditional access settings reduce friction further. Trusted firm devices in the office can be asked for a second factor less often, while sign-ins from new devices or countries are always challenged. That keeps the experience smooth for daily work and strict where attacks actually come from.

Answering the objections

Every rollout meets the same handful of objections. Having a short answer ready for each keeps the project moving without a partner-level argument.

  • I do not have time for this. Setting up the app takes a few minutes once; after that, trusted devices are challenged only occasionally. A compromised mailbox costs days.
  • I am in court without a signal. Authenticator codes and hardware keys work offline, and trusted laptops need fewer prompts.
  • I do not want work apps on my personal phone. That is fine; you can have a hardware key instead.
  • Our IT provider says we are secure already. Ask them to show the enrolment report. If any account can sign in with a password alone, the firm is exposed.
  • Clients will not like it. Multi-factor authentication for staff does not affect clients at all; client portals that use one-time codes are now familiar from online banking.

Measuring whether it worked

Ask your IT provider for a simple monthly report: the percentage of accounts enrolled, any accounts excluded and why, blocked sign-in attempts, and second-factor resets carried out. Aim for every human account enrolled and every exclusion justified in writing. Review the report at partners' meetings for the first three months, then quarterly. When your insurer's renewal questionnaire asks whether multi-factor authentication is enforced for all users and remote access, you want to be able to answer yes with evidence.

A password policy people will follow

Complicated rules produce predictable passwords written on sticky notes. The NCSC recommends combining three random words to create a password that is long enough and strong enough, or using a password manager that creates and remembers strong passwords[2]. A short policy built on that advice might say:

  • Use three random words, or a password manager, for every work account.
  • Never reuse a work password anywhere else, and never use your email password for any other system.
  • Use the firm's password manager for all other work accounts; do not store passwords in browsers on personal devices.
  • Never share a password or approve a sign-in prompt you did not start. If you do by mistake, tell IT straight away.
  • Change a password immediately if you suspect it has been seen or entered on a fake page; otherwise there is no need for routine forced changes.
  • Administrators use a separate admin account for admin tasks only.

Most businesses already have a password policy, 74% according to the breaches survey[1]. The difference is whether it reflects how people actually work and whether multi-factor authentication sits behind it.

Access control: who can get in, and to what

  • Give every person their own account; retire shared reception and secretarial logins.
  • Grant access by team and role, with sensitive matters restricted further.
  • Have a joiners, movers and leavers checklist so access is added, changed and removed on the right day.
  • Review who has administrator rights and remote access every quarter.
  • Make sure your IT provider's engineers use named accounts with multi-factor authentication, not a shared support login.

Attackers increasingly target the help desk rather than the user. Any request to reset a password or a second factor must be verified, for example by calling the person back on their recorded number or confirming in person, before the reset is made.

Leavers, absences and lost phones

The weak moments in any access system are transitions. When someone leaves, disable their account and remove their second-factor registrations on their last day, recover any hardware key, and convert their mailbox to a monitored shared mailbox rather than leaving it open. When someone starts long-term leave, consider suspending remote access until they return. When a phone is lost, the user should report it the same day; IT removes the old registration, checks recent sign-ins and enrols the replacement only after verifying the person by a call to a known number or in person. Write these three procedures down, because they are usually handled under time pressure by whoever happens to be available.

A worked example

Example: a fictional 20-person firm rolls out multi-factor authentication over four weeks. Two partners object that they are often in court without signal. IT gives them hardware keys that work without a network connection and sets their laptops as trusted devices. A part-time bookkeeper without a smartphone also receives a key. After the rollout, the firm's IT provider reports two blocked sign-in attempts from overseas against a fee earner whose password had appeared in a third-party breach. Neither got in.

Client trust is the quiet return on this work: 94% of consumers are confident their legal provider will keep their money safe[5]. Next, look at secure email and file sharing, hybrid working security and, if the worst happens, our ransomware response plan.

Frequently asked questions

Is text message authentication good enough?

It is much better than a password alone, but it can be defeated by SIM swap fraud and by users typing codes into fake pages. Use an authenticator app with number matching, or passkeys, where your systems support them.

Can staff use their personal phones for the authenticator app?

Many firms allow it, since the app holds no client data. Offer a hardware key to anyone who prefers not to, and make the policy clear.

Should we force password changes every 90 days?

Routine forced changes tend to produce weaker, predictable passwords. Require strong, unique passwords, use multi-factor authentication, and change passwords when there is any sign of compromise.

What if a partner refuses to use MFA?

Make it a firm-wide rule with no exemptions by seniority. Senior accounts are the most attractive targets, and insurers increasingly ask whether MFA is enforced for everyone.

References

  1. GOV.UK (DSIT and Home Office) (2026). Cyber security breaches survey 2025/2026 (opens in a new tab) ↑

  2. National Cyber Security Centre (2025). Top tips for staying secure online: three random words (opens in a new tab) ↑

  3. Solicitors Regulation Authority (2020). Cyber security: a thematic review (opens in a new tab) ↑

  4. Office for National Statistics (2026). UK business: activity, size and location, 2026 (legal activities by employment size) (opens in a new tab) ↑

  5. Legal Services Consumer Panel (2026). How consumers are choosing legal services (Tracker Survey 2026) (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