Home · Guides
What to do after a data breach at a tax office: IRS reporting steps
If client tax data may have been stolen, exposed, or locked by ransomware, speed matters. The IRS can try to block fraudulent returns — but only if you report the incident through your Stakeholder Liaison, not the general help line. This page restates the official IRS and FTC reporting steps. It is not legal advice and is not an IRS or FTC publication.
Do this first
- Contain and preserve. The Publication 4557 plan checklist tells firms, if a computer on the internet is compromised, to disconnect it from the internet; to take immediate action to secure information that has been or may have been compromised; and to preserve files or programs that may show how the breach happened. Do not wipe systems before you have a plan for evidence. If feasible, bring in a security professional to assess the breach as soon as possible.
- Start the written record. Note when you first learned of the event, what systems and client files may be involved, and who you notified. Under 16 CFR 314.4(j)(2), a notification event is treated as discovered on the first day it is known to you — including when it is known to any employee, officer, or other agent other than the person who committed the breach.
- Follow the incident-response plan in your WISP, if you have one. The Safeguards Rule requires a written incident-response plan in 16 CFR 314.4(h), except for firms that maintain customer information on fewer than 5,000 consumers (16 CFR 314.6). Publication 5709 still recommends that tax professionals create a data-theft response plan that includes contacting their IRS Stakeholder Liaison. Having fewer than 5,000 clients does not change the IRS reporting advice below.
1. Report to the IRS Stakeholder Liaison immediately
Publication 4557 and the IRS page Data theft information for tax professionals both say to report client data theft to your local IRS Stakeholder Liaison. The data-theft page is explicit: liaisons will notify IRS Criminal Investigation and others in the agency on your behalf, and speed is critical. If the theft is reported quickly, the IRS can take steps to block fraudulent returns filed with your clients’ personal information.
Look up the published contact for your state on Stakeholder Liaison contacts (the IRS last reviewed that page on 17 December 2025). That page is for this kind of stakeholder issue, including a data breach; it is not for tax-law or refund questions. The data-theft page also states that IRS toll-free assistors cannot accept third-party notification of tax-related identity theft. Keep your liaison updated as you learn more.
If you are a tax professional who received a phishing email and there has been a security or data breach, the IRS’s report-phishing page (reviewed 29 October 2026) likewise tells you to contact your Stakeholder Liaison. Suspicious emails that did not lead to a breach can still be sent to phishing@irs.gov (subject “Spearphishing” for a tax-professional targeted email), and reported to TIGTA and, if you choose, the FTC and the FBI’s Internet Crime Complaint Center.
2. Contact law enforcement
The official sources overlap but are not worded identically. Follow what your liaison and counsel tell you, and treat these as the IRS’s published starting points:
- Local police — both Publication 4557 and the IRS data-theft page say to file a police report on the data breach.
- FBI. Publication 4557 says to contact your local FBI office if directed by the IRS. The current data-theft page lists “Federal Bureau of Investigation, your local office” without that qualifier, and also lists the U.S. Secret Service local office “if directed.” Field-office locators: FBI and Secret Service.
- Ransomware. Publication 4557 says that if you are a victim of a ransomware attack, contact the FBI and the Cybersecurity and Infrastructure Security Agency (CISA) in addition to the IRS. CISA’s StopRansomware page likewise tells victims to report to federal law enforcement through the Internet Crime Complaint Center (IC3) or a Secret Service field office, and says they can request technical assistance from CISA.
3. Notify the states where you prepare returns
The IRS data-theft page notes that a breach of personal information can affect victims’ state tax accounts as well as their IRS accounts. It tells tax professionals to use the Federation of Tax Administrators Report a Data Breach page for state tax-agency contacts, and to determine whether they must also contact the state attorney general in each state where they prepare returns. The IRS says most states require that the attorney general be notified, and that the process may involve more than one office.
State tax-agency and attorney-general deadlines vary and can be shorter than the federal FTC clock described below. This page does not list those state deadlines; use the FTA directory and the attorney-general rules that apply to the states where you prepare returns.
4. The FTC 500-consumer notification (Safeguards Rule)
This is a separate federal duty from the IRS liaison report. Under 16 CFR 314.4(j), if a notification event involves the information of at least 500 consumers, you must notify the Federal Trade Commission as soon as possible, and no later than 30 days after discovery. The notice is filed electronically on a form on the FTC’s website, ftc.gov, as the rule itself provides.
16 CFR 314.2(m) defines a notification event as the acquisition of unencrypted customer information without the authorization of the individual to whom it pertains. Customer information is considered unencrypted for this purpose if the encryption key was accessed by an unauthorized person. Unauthorized acquisition is presumed to include unauthorized access to unencrypted customer information unless you have reliable evidence that there has not been, or could not reasonably have been, unauthorized acquisition.
The notice must include: the name and contact information of the reporting financial institution; a description of the types of information involved; the date or date range, if it can be determined; the number of consumers affected or potentially affected; a general description of the event; and whether a law-enforcement official has given you a written determination that public notice would impede a criminal investigation or harm national security, plus a way for the FTC to reach that official. The rule also describes a possible law-enforcement delay of the FTC’s public disclosure.
Two limits to keep straight:
- The under-5,000-consumers exception in 16 CFR 314.6 does not excuse paragraph (j). A smaller firm can still have to file this FTC notice.
- The IRS data-theft page’s shorter phrasing — “File a report with the FTC if you have 500 or more people that have been affected” — is a reminder, not a substitute for the definition and timing in the rule.
5. Clients, credit bureaus, and Form 14039
The IRS data-theft page says to send an individual letter to all victims to inform them of the breach, but to work with law enforcement on timing. Publication 4557 points tax professionals to the FTC’s Data Breach Response: A Guide for Business for help notifying clients and for response and recovery tips. A preserved federal copy of that 2021 FTC guide is in GovInfo; the FTC also discusses business breach response on ftc.gov. The same IRS page lists a business-assistance address, idt-brt@ftc.gov, for more individualized FTC guidance.
On what clients should file with the IRS: they should complete Form 14039, Identity Theft Affidavit, only if they receive a notice or letter from the IRS or their e-filed return is rejected because of a duplicate Social Security number. Do not treat Form 14039 as an automatic enclosure in every breach letter.
The data-theft page also tells firms to consider notifying the major consumer reporting agencies (it lists Equifax, Experian, and TransUnion, with their published fraud-assistance contacts) so that clients who need a fraud alert can be pointed to those services, and to check whether state law requires offering credit monitoring or identity-theft protection. Confirm those contacts on each bureau’s current site before you use them; they can change.
6. Insurance, a new EFIN, and recovery
Publication 4557 and the IRS data-theft page both say to contact your insurance company to report the breach and to see whether the policy covers mitigation, and to use a security expert to determine the cause and scope, stop the breach, and reduce the chance of another one.
On getting back to work, Publication 4557’s recovery list includes:
- Determine how the intrusion or theft occurred and make any required fixes before resuming tax preparation and before being issued a new Electronic Filing Identification Number (EFIN).
- Develop a continuity plan.
- Make full, encrypted backups of business data (and start a routine backup if you did not already have one — including against ransomware, fire, or flood).
- Update your Stakeholder Liaison as the facts develop.
Once the immediate reporting is in motion, put what happened, what you notified, and what you changed into the office WISP so the written plan matches the office you now run. Email authentication (SPF, DKIM, and an enforcing DMARC policy) will not undo a breach, but it is one of the cheaper ways to make it harder for someone to impersonate the firm while clients are already on edge. You can check the domain you send from with our free in-browser test.
After the notifications are in motion. The free email-spoofing check reads only public DNS. If you also need a written plan that includes an incident-response section, PreparerGuard is a paid WISP kit based on Publication 5708. You still have to implement the controls, report an incident yourself, and review the draft. It is not a certification, and it does not file anything with the IRS or the FTC for you.
Check my email domain Build my WISP Publication 4557 checklist
- IRS, Data theft information for tax professionals — irs.gov/individuals/data-theft-information-for-tax-professionals
- IRS, Stakeholder Liaison contacts (reviewed 17 December 2025) — irs.gov
- IRS Publication 4557, Safeguarding Taxpayer Data (Rev. 5-2024) — PDF; Publication 5708 — PDF; Publication 5709 — PDF
- IRS, Report fake IRS, Treasury or tax-related emails and messages (reviewed 29 October 2026) — irs.gov
- Federation of Tax Administrators, Report a Data Breach — taxadmin.org/report-a-data-breach
- 16 CFR 314.2(m) and 314.4(j), 314.6 — eCFR definitions · elements
- CISA, StopRansomware — cisa.gov/stopransomware; FBI Internet Crime Complaint Center — ic3.gov
- FTC, Data Breach Response: A Guide for Business (2021; cited in Publication 4557) — preserved copy at GovInfo
- IRS Form 14039 — irs.gov/pub/irs-pdf/f14039.pdf
Related: IRS Publication 4557 checklist (2026) · FTC Safeguards Rule checklist · WISP template and Form W-12 line 11 · Free DMARC / spoofing check