Skip to content

Free 15-minute cybersecurity consultation — no obligation

Book Free Call
Tax27 min read

Free WISP Template: Safeguard Your Business With IRS Compliance

Download a free WISP template for tax professionals. IRS Publication 4557 and FTC Safeguards Rule compliant. Protect taxpayer data and secure your PTIN in 2026.

Free WISP Template: Safeguard Your Business With IRS Compliance — free wisp template

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 that satisfies federal cybersecurity mandates from the Internal Revenue Service, 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 actions against non-compliant preparers, and the FTC has dramatically increased penalties for Safeguards Rule violations—with fines reaching up to $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 their 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 this 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.

WISP Compliance By The Numbers

$100K
Max FTC Fine Per Violation

FTC Safeguards Rule updated penalty structure

100%
PTIN Holders Need a WISP

IRS Publication 4557 requirement

68%
Breaches Involve Humans

2024 Verizon DBIR finding

$12.5B
Annual Cybercrime Losses

FBI IC3 2024 Annual Report

IRS WISP Requirements: The Federal Regulatory Framework

The requirement for a Written Information Security Plan originates from converging federal regulations governing organizations that handle sensitive taxpayer and financial information. Understanding these mandates enables you to build a free WISP template that addresses all applicable requirements simultaneously, eliminating the compliance gaps that create regulatory exposure and professional liability.

IRS Publication 4557: Safeguarding Taxpayer Data

The Internal Revenue Service published Publication 4557 ("Safeguarding Taxpayer Data") providing explicit guidance for tax professionals on protecting client information under federal requirements. This publication emphasizes 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 data handling activities performed.

The IRS explicitly states that a compliant WISP must function as a living document, undergoing regular review and updates 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 guide breaks down each requirement in detail.

FTC Safeguards Rule and GLBA Compliance

The Gramm-Leach-Bliley Act (GLBA), enacted in 1999 with significant amendments implemented in 2021 and 2023, mandates that financial institutions protect customer information through administrative, technical, and physical safeguards. The FTC defines "financial institution" broadly, explicitly encompassing tax preparers, accountants, credit counselors, real estate appraisers, and any business regularly handling 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. Failure to implement any one of these elements can result in enforcement action, fines, and reputational damage that threatens the viability of your practice. These nine elements include:

  1. Designating a Qualified Individual
  2. Conducting risk assessments
  3. Implementing access controls
  4. Encrypting customer data
  5. Training personnel
  6. Monitoring and testing safeguards
  7. Vetting service providers
  8. Maintaining an incident response plan
  9. Reporting to your board or governing body

State-Level Data Protection Laws

Beyond federal requirements, all 50 states now have data breach notification laws, and many have enacted standalone data privacy statutes that impose additional obligations on tax professionals. States including California (CCPA/CPRA), New York (SHIELD Act), Massachusetts (201 CMR 17.00), and Colorado have requirements that go beyond federal minimums. Your free WISP template should include a section addressing the specific state regulations applicable to your practice locations and client base.

2026 Filing Season Compliance Deadline

The IRS requires all tax preparers to have an updated WISP in place by the start of the 2026 filing season. Firms without a compliant Written Information Security Plan face potential PTIN suspension, FTC enforcement action, and fines up to $100,000 per violation. Download your free WISP template now to begin your compliance process.

Essential Components of an Effective Free WISP Template

A thorough free WISP template must include specific documented elements demonstrating your organizational commitment to protecting sensitive taxpayer information. These integrated components create a defensible security posture satisfying regulatory requirements while protecting against the documented 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 documenting where sensitive taxpayer data resides and what threats could compromise confidentiality, integrity, or availability. An effective free WISP template includes structured worksheets to systematically inventory all data locations, systems, and access points. Your asset management and security assessment process should feed directly into this risk inventory.

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 for 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 access by staff, inadequate training, malicious insiders) and external threats (cyberattacks, ransomware, phishing campaigns, malware, natural disasters, physical theft). The MITRE ATT&CK framework provides 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 overseeing your information security program. This person—referred to as the Data Security Coordinator (DSC) by the IRS and Qualified Individual (QI) by the FTC—must possess the knowledge, skills, and authority to implement and maintain security safeguards.

For solo practitioners, the business owner typically serves as the Data Security Coordinator. Larger firms may designate an IT manager, compliance officer, or engage external cybersecurity consultants to fulfill this role. The key requirement is that this individual has both the authority to enforce security policies and the technical competence to evaluate whether controls are working effectively.

The FTC Safeguards Rule specifically allows you to designate a third-party service provider as your Qualified Individual—but your firm retains ultimate responsibility for compliance. If you outsource this role, ensure your contract includes 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+)
  • 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 current vendor inventory and SOC 2 requirements
  • Schedule annual WISP review with defined triggers for interim updates (personnel changes, new systems, 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 represents one of the most important technical safeguards in any WISP implementation. Your free WISP template must document specific policies governing who can access sensitive taxpayer information, under what circumstances, and through what authentication mechanisms.

According to CISA cybersecurity best practices, effective access control frameworks include:

  • Role-based access control (RBAC): Grant permissions based on job function, not individual identity. A seasonal preparer should not have the same system access as a managing partner.
  • Least privilege principle: Users receive only the minimum access necessary to perform their duties. Restrict administrative rights to designated IT personnel.
  • Multi-factor authentication (MFA): Require MFA on all systems containing taxpayer data—tax preparation software, e-filing portals, cloud storage, email, and remote access tools.
  • Unique user credentials: Eliminate shared logins. Every user must have individual credentials with activity logging enabled.
  • Automatic session timeouts: Configure systems to lock after 15 minutes of inactivity, requiring re-authentication.
  • Strong password policies: Enforce minimum 16-character passwords (per updated NIST SP 800-63B guidelines) with complexity requirements, or adopt passphrase-based authentication.

Encryption Standards for Taxpayer Data Protection

The updated FTC Safeguards Rule mandates encryption of customer information both at rest and in transit. Your free WISP template must specify encryption requirements meeting current industry standards:

  • Data at rest: AES-256 encryption for all devices and storage media containing taxpayer information, including full-disk encryption (BitLocker for Windows, FileVault for macOS, LUKS for Linux)
  • Data in transit: TLS 1.3 (preferred) or TLS 1.2 minimum for all network communications transmitting taxpayer data
  • Email encryption: End-to-end encryption (S/MIME, PGP) or encrypted secure portal solutions for transmitting tax documents and financial information to clients
  • Backup encryption: All backup media encrypted using AES-256 with separate key management from production systems
  • Mobile device encryption: Mandatory encryption on all smartphones and tablets used to access tax practice email, client portals, or taxpayer data
  • Removable media controls: Encryption of USB drives and external storage devices, or prohibition of removable media for taxpayer data transfer

For a deeper dive into encryption standards and how they differ from hashing, read our article on hashing vs. encryption.

Key Takeaway

Encryption is non-negotiable under the 2026 FTC Safeguards Rule. Every device, storage medium, and communication channel handling taxpayer data must use AES-256 encryption at rest and TLS 1.2+ in transit. Your free WISP template must specify these standards explicitly—vague references to "encryption" without naming algorithms and key lengths will not satisfy auditors.

Incident Response Plan for Data Breaches

A vital component of any free WISP template is a documented incident response plan specifying how your organization will detect, contain, investigate, and recover from security incidents affecting taxpayer data. The FTC Safeguards Rule includes specific breach notification requirements that took effect in May 2024, mandating notification to affected customers and 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 identifies potential security incidents—automated alerts from Endpoint Detection and Response (EDR) tools, employee reporting procedures, anomaly detection in tax software logs
  • Containment: Immediate steps to isolate affected systems, disable compromised accounts, and prevent further data exposure
  • Investigation: Procedures for determining scope, root cause, and affected records—including engagement of forensic specialists when warranted
  • Notification: Timelines and procedures for notifying affected taxpayers, the IRS (Form 14039), the FTC, state attorneys general, and law enforcement as required by federal and state law
  • Recovery: Steps to restore systems from clean backups, re-secure compromised access points, and resume operations
  • Post-incident review: Documented lessons learned and WISP updates to prevent recurrence

IRS Identity Theft Reporting Requirements

Tax professionals have additional reporting obligations when taxpayer identity theft is suspected. You must submit 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 include these tax-specific notification steps alongside the standard FTC breach notification procedures. Our identity theft prevention guide covers these requirements in full.

Employee Training and Security Awareness Programs

IRS Publication 4557 specifically requires annual security awareness training for all employees who handle 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 security controls your practice can implement.

Your free WISP template must document a training program covering:

  • Recognizing phishing emails, social engineering tactics, and pretexting attacks targeting tax professionals
  • Proper handling, storage, and disposal of taxpayer documents—both physical and electronic
  • Secure use of tax preparation software, e-filing systems, and client communication portals
  • Reporting procedures for suspected security incidents, lost devices, or suspicious communications
  • Password hygiene, MFA usage, and secure remote work practices including VPN requirements for staff working outside the office
  • Physical security awareness: locking workstations, securing paper files, visitor management
  • Recognition of AI-powered phishing and deepfake social engineering attacks—an emerging threat vector in 2026

Document training completion with signed attendance sheets, quiz scores, and certificates of completion. The FTC expects evidence that training actually occurred—not just that a policy exists on paper. Consider conducting simulated phishing exercises quarterly to measure employee resilience and identify individuals who need additional coaching.

Step-by-Step WISP Implementation Guide

1

Download and Customize Your Free WISP Template

Start with a compliant template based on IRS Publication 4557 and the FTC Safeguards Rule. Customize sections to reflect your firm's size, services, and data handling activities.

2

Designate Your Data Security Coordinator

Formally appoint your DSC/Qualified Individual with documented authority. For solo practitioners, this is you. For larger firms, assign someone with both technical competence and enforcement authority.

3

Conduct a Full Risk Assessment

Inventory every system, device, and location where taxpayer data resides. Assess internal and external threats using the MITRE ATT&CK framework as a reference for common attack techniques.

4

Implement Technical Controls

Deploy MFA on all tax software and e-filing portals, enable AES-256 encryption on all devices, configure role-based access controls, and set up endpoint detection and response (EDR) tools.

5

Create Your Incident Response Plan

Document detection, containment, investigation, notification, and recovery procedures. Include IRS Form 14039 filing steps and FTC 60-day notification requirements.

6

Train All Employees

Conduct security awareness training covering phishing recognition, data handling procedures, and incident reporting. Document attendance and test comprehension with quizzes.

7

Test, Document, and Review Annually

Verify all controls are operational, maintain evidence (screenshots, logs, training records), and schedule your annual WISP review with triggers for interim updates.

Maintaining Ongoing WISP Compliance

A Written Information Security Plan is not a one-time documentation project but an ongoing program requiring regular attention, updates, and continuous improvement. Federal regulations specifically 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 process covering:

  • Regulatory changes: Review updates to IRS Publication 4557, Publication 5708, FTC Safeguards Rule amendments, GLBA modifications, and applicable state data protection regulations
  • Threat evolution: Update risk assessments based on emerging attack vectors including AI-powered phishing, deepfake fraud, business email compromise, and new ransomware variants. Monitor IRS Security Summit threat warnings and tax industry breach reports.
  • Technology changes: Document new tax software deployments, cloud service adoption, hardware refreshes, system decommissioning, and network infrastructure modifications
  • Business changes: Address new service offerings (cryptocurrency taxation, international returns), office location changes, mergers, partnerships, and remote work expansion
  • Personnel changes: Update the designated Data Security Coordinator if changed, revise access controls for role changes, document new employee onboarding and departing employee offboarding procedures
  • Incident analysis: Incorporate lessons learned from security incidents, near-misses, audit findings, and industry breach case studies
  • Control effectiveness: Assess whether implemented safeguards achieved intended security objectives through penetration testing, vulnerability scanning, and monitoring results

Common WISP Implementation Mistakes to Avoid

Learning from implementation challenges faced by other tax practices can help you avoid costly delays and compliance gaps when deploying your free WISP template.

Mistake #1: Creating documentation without actual implementation. The most frequent WISP failure occurs when tax professionals create thorough documentation but fail to actually implement the described controls. IRS auditors and FTC examiners identify this disconnect by testing whether documented controls are operational, requesting evidence of implementation, or interviewing employees about actual practices. Avoid this by testing each control before documenting it as "implemented," using present-tense language describing what you actually do, creating implementation checklists with specific completion dates, and conducting quarterly internal audits verifying controls remain operational year-round.

Mistake #2: Overlooking third-party vendor risk. Your security is only as strong as your weakest vendor. Tax software providers, cloud storage services, document management platforms, and IT support providers all represent potential entry points for attackers. Address third-party risk by maintaining a current vendor inventory, requiring SOC 2 attestations, including security requirements in contracts, and monitoring vendor security incidents.

Mistake #3: Ignoring physical security controls. Many tax professionals focus exclusively on digital safeguards while neglecting physical security. Paper tax returns, printed W-2s, and client correspondence contain the same sensitive data as digital files. Your WISP must document locked filing cabinets, clean desk policies, visitor access procedures, and secure document destruction (cross-cut shredding or professional destruction services).

Mistake #4: Failing to address remote work. With many tax professionals now working remotely at least part-time, your free WISP template must include remote work security policies covering home network security, VPN requirements, prohibited use of public Wi-Fi for tax work, and physical security of devices and documents in home offices.

Bottom Line

Your WISP must match reality. IRS auditors and FTC examiners don't just read your documentation—they test whether controls are actually operational. A beautifully written WISP that describes controls you haven't implemented is worse than no WISP at all, because it demonstrates awareness of requirements paired with deliberate non-compliance.

The Business Case for a Compliant WISP

Beyond regulatory compliance, a properly implemented free WISP template delivers tangible business value that strengthens your tax practice in multiple ways. The FBI's Internet Crime Complaint Center (IC3) 2024 report documented $12.5 billion in cybercrime losses—with tax-related identity theft and business email compromise among the fastest-growing categories. Businesses with formal security plans experience significantly fewer successful cyberattacks and recover faster when incidents do occur.

A compliant WISP also serves as a competitive differentiator. As taxpayers become more aware of data breach risks, demonstrating a documented security program builds client trust and can justify premium service pricing. Many corporate and institutional clients now require their tax preparers to provide evidence of a Written Information Security Plan before engaging services—particularly firms subject to SOC 2 or NIST compliance themselves.

Cyber Insurance and Your WISP

For practices carrying cyber insurance, a compliant WISP is increasingly a prerequisite for coverage. Insurers are tightening underwriting requirements, and firms without documented security programs face higher premiums (30–50% above market rates), coverage exclusions for incidents involving unimplemented controls, claim denials following a breach if the WISP doesn't match actual practices, and policy non-renewal at the end of the coverage term.

A free WISP template provides the essential foundation, but the real value comes from consistent implementation and ongoing commitment. Cybersecurity for tax professionals is not a destination but a continuous process of improvement, adaptation, and vigilance. Regular policy updates, continuous monitoring, and annual reviews will determine your long-term success in protecting taxpayer data and maintaining regulatory compliance.

Need Help Implementing Your WISP?

Our security team has helped thousands of tax professionals create compliant Written Information Security Plans that satisfy IRS Publication 4557 and FTC Safeguards Rule requirements.

Protect Your Tax Practice — Get Your Free WISP Template

Download our IRS-compliant WISP template and get a free cybersecurity assessment from our team. 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

Yes—a free WISP template can satisfy PTIN renewal compliance requirements if you fully customize it to reflect your firm's actual security practices and implement every documented control. The IRS does not mandate a specific format or paid product. What matters is that your Written Information Security Plan addresses the requirements outlined in IRS Publication 4557, is proportionate to your practice size, and reflects controls you have actually deployed—not just documented on paper.

Federal regulations require a formal WISP review at least once per year. However, you must also update your plan whenever significant changes occur: new employees or departures, new tax software deployments, office relocations, security incidents, or changes to federal or state regulations. The IRS expects your WISP to function as a living document that evolves with your practice.

Non-compliance carries multiple penalty categories. The FTC can impose fines up to $100,000 per violation under the updated Safeguards Rule penalty structure. The IRS can suspend or revoke your PTIN, effectively ending your ability to prepare tax returns. State attorneys general can pursue additional fines under state data protection laws. Beyond regulatory penalties, a data breach without a compliant WISP exposes you to civil lawsuits from affected clients and significant reputational damage.

You do not need a completely separate WISP for each location, but your plan must address location-specific risks and controls. A single WISP can cover multiple offices if it includes appendices or sections documenting the physical security measures, local network configurations, personnel assignments, and state-specific regulatory requirements for each location. See our WISP checklist for CPA firms for multi-location guidance.

A WISP is your complete written security program covering risk assessment, access controls, encryption, training, vendor management, and ongoing compliance. An incident response plan is one component within the WISP that specifically documents how your firm will detect, contain, investigate, and recover from a security breach. Think of the WISP as the full playbook and the incident response plan as one chapter focused on what to do when something goes wrong.

Yes, a single WISP can cover both tax preparation and accounting services, since both involve handling sensitive financial information under similar regulatory frameworks. However, your plan should address the specific data types, software systems, and compliance requirements unique to each service line. Accounting services may involve additional requirements such as SOC 2 compliance for client audits or industry-specific regulations like HIPAA if you handle medical practice accounting.

Maintain a compliance evidence package including your current WISP document with revision history, completed risk assessment worksheets, employee training records with signed attendance sheets, system configuration screenshots showing controls in place (MFA enabled, encryption active), vendor contracts with security requirements, incident response test results, and audit logs showing access controls are enforced. The key is demonstrating that documented controls are actually operational—not just written down.

Every firm that holds a PTIN and handles taxpayer data needs a WISP, regardless of size. This includes solo practitioners, seasonal preparers, and large multi-office firms. IRS Publication 4557 explicitly states that the WISP requirement applies to all tax professionals—the plan's complexity should be proportionate to your firm's size and data handling activities, but the requirement itself has no minimum threshold.

Absolutely. If you use cloud-based tax preparation software (Drake Tax, Lacerte, ProConnect, UltraTax CS, or others), your WISP must document the security controls surrounding that usage: access credentials and MFA requirements, data transmission encryption, vendor security certifications, backup procedures, and your process for vetting the provider's security posture. Review our guide on tax preparation software security for specific vendor considerations.

There is no required page count. A solo practitioner's WISP might be 15–25 pages, while a multi-office firm with complex operations could have 50+ pages plus appendices. Focus on substance over length: every section should contain specific, actionable policies with named responsible parties and measurable standards. A concise WISP that accurately describes implemented controls is far more valuable—and compliant—than a lengthy document full of generic language that doesn't reflect your actual practices.

Share

Share on X
Share on LinkedIn
Share on Facebook
Send via Email
Copy URL
(800) 492-6076
Share

Schedule

Need help with IRS compliance?

Our tax cybersecurity specialists can review your security posture and help you get compliant.

Protect your tax practice from cyber threats

Schedule a free consultation to assess your firm's security posture.