A written information security plan, or WISP, is the document that names who protects client data in your firm, which safeguards you use, and what happens after a breach. The IRS says tax and accounting professionals must have one.
In my experience, most companies don’t have one. Plenty have never thought about it. That’s the gap.
I’ll say up front what we do and don’t do. We don’t write your plan. Much of it is internal procedure, and only your firm can decide those. What we handle is the technical side, such as endpoint security, security for Microsoft 365 or Google Workspace, and network security, along with helping clients meet their compliance goals, as part of our IT for accounting and CPA firms. That split is the whole point of this piece.

What a Written Information Security Plan Actually Covers
A written information security plan is a firm’s own document describing how it protects client information. It names the people responsible, lists the data and devices involved, sets the safeguards in use, and spells out what to do after a breach. Under the federal rule behind it, the program has to be written and readily accessible.
The IRS publishes a template. Publication 5708, Creating a Written Information Security Plan for Your Tax & Accounting Practice, comes from the Security Summit, a partnership of the IRS, state tax agencies and the tax industry. Its outline runs from objective, purpose and scope statements through naming a qualified individual, a risk assessment, a hardware inventory and the safety measures in place, to an implementation clause. Six sample attachments follow, including record retention, rules of conduct for client information, breach procedures, and a signed employee acknowledgment.
Two lines in it are worth reading twice. “There is no one-size-fits-all WISP.” And a sole practitioner “can use a more abbreviated and simplified plan than a 10-partner accounting firm.” Shorter is allowed. Missing isn’t. Simple.
Who Needs a Written Information Security Plan
The Security Summit said in an August 18, 2026 news release, IR-2026-92, that federal law requires tax and accounting professionals to create and maintain one. The chain runs through the Gramm-Leach-Bliley Act and the FTC’s Safeguards Rule, 16 CFR Part 314. Publication 5708 states it flatly: “tax and accounting professionals are considered financial institutions, regardless of size.” The rule’s own definition, which the FTC’s guide walks through, lists tax preparation firms among its examples of covered businesses.
Accounting firms aren’t named on that list. The rule defines coverage by activity, so whether a particular firm is covered depends on what the firm does. We’re an IT company, not a law firm, so that question belongs with your attorney.
Size doesn’t switch the requirement off. The rule scales the program to your size and complexity, and firms holding information on fewer than 5,000 consumers are excused from four items in section 314.4, the written risk assessment, the continuous monitoring or periodic testing requirement in paragraph (d)(2), the written incident response plan and the annual report to leadership. Nothing else. That’s a short list. The line-by-line version, what drops away and what stays, is in our piece on cybersecurity for accounting firms.
New York adds a second layer. The NY SHIELD Act, General Business Law section 899-bb, requires any business that owns or licenses computerized data with a New York resident’s private information to keep reasonable safeguards, and it lists administrative, technical and physical examples. As I read the statute, it calls for a data security program and never says the program has to be written. A business that is subject to the federal Gramm-Leach-Bliley rules, and in compliance with them, is deemed compliant. Small businesses get a scaled standard, and meeting any one of three tests qualifies: fewer than 50 employees, under $3 million in gross annual revenue in each of the last three fiscal years, or under $5 million in year-end total assets, per the 2019 SHIELD Act bill that added section 899-bb. Different law, different wording.
| Question | FTC Safeguards Rule | NY SHIELD Act |
|---|---|---|
| Where it lives | 16 CFR Part 314 | General Business Law 899-bb |
| Must the program be written? | Yes, in one or more readily accessible parts (314.3) | The statute describes a program and does not say written |
| How size matters | Scaled to size and complexity; four items waived under 5,000 consumers | Small business (any one of three tests) gets a scaled standard |
| How they connect | Applies to tax and accounting professionals, per the IRS | A business subject to and complying with federal Gramm-Leach-Bliley rules is deemed compliant |
I haven’t quoted a penalty figure. The IRS release doesn’t give one, and the numbers floating around online don’t agree with each other.
Which Parts of a Written Information Security Plan Are IT and Which Are Yours
Here’s the split. Publication 5708 itself says the Summit “strongly encourages tax professionals to consult with technical experts” on security, and its sample remote access policy has the firm’s data security coordinator and its IT contractor approving the tools together. But the rule’s elements don’t all land in the same lap.
| Plan element | Rule | Who usually supplies it |
|---|---|---|
| Name a Qualified Individual | 314.4(a) | Your firm |
| Written risk assessment | 314.4(b) | Your firm, with input from IT |
| Access controls, multi-factor authentication, encryption, logging | 314.4(c) | IT |
| Testing and monitoring of key controls | 314.4(d) | IT, results reviewed by your firm |
| Staff security training | 314.4(e) | Shared |
| Oversight of service providers | 314.4(f) | Your firm, with input from IT |
| Written incident response plan | 314.4(h) | Your firm sets roles and messages, with input from IT on the technical steps |
| Annual written report to leadership | 314.4(i) | Your firm |
The last column is my read of where the work usually falls, not a legal assignment. The technical rows are IT work. The rest isn’t, and nobody should tell you otherwise.

One row deserves its own paragraph. Section 314.4(a) lets the Qualified Individual be an employee, an affiliate or a service provider. With an outside provider, the firm keeps responsibility for compliance and names a senior person to oversee the role. We don’t take that role. Naming someone to run your compliance isn’t IT work. Not our lane. If you want outside help with the procedures side, compliance-specific companies exist, and we’d put you in touch with one.
Why Most Firms Never Write One
The reason isn’t technical. Here’s my take.
“Companies don’t like to do it because it requires them to make a lot of decisions and answer a lot of questions.”
Those questions are real. Who is the data security coordinator, how long do you keep a client’s prior-year return and who gets to open it and when is it destroyed, and what happens to an employee who ignores the policy or to the firm when something goes wrong? Publication 5708 covers every one of them. No software answers them for you.
Neither can we, since “a lot of this stuff is about internal procedures, not IT.” We’ve been asked about it several times. We’ve never run a campaign offering to write one, and this post isn’t one.

What Insurers Want to See
Short version, from my side of the desk.
“… it’s the kind of thing that insurance companies want to see.”
In my experience, insurance questionnaires can get very detailed, and a firm without good answers looks like it isn’t taking security seriously. A written plan puts those answers in one place. It isn’t a guarantee of coverage. Proof of the controls is a separate job, which we cover in getting audit-ready for your cyber insurance renewal.
Starting Your Written Information Security Plan
- Read the Requirements and Getting Started sections of Publication 5708 before you touch the sample template. They explain what the plan is for.
- Pick one data security coordinator. The IRS says that in a firm with two or more practitioners, this person and the public information officer should usually be different people.
- List every device that touches client data. Computers, yes, but also phones, printers and the router in the back room. Attachment E in Publication 5708 is a form for exactly this list.
- Set retention rules. How long you keep client records, who can open them, when they’re destroyed.
- Have everyone sign and date an acknowledgment. The IRS suggests refreshing them at annual training and keeping them on file.
- Store a copy offsite or in the cloud, as the IRS recommends.
- Put the review on the calendar. Publication 5708 calls the plan an “evergreen document.”
Then keep it alive.
Help meeting compliance goals is part of our managed IT services, and VJNetworks has supported small businesses across the Tri-State area since 2004, with 97% client retention.
Things Tax Preparers Ask About a WISP
Do I need a WISP if I’m a one-person practice?
Is Publication 5708 enough on its own?
Does New York’s SHIELD Act make me write one?
We hold information on fewer than 5,000 consumers. Can we skip it?
Can my IT provider write the plan for me?
How often does the plan need updating?
What if client data is stolen?
Talk with our team about the technical side of your written plan. No cost, no obligation.
