
Free WISP Template: What Tax Professionals Need to Know in 2026
A free WISP template gives tax professionals and financial service providers a pre-structured Written Information Security Plan (WISP) that satisfies federal cybersecurity mandates from the Internal Revenue Service (IRS), the Federal Trade Commission (FTC) Safeguards Rule, and the Gramm-Leach-Bliley Act (GLBA) — without building documentation from scratch. Every tax professional holding a Preparer Tax Identification Number (PTIN) must implement and maintain a compliant WISP as a mandatory condition for credential renewal and continued professional practice.
Organizations handling nonpublic personal information — including accountants, financial advisors, credit counselors, and related service providers — face identical compliance requirements under federal law. The IRS Security Summit has intensified enforcement against non-compliant preparers, and the FTC has raised penalties for Safeguards Rule violations to as much as $100,000 per violation under the updated penalty structure. A properly implemented free WISP template is the baseline requirement for operating a legitimate tax practice in 2026.
According to IRS Publication 4557, every tax preparer who handles taxpayer data must maintain a written security plan proportionate to firm size and data-handling activities. Whether you are a solo practitioner filing 50 returns or a multi-office firm processing thousands, the requirement applies equally — and a free WISP template provides the structured foundation you need to comply. For a step-by-step walkthrough, see our guide on how to create a WISP, or download our ready-to-use free WISP template for 2026.
WISP Compliance By The Numbers
FTC Safeguards Rule enforcement
FBI IC3 Annual Report
Verizon 2024 DBIR
Effective May 2024
IRS WISP Requirements: The Federal Regulatory Framework
The requirement for a Written Information Security Plan comes from converging federal regulations governing organizations that handle sensitive taxpayer and financial information. Understanding these mandates lets you build a free WISP template that addresses every applicable requirement at once, closing the compliance gaps that create regulatory exposure and professional liability.
IRS Publication 4557: Safeguarding Taxpayer Data
The IRS published Publication 4557 ("Safeguarding Taxpayer Data") to give tax professionals explicit guidance on protecting client information under federal requirements. The publication states that all tax professionals holding a PTIN must maintain a Written Information Security Plan appropriate to their practice size, operational complexity, and the nature of the data-handling activities they perform.
The IRS is direct that a compliant WISP must function as a living document — reviewed and updated regularly to address emerging threats, changing business operations, new technology deployments, and evolving regulatory requirements. Static documentation created once and never revised fails to meet federal compliance standards. Publication 4557 also cross-references IRS Publication 5708 (the IRS's own WISP template guidance), NIST SP 800-171 for protecting controlled unclassified information, and the NIST Cybersecurity Framework 2.0 as the recommended risk-management structure for tax practices of all sizes. Our IRS Publication 4557 compliance guide breaks down each requirement in detail.
FTC Safeguards Rule and GLBA Compliance
The Gramm-Leach-Bliley Act, enacted in 1999 with significant amendments in 2021 and 2023, requires financial institutions to protect customer information through administrative, technical, and physical safeguards. The FTC defines "financial institution" broadly, explicitly including tax preparers, accountants, credit counselors, real estate appraisers, and any business that regularly handles nonpublic personal information in connection with financial services.
The FTC Safeguards Rule mandates nine specific security elements that every compliant free WISP template must address. Failing to implement any one of them can trigger enforcement, fines, and reputational damage that threatens the viability of your practice. Our breakdown of the FTC Safeguards Rule for tax preparers maps each element to practical controls. The nine required elements are:
- Designate a Qualified Individual to run the program
- Conduct a written risk assessment
- Implement access controls
- Encrypt customer data
- Train personnel
- Monitor and test safeguards
- Vet service providers
- Maintain a written incident response plan
- Report to your board or governing body
State-Level Data Protection Laws
Beyond federal requirements, all 50 states have data breach notification laws, and many have enacted standalone privacy statutes that add obligations for tax professionals. California (CCPA/CPRA), New York (SHIELD Act), Massachusetts (201 CMR 17.00), and Colorado all impose requirements that go beyond federal minimums. Your free WISP template should include a section addressing the specific state regulations that apply to your practice locations and client base.
2026 Filing Season Compliance Deadline
The IRS expects every PTIN holder to have a current, implemented WISP in place at the start of the 2026 filing season. Preparers who attest to a WISP they cannot produce — or whose documentation does not match actual practices — risk PTIN suspension, EFIN revocation, and FTC enforcement. Review and update your plan before you file your first 2026 return.
Essential Components of an Effective Free WISP Template
A thorough free WISP template must include specific documented elements that demonstrate your commitment to protecting sensitive taxpayer information. Together, these components create a defensible security posture that satisfies regulators while protecting against the real-world threats targeting tax professionals today.
Risk Assessment and Taxpayer Data Inventory
The foundation of any Written Information Security Plan is a thorough risk assessment that documents where sensitive taxpayer data lives and what threats could compromise its confidentiality, integrity, or availability. An effective free WISP template includes structured worksheets to systematically inventory every data location, system, and access point. For each location where taxpayer data resides, document the specific types of personally identifiable information stored:
- Social Security numbers and Taxpayer Identification Numbers (TINs)
- Financial account data, including bank routing and account numbers
- W-2, 1099, and other income-reporting forms
- Authentication credentials for tax software and e-filing systems
- Medical information relevant to HSA and medical-deduction documentation
- Dependent details and family-relationship records
- Electronic Filing Identification Numbers (EFINs) and CAF numbers
Assess both internal threats (employee errors, unauthorized staff access, inadequate training, malicious insiders) and external threats — ransomware, phishing campaigns, malware, natural disasters, and physical theft. The MITRE ATT&CK framework offers a structured taxonomy of adversary tactics that can inform your threat assessment — particularly techniques like T1566 (Phishing), T1486 (Data Encrypted for Impact), and T1078 (Valid Accounts) that are commonly used against tax practices.
Data Security Coordinator and Qualified Individual Designation
Both IRS Publication 4557 and the FTC Safeguards Rule require formal designation of a responsible individual to oversee your information security program. This person — the Data Security Coordinator (DSC) under IRS terminology and the Qualified Individual (QI) under the FTC — must have the knowledge, skills, and authority to implement and maintain security safeguards.
For solo practitioners, the business owner typically serves as the DSC. Larger firms may designate an IT manager, a compliance officer, or an external cybersecurity partner. The key requirement is that this individual has both the authority to enforce security policies and the technical competence to judge whether controls are actually working. The Safeguards Rule lets you name a third-party service provider as your Qualified Individual — but your firm keeps ultimate responsibility for compliance. If you outsource the role, make sure your contract spells out reporting requirements, defined response times, and clear accountability for control failures.
Essential WISP Components Checklist
- Designate a Data Security Coordinator (DSC) / Qualified Individual (QI) with documented authority and contact information
- Complete a written risk assessment covering all systems that store or process taxpayer data
- Inventory all data locations: servers, workstations, cloud services, mobile devices, paper files, and backup media
- Document access control policies with role-based permissions for every system containing taxpayer data
- Implement and document multi-factor authentication on all tax software and e-filing portals
- Specify encryption standards for data at rest (AES-256) and data in transit (TLS 1.2 or higher)
- Create a written incident response plan with defined roles, notification timelines, and escalation procedures
- Establish an annual employee security awareness training program with documented attendance
- Document third-party vendor risk management procedures with a current vendor inventory and SOC 2 requirements
- Schedule an annual WISP review with defined triggers for interim updates such as personnel changes, new systems, or incidents
- Maintain evidence of all controls: configuration screenshots, audit logs, training records, test results, and backup verification reports
- Document physical security controls: locked offices, clean desk policies, visitor logs, and secure document disposal procedures
Access Control and Encryption Requirements
Access Control Policies and Authentication
Access control is one of the most important technical safeguards in any WISP. Your free WISP template must document who can access sensitive taxpayer information, under what circumstances, and through what authentication mechanisms. According to CISA cybersecurity best practices, an effective access-control framework includes:
- Role-based access control (RBAC): Grant permissions by job function, not individual identity. A seasonal preparer should not have the same system access as a managing partner.
- Least privilege: Give users only the minimum access needed to do their work, and restrict administrative rights to designated IT personnel.
- Multi-factor authentication (MFA): Require MFA on every system containing taxpayer data — tax software, e-filing portals, cloud storage, email, and remote-access tools.
- Unique credentials: Eliminate shared logins. Every user gets individual credentials with activity logging enabled.
- Automatic session timeouts: Lock systems after 15 minutes of inactivity, requiring re-authentication.
- Strong password policies: Enforce minimum 16-character passwords per updated NIST SP 800-63B guidelines, or adopt passphrase-based authentication backed by a password manager.
Encryption Standards for Taxpayer Data Protection
The updated FTC Safeguards Rule requires encryption of customer information both at rest and in transit. Your free WISP template must specify encryption that meets current industry standards:
- Data at rest: AES-256 for all devices and storage media holding taxpayer information, including full-disk encryption (BitLocker for Windows, FileVault for macOS, LUKS for Linux).
- Data in transit: TLS 1.3 preferred, TLS 1.2 minimum, for all network communications carrying taxpayer data.
- Email encryption: End-to-end encryption (S/MIME, PGP) or an encrypted secure portal for transmitting tax documents and financial information to clients.
- Backup encryption: AES-256 on all backup media, with key management kept separate from production systems.
- Mobile device encryption: Mandatory on every phone or tablet used to reach practice email, client portals, or taxpayer data.
- Removable media controls: Encryption of USB drives and external storage, or an outright prohibition on removable media for taxpayer data.
For a deeper look at how encryption differs from hashing — and why it matters for your WISP — read our article on hashing vs. encryption. A secure client portal for sensitive tax data often satisfies both the in-transit and email-encryption requirements in a single tool.
Why This Matters
Documentation without implementation is the most common WISP failure. The FTC and IRS test whether your stated controls — MFA, AES-256 encryption, access logging — are actually operational. Write your WISP in the present tense to describe what you genuinely do, and keep dated evidence (screenshots, logs, training records) to prove it during an examination.
Incident Response Plan for Data Breaches
A vital part of any free WISP template is a documented incident response plan describing how your organization detects, contains, investigates, and recovers from security incidents affecting taxpayer data. The FTC Safeguards Rule breach-notification provisions took effect in May 2024 and require notice to the FTC within 60 days when unauthorized access to unencrypted information of 500 or more consumers occurs. Your incident response procedures must address:
- Detection and identification: How your firm spots potential incidents — automated alerts from Endpoint Detection and Response (EDR) tools, employee reporting procedures, and anomaly detection in tax-software logs.
- Containment: Immediate steps to isolate affected systems, disable compromised accounts, and prevent further exposure.
- Investigation: Procedures for determining scope, root cause, and affected records — including engaging forensic specialists when warranted.
- Notification: Timelines and procedures for notifying affected taxpayers, the IRS, the FTC, state attorneys general, and law enforcement as required.
- Recovery: Restoring systems from clean backups, re-securing compromised access points, and resuming operations.
- Post-incident review: Documented lessons learned and WISP updates to prevent recurrence.
For a tax-specific playbook with roles and timelines, see our incident response plan for tax practices.
IRS Identity Theft Reporting Requirements
Tax professionals carry extra reporting duties when client identity theft is suspected. You must file Form 14039 (Identity Theft Affidavit) on behalf of affected clients, notify the IRS e-Services help desk if your EFIN is compromised, and report the incident to local law enforcement and the FBI's Internet Crime Complaint Center (IC3). Your free WISP template should fold these tax-specific steps into the standard FTC breach-notification flow. Our identity theft prevention resources for tax pros cover these requirements in full.
Employee Training and Security Awareness Programs
IRS Publication 4557 specifically requires annual security awareness training for every employee who handles taxpayer data. The 2024 Verizon Data Breach Investigations Report found that 68% of breaches involved a human element — making training one of the most cost-effective controls your practice can deploy. Your free WISP template must document a training program covering:
- Recognizing phishing emails, social engineering, and pretexting attacks aimed at tax professionals
- Proper handling, storage, and disposal of taxpayer documents — physical and electronic
- Secure use of tax software, e-filing systems, and client portals
- Reporting procedures for suspected incidents, lost devices, or suspicious messages
- Password hygiene, MFA usage, and secure remote work including VPN requirements for off-site staff
- Physical security: locking workstations, securing paper files, and visitor management
- Recognition of AI-powered phishing and deepfake social engineering — an emerging threat vector in 2026
Document completion with signed attendance sheets, quiz scores, and certificates. The FTC expects evidence that training actually happened — not just a policy on paper. Consider quarterly simulated phishing exercises to measure resilience and identify staff who need extra coaching. A structured security awareness training program makes this evidence easy to maintain.
Step-by-Step WISP Implementation Guide
Designate Your Data Security Coordinator
Name a DSC / Qualified Individual in writing, with the authority and technical competence to run the program. Record their contact details and responsibilities in the WISP.
Inventory Data and Conduct a Risk Assessment
Map every location where taxpayer data lives — servers, workstations, cloud apps, mobile devices, and paper files — then assess internal and external threats against each.
Implement Access Controls and MFA
Apply role-based access and least privilege, eliminate shared logins, and turn on multi-factor authentication for tax software, e-filing portals, email, and remote access.
Deploy Encryption Across the Board
Enable AES-256 full-disk encryption at rest and TLS 1.2+ in transit, encrypt backups and mobile devices, and adopt a secure portal for client document exchange.
Build Your Incident Response Plan
Define detection, containment, investigation, notification, and recovery steps — including IRS Form 14039 and FTC 60-day notification requirements.
Train Staff and Document It
Run annual security awareness training with signed attendance and quiz results, reinforced by quarterly simulated phishing tests.
Review, Test, and Update Annually
Schedule a yearly WISP review with interim triggers for new systems, personnel changes, or incidents, and keep dated evidence that every control is operational.
Maintaining Ongoing WISP Compliance
A Written Information Security Plan is not a one-time documentation project but an ongoing program that needs regular attention, updates, and continuous improvement. Federal regulations require annual reviews at minimum, with updates triggered by significant business changes, emerging threats, security incidents, or regulatory modifications.
Annual Review and Update Requirements
Your free WISP template should include a structured annual review covering:
- Regulatory changes: Updates to IRS Publication 4557, Publication 5708, FTC Safeguards Rule amendments, GLBA modifications, and applicable state laws.
- Threat evolution: Refreshed risk assessments reflecting AI-powered phishing, deepfake fraud, business email compromise, and new ransomware variants, informed by IRS Security Summit warnings and industry breach reports.
- Technology changes: New tax software, cloud adoption, hardware refreshes, system decommissioning, and network changes.
- Business changes: New service lines (cryptocurrency taxation, international returns), office moves, mergers, partnerships, and remote-work expansion.
- Personnel changes: An updated DSC where needed, revised access for role changes, and documented onboarding and offboarding procedures.
- Control effectiveness: Whether safeguards met their objectives, validated through penetration testing, vulnerability scanning, and monitoring.
Common WISP Implementation Mistakes to Avoid
Learning from the challenges other practices have faced helps you avoid costly delays and compliance gaps.
Mistake #1 — Documentation without implementation. The most frequent failure is creating thorough documentation while never deploying the described controls. Auditors test for this by requesting evidence and interviewing employees. Test each control before you call it "implemented," use present-tense language describing what you actually do, and run quarterly internal audits.
Mistake #2 — Overlooking third-party vendor risk. Your security is only as strong as your weakest vendor. Tax software, cloud storage, document management, and IT support are all potential entry points. Maintain a current vendor inventory, require SOC 2 attestations, write security requirements into contracts, and monitor vendor incidents.
Mistake #3 — Ignoring physical security. Paper returns, printed W-2s, and client correspondence hold the same sensitive data as digital files. Document locked filing cabinets, clean-desk policies, visitor procedures, and secure destruction such as cross-cut shredding.
Mistake #4 — Failing to address remote work. With many preparers now working remotely part of the year, your free WISP template must cover home network security, VPN requirements, a ban on public Wi-Fi for tax work, and physical security of devices and documents in home offices. Our guide to choosing a VPN can help you set that standard.
The Business Case for a Compliant WISP
Beyond regulatory compliance, a properly implemented free WISP template delivers tangible business value. The FBI's Internet Crime Complaint Center documented $12.5 billion in cybercrime losses in 2024 — with tax-related identity theft and business email compromise among the fastest-growing categories. Firms with formal security plans suffer fewer successful attacks and recover faster when incidents occur.
A compliant WISP is also a competitive differentiator. As taxpayers grow more aware of breach risk, a documented security program builds client trust and can justify premium pricing. Many corporate and institutional clients now require their preparers to provide evidence of a Written Information Security Plan before engaging services — especially firms subject to SOC 2 or NIST compliance themselves. If you serve CPA or accounting clients, our cybersecurity guidance for accounting and CPA firms shows how a WISP fits a broader program.
Cyber Insurance and Your WISP
For practices carrying cyber insurance, a compliant WISP is increasingly a prerequisite for coverage. As underwriting tightens, firms without documented security programs face premiums 30–50% above market, coverage exclusions for incidents involving unimplemented controls, claim denials when the WISP does not match actual practice, and non-renewal at the end of the term. Our overview of cyber insurance requirements for small businesses details what underwriters now expect.
A free WISP template provides the essential foundation, but the real value comes from consistent implementation and ongoing commitment. Cybersecurity for tax professionals is a continuous process of improvement, adaptation, and vigilance — and regular updates, monitoring, and annual reviews will determine your long-term success in protecting taxpayer data and maintaining compliance.
Need Help Implementing Your WISP?
Our security team has helped thousands of tax professionals turn a WISP template into fully implemented, audit-ready controls that satisfy IRS Publication 4557 and the FTC Safeguards Rule.
Bottom Line
Every PTIN holder who touches taxpayer data needs an implemented WISP in 2026. A free WISP template gives you the structure to satisfy IRS Publication 4557, the FTC Safeguards Rule, and GLBA — but compliance depends on deploying the controls it describes, keeping evidence, and reviewing the plan at least annually.
Protect Your Tax Practice — Get Your Free WISP Template
Download our IRS-compliant WISP template and get a free cybersecurity assessment. We'll identify gaps in your current security posture and build a plan that satisfies IRS Publication 4557 and FTC Safeguards Rule requirements.
Frequently Asked Questions
A free WISP template gives you the correct structure, but it only satisfies PTIN renewal requirements once you fully customize it to your practice and implement the controls it describes. The IRS expects a living document tailored to your firm size, systems, and data-handling activities — not a blank form. Complete every section, deploy the safeguards (MFA, encryption, access controls), and keep evidence that they are operational.
At minimum, review and update your WISP annually. You should also update it whenever a significant change occurs: a new tax software deployment, an office move, a merger, a change in your Data Security Coordinator, a security incident, or an amendment to IRS or FTC requirements. Document the date of each review and the changes made.
Non-compliance can lead to PTIN suspension, EFIN revocation, and FTC enforcement with penalties reaching $100,000 per violation under the updated Safeguards Rule structure. A breach involving an inadequate or unimplemented WISP can also trigger state notification penalties, civil liability, denial of cyber insurance claims, and significant reputational harm.
No. One WISP can cover a multi-office firm, but it must address the specific systems, data flows, and physical security controls at each location. Document location-specific details — such as who serves as the on-site security contact and how paper records are secured — within a single, unified plan rather than maintaining disconnected documents.
A WISP is the overarching security program covering risk assessment, access controls, encryption, training, and vendor management. An incident response plan is one required component of the WISP that specifies how you detect, contain, investigate, notify, and recover from a security incident. The incident response plan lives inside the WISP, not separate from it.
Yes. Both tax preparers and accountants qualify as financial institutions under GLBA and the FTC Safeguards Rule, so the same framework applies. Customize the data inventory and risk assessment to reflect the full range of services you provide — including bookkeeping, payroll, and advisory work — since each may involve different systems and data types.
Produce the written plan plus evidence that its controls are operational: configuration screenshots, MFA settings, encryption confirmations, access logs, training attendance records and quiz scores, vendor SOC 2 attestations, backup verification, and dated records of your annual reviews. Examiners test whether documented controls actually exist, so present-tense, evidence-backed documentation is essential.
Every firm, regardless of size. The requirement applies to solo practitioners filing a handful of returns just as it does to multi-office firms processing thousands. The plan must be proportionate to your size and complexity, but no PTIN holder who handles taxpayer data is exempt.
Yes. Cloud-based tax software, document storage, and client portals all process or store taxpayer data and must be covered. Document the vendor's security posture (require a SOC 2 report), enable MFA, confirm encryption in transit and at rest, and include the service in your access-control and vendor-risk sections.
There is no required length. A solo practitioner's WISP may run 10–20 pages, while a larger firm's plan can be considerably longer. Quality matters more than length: the document must address all nine FTC Safeguards Rule elements and IRS Publication 4557 expectations, accurately describe your implemented controls, and be detailed enough to guide staff and satisfy an examiner.
Schedule
Need help with IRS compliance?
Our tax cybersecurity specialists can review your security posture and help you get compliant.



