Picture a normal Tuesday morning in a tax office. A staff member opens a workstation and finds client files renamed with a strange extension and a ransom note on the screen. In the next ten minutes, a lot of decisions get made. Who unplugs the computer? Who calls the IT provider? Who decides whether clients need to hear about it, and who calls the insurance carrier? If those answers live only in the owner's head, the first hour usually goes badly.
The FTC Safeguards Rule asks every firm it covers to answer those questions ahead of time, in writing. For tax preparers, CPAs, enrolled agents and bookkeepers, the incident response plan is one of the parts of the written information security plan (WISP) that gets skipped most often, and the weeks before filing season are a good time to fix that.
What the Rule asks for
The requirement is in 16 CFR 314.4(h). A firm must establish a written incident response plan designed to promptly respond to, and recover from, any security event materially affecting the confidentiality, integrity or availability of customer information in its control. The Rule lists seven areas the plan has to address:
- Goals. What the plan is meant to achieve, such as stopping the damage, protecting client data and getting the office working again.
- Internal processes. The steps the office follows when something goes wrong.
- Roles and decision-making authority. Who is in charge, who does what, and who can make which calls.
- Communications. How information is shared inside the office and with outside parties.
- Remediation. How weaknesses found during an incident get fixed.
- Documentation and reporting. How security events and the response to them are recorded and reported.
- Evaluation and revision. How the plan is reviewed and updated after a security event.
IRS Publication 4557, Safeguarding Taxpayer Data, points tax professionals to the same Safeguards Rule requirements, so a plan built around these seven areas serves both. The FTC's own summary, FTC Safeguards Rule: What Your Business Needs to Know, is a useful plain-language companion.
The FTC notification deadline belongs in the plan
Since May 13, 2024, the Rule has also included a reporting requirement in 16 CFR 314.4(j). When a firm discovers a notification event, meaning unauthorized acquisition of unencrypted customer information involving at least 500 consumers, it must notify the FTC as soon as possible and no later than 30 days after discovery, using the form on the FTC's website. That clock starts at discovery, not when the investigation wraps up, so the plan should say who tracks the date and who files the report.
The penalty for violating the Rule is $50,000 per violation, which is one more reason to have the steps written down before they are needed.
What the IRS asks tax professionals to do after data theft
The IRS page Data Theft Information for Tax Professionals lays out who to contact when client data is stolen. The first call it lists is the office's local IRS Stakeholder Liaison, who notifies the right IRS teams on the office's behalf. The page also covers contacting state tax agencies, law enforcement, security experts and the office's insurance carrier. A good incident response plan copies these contacts into one place, with names and phone numbers filled in, so nobody is searching irs.gov while the office is down.
For a closer look at what the weeks after a breach involve, see Client Data Breach Notification: 30 Days of What Actually Happens.
What a practical plan looks like for a small office
A tax practice does not need a 40-page binder. A few pages that staff can actually find and follow will do more good. The most useful plans for small offices share a few traits:
- One person in charge, plus a backup. Usually the Qualified Individual named in the WISP, with a second person who can step in during vacations or the owner's busiest weeks.
- A first-hour checklist. Disconnect the affected computer from the network, don't wipe or restart it, call the IT or security provider, and write down what was seen and when.
- A contact sheet. The IT or security provider, the insurance carrier and its breach hotline, the IRS Stakeholder Liaison, the office's attorney and the tax software vendor's support line.
- A printed copy. If the network is down or files are encrypted, a plan saved only on the server is no help.
- A review date. The plan gets updated after any incident and whenever staff, software or providers change.
This week's checklist
- Open the WISP and check whether it has a written incident response plan that covers all seven areas in 314.4(h).
- Name the person in charge of incidents and a backup, and write both names in the plan.
- Build the contact sheet, including the local IRS Stakeholder Liaison and the insurance carrier's breach line.
- Add the FTC 30-day notification step for events involving 500 or more consumers, with the person responsible.
- Print the plan and keep a copy somewhere staff can reach without a computer.
- Walk the staff through it in a 20-minute meeting before filing season starts.
Watch Cloud Cyber Security helps tax offices build and maintain a WISP, including the incident response plan, aligned with the FTC Safeguards Rule and IRS Publication 4557, backed by 24/7 monitoring and endpoint protection that can isolate an affected computer while the office follows its plan.



