Skip to main content
Financial Services

IRS Publication 5708: How Tax and CPA Firms Build a WISP

Ken Satkunam, CISM
Ken Satkunam, CISM

Published · 10 min read

IRS Publication 5708: How Tax and CPA Firms Build a WISP

IRS Publication 5708 is the IRS and Security Summit guide that shows tax and accounting firms how to build a written information security plan (WISP), the document the FTC Safeguards Rule requires every paid tax preparer to keep. It explains what the plan must cover, who owns it, and how to scale it from a sole practitioner to a multi-partner CPA firm.

Key takeaways

  • Publication 5708 (Rev. 8-2024) states that tax and accounting professionals are financial institutions under the Gramm-Leach-Bliley Act and the FTC Safeguards Rule, regardless of size, and must keep a written, accessible WISP.
  • The publication's outline has seven parts: objectives and scope, a qualified individual, a risk assessment, a hardware inventory, documented safety measures, an implementation clause, and attachments.
  • Form W-12 (Rev. October 2026), the PTIN application and renewal form, asks every preparer on line 11 to acknowledge that the law requires a WISP.
  • A WISP built only from the IRS sample template can still miss Safeguards Rule elements such as encryption, logging, a written incident response plan and testing, so map it against 16 CFR 314.4.

What is IRS Publication 5708?

Publication 5708, titled "Creating a Written Information Security Plan for your Tax & Accounting Practice," is a free IRS guide with a fill-in sample WISP. The current version is Rev. 8-2024. It was prepared by the Security Summit, the IRS partnership with state tax agencies and the tax industry that fights identity theft and refund fraud.

The guide includes an outline, a sample template, detail on each section, six sample attachments and a glossary. The IRS says the sample is a starting point, not a substitute for a plan built around your own firm. It pairs with IRS Publication 4557, Safeguarding Taxpayer Data (Rev. 6-2024): Publication 4557 describes the safeguards, and Publication 5708 shows how to write them down.

Is a WISP legally required for tax and CPA firms?

Yes. Publication 5708 says plainly that "the law requires you to have one." Under the GLBA and the FTC Safeguards Rule, tax and accounting professionals are treated as financial institutions regardless of size, and the rule requires them to implement and maintain a written information security program.

The underlying regulation is the FTC's Standards for Safeguarding Customer Information, 16 CFR Part 314. Section 314.4 lists the required elements, and the WISP is where a firm documents how it meets each one.

The IRS also builds the requirement into PTIN administration. Line 11 of Form W-12 (Rev. October 2026), "Data Security Responsibilities," reads: "I am aware that paid tax return preparers are required by law to create and maintain a written information security plan that provides data and system security protections for all taxpayer information." The IRS PTIN page says 2027 PTIN applications and renewals are now being processed, so every preparer renewing this season will see that question.

What sections does a Publication 5708 WISP include?

Publication 5708 lists seven "bare essentials" and tells firms to include every required element while scaling the depth to the size and type of the practice. The outline is:

  1. Objectives, purpose and scope. What the plan protects and what it does not cover. The sample's definition of PII covers Social Security numbers, income and tax data and account numbers.
  2. A qualified individual. The person who coordinates the program, plus a list of authorized users, their access levels and their responsibilities.
  3. Risk assessment. The types of information the office handles, the ways it could be lost, internally or externally, and how the firm will monitor and test for new risks.
  4. Hardware inventory. Every device that touches taxpayer data, its physical location and what it stores or processes.
  5. Documented safety measures. Policies for data collection and retention, disclosure, network protection, user access, electronic data exchange, Wi-Fi, remote access, connected devices and reportable incidents, plus an employee code of conduct.
  6. An implementation clause. The statement that puts the plan into effect, dated and signed by the owner or principal officer and the DSC.
  7. Attachments. Supporting documents that change more often than the core plan.

The six sample attachments are: A, record retention policies; B, rules of behavior for safeguarding client PII; C, security breach procedures and notifications; D, employee and contractor acknowledgment; E, a hardware inventory of devices containing PII; and F, a list of employees authorized to access PII.

Who should own the WISP inside a tax or accounting firm?

Publication 5708 asks firms to name two roles: a Data Security Coordinator (DSC) and a Public Information Officer (PIO). In firms with two or more practitioners, the guide recommends that these be different people, because both have work to do at the same time during an incident.

  • Data Security Coordinator: runs the program day to day, from fixing weaknesses to training staff and checking third-party providers.
  • Public Information Officer: the "one voice" for client notifications and outside statements.

The Safeguards Rule calls the program owner the Qualified Individual. Under 16 CFR 314.4(a), that person may be an employee, or may work for an affiliate or a service provider. A firm that uses a provider keeps responsibility for compliance and must name a senior staff member to oversee that person. Many small firms fill the role with an outside virtual CISO while a partner keeps oversight.

How do you build a WISP step by step?

Start with an inventory and a risk assessment, then write the policies, then sign and train. A practical sequence that follows the Publication 5708 outline looks like this:

  1. Map your data. List every type of information you hold, on paper and electronically: client PII, employee records and business financials. Note where each lives.
  2. Inventory devices. Record each laptop, desktop, phone, printer, router and modem, where it is, who uses it and what it processes.
  3. Assess risks in writing. Consider theft of paper or electronic files, remote account takeover, accidental disclosure and loss from fire or storms. Under 16 CFR 314.4(b), the written risk assessment must include criteria for rating risks and say how each risk will be reduced or accepted.
  4. Document your safeguards. Write down the controls you actually run, such as multi-factor authentication for remote access, encryption of files containing PII, a separate guest Wi-Fi network and encrypted remote access tools.
  5. Name the roles and the review date. Fill in the DSC, the PIO and an annual review date.
  6. Sign, train and file. Have staff sign the acknowledgment in Attachment D at each annual training. Store the WISP in a readable format such as PDF or Word, and keep a copy offsite or in the cloud.

A cybersecurity risk assessment is the fastest way to complete the first three steps with evidence instead of guesses, and it gives the WISP a defensible starting point.

What should the WISP say about data breaches?

Attachment C should list who you will notify if client data is stolen or lost. Publication 5708's sample names the IRS Stakeholder Liaison, the state attorney general, state tax agencies, the FBI's Internet Crime Complaint Center, the FTC, law enforcement, your tax software vendor, your insurer, legal counsel and affected clients.

The FTC notice has a firm deadline. Under 16 CFR 314.4(j), a firm that discovers a notification event involving the information of at least 500 consumers must notify the FTC as soon as possible and no later than 30 days after discovery, using the FTC's online form. This came from a final rule effective May 13, 2024.

The sample procedures also suggest practical checks, such as reviewing your EFIN activity report in IRS e-Services to see whether more returns were filed on your EFIN than you transmitted. Our FTC Safeguards Rule compliance guide covers notification in more depth.

Where do sample-template WISPs usually fall short?

The most common gap is a plan that copies the IRS template but does not map to the Safeguards Rule element by element. Section 314.4 asks for more than the template's summary, and a plan should address each item:

  • Encryption of customer information in transit over external networks and at rest, or compensating controls approved by the Qualified Individual.
  • Secure disposal of customer information no later than two years after it was last used for the customer, unless it must be kept for business or legal reasons.
  • Change management procedures, and monitoring and logging of authorized users' activity.
  • Continuous monitoring, or annual penetration testing plus vulnerability assessments at least every six months.
  • A written incident response plan covering roles, communications, remediation and lessons learned.
  • A written report from the Qualified Individual to the board or a senior officer at least annually.

Under 16 CFR 314.6, firms that hold customer information on fewer than 5,000 consumers are exempt from four provisions: the written risk assessment, the penetration testing and vulnerability assessment schedule, the written incident response plan and the annual board report. They still need the rest of the program, including the WISP itself.

The other common gap is a plan nobody updates. Publication 5708 calls the WISP an evergreen document; one that names a departed employee as DSC will not help in an incident.

What else do tax and CPA firms ask about building a WISP?

Does a sole practitioner need a WISP?

Yes. Publication 5708 says there is no one-size-fits-all WISP and that a sole practitioner can use a more abbreviated plan than a 10-partner firm. The written plan is still required.

Do I submit my WISP to the IRS with my PTIN renewal?

Form W-12 line 11 is a yes or no acknowledgment that you know the law requires a WISP. The form does not ask you to attach the plan, but you should be able to produce it if asked.

Can our IT provider act as our Qualified Individual?

Yes, 16 CFR 314.4(a) allows a service provider to serve as Qualified Individual. Your firm keeps responsibility for compliance and must name a senior person to oversee that provider.

For the controls behind the plan, read what cybersecurity an accounting firm actually needs and managed IT for accounting firms. NorthStar supports tax and CPA firms through our financial services IT and security program and helps with FTC Safeguards Rule requirements. More articles are in our financial services resource hub, or start with a free security check.

Sources

Industry Resources

Financial Services IT & Cybersecurity

NorthStar helps tax, CPA and financial firms assess risk, document their written information security plan and run the safeguards behind it.

Learn More →
WISPIRS Publication 5708FTC Safeguards RuleTax PreparersCPA Firms
Share this article

About the author

Ken Satkunam, CISM

Ken Satkunam, CISM

President & Founder, NorthStar Technology Group

Ken has spent over 25 years in IT leadership, serving in roles from technical support to CIO for organizations as large as 23,000 employees. He founded NorthStar Technology Group in 2000 to help regulated organizations build secure, compliant, and operationally resilient technology environments. Ken holds the Certified Information Security Manager (CISM) credential from ISACA and is the co-author of the Amazon best-seller "Cyber Attack Prevention." He has been quoted in industry publications including eWeek and DM News, and NorthStar has been recognized on the Inc. 5000 list in both 2024 and 2025.

CISMInc. 5000MSP 500Published Author25+ Years

Need Help With Your Technology Strategy?

Our experts can help you assess your current posture and build a roadmap for success.