Crashcart Start your free trial

FTC Safeguards Rule and the WISP

How the Safeguards Rule small business exemption works

The Safeguards Rule small business exemption, in 16 CFR 314.6, covers a firm that keeps customer information on fewer than 5,000 consumers. It excuses four things: the formal written risk assessment, the fixed testing schedule, the written incident response plan and the qualified individual's yearly written report. The written security program, the qualified individual, multi-factor authentication, encryption, training and the FTC breach notice all still apply. Count every individual whose records you hold, former clients included, and write the number down with the date.

The full guide to the FTC Safeguards Rule covers every requirement. This post covers the exemption itself: its exact wording, how to count, what happens when a firm passes 5,000, and why the excused documents can still be worth writing.

What 16 CFR 314.6 says

The whole section is one sentence. Here is the text of 314.6:

Section 314.4(b)(1), (d)(2), (h), and (i) do not apply to financial institutions that maintain customer information concerning fewer than five thousand consumers.

It doesn't exempt anyone from the rule. It removes four paragraphs from 16 CFR 314.4 and leaves everything around them in place. Read the paragraph numbers closely, because each excused part has a neighbor that still applies:

Excused by 314.6 Still required
314.4(b)(1): the risk assessment in writing, with criteria for rating risks and deciding how each is reduced or accepted 314.4(b): basing the program on a risk assessment, and 314.4(b)(2): repeating it periodically
314.4(d)(2): continuous monitoring, or a yearly penetration test plus vulnerability assessments every six months 314.4(d)(1): regularly testing or monitoring whether your safeguards work
314.4(h): the written incident response plan and its seven required areas 314.4(j): notice to the FTC within 30 days of a breach involving 500 or more consumers
314.4(i): the qualified individual's yearly written report 314.4(a): one qualified individual who oversees and enforces the program

The eight safeguards in 314.4(c), staff training, vendor oversight and keeping the program current all stay too, along with the written program in 314.3.

The FTC was asked to go further and declined. In the notice that adopted the 2021 changes, it records a request to excuse small firms from naming a qualified individual and another to exempt businesses with 15 or fewer employees from the rule entirely. It kept the exemption as proposed (86 FR 70300).

How to count consumers for the small business exemption

The threshold counts consumers, and 16 CFR 314.2 defines the word. Under 314.2(b), a consumer is "an individual who obtains or has obtained a financial product or service from you that is to be used primarily for personal, family, or household purposes, or that individual's legal representative." A customer is a consumer with a continuing relationship, and 314.2(e) lists becoming "your client for the purpose of obtaining tax preparation or credit counseling services" as one.

The rule's text stops there. We read it alongside the December 2021 Federal Register notice that adopted the current version, looking for anything on how to count, and found the answer in footnote 344 on page 70301. The Commission "understands this provision to count all individual consumers about which a financial institution maintains customer information, including both current and former customers." The same footnote says the count is of consumers, not transactions, so a firm with 100 transactions for one customer counts one consumer.

In practice, for a tax or accounting office:

  • Count people, not returns. A client whose returns you've prepared for ten years is one consumer.
  • Count former clients whose records you still hold, in prior years of the tax software, on the shared drive, in the file room and in any vendor's cloud. Customer information includes records kept "on behalf of you" (314.2(d)).
  • Count both spouses on a joint return. The rule counts individuals, and both spouses obtained the service. This is our reading; the rule doesn't address joint returns by name.
  • Leave out work done only for a business. A partnership or S corporation return isn't a service for personal, family or household purposes. The owners' personal returns are, and so is a sole proprietor's Schedule C, which is part of their personal return.
  • Count the unclear groups if you're close to the line. Dependents named on a client's return and employees of a business whose payroll you run don't fit the definitions neatly. If your total is near 5,000, include them. Counting high costs you some paperwork. Counting low leaves four required documents unwritten.

To get the number, export the client list from your tax software for every year you still keep, remove duplicates, and add anyone whose records exist only on paper.

Former clients count until their records are gone

Because former clients count, your retention policy moves your number. The rule requires you to dispose of customer information no later than two years after it was last used for that customer, unless you need it for business operations, the law requires keeping it, or targeted disposal isn't reasonably feasible (314.4(c)(6)). Federal law separately requires a preparer to keep a copy of each return, or a list of client names and taxpayer ID numbers, for three years after the close of the return period (26 U.S.C. 6107(b)).

The FTC expected firms to connect the two. The same page of the 2021 notice says a firm "may choose to dispose of information so it holds information on few enough consumers to qualify for exemption" (86 FR 70301). A firm holding fifteen years of returns for clients who left long ago may be over 5,000 only because of files it no longer needs. A written disposal schedule that you follow meets 314.4(c)(6) and can bring the count down. Check your state's record-keeping rules for preparers before you delete anything.

What happens when you pass 5,000

The rule has no grace period and no phase-in. Section 314.6 is written in the present tense, covering firms that "maintain" information on fewer than 5,000 consumers, so our reading is that the four paragraphs apply as soon as you hold records on more. Once they do, you need:

  1. A written risk assessment with criteria for rating risks, criteria for judging the confidentiality, integrity and availability of your systems and data, and how each risk will be reduced or accepted (314.4(b)(1)).
  2. Continuous monitoring, or a penetration test every year plus vulnerability assessments at least every six months and after material changes (314.4(d)(2)).
  3. A written incident response plan covering the seven areas in 314.4(h), from its goals to how it gets revised after an event.
  4. A written report from the qualified individual at least once a year to your board, or to a senior officer if you have none (314.4(i)). The post on who can be the Safeguards Rule qualified individual covers who receives it in a firm without a board.

If one more busy season could put you over, write them before it starts. Building a risk assessment and an incident plan in February is a bad trade.

Why keep the excused documents anyway

The exemption removes paperwork. The risks behind it are still there, and three of the four documents earn their keep even under 5,000.

The incident response plan. The FTC breach notice in 314.4(j) applies at 500 affected consumers whether or not you're exempt, with 30 days from discovery. A firm with 3,000 clients that loses an unencrypted laptop has to decide whether it was a notification event, count who was affected and file the FTC's form inside that window, plus whatever its state's breach law requires. Deciding who makes those calls is easier on a quiet afternoon. If your plan started from IRS Publication 5708, its Attachment C notification list is a start; the post on writing a WISP for a tax practice covers what to add.

The risk assessment. You still have to base the program on one and repeat it periodically (314.4(b) and (b)(2)). Only the written format and the formal criteria are excused. Writing it down is the simplest proof that it happened, and a short table is enough for a small office.

The yearly report. The rule still requires adjusting the program after material changes (314.4(g)). A dated page each year listing what changed, what you tested and what you decided is a cheap way to meet that, and it means crossing 5,000 later changes little.

The testing schedule is the one we'd skip if money is tight, since 314.4(d)(1) already requires you to test or monitor in some form. If we had to pick one document to write first, it would be the incident plan.

Writing down your count

Write the count where anyone reading your plan will see it, near the top of the WISP. Include the number, the date, the sources you counted from, which years of records they cover, how you handled joint returns and business-only clients, and who did the count. A reader who finds four parts of 314.4 missing from the plan will see why.

Recount once a year. The PTIN renewal is a convenient date, since line 11 of Form W-12 already asks every preparer about the plan.

Crashcart asks about this during setup. When a firm is under 5,000, the plan Crashcart drafts lists the parts the firm is excused from and marks the risk assessment optional. The count and the decision to rely on the exemption stay with the firm.

This is general information, not legal advice. For your situation, ask your attorney.

More in this topic

Crashcart runs IT and security for small offices for $35 a computer a month. Start a 14-day free trial.