If you prepare tax returns for pay, you need a written information security plan, usually called a WISP. It is the document that says how your practice protects client data, who is in charge of that, and what happens if something goes wrong. Many tax preparers know they are supposed to have one. Fewer have one that matches how their office actually works.
This guide covers what a WISP is, why tax preparers need one, what goes in it, and a free way to build a first draft in one sitting.
What a WISP is
A WISP is a written description of your practice's information security program. It names the person responsible, lists the client data you hold and where it lives, describes the risks to that data, explains the safeguards you use, and sets out the steps you will follow after a security incident. A good WISP is specific to your office. A template with your firm name pasted into the header is a starting point, not a finished plan.
Why tax preparers need one
Two sources point tax professionals to a WISP:
- The FTC Safeguards Rule. Under the Gramm-Leach-Bliley Act, tax preparers are treated as financial institutions. The FTC Safeguards Rule, 16 CFR Part 314, requires covered firms to develop, implement and maintain a written information security program. That is federal law.
- The IRS. Publication 4557, Safeguarding Taxpayer Data, recommends the safeguards a tax practice should have, and Publication 5708 walks through creating a WISP for a tax and accounting practice. The IRS and its Security Summit partners have also reminded tax pros that they must have a written plan (IR-2025-79).
What goes in a WISP for a tax practice
The Safeguards Rule lists the elements of the program in 16 CFR 314.4. In a tax office, those become these sections:
- Qualified Individual. One named person who oversees the program, plus a backup. See Who Owns the WISP?
- Data inventory. The client data you hold (Social Security numbers, bank details, prior-year returns, W-2s) and where each lives: tax software, portal, email, cloud storage, paper files.
- Risk assessment. The threats your office faces, such as phishing, ransomware, a lost laptop or a compromised vendor, and how each is addressed.
- Safeguards. Access controls, multi-factor authentication, encryption, endpoint protection, secure disposal, backups, and monitoring of who uses client data.
- Testing and monitoring. How you check that the safeguards keep working.
- Staff training. Security awareness training and how often it happens.
- Vendors. Every service provider that touches client data, and the security terms in each contract.
- Incident response. Who does what in the first hour, who to call, and the FTC notice for events involving 500 or more consumers. See Breach Plan Ready?
- Annual review. A dated review each year, and whenever staff, software or vendors change. See the Annual WISP Review Checklist.
Smaller practices: what changes under 5,000 consumers
Under 16 CFR 314.6, firms that keep customer information on fewer than 5,000 consumers do not have to meet four specific parts of the Rule: putting the risk assessment in writing, the annual penetration test and twice-yearly vulnerability scans, the written incident response plan, and the Qualified Individual's annual written report. Everything else still applies, including the written information security program itself, and the IRS still recommends covering these items. For most small offices, writing them down anyway is the simpler path.
Common mistakes
- A downloaded template that was never customized to the office.
- No Qualified Individual named, or the person named has left.
- No vendor list, even though the plan says vendors are reviewed.
- No incident contacts, so nobody knows who to call when the office is down.
- No review date, so the plan describes how the office worked two years ago.
For a section-by-section walkthrough, see How to Write a WISP That Actually Holds Up.
Build yours free
Watch Cloud's free WISP builder asks plain-English questions about your practice and produces a draft WISP shaped around your answers. When it is done, run the free Compliance Gap Check to see which safeguards the FTC Safeguards Rule requires that your answers show as gaps, and the fix for each one.
Watch Cloud Cyber Security helps tax preparers, CPAs, enrolled agents and bookkeepers build and maintain a WISP aligned with the FTC Safeguards Rule and IRS Publication 4557, backed by 24/7 monitoring and endpoint protection.
This article is general information, not legal advice.


