What the IRS WISP Template PDF Is and Why You Need It
The IRS WISP template PDF gives tax professionals a structured starting point for meeting one of the most frequently overlooked federal compliance requirements in the industry. Under the Gramm-Leach-Bliley Act (GLBA) and the FTC Safeguards Rule, every tax preparer who handles client financial data must maintain a Written Information Security Plan (WISP)—a documented set of policies and procedures designed to protect sensitive taxpayer information from unauthorized access, theft, or disclosure.
The IRS, through its Security Summit initiative—a public-private partnership between the IRS, state tax agencies, and the nation's tax industry—developed a sample WISP template specifically for small practices and sole practitioners who lack dedicated IT staff. This guide walks you through where to find and download that template, what each section requires, and how to tailor it to your practice size and complexity.
Whether you operate as a sole practitioner or manage a growing accounting firm with multiple staff members, the WISP requirement applies to you. The IRS makes clear in Publication 4557, Safeguarding Taxpayer Data that no specific format is mandated—but the plan must exist, be written, and be actively implemented. For a broader overview of your obligations, the IRS WISP requirements guide covers the full regulatory framework in detail.
Why Tax Professionals Are Prime Targets
IBM Cost of Data Breach Report 2024
IBM Cost of Data Breach Report 2024
Verizon Data Breach Investigations Report 2024
Who Is Required to Have a WISP Under Federal Law
Tax preparers are classified as financial institutions under the GLBA, which means the FTC Safeguards Rule—codified at 16 C.F.R. Part 314—applies directly to your practice. The FTC's updated Safeguards Rule, which reached full enforcement in June 2023, added new specificity to what a written security program must document and implement. The IRS reinforces these obligations through Publication 4557 and through the IRS Publication 4557 compliance framework.
If your practice prepares federal tax returns for clients, you are required to:
- Maintain a written, implemented, and regularly updated information security plan
- Designate an employee or contractor as your security program coordinator
- Conduct periodic risk assessments of your data systems and identify foreseeable threats
- Implement safeguards to address each identified risk
- Monitor and test the effectiveness of your controls on an ongoing basis
- Oversee all service providers who handle taxpayer data on your behalf
Violations of the FTC Safeguards Rule can result in civil penalties of up to $100,000 per violation and personal liability for practice owners and officers. These penalties apply independently of any IRS disciplinary action your practice might face following a breach.
Tax professionals with an Electronic Filing Identification Number (EFIN) face a compounding risk: if your EFIN credentials are stolen, fraudulent returns can be filed under your identity, exposing you to regulatory sanction and client harm. Protecting your EFIN and associated access credentials is one of the primary goals a well-implemented WISP addresses directly. For context on the broader threat environment facing your practice, the guide on cyberattacks on tax firms documents the most common attack methods used against preparers in recent years.
The WISP Requirement Has No Minimum Practice Size
Unlike some federal regulations that exempt very small businesses, the WISP requirement applies to all compensated tax professionals who handle client financial data—including sole practitioners who prepare as few as one federal return per year. The IRS WISP template PDF is designed to scale with your practice, but having no written plan at all is never acceptable under federal law.
Where to Download the IRS WISP Template PDF
The IRS Security Summit publishes an official sample WISP document that serves as the most authoritative starting point for any tax professional building a security plan. You can access it directly from the IRS Written Information Security Plan page, where it is available as an editable Word document. Bellator Cyber Guard also offers a free WISP template updated for 2026 that incorporates the IRS Security Summit framework alongside the latest FTC Safeguards Rule requirements, giving your practice a more complete compliance baseline from the start.
When downloading any WISP template, verify the source before opening the file. Threat actors have been known to distribute malware-laden documents disguised as compliance resources—a documented tactic in phishing campaigns specifically targeting tax professionals. Download only from official .gov domains or verified cybersecurity providers.
What the IRS WISP Template PDF Contains
The Security Summit sample document is organized into five major sections, each addressing a distinct area of information security:
- Business Description and Information Systems — Identifies the types of client data your practice handles, the systems used to process it, and who has access to each data category.
- Employee Management and Training — Documents your hiring practices, background check procedures, onboarding security training requirements, and ongoing security awareness schedules.
- Information Systems and Policies — Covers your technical safeguards: password policies, multi-factor authentication (MFA), encryption standards, software update procedures, and remote access controls.
- Detecting and Responding to Threats — Defines how your practice monitors for breaches, detects unauthorized access attempts, and responds to incidents—including required IRS notification procedures.
- Physical Security Elements — Addresses office access controls, workstation placement, document destruction policies, and device security for laptops and mobile devices used outside the office.
Beyond these five sections, the IRS template includes a Data Theft Response Plan—an essential sub-document that specifies exactly what steps your practice will take if a breach occurs, including how to reach your IRS Stakeholder Liaison within the required timeframe.
How to Complete the IRS WISP Template PDF Step by Step
Download the Official Template
Get the IRS Security Summit WISP template from the IRS website or use Bellator's 2026-updated version. Save a working copy in both editable and PDF formats before making any changes to the original.
Inventory Your Data Systems
Document every location where client data is stored: tax software databases, cloud storage accounts, email archives, paper files, external drives, and any portable devices used in your practice. This inventory is the foundation of your risk assessment.
Identify Foreseeable Threats
List the realistic threats facing your practice: phishing emails, ransomware, stolen laptops, insider misuse, and third-party vendor breaches. Reference the IRS's documented threat list in Publication 4557 as a starting framework.
Designate a Security Coordinator
Name the specific person responsible for implementing and maintaining your WISP. For sole practitioners, this is typically the owner. For larger firms, this may be an office manager, IT contractor, or Managed Security Service Provider (MSSP).
Document Safeguards for Each Identified Risk
For every threat identified, document the specific control in place: MFA requirements, encrypted storage configurations, employee training schedules, vendor agreements, and tested backup procedures.
Create Your Data Theft Response Plan
Define the exact steps your practice will take within 24 hours of discovering a breach—including notifying your IRS Stakeholder Liaison, affected clients, relevant state agencies, and law enforcement through the FBI's IC3 portal.
Train Staff and Implement Technical Controls
Review the completed WISP with all employees who handle client data. Document the training date and obtain a signed acknowledgment from each employee. Activate any technical controls not yet deployed.
Schedule Annual Reviews and Trigger-Based Updates
Set a recurring calendar reminder to review and update your WISP at least once per year, and immediately after any significant change to your systems, staffing, or data handling practices.
Customizing the IRS WISP Template PDF for Your Practice Size
One of the most practical aspects of the IRS WISP template PDF is its built-in scalability. The IRS explicitly states that a sole practitioner's plan will look very different from a 10-partner accounting firm's—and that difference is by design. Your WISP must be appropriate to the actual size and complexity of your practice, not a generic boilerplate that doesn't reflect how your business operates. Reviewing the best WISP templates for accountants by practice size can help you calibrate the right level of detail before you begin.
Sole Practitioners
If you work alone and prepare returns using a small number of client-facing systems, your WISP can be relatively brief while still covering all five required sections. The IRS Security Summit designed an abbreviated framework specifically for this scenario. Your "employee management" section, for example, may simply note that you are the sole practitioner and that you complete annual security awareness training from a named provider each year.
Areas sole practitioners frequently underestimate: remote access security when working from a laptop outside the office, cloud storage permission settings that may expose client files to unauthorized sharing, and what happens to client data if you become incapacitated or permanently close your practice. Each of these scenarios warrants specific documentation in your WISP.
Small and Mid-Size Practices
Practices with two to ten employees face a wider attack surface. Each additional user account, shared network drive, or remote worker creates new vectors for unauthorized access to client data. At this scale, your WISP should include role-based access controls—documenting exactly which employees can access which client records—alongside the standard narrative sections. For practices using tax software from multiple vendors such as Drake, Lacerte, or ProSeries, the WISP should address each platform's data handling practices and how you verify vendor security through written agreements or attestations. See accounting firm WISP examples for detailed structural models at this scale.
Larger Accounting Firms
Firms with 11 or more employees, multiple office locations, or significant cloud infrastructure should treat the IRS WISP template PDF as a baseline rather than a finished compliance product. At this scale, NIST SP 800-171—the National Institute of Standards and Technology's guidance on protecting Controlled Unclassified Information—provides a more rigorous framework that complements the IRS template and helps position the firm for SOC 2 Type II or ISO 27001:2022 readiness if needed.
WISP Requirements by Practice Size
| Feature | Sole Practitioner | RecommendedSmall Practice (2–10 Staff) | Large Firm (11+ Staff) |
|---|---|---|---|
| Document Length | 3–5 pages | 8–15 pages | 20+ pages |
| Risk Assessment | Basic written review | Documented assessment | Formal annual assessment |
| Employee Security Training | Self-directed annual | Structured + documented | Program with signed records |
| Incident Response Plan | IRS notification steps | Full response procedures | 24/7 escalation paths |
| Vendor Management | Basic agreements | Written contracts | Formal third-party audits |
| IT Security Coordinator | Owner/practitioner | Designated staff member | Dedicated role or MSSP |
| Physical Security Section | Office and device locks | Shared space + device controls | Badge access + camera systems |
| Annual WISP Review | Required | Required | Required + change management |
Core Components Every Tax Practice WISP Must Include
Data Inventory & Classification
A complete record of every location where client data lives—software databases, email archives, cloud drives, paper files, and portable devices used outside the office.
Employee Security Training
Documented annual training covering phishing recognition, password hygiene, secure file transfer, and proper handling of sensitive client data throughout the year.
Access Controls & Authentication
Role-based permissions, multi-factor authentication on all tax software and email accounts, and a defined process for revoking access immediately when staff depart.
Incident Response Plan
Step-by-step procedures for detecting, containing, and reporting data breaches—including direct contact information for your IRS Stakeholder Liaison.
Vendor Oversight
Written agreements with all third-party service providers who access client data, including cloud backup services, IT contractors, and tax software vendors.
Physical Security Controls
Office access policies, automatic screen locking requirements, full-disk encryption for laptops and mobile devices, and documented secure document destruction procedures.
Completing the Data Theft Response Plan Section
The Data Theft Response Plan is frequently the most overlooked section of the IRS WISP template PDF—and the most consequential when something goes wrong. If your practice experiences a breach, the IRS expects you to act within a defined timeframe and notify specific parties in a specific order. Failing to follow these procedures can result in EFIN suspension and civil penalties on top of any direct harm to your clients.
Immediate Actions Within 24 Hours of Discovery
- Disconnect the affected system from your network to prevent further data exfiltration
- Preserve all system logs and forensic evidence—do not wipe or reformat any device before consulting a cybersecurity professional
- Contact your local IRS Stakeholder Liaison to report the incident and receive guidance on next steps
- Notify your state tax agency's designated security contact
- File a report with the FBI Internet Crime Complaint Center (IC3) at ic3.gov
Client Notification Requirements
Most states mandate notification to affected clients within 30 to 72 hours of breach discovery. Your WISP should identify the specific state breach notification laws applicable to your practice—including requirements for clients in states other than your own—and document the notification template your practice will use. State attorneys general actively enforce these laws against tax and financial service businesses, often independently of any IRS or FTC action.
Recovery and Post-Incident Review
After immediate containment, your response plan should address how you will restore operations from clean backups, verify restored data integrity, and document changes made to your security controls to prevent recurrence. For practices facing ransomware—one of the most frequent attack methods used against tax firms—a tested, offsite backup and recovery procedure is the difference between a recoverable incident and catastrophic data loss. The guide on ransomware protection for tax practices details backup architectures that meet IRS data retention standards. You can also review the IRS WISP requirements for handling W-9 and related forms to ensure your response plan accounts for all document types your practice manages.
Storing, Distributing, and Maintaining Your Completed WISP
Completing the IRS WISP template PDF is not a one-time event. Federal regulations require that your plan be actively implemented, periodically reviewed, and updated when material changes occur in your business. Both the IRS and FTC expect to see evidence that your WISP is a living document—not a file created once, never touched again, and produced under pressure only when a regulator comes calling.
Where to Store Your WISP
Maintain your WISP in at least two locations: a local copy accessible to your designated security coordinator and an offsite or cloud-based copy for disaster recovery. Password-protect the document—it contains details about your security architecture that should not be visible to unauthorized parties. If you store it in a cloud service, ensure that provider appears in your vendor management section, since their own security practices directly affect the confidentiality of your plan.
Employee Acknowledgment and Training Records
Every employee who handles client data should receive a copy of the relevant WISP sections and sign a dated acknowledgment confirming they have read and understood the policies. Retain these records as part of your compliance documentation. If the IRS or FTC ever audits your security program, signed acknowledgments are among the first documents they will request. This practice aligns directly with IRS Publication 4557 guidance on employee training documentation requirements.
When to Update Your WISP
The FTC Safeguards Rule requires updates whenever a material change occurs in your business or technology environment. Events that trigger an immediate update include:
- Hiring a new employee with access to client data
- Changing your tax software, cloud storage provider, or business email platform
- Opening a new office location or establishing a remote work policy for the first time
- Experiencing a security incident or near-miss event of any kind
- Receiving notification that a vendor who holds your client data has experienced a breach of their own
Beyond these event-driven updates, conduct a formal annual review before tax season—the period when targeted attacks against tax professionals intensify measurably. The tax season cybersecurity checklist is a practical companion to your annual WISP review. For the complete regulatory picture underlying your obligations, the FTC Safeguards Rule guide for tax preparers and the IRS Written Information Security Plan overview provide authoritative context that will help you keep your WISP current and defensible.
Get Expert Help Completing Your IRS WISP
Bellator Cyber Guard's tax cybersecurity specialists will assess your current security posture, complete your WISP documentation, and implement the controls required to satisfy IRS Publication 4557 and FTC Safeguards Rule requirements—before your next tax season begins.
Frequently Asked Questions About the IRS WISP Template PDF
The IRS publishes the official sample WISP document on the IRS Tax Professionals WISP page as an editable Word document. Bellator Cyber Guard also provides a free 2026-updated WISP template that incorporates the latest FTC Safeguards Rule requirements alongside the IRS Security Summit framework. Always verify the source before opening any downloaded file—malware disguised as compliance documents is a documented tactic used against tax professionals.
Yes. The WISP requirement under the FTC Safeguards Rule and IRS Publication 4557 applies to all compensated tax professionals who handle client financial data, regardless of how many returns they prepare. The IRS Security Summit created a simplified template specifically for sole practitioners, but having no written plan at all constitutes a federal violation subject to civil penalties.
Operating without a WISP violates the FTC Safeguards Rule, which can result in civil penalties of up to $100,000 per violation. The IRS may suspend your EFIN if you experience a breach and cannot demonstrate that adequate safeguards were in place before the incident. State attorneys general can also pursue enforcement under state-level breach notification and data protection laws, creating layered exposure for unprepared practices.
There is no mandated page count. A sole practitioner's WISP may run 3–5 pages, while a firm with multiple employees, locations, or cloud-based systems may require 15–25 pages or more. Document length matters less than specificity—every section should reflect your actual systems, people, and procedures rather than generic placeholder language.
At minimum, review and update your WISP annually. The FTC Safeguards Rule also requires updates whenever a material change occurs in your practice—such as adding staff, switching tax software platforms, or experiencing a security incident. Many practices tie their annual review to the conclusion of tax season or the start of a new calendar year.
No. Your WISP does not require notarization and is not submitted to the IRS. However, it must be available for inspection if the FTC or a state regulator audits your compliance program. You should also retain signed employee acknowledgments demonstrating that all relevant staff received and reviewed the plan.
A WISP is your overarching written security program—it covers your complete approach to protecting client data, including policies, employee training, technical controls, and vendor management. An incident response plan is one component within the WISP that documents the specific steps your practice will take when a breach or security event occurs. The IRS WISP template PDF includes a dedicated Data Theft Response Plan section that fulfills this function.
No. The IRS sample document is a template, not a completed compliance document. Every placeholder must be replaced with information specific to your practice—your software systems, employee roles, office configuration, vendor relationships, and actual procedures. A generic, uncustomized WISP would not satisfy regulatory requirements and would provide no practical guidance if an incident actually occurred.
If you receive compensation for preparing federal tax returns—regardless of who your clients are—the WISP requirement applies to your practice. Unpaid volunteer preparers may fall outside the FTC's definition of a covered financial institution, but compensated preparers at any volume are covered by the Safeguards Rule.
The IRS Stakeholder Liaison is a regional IRS representative who serves as the first point of contact for tax professionals experiencing a data breach or identity theft event. Your WISP's Data Theft Response Plan must include the direct phone number for your local Stakeholder Liaison so that you can make the required notification within 24 hours of discovering a breach. Contact details are listed on the IRS Stakeholder Liaison local contacts page.
Free Consultation
Need help with IRS compliance?
Our tax cybersecurity specialists can review your security posture and help you get compliant.
