Home · Guides

Multi-factor authentication requirement for tax preparers: FTC Safeguards Rule and IRS guidance (2026)

Under the FTC Safeguards Rule, a tax office must use multi-factor authentication (MFA) for anyone who can reach an information system that holds — or connects to a system that holds — customer information. This page restates 16 CFR 314.4(c)(5) in plain language, explains who it applies to, and collects the practical setup steps the IRS and the Security Summit recommend for small offices. It is not legal advice and is not an IRS or FTC publication.

What 16 CFR 314.4(c)(5) requires

The Safeguards Rule’s list of required safeguards includes this sentence, quoted from the current official text:

Implement multi-factor authentication for any individual accessing any information system, unless your Qualified Individual has approved in writing the use of reasonably equivalent or more secure access controls.

That is 16 CFR 314.4(c)(5). Two definitions in 16 CFR 314.2 control the scope:

“Any individual” is broader than the owner and the tax preparers. An authorized user under 16 CFR 314.2(a) includes any employee, contractor, agent, customer, or other person authorized to access your information systems or data. If a seasonal staff member, an IT contractor, or a client portal login can reach a system in scope, MFA is in play unless a written, reasonably equivalent control has been approved.

Who this applies to

IRS Publication 5708 states the coverage rule directly: under the Gramm-Leach-Bliley Act and the Safeguards Rule, “tax and accounting professionals are considered financial institutions, regardless of size,” and a written information security plan (WISP) is required. Publication 5708 then lists MFA, in the same words as 314.4(c)(5), among the elements the FTC requires as part of that plan.

Firm size does not turn MFA off. 16 CFR 314.6 is one sentence. It excuses only § 314.4(b)(1), (d)(2), (h), and (i) for financial institutions that maintain customer information concerning fewer than 5,000 consumers — the written risk-assessment detail, certain annual testing, the written incident-response plan, and the annual report to the board or a senior officer. MFA lives in § 314.4(c)(5) and is not on that list. The IRS has said the same thing in two places you can hand to a colleague: Publication 4557 says MFA “is required for all companies regardless of size,” and the September 4, 2026 Security Summit release (IR-2026-106) says “the MFA requirement applies to tax preparation firms regardless of size.”

The only written exception

The rule allows one off-ramp: your Qualified Individual — the person designated under 16 CFR 314.4(a) to oversee and enforce the information security program — may approve, in writing, access controls that are reasonably equivalent or more secure than MFA. The text does not create an exception for inconvenience, cost, a vendor that has not turned MFA on, or a one-person practice.

If you rely on that approval, keep it with the WISP, name the system and the users, describe the replacement controls, and revisit it when the system or the vendor changes. A PreparerGuard WISP is a drafting kit, not a decision that a given exception is defensible; that judgment stays with the Qualified Individual.

Practical setup for a small tax office

The rule is system-based, not product-based. For a typical office, the IRS and Security Summit point to the same handful of places. IR-2026-106’s MFA best-practice list is: use MFA across all services and data access points; review current methods from time to time; offer authentication options that users can actually complete; enable MFA in tax software, cloud storage, email, and other services that contain sensitive client information; and use individual accounts — never shared usernames or passwords.

Email

Turn MFA on for every mailbox that can send or receive client information, including the owner’s account and any staff mailboxes. Publication 4557 tells tax professionals to use the most secure MFA option the product offers, not only for tax software but also for “email accounts and storage provider accounts.” Its basic example is a username and password plus a security code sent as a text to a mobile phone. If your provider also offers an authenticator app or a hardware security key, Publication 4557’s “most secure option” and “highest multifactor authentication available” language is the reason to prefer that over a weaker method the product still supports.

Give each person their own mailbox and credentials. IR-2026-106 is explicit: use individual accounts and never share usernames or passwords. Publication 4557 says the same for passwords: do not share them among employees; each person with access to client accounts should have a unique password.

Tax software and IRS accounts

Publication 4557 notes that tax software products for both taxpayers and tax professionals now offer MFA, and it tells you to turn on the most secure option available. Do this in the vendor’s security or user-management settings, with a unique login for each preparer and staff member who can open a client return. The same publication’s glossary explains that IRS e-Services is protected by IRS Secure Access, a two-factor process that asks returning users for their credentials plus a security code sent to a mobile phone — and again tells tax professionals to use the highest MFA available.

Cloud storage and file sharing

IR-2026-106 includes cloud storage alongside tax software and email. Publication 4557’s information-systems checklist adds a concrete caution: if you use a cloud storage service, use a strong password and MFA options, and beware of thieves posing as the provider. Treat any portal, backup service, or shared drive that holds returns, organizer files, or ID images as in scope.

Remote access, office computers, and the network

IR-2026-106 says tax professionals should use MFA to secure client information on computers and networks and to access client information stored in tax preparation software. For people who work from home or from another office, Publication 4557 is more specific: “Use of multi-factor authentication (discussed earlier) and a secure Virtual Private Network (VPN) should be minimum standards for remote access to the firm’s office network.” A VPN, in that publication’s words, “provides a secure, encrypted tunnel to transmit data between a teleworking employee and the company network.”

The 2026 Security Summit “Security Six” list, in IR-2026-85 (August 4, 2026), puts the same two controls side by side: MFA, which it identifies as a requirement under the Safeguards Rule, and a VPN for remote users. Publication 4557 also advises against using public Wi-Fi — for example at a café or airport — to access business email or sensitive documents.

What the IRS Security Summit and Publication 4557 add

The Safeguards Rule is the legal requirement. The IRS materials are educational, but they are the guidance most tax offices are actually handed:

Write the choices you actually made — which systems have MFA, which method you use, who is enrolled, and any written exception — into the office WISP so the plan matches the office you run. Publication 5708 includes MFA among the required plan elements; our FTC Safeguards Rule checklist places that element next to the rest of § 314.4.

Two practical next steps. MFA will not help if someone can impersonate the firm’s mail domain and ask a client for a document or a “refund” wiring. The in-browser check reads public MX, SPF, DMARC, and common DKIM selectors only; it does not log into your mail. Then record MFA, email authentication, and the rest of the Safeguards Rule items in a written WISP. A PreparerGuard WISP is a paid drafting kit based on Publication 5708; you still have to turn the controls on and review the draft. It is not a certification of compliance.

Check my email domain   Build my WISP   Download a sample WISP

Sources (primary, retrieved 18 November 2026):
  1. 16 CFR 314.4(c)(5), Elements — eCFR; official 2026 CFR text — GovInfo PDF, 16 CFR part 314
  2. 16 CFR 314.2(a), (j), and (k), definitions of authorized user, information system, and multi-factor authentication — eCFR
  3. 16 CFR 314.6, Exceptions — eCFR
  4. IRS Publication 4557, Safeguarding Taxpayer Data: A Guide for Your Business (Rev. 5-2024; footer also Rev. 6-2024) — irs.gov/pub/irs-pdf/p4557.pdf
  5. IRS Publication 5708, Creating a Written Information Security Plan for your Tax and Accounting Practice — irs.gov/pub/irs-pdf/p5708.pdf
  6. IRS, Security Summit: Strengthen defenses against tax identity theft, IR-2026-106 (September 4, 2026) — irs.gov
  7. IRS, Security Summit warns tax pros to watch out for phishing emails and other attacks, IR-2026-85 (August 4, 2026), Security Six — irs.gov

Related: FTC Safeguards Rule checklist · Publication 4557 checklist · WISP template and Form W-12 line 11 · Free DMARC / spoofing check

Disclaimer. PreparerGuard provides document-drafting tools and passive, public-DNS email checks. It is not legal, tax, or professional advice, is not affiliated with or endorsed by the IRS or the FTC, and does not guarantee compliance or security. “WISP” refers to the written information security plan described in IRS Publication 5708. You must review, adapt, and adopt any plan yourself.