In July 2026, the IRS Office of Professional Responsibility advised tax practitioners to include timely notice to their insurer in data-breach procedures. That instruction exposes a broader operational gap: a firm’s WISP, cyber-insurance application, control evidence, and issued policy may describe four different versions of the same practice.
Tax preparation firms maintain written information security plans because federal rules treat tax preparation as a financial activity. The Federal Trade Commission Safeguards Rule requires covered firms to develop, implement, and maintain a written information security program suited to their size, operations, and customer information. IRS Publication 5708 gives small tax and accounting practices a practical WISP framework and describes the plan as an evergreen record that should change with the business.
There is an important scope distinction. Several specific Safeguards Rule duties, including the prescribed written incident response plan, do not apply to a financial institution that maintains customer information concerning fewer than 5,000 consumers. That exception is not a blanket exemption from the Rule. The IRS still recommends breach procedures and a data theft response plan. A firm should confirm its obligations with qualified counsel instead of assuming that a template settles the question.
Why the documents drift apart
A WISP may be drafted by an IT provider, a managing partner, or a compliance consultant. A cyber insurance application may be completed months later by an office manager working with a broker. The policy can then sit in an inbox until an incident occurs. Each document may have been reasonable when created, yet the facts can diverge as staff, software, vendors, and controls change.
The compliance and insurance questions also serve different purposes. The WISP explains how the firm protects customer information. The application supplies facts an insurer uses to evaluate risk. The policy states the coverage, conditions, limits, sublimits, and exclusions actually issued. Insurers commonly ask about controls, such as multifactor authentication, endpoint detection, backups, email security, and encryption, but the wording and significance of each answer vary by insurer and policy.
A simple example shows how the records can diverge. A firm may answer “yes” to multifactor authentication because its email is protected, while a seasonal preparer can still reach the tax portal using only a password. The WISP, application, and actual control environment now tell three different stories.
Seven steps for the annual review
1. Confirm who owns the crosswalk
The qualified individual responsible for the information security program may not be the person who signs the insurance application. Name one owner for the cross-check and require participation from the application signer, the person responsible for IT, and the insurance broker. The owner should record who verified each answer and when.
2. Test every control statement against current practice
Turn every broad answer into a testable statement. If the application says multifactor authentication is used, identify the systems, users, and access paths it covers. Check administrators, seasonal staff, remote access, and third-party technicians. Apply the same discipline to encryption, endpoint protection, patching, and backups. A documented exception is more useful internally than an unsupported absolute. Answer the application exactly as asked and disclose exceptions through the process the broker and insurer specify.
3. Keep evidence beside each answer
Retain evidence that can be reproduced without guesswork: configuration exports, screenshots with dates, backup test results, training records, access reviews, vendor contracts, and incident exercises. Evidence should support both the WISP and the application answer. It also helps the firm identify a control that was planned but never implemented.
4. Reconcile the service provider inventory
List the systems and providers that receive, store, or can access customer information, including tax software, portals, payroll applications, cloud storage, managed IT services, and contractors. The Safeguards Rule calls for an accurate information inventory and service-provider oversight. Compare that inventory with the vendors named or assumed in the insurance application and with any dependent-system coverage in the policy.
5. Put insurer notice in the response sequence
That IRS advice should appear in the firm’s incident sequence. The plan should identify the policy number, notice method, broker, and carrier contacts, and who is authorized to call. It should also tell staff to check before retaining major vendors or committing to payments when circumstances permit. Policy wording controls. One illustrative small business cyber form states that a call to its incident response coach does not itself constitute policy notice, which shows why the firm must read its own notice provision.
6. Read coverage boundaries before an incident
Use scenarios that resemble the firm’s work. Ask the broker how the issued policies would address a phishing transfer, stolen taxpayer data, corrupted returns, a cloud vendor outage, client notification costs, and lost income during system restoration. Record the answer and the controlling policy provision. Confirm retentions, sublimits, waiting periods, retroactive dates, and exclusions. Do not assume that cyber insurance, crime coverage, and professional liability respond to the same event.
7. Trigger a review after material change
Review the crosswalk at renewal and after a material change, such as a new portal, managed service provider, remote-work arrangement, acquisition, security incident, or change in a key control. The Safeguards Rule requires covered firms to adjust their programs when operations, risk assessments, or other material circumstances change. The insurance record should not wait until the next renewal if a current answer may no longer be accurate.
Run a 30-minute crosswalk
Choose 10 statements that appear, directly or indirectly, in both the WISP and the insurance process. For each statement, record the exact WISP language, the application answer, the supporting evidence, the relevant policy term or broker question, the owner, and the last verification date. Use three statuses only: verified, correct now, and ask the broker.
If the review finds a questionable or outdated application answer, do not backdate documents or silently rewrite the record. Ask the broker and qualified counsel how to correct or supplement it. If the WISP describes a control that does not exist, either implement the control promptly or revise the plan to reflect the present state while documenting the remediation work.
Keep four records aligned
A useful WISP describes the practice that exists. The insurance application should describe that same practice on the date it is signed. The issued policy should be understood against those facts, and the incident response plan should connect the people who must act. The crosswalk does not guarantee compliance or coverage. It exposes contradictions early, when the firm can still correct a control, clarify an answer, or ask a precise coverage question.
ABOUT THE AUTHOR:
The Small Business Insured Editorial Team publishes independent, source-led insurance and cyber-risk guidance for U.S. tax and accounting professionals. Its work helps small firms connect coverage decisions, compliance duties, and practical risk controls. Learn more here.
Disclosure: Small Business Insured is an independent educational publisher. No insurer, broker, software vendor, or security provider paid for or influenced this article. This material provides general information and is not legal, tax, insurance, or cybersecurity advice. Coverage depends on the issued policy and the facts of a loss.
Note: The Chubb form and Travelers underwriting materials are illustrations only. They do not describe every insurer, policy, or application.
Photo credit: rawpixel.com/Freepik
Sign in to get access to this free resource, and all of our whitepapers and reports.
Download this content today!
Register Now Already registered? Click here to Log In