Guide · Updated October 10, 2026
IRS Publication 5708 walkthrough: build your WISP draft
A practical walkthrough of the seven sections in the free IRS WISP outline, with prompts for your tax practice's actual safeguards.
A draft is a start, not compliance. Not legal or tax advice. This independent resource is not approved or endorsed by the IRS or FTC.
Start with the official publication
IRS Publication 5708, Creating a Written Information Security Plan for your Tax & Accounting Practice, includes a free sample template and explanatory material. The version checked for this guide is Rev. August 2024. It warns that the sample is not a substitute for your own research or a plan based on your business's specific needs.
Keep the official PDF beside your draft. For every statement, ask: is this true today, who owns it, and where is the evidence?
I. Objectives, purpose and scope
Describe the information and operations the program protects. Map paper records, software, portals, devices, backups and remote work. State the purpose and limits of the program without excluding data you actually handle.
II. Designate a qualified individual
Name the person responsible for coordinating the security program, their duties and oversight. Record authorized users, access levels and responsibilities. Do not assume assigning a name alone establishes qualifications or implements safeguards.
III. Assess risks
Identify internal and external risks to customer information. Evaluate likely impact, existing controls and remaining gaps. Keep a risk register with an owner, evidence and a next step. Check which specific requirements apply to your practice.
IV. Inventory hardware
List devices and systems that hold or access customer information, including cloud services and backups. Record ownership, location, access, protection and retirement procedures. Never record passwords or secret keys in the inventory.
V. Document safety measures in place
Describe actual administrative, technical and physical safeguards. Address access, MFA, encryption, secure exchange, updates, retention, disposal, training and provider oversight as applicable. Prepare response and notification procedures. Planned controls belong in a gap list, not in claims of current protection.
VI. Draft an implementation clause
Record the adoption process, approvals, effective date and review schedule. Sign only accurate statements after responsible review. A signature does not turn an unimplemented control into a working safeguard.
VII. Attachments
Keep supporting policies and records: retention, personnel conduct, incident response and notification, employee acknowledgements, hardware inventory and authorized-user register. Keep evidence and version history securely and update them as the practice changes.
A draft is only the starting point
Replace every placeholder. Verify controls against your real practice, implement missing safeguards, test their effectiveness and review changes. Get qualified security or legal help when needed. There is no universal completion time or template that guarantees compliance.
Use PTIN renewal season as a review checkpoint, not a reason to make inaccurate statements.