Key takeaways
- IRS Publication 5708 is a free sample WISP from the Security Summit, and it says it is not a substitute for a plan tailored to the firm.
- Tax preparers are financial institutions under 16 CFR 314.2(h)(2)(viii), so the WISP is measured against 16 CFR 314.4.
- The sample plan does not address penetration testing, vulnerability assessments, board reporting or a formal change management process.
- Firms with customer information on fewer than 5,000 consumers are exempt from four Safeguards Rule requirements under 16 CFR 314.6.
- Publication 5708 says to review the plan at least annually or when business practices change materially.
A written information security plan (WISP) is required for every paid tax practice, and the IRS gives one away. Publication 5708 is a sample plan written by the Security Summit for tax and accounting firms. The question for a managing partner is whether filling in that template is enough, or whether the firm needs a plan written around how it actually runs. The answer depends on the firm's size, its systems and how many FTC Safeguards Rule requirements apply to it.
Is IRS Publication 5708 enough for a tax practice's WISP?
IRS Publication 5708 alone is rarely enough for a tax practice's WISP: it is a sound foundation for a small, simple practice and a framework to build on for most other firms. The IRS says as much. Publication 5708 (Rev. 8-2024) states that it is "not intended to replace your own research" or serve as a substitute for developing the firm's own plan, and that "there is no one-size-fits-all WISP."
The legal requirement sits in the FTC Safeguards Rule. Tax preparers are financial institutions under 16 CFR 314.2(h)(2)(viii), and in IR-2026-92 (August 18, 2026) the IRS and its Security Summit partners stated that "Federal law requires tax and accounting professionals to create and maintain a Written Information Security Plan." The measure of a WISP is whether the program meets 16 CFR 314.4, not whether it follows a particular template.
What does Publication 5708 give a firm?
Publication 5708 gives a firm a clear outline, sample policy language and six attachments that a small practice can adapt. The main pieces are:
- A summary of the Safeguards Rule elements, including a Qualified Individual, a risk assessment, multi-factor authentication (MFA), vendor oversight and FTC notification of security events affecting 500 or more people within 30 days of discovery.
- A sample template covering objectives, purpose, scope, responsible officials, inside and outside risk mitigation, and implementation.
- Two named roles: a Data Security Coordinator who runs the plan and a Public Information Officer who speaks for the firm. The guide says that in most firms of two or more practitioners these should be different people.
- Attachments A through F: record retention, rules of behavior, breach procedures, an employee acknowledgment form, a hardware inventory and an authorized access list.
- Practical baselines, such as MFA for remote access, event logging on systems that hold PII, and log reviews at intervals not exceeding 90 days.
It also scales. The guide says a sole practitioner can use "a more abbreviated and simplified plan" than a 10-partner firm, and that the plan should be reviewed at least annually or when business practices change materially.
Where does the template stop short of the Safeguards Rule?
Publication 5708 stops short of the Safeguards Rule on testing, board reporting, change management, disposal, encryption and incident response, which are places an examiner, insurer or breach investigator may look first. Set against 16 CFR 314.4, the sample plan leaves these items out or leaves them for the firm to complete:
- Testing. 314.4(d)(2) requires effective continuous monitoring or, failing that, annual penetration testing and vulnerability assessments at least every six months. Publication 5708 calls for continual monitoring but does not discuss penetration tests or vulnerability assessments.
- Board reporting. 314.4(i) requires the Qualified Individual to report in writing at least annually to the board or, where there is none, a senior officer. The template has no reporting section.
- Change management. 314.4(c)(7) requires change management procedures. The template requires approval before new software is installed but describes no broader process.
- Disposal. 314.4(c)(6) requires disposal of customer information no later than two years after it was last used, subject to listed exceptions. Attachment A leaves the retention period blank.
- Encryption. 314.4(c)(3) requires encryption of all customer information held or transmitted, with alternative controls approved by the Qualified Individual where encryption is infeasible. The template calls for encryption on USB drives, remote access tools and Wi-Fi, and allows network files and email to be password-protected instead of encrypted. It has no approval step for alternatives.
- Incident response. 314.4(h) requires a written incident response plan with specific elements, from roles and decision authority to post-event revision. The template recommends creating one and supplies breach notification procedures in Attachment C. It does not include a response plan template.
A firm that fills in the brackets without addressing these items ends up with a document that may not match the rule it exists to satisfy.
Does firm size change the answer?
Yes, firm size changes the answer: under 16 CFR 314.6, a financial institution that maintains customer information on fewer than 5,000 consumers is exempt from four requirements: the written risk assessment in 314.4(b)(1), the monitoring and testing requirement in 314.4(d)(2), the written incident response plan in 314.4(h) and the annual written report in 314.4(i).
Publication 5708 does not mention that exemption. It says tax professionals are financial institutions "regardless of size," which is also true: every paid preparer is covered, while smaller firms carry fewer written obligations. The count is of consumers whose information the firm maintains, so prior-year clients kept in archives may count toward it. A firm near the line should take its count to the counsel review below.
For a single-office practice under the threshold, with one tax platform and a few staff, a carefully completed Publication 5708 plus the remaining 314.4 items can be proportionate. Change management, disposal and encryption apply at any size. At 5,000 consumers or more, testing, the written incident response plan and the annual written report are also required.
When does a custom WISP make more sense?
A custom WISP makes more sense when the firm is more complex than Publication 5708 assumes. The guide itself says a plan should be appropriate to the firm's "size, scope of activities, complexity, and the sensitivity" of the information it handles. Signs a firm has outgrown the sample:
- Information on 5,000 or more consumers.
- More than one office, remote or seasonal staff, or contractors with access to client files.
- Client portals, cloud file storage, Microsoft 365 or AI tools that touch client data.
- Several service providers handling client information, such as payroll, e-signature or offshore processing.
- Cyber insurance applications or client questionnaires that ask for evidence the template does not produce, such as test results or a board report.
A custom plan does not mean starting from a blank page. Many firms keep the Publication 5708 structure and attachments, rewrite the policy sections to describe their real systems, add the missing rule elements and attach the evidence that shows each control is working.
How do the two approaches compare?
Publication 5708 and a custom WISP differ most in fit and rule coverage, and least in upkeep:
- Cost: Publication 5708 is free. A custom plan takes more time or outside help up front.
- Fit: the template describes a generic practice. A custom plan describes your systems, vendors and people.
- Rule coverage: the template leaves the gaps above. A custom plan maps each paragraph of 16 CFR 314.4 to a policy and an owner.
- Evidence: both need records, but a custom plan usually names the proof for each control, such as MFA reports, training sign-offs and test results.
- Upkeep: both have to be reviewed at least annually and after material changes.
What should a tax practice do this quarter?
As of November 2026, the weeks before the 2027 filing season are a practical window for a tax practice to test the WISP it already has:
- Pull the current WISP. If it came from Publication 5708, confirm every bracket is filled and Attachment A states a retention period.
- Count the consumers whose information the firm keeps to see whether the 314.6 exemption applies.
- Walk the plan through 16 CFR 314.4 paragraph by paragraph and list each gap with an owner and a date.
- Confirm MFA on every system that holds client data. In IR-2026-106, the IRS said the MFA requirement applies to tax preparation firms regardless of size and recommended MFA across all services and data access points.
- Collect signed training acknowledgments, which Publication 5708 recommends refreshing at each annual training.
- Set the next review date. Our guide to updating your WISP before the 2027 filing season covers what counts as a material change, and the PTIN renewal WISP question explains why the answer you give the IRS should be accurate.
What should your counsel review before filing season?
Counsel review should cover the small-firm exemption, the retention period and breach notification duties, ideally before the firm adopts its WISP for the 2027 filing season, or sooner if its consumer count is close to 5,000. Bring these decisions:
- Whether the small-firm exemption applies under 16 CFR 314.6. Bring client counts by year, the archive inventory and the current retention schedule.
- The retention period to write into Attachment A, set against the two-year disposal rule and its exceptions in 16 CFR 314.4(c)(6). Bring the current retention policy, engagement letters and any business reasons for keeping records longer.
- Who must be notified after a security event, including FTC notice for events involving 500 or more consumers within 30 days of discovery under 16 CFR 314.4(j). Bring the breach procedures from Attachment C, the cyber insurance policy and a list of the states where clients live.
How can s90 help?
If you are not sure your WISP would hold up to a cyber insurance questionnaire, a client's security review or a breach investigation, that is the gap s90's IRS WISP compliance service is built to close. s90 builds and maintains WISPs for CPA firms and tax practices across Los Angeles and Orange County. We start from the IRS framework, map it to the FTC Safeguards Rule, and keep the evidence current through the year, from MFA reports to the Qualified Individual's annual report. If you would like a second look at your plan before filing season, we are happy to review it with you.




