IRS OPR Tells Firms to Notify Insurers in Breach Plans
IRS OPR's July 2026 breach-notice advice exposes the four-document gap between a firm's WISP, insurance application, control evidence, and issued policy — and a seven-step fix.

Adjustments
- In July 2026 the IRS Office of Professional Responsibility advised practitioners to include timely insurer notice in breach procedures.
- Firms holding data on fewer than 5,000 consumers are exempt from some Safeguards Rule duties, including the written incident response plan.
- IRS Publication 5708 provides the WISP framework; the FTC Safeguards Rule drives the underlying requirement.
- At least one small business cyber form states a call to its incident response coach does not constitute policy notice.
- The recommended annual crosswalk covers 10 statements with three statuses: verified, correct now, ask the broker.
In July 2026, the IRS Office of Professional Responsibility advised tax practitioners to build timely notice to their insurer directly into their data-breach procedures. That single instruction exposes a wider operational gap. A firm's WISP, cyber-insurance application, control evidence, and issued policy may describe four different versions of the same practice — and each version may have been accurate when written.
The regulatory frame is specific. Tax preparation counts as a financial activity, so the FTC 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 treats the plan as an evergreen record that changes with the business.
Who escapes the incident-response mandate?
One scope carve-out matters. Several specific Safeguards Rule duties, including the prescribed written incident response plan, do not apply to a financial institution maintaining customer information on 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. Firms should confirm obligations with qualified counsel rather than assume a template settles the question.
Why do the four documents drift apart?
A WISP may be drafted by an IT provider, a managing partner, or a compliance consultant. An application may be completed months later by an office manager working with a broker. The policy then sits in an inbox until an incident occurs. The facts diverge as staff, software, vendors, and controls change.
The documents also serve different purposes. The WISP explains how the firm protects customer information. The application supplies facts an insurer uses to price risk. The policy states the coverage, conditions, limits, sublimits, and exclusions actually issued. Insurers commonly ask about multifactor authentication, endpoint detection, backups, email security, and encryption — but the wording and significance of each answer vary by insurer.
A concrete example shows the drift. A firm answers "yes" to multifactor authentication because its email is protected, while a seasonal preparer still reaches the tax portal with only a password. Three documents now tell three different stories.
What does the seven-step annual review require?
- Name a crosswalk owner. The qualified individual running the security program may not be the person who signs the application. Assign one owner and require participation from the application signer, the IT lead, and the broker. Record who verified each answer and when.
- Test every control statement. Convert broad answers into testable statements. If the application says MFA is used, identify the systems, users, and access paths it covers — administrators, seasonal staff, remote access, third-party technicians. Apply the same discipline to encryption, patching, and backups. A documented exception beats an unsupported absolute.
- Keep evidence beside each answer. Configuration exports, dated screenshots, backup test results, training records, access reviews, vendor contracts, and incident exercises. Evidence should support both the WISP and the application, and exposes controls planned but never implemented.
- Reconcile the vendor inventory. List every system and provider touching customer information — tax software, portals, payroll applications, cloud storage, managed IT, contractors. Compare it against vendors named or assumed in the application and any dependent-system coverage in the policy.
- Put insurer notice in the response sequence. The plan should carry the policy number, notice method, broker and carrier contacts, and who is authorized to call. One illustrative small business cyber form states that a call to its incident response coach does not itself constitute policy notice — read your own provision.
- Read coverage boundaries before an incident. Ask the broker how issued policies treat a phishing transfer, stolen taxpayer data, corrupted returns, a cloud vendor outage, notification costs, and lost income during restoration. Confirm retentions, sublimits, waiting periods, retroactive dates, and exclusions. Do not assume cyber, crime, and professional liability respond to the same event.
- Trigger review after material change. New portal, new MSP, remote-work arrangement, acquisition, incident, or control change. The Safeguards Rule requires program adjustment when material circumstances change; the insurance record should not wait for renewal.
Can a 30-minute crosswalk find the gaps?
Choose 10 statements appearing in both the WISP and the insurance process. For each, record the exact WISP language, the application answer, supporting evidence, the relevant policy term, the owner, and the last verification date. Use three statuses only: verified, correct now, and ask the broker.
The discipline matters most when the review finds trouble. Do not backdate documents or silently rewrite the record. Ask the broker and counsel how to correct or supplement a questionable answer. If the WISP describes a control that does not exist, implement it promptly or revise the plan — documented either way.
The crosswalk does not guarantee compliance or coverage. It exposes contradictions early, when a firm can still correct a control, clarify an answer, or ask a precise coverage question. The promise is narrow. The exposure it prevents is not.
via ftc.gov (Original)
More from Sophie Lindqvist
Show full bio
Correspondent covering companies, deals and strategy in CPA News is a professional daily at CPA News.
8 articles
Linked entries
- CP2100 Notices Land in April: Three W-9 Myths That Cost Payers
- BEC Losses Hit $3.05 Billion: Why Payment Controls Are Cybersecurity
- SEC SOX proposal could exempt 1,596 companies from 404(b) attestation
- PCAOB creates five specialist enforcement units for misconduct probes
- PCAOB Creates Five Audit-Misconduct Units as Budget Falls 9.4%