
Every paid tax preparer is required to have a Written Information Security Plan (WISP), but many firms aren't sure what theirs is supposed to contain, and a downloaded template with the firm's name at the top rarely reflects how the practice actually operates. When a regulator, insurer, or breach investigator asks for documentation, the details matter. This session walks through the WISP section by section using IRS Publication 4557 as the guide, explaining what each part does, what it must address, and the records a firm should keep to show its plan is being followed. If you've ever looked at your WISP and wondered whether it would hold up, this session gives you the yardstick to measure it against. You'll learn the purpose of each required element, the security controls the IRS expects behind them, what to keep on file for the vendors who handle client data, and what an incident response plan needs to cover. You'll leave knowing what a complete plan looks like and where your own firm's plan likely needs work.
Tax partners, solo practitioners, firm administrators, and IT managers responsible for tax data security.
A template with your firm name at the top isn't enough if it doesn't match how you actually operate. This session explains what each section should cover and what records should back it up, so you can compare that against your own plan.
No. We walk through what the plan must contain and why, so you can see what a complete plan looks like. Writing your own plan is work you'll do afterward, with a much clearer idea of what it needs.
No, this is a basic level course with no prerequisites. We focus on the administrative and operational requirements the IRS expects from tax professionals rather than deep technical coding or network engineering.
Yes. We outline the components of an incident response plan, including roles, containment, and who you are required to notify.
We will. You'll learn what information to request from third-party vendors and what documentation to keep on file to show you've done your due diligence.
I've watched too many practitioners sign off on a security template they haven't actually read, only to panic when an insurer asks for proof of their internal controls. I wrote this course because a plan that doesn't reflect your daily workflow isn't just useless; it's a liability. You deserve a clear way to understand what your plan should say without getting lost in technical jargon.
Reach out for more information or to bring this training to your organization.
Interested in bringing this training to your team, or want more information? Send a note and we’ll get back to you.