Crashcart Start your free trial

FTC Safeguards Rule and the WISP

How to write a WISP for a tax practice

The usual starting point for a WISP for tax preparers is IRS Publication 5708, a free template from the IRS and its Security Summit partners. Work through its sections in order and replace every bracket, and every sentence that doesn't describe your office, with what is true today. The template's blanks only ask for names and dates, so you also have to add what the FTC Safeguards Rule requires and the template leaves to you: a list of the devices that hold client data, a risk assessment, multi-factor authentication on every system, encryption on every computer and an incident response plan. Then the owner and the person in charge of the plan sign it.

A WISP is the written information security plan that the Federal Trade Commission's Safeguards Rule, 16 CFR Part 314, requires of every "accountant or other tax preparation service that is in the business of completing income tax returns" (16 CFR 314.2(h)). The full guide to the FTC Safeguards Rule covers who it applies to and each requirement. This post covers the writing, using Publication 5708 section by section.

The example lines below are for Ridgeway Accounting, a made-up 8-person firm we use for demos. Replace every detail with your own.

What is in Publication 5708

We read the current revision, Rev. 8-2024, page by page and counted what it asks you to fill in. It runs 29 pages: an introduction, a seven-part outline, the sample template itself (printed pages 5 to 12), a section of added guidance, six sample attachments lettered A to F, a glossary and a page of links.

The template body has 14 bracketed placeholders. Six of them ask for the firm's name. Two ask for a person's name, for the Data Security Coordinator and the Public Information Officer. Three ask for dates: last modified, the annual review and the implementation date. One asks for the owner's title. The last two are instructions, one to review the plan yearly and one to write and attach your rules of behavior. After those come two signature lines, each with a date.

None of the 14 asks about your computers, software, vendors or risks. Those details go in two attachments that arrive as empty tables: Attachment E, the hardware inventory, with five columns, and Attachment F, the list of people with access, with six columns and one sample row. The outline's step III, Assess Risks, has no matching section in the template at all.

So a firm can fill in every bracket and sign a plan that names none of its own computers. Most of the real work is in the parts the brackets skip.

What the rule requires that the template leaves out

The template covers many of the rule's requirements in its policy language. These are the gaps we found when we compared it against 16 CFR 314.4:

Rule requirement What Publication 5708 has What to add
Written risk assessment, 314.4(b)(1) Guidance only, no template section A risk assessment section
Multi-factor authentication for "any individual accessing any information system", 314.4(c)(5) Policy text covers remote login only Every system, by name
Encryption of customer information at rest and in transit over external networks, 314.4(c)(3) USB drives, emailed files and files on the network Disk encryption on every computer
Continuous monitoring, or a yearly penetration test plus vulnerability assessments every six months, 314.4(d)(2) A promise of continual monitoring, a 30-day review and event log reviews at least every 90 days Which one you use, and how it is done
Incident response plan covering seven areas, 314.4(h) Attachment C, mostly a notification list Roles, response steps, recovery, review after an event
Yearly written report from the Qualified Individual, 314.4(i) Nothing A dated yearly report
Oversight of every service provider, 314.4(f) Excepts tax software vendors and e-file transmitters Every vendor, including those

The template also adds things the rule doesn't ask for: a Public Information Officer, background checks, a ban on after-hours remote access, a 365-day password change and an offer to show the plan to clients. Keep each one only if your office does it.

Count your clients first

A firm that keeps customer information on fewer than 5,000 consumers is excused from four parts of the rule: the written risk assessment criteria in 314.4(b)(1), the testing schedule in 314.4(d)(2), the written incident response plan in 314.4(h) and the yearly report in 314.4(i) (16 CFR 314.6). Four rows of the table above are among them.

Count consumers, meaning individuals, not returns or households, and write the number and the date in the plan. The sections below say where the exception changes what you write. Keeping the excused documents anyway costs little and leaves you ready if an insurer or client asks.

What to write in each section of a WISP for tax preparers

Cover page

Fill in the firm name and the last modified date. The cover also says the plan is available to all employees and to clients on request. The rule requires the program to be written and "readily accessible" (16 CFR 314.3(a)); the client offer is the template's idea, so keep it or strike it.

Ridgeway Accounting (made-up example). Last modified/reviewed: November 3, 2026.

Objective, purpose and scope (sections I to III)

Section I defines personally identifiable information (PII) as a person's name plus items like a Social Security number, income data or an account number. Check the list against what you keep and add anything missing. Sections II and III can mostly stay as written.

Scope items A to C promise that the firm identifies risks, assesses them and evaluates its safeguards. The plan needs the risk assessment that proves it, which the template never supplies. Add a line that says where it is.

Ridgeway (made-up example): F. Our risk assessment is Attachment G, last updated October 20, 2026.

Identified responsible officials (section IV)

The template's Data Security Coordinator is the rule's Qualified Individual, the one person who oversees and enforces the plan (314.4(a)). Use both names so nobody wonders whether you named the right role. The template has no slot for a backup, so add one.

Ridgeway (made-up example): Ridgeway Accounting has designated Dana Ruiz, owner, as Data Security Coordinator and Qualified Individual under 16 CFR 314.4(a). When Dana is away, Sam Patel, senior preparer, acts in the role.

If the Qualified Individual works for an outside IT provider, the rule says your firm keeps responsibility for compliance and must name a senior person on staff to oversee them, and the provider must keep a program that meets the rule. The Public Information Officer is template-added. Its own guidance says most firms with two or more practitioners should give the two roles to different people. A sole practitioner holds both.

Add a risk assessment

This is the biggest gap. Over 5,000 consumers, the assessment must be written and include criteria for rating risks, criteria for judging how well your systems and data are protected, and how each risk will be reduced or accepted (314.4(b)(1)). Under 5,000, you still base the plan on an assessment of risks; it doesn't need that formal structure.

A table is enough for a small office: the risk, how likely it is, how bad it would be, the safeguard in place and the decision. Start with the risks the template's own guidance names, such as theft of paper files, remote access takeover and fire. Then add a phished email password, a former employee whose account still works and a backup nobody has tested.

Ridgeway (made-up example): Stolen laptop. Likelihood medium, impact high. BitLocker on all 3 laptops. Mitigated.

Inside the firm risk mitigation (section V)

Four policies sit here. In the collection and retention policy, replace the generic list of storage locations with yours: the tax software, the shared drive, the portal, the filing cabinets.

Attachment A holds the one blank in the retention policy: "kept longer than ____ Years." The rule says to dispose of customer information no later than two years after it was last used for that customer, unless you need it for business, the law requires keeping it, or targeted disposal isn't feasible (314.4(c)(6)). Federal law 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)). Pick the number you follow and write it in.

The personnel policy commits you to background checks for new hires with access to PII. Delete it if you don't run them. Keep the line that disables a departing employee's access "at the time of termination," and do it every time; the employee offboarding checklist covers the steps.

The disclosure policy has the annual review date blank, and a generic list of who you share data with. Replace the list with named vendors. The template excepts tax software vendors and e-file transmitters from meeting your plan's standards, but the rule's vendor section, 314.4(f), names no exception, so list them too.

Outside the firm risk mitigation (section VI)

The network protection policy promises event log reviews "not to exceed 90 days" and a top-down security review "at least every 30 days." Change each number to what your office does. It also sets passwords at eight or more characters, while Attachment B says the National Institute of Standards and Technology (NIST) recommends at least 12. Pick one and match what your systems enforce.

The access policy requires multi-factor authentication, a code from your phone on top of the password, only for remote login. The rule requires it for any individual accessing any information system, unless the Qualified Individual approves an equivalent control in writing. Name each system.

Ridgeway (made-up example): Multi-factor authentication is required for every user of Microsoft 365, our tax software, the client portal and remote access.

The electronic exchange policy covers emailed files, the portal and BitLocker on USB drives. The rule requires encryption of all customer information at rest, which includes the disks of your laptops and desktops. Add a line for them.

Implementation (section VII)

Three policies, Remote Access, Connected Devices and Information Security Training, print after the signature lines on printed page 12. Move them above. Connected Devices is the closest the template comes to the change management the rule requires (314.4(c)(7)), so make it describe how a new computer or program gets approved in your office. Training is required under 314.4(e); record it with Attachment D. Then the owner and the Data Security Coordinator sign and date the plan.

Attachments A to F

Attachment C lists who to notify after a breach, including the FTC within 30 days when 500 or more consumers are affected (314.4(j)). Over 5,000 consumers, add the rest of the incident response plan: who decides, the first steps, recovery and a review afterward. Have every person sign Attachment D, seasonal staff included. Add a disk encryption column to Attachment E. In Attachment F, the template suggests closing the old row and starting a new one whenever someone's access changes, which gives you a dated history.

A checklist for the first draft

  1. Count your consumers and write the number and date in the plan.
  2. Fill in all 14 brackets and both signature lines.
  3. Name the Qualified Individual and a backup.
  4. Write the risk assessment table.
  5. List every device in Attachment E and every person with access in Attachment F.
  6. Name every system that requires multi-factor authentication.
  7. Add disk encryption for every computer.
  8. Replace the template's vendor list with yours, tax software included.
  9. Strike every promise your office doesn't keep.
  10. Train staff, collect Attachment D signatures, and sign.

Keeping the plan current

A WISP goes stale the first time the office changes. A new laptop isn't in Attachment E. A preparer leaves and their row in Attachment F never gets an end date. You switch portals and the vendor list names the old one. The rule requires adjusting the plan after material changes to your operations (314.4(g)), and the template asks for a review at least once a year.

Tie the review to a date you already have. Each PTIN renewal asks every preparer to confirm on line 11 of Form W-12 that they know the plan is required. That's a good day to walk the inventory, the access list and the vendor list, update the last modified date and sign again.

Crashcart does this upkeep for small tax and accounting firms. It drafts the WISP from your computers and setup answers, keeping what still applies from a Publication 5708 plan you paste in. Each morning it checks the safeguards on every computer. New devices on your network go into the plan's inventory, and it tells you when your systems stop matching the plan. You name the Qualified Individual, answer what only you know, and sign it each year.

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.