
What Is IRS Publication 5708 and Who Needs It?
Federal law requires every professional tax preparer in the United States to maintain a Written Information Security Plan (WISP)—a formal, documented strategy for protecting sensitive taxpayer data. To help practitioners meet this obligation without hiring a law firm or a security consultant, the Security Summit—a public-private partnership between the IRS, state tax agencies, and the tax software industry—published IRS Publication 5708, Creating a Written Information Security Plan for Your Tax & Accounting Practice.
The requirement flows from the Gramm-Leach-Bliley Act (GLBA) and the Federal Trade Commission (FTC) Safeguards Rule, which classify tax preparers as "financial institutions" for data security purposes. The IRS reinforces this in IRS Publication 4557, Safeguarding Taxpayer Data, which outlines baseline security expectations and explicitly cross-references the WISP requirement. Non-compliance exposes your practice to FTC enforcement actions, state penalties, and—most damaging—the reputational fallout of a taxpayer data breach.
The IRS Publication 5708 WISP template was intentionally written in plain language, making it practical for sole practitioners and small accounting firms that do not have in-house information security staff. Whether you operate a one-person practice or a regional CPA firm, the template gives you a fillable framework you can adapt to your actual systems, staff, and client base. Building a sound understanding of cybersecurity for tax professionals starts here.
Tax Preparers Are a High-Value Target
IBM Cost of Data Breach Report 2024
IRS Identity Theft Statistics, 2023
Verizon Data Breach Investigations Report 2024
What the IRS Publication 5708 WISP Template Covers
The Security Summit designed the IRS Publication 5708 WISP template around five core security areas that every tax practice must address, regardless of size. Think of the document as a structured questionnaire: it prompts you to inventory your systems, identify risks, select safeguards, and document your decisions. The template does not prescribe a single correct answer—it guides you to document the right answers for your practice.
Here is what each major section addresses:
- Designated Security Coordinator: You must name one individual—even in a solo practice, that person is you—who is accountable for the WISP. This person owns the plan, conducts annual reviews, and serves as the point of contact for security incidents.
- Risk Assessment: The template walks you through identifying the types of taxpayer data you collect, the systems that store or transmit it, and the realistic threats those systems face. This is not a hypothetical exercise—it shapes every safeguard you subsequently choose.
- Technical Safeguards: From two-factor authentication for tax software to disk encryption and firewall configuration, the template itemizes controls and asks you to document whether each is in place or has a compensating measure.
- Physical Safeguards: Office access controls, clean-desk policies, and secure document disposal are all addressed—frequently overlooked areas where tax offices face genuine exposure.
- Service Provider Management: If you use cloud storage, payroll processors, or any third party that touches taxpayer data, the WISP requires you to document those vendors and confirm they maintain their own security practices.
- Employee Training: The plan must reflect how and when staff are trained on security policies, phishing recognition, and data handling procedures.
- Data Theft Response Plan: This subsection directs you to document the steps you will take immediately after discovering a breach, including how to contact your IRS Stakeholder Liaison.
Each section includes fillable prompts, checkboxes, and sample policy language. You are not starting from a blank page—you are customizing a professionally structured document.
How to Implement Your WISP Using IRS Publication 5708
Download and Read IRS Publication 5708
Obtain the current version directly from IRS.gov. Read the full document before filling in any section—the introductory guidance clarifies scope decisions you will make throughout.
Designate Your Security Coordinator
Formally name the individual responsible for your WISP. In a solo practice this is the owner; in larger firms it may be an office manager or IT lead. Document this person's name and contact information in the plan.
Complete the Risk Assessment
Inventory every location where taxpayer data lives—workstations, laptops, cloud drives, email servers, tax software portals. Rate the likelihood and impact of each threat category the template identifies.
Select and Document Your Safeguards
For each risk identified, document the technical, physical, or administrative safeguard you have in place. If a control is not yet implemented, document a target remediation date.
List and Vet Service Providers
Identify every third-party vendor with access to taxpayer data. Confirm they maintain their own security plans and document their contact information and the specific data they can access.
Write Your Data Theft Response Plan
Document step-by-step actions your practice will take within the first 24–72 hours of a confirmed breach, including IRS Stakeholder Liaison notification and client communication procedures.
Train Your Team and Store the Document
Conduct initial training with all staff and record attendance. Store the finalized WISP in PDF and Word formats, with a backup copy in offsite or cloud storage for disaster recovery.
Review and Update Annually
The FTC Safeguards Rule requires annual testing and review of your information security program. Set a recurring calendar reminder—many practices align this with the end of filing season.
Tailoring the IRS Publication 5708 WISP Template to Your Firm's Size
One of the most valuable aspects of the IRS Publication 5708 WISP template is its explicit acknowledgment that there is no one-size-fits-all security plan. The Security Summit built the document so that a sole practitioner and a ten-partner accounting firm can both use it—but produce appropriately different outputs.
For sole practitioners, the WISP can remain relatively concise. If you work from a single workstation, use one cloud-based tax platform, and have no employees, your risk surface is limited. Your WISP still needs every required section, but the answers will be brief. The template's sample language is already written with smaller practices in mind.
For firms with two to ten staff members, the plan grows more detailed. You now have multiple endpoints to secure, employees who need formal training documentation, and likely several service provider relationships to catalog. Pay particular attention to the employee training and access control sections—staff turnover is one of the most common causes of data exposure in small tax offices.
For firms with more than ten employees, the template serves as a foundation, but you will almost certainly need to supplement it. At this scale, role-based access controls, formal onboarding and offboarding procedures, and network segmentation deserve their own policy documents that your WISP can reference. Review our WISP checklist for CPA firms to confirm you have addressed the additional requirements larger practices face under the FTC Safeguards Rule.
Regardless of firm size, the FTC requires that your security program be appropriate for the sensitivity of the data you handle, not just its volume. If you specialize in high-net-worth clients, business tax returns, or payroll services, your risk assessment should reflect the heightened sensitivity of that data—and your safeguards should match.
Core Components Every WISP Must Include
Designated Security Coordinator
A named individual accountable for maintaining, testing, and updating the WISP on an ongoing basis.
Written Risk Assessment
A documented inventory of data, systems, and threats—the foundation on which every safeguard decision rests.
Technical Safeguards
Multi-Factor Authentication (MFA), encryption, endpoint protection, and firewall configurations documented and verified.
Service Provider Oversight
A list of every vendor with data access, along with confirmation of their own security practices and written agreements.
Employee Security Training
Documented training covering phishing recognition, data handling, password policies, and incident reporting procedures.
Data Theft Response Plan
Step-by-step breach response procedures including IRS Stakeholder Liaison notification within the required timeframe.
The Data Theft Response Plan: Your Most Time-Sensitive Section
Of all the sections in the IRS Publication 5708 WISP template, the data theft response plan demands the most immediate attention when something goes wrong. Tax preparers who discover a breach have a narrow window to act: IRS Stakeholder Liaisons expect prompt notification, state laws may impose 72-hour reporting deadlines to affected individuals, and delayed action amplifies both the financial and reputational damage.
Your response plan should answer four questions before an incident ever occurs:
- Who is your IRS Stakeholder Liaison? Every state has one. The IRS publishes a contact directory—find your liaison now and record their direct line in the WISP, not buried in a bookmark folder you may not be able to access during a crisis.
- What data was exposed, and where? This is why the risk assessment section matters so much. If you have already inventoried every location where taxpayer data lives, you can rapidly assess the scope of any breach rather than guessing under pressure.
- Who else must be notified? Depending on your state, a breach affecting client Social Security numbers or financial account information may trigger mandatory notification to the state attorney general, affected clients, and potentially credit bureaus. Your response plan should list these obligations explicitly.
- How will you contain and recover? Document the immediate steps: isolating compromised systems, revoking affected credentials, engaging your IT provider or managed security service, and preserving evidence for forensic review.
A well-documented response plan is not just good practice—it is evidence of reasonable care if your practice ever faces regulatory scrutiny. Pairing your WISP with a tested ransomware protection strategy for your tax practice significantly reduces the likelihood you will ever need to execute this plan.
Common WISP Gaps That Leave Tax Practices Exposed
After working with tax and accounting firms across the country, the same documentation gaps appear repeatedly. Most are not the result of negligence—they reflect a document completed once and never revisited. The IRS Publication 5708 WISP template is only as effective as the discipline behind it.
Gap 1: Treating the WISP as a one-time task. The FTC Safeguards Rule explicitly requires annual testing and review of your security program. If your WISP has a creation date but no revision history, it is likely out of compliance. Set an annual review date—many practitioners align it with the end of filing season.
Gap 2: Missing or incomplete service provider documentation. Tax offices routinely add new software tools—e-signature platforms, document portals, payroll integrations—without updating the WISP. Every new vendor that touches taxpayer data needs to appear in your service provider section before they go live, not after.
Gap 3: No evidence of employee training. Telling staff about security policies verbally is not sufficient documentation. The WISP must reflect that training occurred, who attended, and what was covered. Formal security awareness training for tax firms generates the attendance records and content logs your WISP needs to reference.
Gap 4: Weak or missing MFA documentation. The IRS has made Multi-Factor Authentication (MFA) an explicit requirement for accessing tax software and client portals. Your WISP should document not only that MFA is enabled, but which systems it covers and the authentication method used. Our guide on two-factor authentication for tax software walks through implementation specifics.
Gap 5: No physical security provisions. Digital safeguards get most of the attention, but the template also covers physical access controls—locking filing cabinets, clean-desk policies, visitor logs, and secure document disposal. These sections are frequently left blank.
A formal tax safeguard compliance review can identify which of these gaps apply to your practice and prioritize remediation before a breach or audit exposes them first.
WISP Requirement Applies to ALL Tax Preparers
The FTC Safeguards Rule and IRS Publication 4557 make no exception for small practices or solo preparers. If you prepare federal tax returns professionally—even part-time during filing season—you are legally required to have a Written Information Security Plan on file and up to date.
Where to Get the Template and What to Do Next
The IRS Publication 5708 WISP template is available at no cost directly from the IRS. Download IRS Publication 5708 as a PDF from IRS.gov. For additional context on your compliance obligations and data handling requirements, also download IRS Publication 4557 and IRS Publication 5293, the Data Security Resource Guide for Tax Professionals—all three documents are designed to work together.
Once you have the template, the NIST Small Business Information Security guide provides a risk management framework that aligns well with the risk assessment section of your WISP and helps you evaluate safeguard options systematically. For guidance on storing and distributing the finalized WISP securely to remote staff, explore options for a secure client portal for your tax practice.
If you need help completing the template, identifying gaps in your current security posture, or verifying that your WISP meets the current FTC and IRS requirements, Bellator Cyber Guard offers a structured WISP assessment for tax and accounting practices. Our team works exclusively with financial and tax professionals and understands the specific data environments—and the specific threat actors—that target this industry.
Get a Free WISP Assessment for Your Tax Practice
Not sure if your WISP is complete, current, and compliant? Our cybersecurity experts will review your plan against IRS Publication 5708 requirements and identify any gaps before a breach or audit does.
Frequently Asked Questions
IRS Publication 5708, titled Creating a Written Information Security Plan for Your Tax & Accounting Practice, is a fillable WISP template published by the Security Summit—a partnership of the IRS, state tax agencies, and the tax software industry. It provides tax preparers with a structured, plain-language framework for documenting their data security programs without requiring outside legal or technical expertise.
All professional tax preparers in the United States are required to maintain a WISP. The obligation flows from the Gramm-Leach-Bliley Act and the FTC Safeguards Rule, which classify tax preparers as financial institutions for security purposes. There is no size threshold—a sole practitioner preparing a handful of returns is held to the same legal standard as a large regional CPA firm, though the scope of the plan should reflect the scale and complexity of the practice.
The IRS and FTC do not mandate a specific page count. A sole practitioner's WISP may be a few pages; a larger firm's plan may run 20 or more pages with attached policy documents. What matters is that every required section is addressed with specificity appropriate to your practice. A vague, one-paragraph answer to a risk assessment prompt does not satisfy the regulatory requirement.
The FTC Safeguards Rule requires annual testing and review of your information security program. You should also update your WISP any time a material change occurs—new employees, new software vendors, new office locations, or any security incident. Many practices align their annual WISP review with the post-filing-season period, when staff availability allows for a thorough update.
IRS Publication 4557 explains the legal requirement to safeguard taxpayer data and outlines the categories of safeguards the IRS expects tax preparers to implement. IRS Publication 5708 is the practical companion: the actual fillable WISP template tax preparers use to document compliance with those requirements. Use Publication 4557 to understand what is required; use Publication 5708 to document that you have done it.
No. The template is a starting point, not a finished product. Generic or lightly edited placeholder text does not satisfy the FTC's requirement for a security program appropriate to the size and complexity of your practice and the sensitivity of the data you handle. Every section must reflect your actual systems, vendors, staff, and procedures.
Operating without a WISP exposes your practice to FTC enforcement action under the Safeguards Rule, potential state penalties for failure to maintain a data security program, and possible loss of IRS e-file privileges in severe cases. Beyond regulatory consequences, absence of a WISP is likely to be treated as evidence of negligence if client data is ever breached and litigation follows. Cyber liability insurers also increasingly require a current WISP as a condition of coverage.
There is no legal requirement for an attorney or security professional to sign off on your WISP. However, given that the document is your primary evidence of compliance with federal law, having it reviewed by a cybersecurity professional familiar with IRS and FTC requirements is a sound investment. A professional review can identify gaps you may have missed and ensure your safeguard selections actually address the risks in your risk assessment—not just check boxes.
Schedule
Need help with IRS compliance?
Our tax cybersecurity specialists can review your security posture and help you get compliant.



