

What is a Written Information Security Plan for Tax and Accounting Firms?
A written information security plan is the document that says who protects client information at a tax or accounting firm, what risks the firm faces, which safeguards are in place and how staff respond to an incident. The IRS says federal law requires one, and every PTIN application includes a data security attestation.
By James Denney, Sales & Marketing Director | Technically reviewed by the AllTech security engineering team | Updated November 12, 2026
This guide is general information, not legal advice. Confirm your obligations with your attorney.
A written information security plan describes who protects client information, the risks the firm faces, its safeguards, staff training and incident response.
The IRS says federal law requires tax and accounting professionals to create and maintain one, and every PTIN application includes a data security attestation.
IRS Publication 5708 offers a template, but the plan only works if the safeguards it lists are actually in place.
Review the plan every year and whenever the firm adds staff, software, offices or providers.
Overview
A written information security plan, often called a WISP, is the document a tax or accounting firm keeps to describe how it protects client information: who is responsible, what risks the firm faces, which safeguards are in place, how staff are trained and what happens when something goes wrong. It is the written form of the information security program the FTC Safeguards Rule requires of firms that prepare income tax returns.
The IRS is direct about it. In an August 2026 release, the IRS and its Security Summit partners said federal law requires tax and accounting professionals to create and maintain a written information security plan, and every paid preparer confirms awareness of that duty when applying for or renewing a PTIN. A plan that sits in a drawer does not protect anyone, so the work is keeping it accurate and putting it into practice.
Benefits of a Written Information Security Plan for Tax and Accounting Firms
Meets a federal requirement. The plan documents the program the FTC Safeguards Rule requires, and backs up the data security attestation on the PTIN application.
Protects client trust. Clients hand over Social Security numbers, bank details and full financial pictures, and a working plan is how the firm keeps that information safe.
Makes the response faster. When a laptop is lost or an account is taken over, the plan already says who calls the IRS, the bank, law enforcement and the clients.
Answers insurers and clients. Cyber insurers, lenders and business clients increasingly ask for the plan or its key controls before they sign.
Turns security into a routine. A plan reviewed every year keeps training, access and safeguards current instead of rebuilt during tax season.

How AllTech Delivers
AllTech IT Solutions helps tax and accounting firms across Alabama, the Florida Panhandle and South Georgia, from offices in Birmingham and Dothan, build and maintain a written information security plan that matches how the firm actually works. The work starts with a review of where client data lives, who can reach it, which tax and practice software the firm uses and which outside providers touch it, so the plan describes real controls rather than a template.
From there, AllTech puts the safeguards the plan describes in place and keeps them running: multifactor sign in, encryption, email security, monitoring, backups and staff training. Every AllTech engineer recertifies in CJIS security awareness training each year and holds a current FBI background check. Backups are full images on an on site appliance with an immutable cloud copy that cannot be altered or deleted from the client network, and a Virtual Technology Advisor reviews the plan with the partners every year.
Key Areas Addressed
Cybersecurity Risk Assessment
The risk assessment the plan is built on, written to the criteria the Safeguards Rule lists.
Cybersecurity as a Service
The managed program that keeps the safeguards in the plan running and monitored month to month.
Incident Response Handbook
The written steps for a data theft or loss, including the IRS, law enforcement, state and client notifications.
Data Backup and Disaster Recovery
Tested image backups so client files and tax software can be restored after an attack or hardware failure.
Business Data Management
Clear rules for where client documents live, who can open them and how long they are kept.
Virtual Technology Advisor
A senior advisor who reviews the plan with the partners each year and adjusts it as the firm changes.
The AllTech Approach to Written Information Security Plans
Describe the firm as it is. The plan is built from a review of real systems, people and providers, not copied from a template.
Name who is responsible. One or more people are designated to coordinate the program, as the FTC requirements call for.
Put the controls behind the words. Every safeguard the plan lists is actually in place, monitored and documented.
Write the first hour of a breach. The plan lists who calls the IRS, law enforcement, state agencies and clients, so nothing waits on a decision.
Review it every year. The plan is updated before each filing season and whenever the firm adds staff, software or offices.
Related Services
Professional Services IT
Managed IT and security for accounting, law, engineering, architecture and consulting firms.
IT Support for Professional Services
The companion guide on everyday IT support for professional firms, from billable uptime to the FTC Safeguards Rule.
FTC Safeguards Compliance
The guide to the FTC Safeguards Rule for financial services firms, which applies the same rule from the lender side.
About the author
James Denney is the Sales & Marketing Director at AllTech IT Solutions. He has 25+ years in IT, including nearly two decades running IT and operations for wholesale distributors and six years as an AllTech engineer. Every guide is technically reviewed by the AllTech security engineering team.
Frequently Asked Questions
What is a written information security plan for a tax or accounting firm?
It is the document that describes how the firm protects client information: who is responsible, the risks it faces, the safeguards in place, how staff are trained and how the firm responds to an incident. Tax professionals often call it a WISP.
It is the written form of the program the FTC Safeguards Rule requires of firms that prepare income tax returns. For the security program behind it, see What is Cybersecurity as a Service for Professional Services.
Is a written information security plan required?
Yes. In IRS release IR-2026-92 on August 18, 2026, the IRS and Security Summit partners said federal law requires tax and accounting professionals to create and maintain a written information security plan. The requirement comes from the Gramm Leach Bliley Act and the FTC Safeguards Rule.
Under 16 CFR 314.2(h)(2)(viii), an accountant or other tax preparation service in the business of completing income tax returns is a financial institution, so the firm must maintain an information security program meeting the elements in 16 CFR 314.4.
What does the PTIN application say about data security?
Form W 12, the application and renewal form for a preparer tax identification number, includes a Data Security Responsibilities question. The preparer checks a box confirming awareness of the legal obligation to have a data security plan and to provide data and system security protections for all taxpayer information.
That means every paid preparer has already attested to the duty. The plan is how the firm shows it is meeting it.
What should a written information security plan include?
The IRS says a good plan focuses on three areas: employee management and training, information systems, and detecting and managing system failures. Under the FTC requirements, the firm must also designate one or more people to coordinate the program, assess risks, test safeguards and choose service providers that can maintain appropriate safeguards.
The Safeguards Rule also lists specific controls, including encryption of customer information under 16 CFR 314.4(c)(3) and multifactor authentication under 16 CFR 314.4(c)(5).
Is there a template for a written information security plan?
Yes. IRS Publication 5708, Creating a Written Information Security Plan for Your Tax and Accounting Practice, provides a template to help tax professionals, especially smaller practices, develop a plan.
A template is a starting point. The plan only helps if it describes the firm accurately and the safeguards it lists are actually in place, which is where most of the work is.
Do small tax practices get any relief?
Partly. Under 16 CFR 314.6, firms that maintain customer information on fewer than 5,000 consumers are exempt from four specific requirements, including the written risk assessment, the written incident response plan and the annual written report to the board.
All other requirements still apply, including encryption, multifactor authentication, access controls, staff training and oversight of service providers. Smaller firms still benefit from writing those pieces down.
When must a tax firm notify the FTC about a breach?
Under 16 CFR 314.4(j), effective May 13, 2024, a covered firm must notify the FTC of a notification event involving the information of at least 500 consumers, as soon as possible and no later than 30 days after discovery.
This federal notice is separate from any state notice owed to clients and from the IRS reporting steps, so one incident can start several clocks at once.
What should a tax firm do after a data theft?
IRS guidance for tax professionals says to contact the local IRS Stakeholder Liaison quickly so the IRS can help block fraudulent returns, and to contact the FBI or Secret Service and local police.
The same guidance lists notifying state tax agencies and state attorneys general where the firm prepares returns, the insurer and affected clients. The plan should list each call and who makes it.
What does Alabama law require if client data is breached?
The Alabama Data Breach Notification Act requires reasonable security measures under Ala. Code 8-38-3(a). If a breach is reasonably likely to cause substantial harm, Ala. Code 8-38-5(b) requires notice to affected individuals within 45 days, and Ala. Code 8-38-6(a) requires notice to the Attorney General when more than 1,000 Alabama residents are notified.
Florida firms face a shorter clock, with notice to individuals within 30 days under Florida Statutes 501.171(4)(a). This is general information, not legal advice.
How often should the plan be updated?
At least every year, and whenever the firm adds staff, offices, software or outside providers. Under 16 CFR 314.4(b)(2), the firm must periodically reassess the risks to customer information and the safeguards in place.
Many firms review the plan before each filing season, when the volume of client data is about to peak.
How much does help with a written information security plan cost?
Cost depends on the size of the firm, the systems and providers involved, and how many of the safeguards are already in place. At AllTech, a straightforward environment with roughly one user per device typically lands between $150 and $200 per seat per month, covering both the security program and day to day IT support, and heavier compliance needs move it up.
The work is scoped after a short conversation about the firm and its clients. To start that conversation, contact AllTech in Birmingham or Dothan.
The general guide
