FTC Safeguards Rule and the WISP
MFA requirements under the FTC Safeguards Rule
The Safeguards Rule MFA requirement, 16 CFR 314.4(c)(5), says to use multi-factor authentication for any individual accessing any information system, unless your qualified individual approves in writing a control that is reasonably equivalent or more secure. "Any individual" means staff, contractors and clients alike. "Any information system" means anything that holds client information or connects to something that does, which in a tax office includes email, tax software, the client portal, cloud storage, remote access and the office computers. The requirement has applied since June 9, 2023, and the exemption for firms with fewer than 5,000 consumers doesn't touch it.
Multi-factor authentication, or MFA, means proving who you are with two different kinds of evidence, such as a password and a code from your phone. The full guide to the FTC Safeguards Rule covers the rest of the rule. This post covers the MFA paragraph, the people and systems it reaches in a small office, the written exception and the dates.
What 314.4(c)(5) says
The rule's list of safeguards in 16 CFR 314.4(c) includes this one, word for word:
(5) 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 one requirement and one exception. The paragraph has no size threshold and no carve-out for the office network. The small business exemption in 16 CFR 314.6 excuses four other parts of 314.4, (b)(1), (d)(2), (h) and (i), and leaves (c)(5) in place.
What counts as multi-factor authentication
The definition is in 16 CFR 314.2(k):
(k) Multi-factor authentication means authentication through verification of at least two of the following types of authentication factors: (1) Knowledge factors, such as a password; (2) Possession factors, such as a token; or (3) Inherence factors, such as biometric characteristics.
The word that matters is "types." A password plus a security question is two things you know, which is one type, so by the definition's own terms it isn't MFA. A password plus a code on your phone, an app approval or a security key is two types. So is a fingerprint plus a device.
The definition names no product. The FTC's December 2021 notice adopting it says it "does not require any particular technology or technique" (86 FR 70290), so a text message code qualifies, though some methods resist phishing better than others.
Single sign-on, where one sign-in opens several programs, is fine. A footnote on the same page says so, as long as everyone who reaches each program went through MFA first.
Who "any individual" covers
The rule's definitions don't define "individual," but they define who is allowed in. Under 16 CFR 314.2(a), an authorized user is "any employee, contractor, agent, customer, or other person that is authorized to access any of your information systems or data." The 2021 notice says the final rule requires MFA whenever any individual, "employee, customer or otherwise," accesses an information system (86 FR 70290).
In a small tax office, that list usually includes:
- the owner and partners, and any administrator account they use
- every preparer, seasonal staff included
- the office manager and the front desk
- an outside IT person or company with remote access
- contract bookkeepers or other outside staff who sign in to your systems
- clients who sign in to your portal to upload documents or download returns
Clients surprise most people. One commenter on the rule said requiring MFA when a customer reaches their information from outside "could create problems for some institutions" (86 FR 70289). The Commission still agreed MFA is justified "when external users, such as customers, and internal users, such as employees," access an information system (86 FR 70290). If your portal comes from a vendor, check whether it can require MFA for clients, and turn it on.
Seasonal staff are the other common gap. The post on seasonal preparer accounts covers setting up their MFA on day one.
What "any information system" covers in a tax office
The definition in 314.2(j) is long. Its core is "a discrete set of electronic information resources organized for the collection, processing, maintenance, use, sharing, dissemination or disposition of electronic information containing customer information or connected to a system containing customer information." It goes on to name phone systems and building controls when they hold customer information or connect to a system that does.
The phrase "or connected to a system containing customer information" is what makes the list long. The proposed rule of April 2019 would have required MFA for anyone accessing customer information or "internal networks that contain customer information." Some commenters asked the FTC to drop MFA for access from inside the office network. It declined, and changed the wording to "any information system" to clear up the confusion (86 FR 70289 to 70290).
| System | Why it counts | Who needs MFA on it |
|---|---|---|
| Email (Microsoft 365, Google Workspace) | Returns and documents travel as attachments | Every mailbox user and every admin account |
| Tax software | Holds the returns | Every preparer sign-in |
| Client portal and cloud storage | Holds uploaded documents | Staff, and clients who sign in |
| Remote access to the office | Reaches the computers and server that hold client files | Everyone who connects, including your IT provider |
| Office computers | Hold client files and connect to everything above | Whoever signs in at the keyboard |
MFA on a mailbox keeps out someone who has the password. It does nothing about mail that only pretends to come from your address, which the guide to email security for small businesses covers.
The office computers are the hardest row. Read literally, signing in to a Windows desktop that holds client files is accessing an information system. Microsoft describes Windows Hello for Business as two-factor authentication, a key protected by the computer's security chip plus a PIN or fingerprint, which lines up with the rule's possession and knowledge or inherence types. It needs Windows Pro or higher and accounts in Microsoft Entra ID or Active Directory. Where that isn't in place, this is the row most likely to need the written exception below.
Remote access names in our lead data
Remote access is easy to leave off the list once it's set up. On October 16, 2026 we looked up, through Cloudflare's public DNS, twelve host names commonly used for remote access (such as remote, vpn, rds, rdweb, sslvpn, gateway and citrix) and eight used for client portals (such as portal, clients, secure and files) under the website domains of the 316 small tax and accounting firms in our research. These are firms in Alabama, Tennessee and Georgia with 3 to 12 preparers and their own website, drawn from the IRS public list of PTIN holders. We also looked up a made-up name under each domain and set aside the 46 that answered for it, since those answer for any name at all, plus 1 domain we couldn't read.
Of the remaining 269 domains, 35, about 1 in 8, had at least one remote access name pointing to an internet address other than the firm's website. The most common names were remote (22 domains) and vpn (11). Another 14 had a portal-style name.
We only looked up names and connected to nothing. A name doesn't prove a service is running, and remote access can work with no name at all. Still, each of those 35 firms has published a way into the office from the internet, and if it leads to client data, everyone who uses it needs MFA.
The qualified individual's written approval
The one exception reads "unless your Qualified Individual has approved in writing the use of reasonably equivalent or more secure access controls." The qualified individual is the one person who oversees your security program; the post on who can be the qualified individual covers the role.
The bar is high on purpose. A commenter asked the FTC to accept "effective alternative compensating controls" instead (86 FR 70289). The FTC declined, saying "any alternative measure should provide at least as much protection as multi-factor authentication" (86 FR 70290). Compare the encryption paragraph next to it, 314.4(c)(3), which does accept "effective alternative compensating controls reviewed and approved by your Qualified Individual" and doesn't say "in writing." The MFA exception is the stricter of the two.
The FTC expects the exception to be used "when the need for quick access outweighs the security benefits of multi-factor authentication." A note that says "MFA wasn't practical" doesn't meet that bar. The rule doesn't say what the approval must contain. We'd put these in it:
- The system, and who signs in to it.
- Why MFA isn't used there.
- The control used instead, and why it protects at least as well.
- The qualified individual's name, signature and the date.
- A date to look at it again, such as the next yearly review.
Keep it with the WISP. It is the answer when anyone asks why one system has no MFA.
When the MFA requirement took effect
The FTC adopted the current MFA paragraph in December 2021, with a compliance date of December 9, 2022. In November 2022 it pushed that date to June 9, 2023 for 314.4(a), (b)(1), (c)(1) through (8), (d)(2), (e), (f)(3), (h) and (i), citing "a reported shortage of qualified personnel" and supply chain delays (87 FR 71509). MFA is (c)(5), so it has applied since June 9, 2023.
Today's 16 CFR 314.5 won't show you that date. The FTC rewrote the section in November 2023, and it now gives only the May 13, 2024 date for the breach notice in 314.4(j). The June 2023 date lives in the 2022 notice.
Checking who has MFA
Keep a grid with every system down one side and every person across the top, and mark where MFA is on. For Microsoft 365, the post on turning on MFA in Microsoft 365 shows where to see who has registered. Tax software and portal vendors each have their own admin page. Check again whenever someone joins, leaves or gets a new phone, and at the yearly review.
Once you connect Microsoft 365, Crashcart checks every day whether each enabled account has MFA registered, and whether security defaults or a Conditional Access policy requires it. Each change goes into the evidence log under 314.4(c)(5). Without a connection, MFA stays on your list as an item you confirm and sign off. The tax software, the portal and any written exception stay with you and your qualified individual.
Safeguards Rule MFA checklist
- List every system that holds client information or connects to one: email, tax software, portal, cloud storage, remote access, office computers.
- List everyone who signs in to each, including your IT provider, contractors and clients.
- Turn on MFA for each person on each system, starting with email and admin accounts.
- Confirm each method uses two different factor types.
- For any system without MFA, either fix it or have the qualified individual sign a written approval of an equivalent or stronger control.
- Write in the WISP which systems require MFA and where the approvals are kept.
- Recheck when people join or leave, and at the yearly review.
This is general information, not legal advice. For your situation, ask your attorney.
More in this topic
- FTC Safeguards Rule requirements for small businesses
- FTC Safeguards Rule breach notification requirements
- The IRS Security Six for small tax offices
- How the Safeguards Rule small business exemption works
- Setting up and removing seasonal preparer accounts
- Who can be the Safeguards Rule qualified individual
- How to answer the WISP question on Form W-12
- How to write a WISP for a tax practice
Crashcart runs IT and security for small offices for $35 a computer a month. Start a 14-day free trial.