It’s March 14th. Your senior preparer can’t get the code to log into the tax software. The phone’s dead, the queue’s full, and somebody says, “Can’t we just turn MFA off until April?”
Short answer: no. Turning it off isn’t a shortcut. It’s a compliance violation.
This guide covers what the rule actually requires, which MFA methods hold up against today’s attacks, and how to set it up so it doesn’t wreck your busiest weeks. It’s written for CPA firm owners, partners, and office managers. No IT degree needed.
Key takeaways
- MFA is a federal requirement for tax and CPA firms of every size: FTC Safeguards Rule 16 CFR 314.4(c)(5) requires it for anyone accessing customer information.
- MFA means at least two different factor types: something you know, something you have, or something you are.
- Passkeys and FIDO2 security keys are the strongest options. Upgrade partners and anyone who transmits returns or moves money first.
- Enforce MFA on tax software, email, client portals, remote access, QuickBooks, cloud storage, IRS e-Services, and banking and payroll portals.
- Document which systems enforce MFA and which methods are approved in your WISP.
Is MFA required for tax and CPA firms?
Yes. If your firm prepares returns or handles client financial data, MFA is a federal requirement.
The FTC Safeguards Rule treats tax and accounting firms as financial institutions, regardless of size. Section 16 CFR 314.4(c)(5) requires MFA for any individual accessing any information system that holds customer information. The IRS and its Security Summit partners have said the same thing publicly: failing to use MFA violates the FTC’s safeguards rules.
There’s one narrow exception. Your firm’s Qualified Individual can approve a “reasonably equivalent or more secure” access control instead, but it has to be in writing. “We were busy” doesn’t count.
A few points people miss:
- It covers in-office staff too. Not just remote logins.
- Small firms aren’t off the hook. Firms with data on fewer than 5,000 consumers skip a few provisions (like the written incident response plan and annual board report), but MFA, encryption, access controls and staff training still apply.
- MFA lives inside your WISP. Your written information security plan is where you prove MFA is in place. More on that below.
What counts as MFA (and what doesn’t)
Under the rule, MFA means at least two of three factor types:
- Something you know (password, PIN)
- Something you have (phone app, security key, token)
- Something you are (fingerprint, face)
A password plus a security question? That’s two “know” factors. It doesn’t qualify.
MFA methods ranked for CPA firms
Not all MFA is equal. Attackers who target tax firms have learned how to beat the weaker types.
| Method | Protection level | Best for | Watch out for |
|---|---|---|---|
| FIDO2 security key / passkey | Highest (phishing-resistant) | Partners, admins, anyone with e-file or banking access | Keep a registered backup key |
| Authenticator app with number matching | Strong | All staff | Needs a recovery plan for lost phones |
| Authenticator app, plain push (approve/deny) | Moderate | Better than SMS | Push bombing |
| SMS or voice code | Weak | Last resort only | SIM swaps, phishing proxies |
| Email code | Weak | Avoid for client-data systems | Shares the inbox attackers already target |
CISA calls passkeys and FIDO2 keys the gold standard. If you only upgrade a few people this year, start with partners and whoever can transmit returns or move money.
How attackers get around weak MFA
MFA stops most password-only attacks. But three tricks keep showing up at accounting firms:
- Push bombing. The attacker has your password and spams approval prompts, often late at night, until someone taps “Approve” just to make it stop.
- Phishing proxies. A fake login page passes your password and one-time code to the real site in real time. SMS and app codes don’t stop this. Security keys do.
- Help desk impersonation. Someone calls pretending to be a staff member with a “new phone” and asks for an MFA reset.
These often start with a phishing email or a fake “fix this error” prompt, the same playbook behind ClickFix attacks targeting CPA firms. Number matching, conditional access, and a strict identity check before any reset close most of these gaps. That’s the kind of layered setup covered under TechFiscal’s cybersecurity services for CPA firms.
Where your firm needs MFA turned on
The rule says “any information system” with customer data. For a typical CPA firm, that list is longer than people think:
- Tax software (Drake, Lacerte, UltraTax, ProSeries and others)
- Email, especially Microsoft 365 or Google Workspace admin accounts
- Client portals and document management
- Remote desktop, VPN, and hosted tax software environments
- Accounting apps like QuickBooks
- Cloud storage and backups
- e-Services and other IRS-facing accounts
- Banking and payroll portals
If you run Drake in a hosted environment or Lacerte on a cloud server, you may need MFA at two layers: the hosting login and the software itself. Check both.
The lost-phone problem (and how to stop it killing tax season)
This is why most firms want MFA gone. One lost phone in March can lock a preparer out for a day or more.
Fix it before it happens:
- Keep an inventory of every MFA-protected system and who has access.
- Register two methods per person. An authenticator app plus a security key, for example.
- Store recovery codes securely, not in the same mailbox the attacker would target.
- Write a reset procedure. Verify identity through a known channel (call back on the number in your HR file, or confirm in person) before resetting anyone’s MFA.
- Know who handles resets during season. Your IT provider should be able to do this fast. That’s where managed IT support for CPA firms pays off: someone on call who already knows your systems.
How to document MFA in your WISP
Auditors, insurers and the IRS want proof, not promises. Your WISP should state:
- Which systems have MFA enforced
- Which MFA methods are approved (and for which roles)
- Any exceptions, with the Qualified Individual’s written approval and the compensating control
- Your reset and lost-device procedure
- How often you review MFA coverage (at least yearly)
If you don’t have a WISP yet, start with TechFiscal’s free WISP template guide, then fill in the MFA section with the points above.
7 common MFA mistakes at tax firms
- Turning MFA off “just for tax season”
- Protecting the tax software but not email
- Using SMS for partners and admins
- Shared logins, so MFA goes to one person’s phone
- No backup method, so one lost phone means a lockout
- Resetting MFA over the phone without verifying identity
- Never writing any of it down in the WISP
Quick MFA checklist for your firm
- MFA on tax software, email, portals, remote access and banking
- Number matching on for all push-based authenticator apps
- Security keys or passkeys for partners and admins
- Two registered MFA methods per user
- Written reset procedure with identity verification
- MFA section in your WISP, reviewed yearly
- Staff trained to deny and report unexpected prompts
Related reading: what to do when staff put client data in ChatGPT.
FAQs
Is MFA required for tax preparers by law? Yes. The FTC Safeguards Rule (16 CFR 314.4(c)(5)) requires MFA for anyone accessing systems with customer information. The IRS treats it as a federal requirement for tax professionals.
Does a solo tax preparer need MFA? Yes. The rule applies regardless of firm size. Small firms are exempt from a few provisions, but not MFA.
Can I turn off MFA in my tax software during busy season? No. The IRS has said that not using MFA violates the FTC Safeguards Rule. Fix the friction with backup methods and a fast reset process instead.
Is SMS text-code MFA good enough? It technically counts as a second factor, but it’s the weakest option. Use an authenticator app with number matching for staff, and security keys or passkeys for partners and admins.
What is phishing-resistant MFA? MFA that can’t be relayed through a fake login page, like FIDO2 security keys and passkeys. CISA considers it the strongest option available.
What happens if our firm has a breach? If unencrypted data on 500 or more consumers is exposed, you must notify the FTC within 30 days of discovery. You should also report data theft to your IRS stakeholder liaison.
Where should MFA be documented? In your WISP: which systems use it, which methods, any approved exceptions, and your reset procedure.
Not sure where your firm stands?
A common pattern: MFA is on in the tax software, and missing on email, portals and remote access. TechFiscal builds IT and security for CPA and accounting firms, and we’ll map where MFA is missing before your next tax season starts.
Get a free IT and compliance assessment
This article is general information, not legal advice. Confirm current requirements with the FTC, the IRS, or your compliance advisor.
