If your firm prepares tax returns, the Federal Trade Commission treats you as a financial institution, and the FTC Safeguards Rule requires you to maintain a written information security program. There is no size exemption from the Rule itself: a solo preparer is covered, although a firm with information on fewer than 5,000 consumers is excused from a few of its elements. The IRS reinforces the same requirement from a different direction: Publication 4557 expects every tax professional to have a Written Information Security Plan (WISP), and PTIN renewal asks you to attest that a data-security plan exists.
This article walks through what the program must cover, what a good WISP describes, and the mistake that makes firms feel compliant while staying exposed. It is general information, not legal advice.
What the Safeguards Rule requires
The Rule is prescriptive about program elements, not about products. Buying tools without documenting a program leaves a firm non-compliant while feeling secure. The elements:
- A Qualified Individual. One named person accountable for the program — an employee or a designated service provider. Accountability stays with the firm, and the person must actually be positioned to oversee the program, not named on paper and never told.
- A written risk assessment. What client data you hold, where it lives, and what could happen to it — in writing, and kept current.
- Safeguards matched to the risks. Access controls, encryption in transit and at rest, multi-factor authentication, and secure disposal — the controls that fit your actual environment.
- Testing and monitoring. Regular testing of safeguards and monitoring for unauthorized access, sized to the firm.
- Training. Staff training on the program, including how to recognize phishing and social engineering.
- Vendor oversight. Service providers with access to client data must be overseen — contracts, reviews, and a record of both.
- An incident response plan. What happens when something goes wrong, written down before it does, with roles assigned.
- Annual review and updates. The program is reviewed at least annually and whenever the business, systems, or risks change.
- Breach reporting. Events affecting 500 or more consumers must be reported to the FTC within 30 days.
What a WISP must describe
A Written Information Security Plan documents how your firm protects client financial data in your actual environment. The key phrase is “actual environment.” A downloaded template with the firm name inserted, describing controls the firm does not have, does not satisfy the requirement — and reads badly under scrutiny, because it describes a security program that doesn’t exist.
A defensible WISP names: the Qualified Individual; the systems that hold client data (tax software, portals, email, backups, personal devices if used); the controls in place on each; who has access and how it is granted and removed; how vendors are overseen; the training schedule; and the incident response steps. It is signed, dated, and reviewed annually.
Timing: before tax season, not during it
The work takes weeks, not days, because it requires the inventory: every system, every vendor, every access path. Firms that start in January discover the gaps while returns are due. The firms that do this well start in the fall, finish before the season, and treat the annual review as a calendar event, not a reaction to an incident or a letter.
